After unlocking the bootloader, I booted to fastboot, did 'fastboot flash recovery recovery recovery.img'. Then, I pressed volume up and power at the same time until the Android logo showed up. Then, the screen flashed white, and rebooted, this time to the normal Android. I have never seen this white flash before, not in the stock recovery or normal reboot.
Mods, please don't ban me for circumventing the spam filter, but this is just a video of the procedure https: //youtu .be/Yq59DCqhhOc
All help is appreciated
Discapot said:
After unlocking the bootloader, I booted to fastboot, did 'fastboot flash recovery recovery recovery.img'. Then, I pressed volume up and power at the same time until the Android logo showed up. Then, the screen flashed white, and rebooted, this time to the normal Android. I have never seen this white flash before, not in the stock recovery or normal reboot.
Mods, please don't ban me for circumventing the spam filter, but this is just a video of the procedure https: //youtu .be/Yq59DCqhhOc
All help is appreciated
Click to expand...
Click to collapse
That means your recovery was not properly flashed or was incompatible. Find a proper recovery and flash it.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
That means your recovery was not properly flashed or was incompatible. Find a proper recovery and flash it.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
I did 'fastboot flash recovery recovery.img', and it saif 'Finished' with no errors. Then it must be the img that is incompatible right?
Discapot said:
I did 'fastboot flash recovery recovery.img', and it saif 'Finished' with no errors. Then it must be the img that is incompatible right?
Click to expand...
Click to collapse
Yes
HIT THANKS IF FOUND USEFUL
Related
*Fixed*
uppon2 said:
I just go the phone today and I have unlocked it and it all went well. I was looking at installing ViperDNA on to my phone. So I started to follow instructions in the Viper thread
1. I "tried" to install TWRP through the Goo method and after downloading the file it told me that recovery was no installed.
2. I rebooted in to bootloader and hit power button to enter fastboot then I scrolled down to where it says recovery and I hit power again. Phone displayed a message up the top that it was now entering recovery. The phone did not go to recovery it simply rebooted all the way back to my phones home screen.
I then though hmm well maybe I didn't install it properly so I follwed the instructions using Goo again but still nothing happened.
I noticed there was an alternative method to flash recovery by using ADB. I put the file in to the same directory as where my adb/fastbood reside and I booted in to fastboot again and in cmd prompt I entered "flash recovery openrecovery-twrp-2.4.0.0-dlx.img"
It seemed to flash and gave me a response which I can't remember now but it said OK!.
I then proceeded to try and enter recovery again but this time it has sent my phone in to a bootloop. It will not pass the Droid splashscreen. I can however still access bootloader mode.
I also noticed now in my Bootloader above where it says Unlocked it also says Tampered?
Phone doesn't seem to be recognised by ADB anymore neither. adb devices returns with a blank space
I'm a long time Samsung user so usually in this situation I would use Odin and flash a stock firmware but I don't know the process with HTC
I don't have a backup because I hadn't got to this stage yet!
Any advice as to what to do now
Click to expand...
Click to collapse
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
lazarus2297 said:
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
Click to expand...
Click to collapse
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
uppon2 said:
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
Click to expand...
Click to collapse
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
lazarus2297 said:
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
Click to expand...
Click to collapse
lol. Now Aroma is being a pain in the ass. It won't let me click Next to install. haha
EDIT* Maybe because of the smaller TWRP or maybe not but I had to try again and then click next but about 2" higher than where it says it :S
I am not a huge fan of aroma... i had issues when i tried to flash my DNA the first time.. that is something that you just have to keep trying unfortunately it seems... i have seen where people had to aroma freeze on them multiple times before finally completing the flash... some tips i have seen is keep the phone flat... also keep it plugged in.. I can't vouch for any of these being actual fixes but hey "it's only weird if it doesn't work"
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
uppon2 said:
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
Click to expand...
Click to collapse
glad to hear it sorry for the slow response.. i was away for a bit..
lazarus2297 said:
glad to hear it sorry for the slow response.. i was away for a bit..
Click to expand...
Click to collapse
All good. Thanks for your assistance
I am usually the guy helping other people. It's quite an unusual change going from Samsung to HTC!
Hi all,
I was frustrated with the performance of stock ROM on my xperia sola and tried to flash it with custom ROM (CyanogenMod 11). Something went wrong. And now I can't boot device This is my firts try, so probably I did something wrong during the process.
What I did
In general I followed this procedure and did not managed to get to their step 12.
Details:
1. At first I unlocked bootloader (using official Sony procedure)
2. Then I iInstalled RecoverX from Play.
3. Then rooted the device.
4. Then downloaded stable CyanogenMod 11 (cm11.0-0-pepper.zip), copied it to SD card. I've also extracted boot.img and flashed it using fastboot (with no errors).
The problem
After the steps above the device does not boot. I see "sony xperia ste" screen, then it disappears and screen is grey.
I've tried to enter the recovery mode (by holding volume down button), but the result is the same - grey screen.
What I tried (and it did not worked)
I'm still able to enter fastboot mode. So I tried the step 4. with latest nightly build (cm11.0-14-pepper.zip). I've flashed boot.img successfully, but the result is the same (grey screen).
Any ideas what can be done to reanimate the device?
Thanks in advance!
lvivets said:
Hi all,
I was frustrated with the performance of stock ROM on my xperia sola and tried to flash it with custom ROM (CyanogenMod 11). Something went wrong. And now I can't boot device This is my firts try, so probably I did something wrong during the process.
What I did
In general I followed this procedure and did not managed to get to their step 12.
Details:
1. At first I unlocked bootloader (using official Sony procedure)
2. Then I iInstalled RecoverX from Play.
3. Then rooted the device.
4. Then downloaded stable CyanogenMod 11 (cm11.0-0-pepper.zip), copied it to SD card. I've also extracted boot.img and flashed it using fastboot (with no errors).
The problem
After the steps above the device does not boot. I see "sony xperia ste" screen, then it disappears and screen is grey.
I've tried to enter the recovery mode (by holding volume down button), but the result is the same - grey screen.
What I tried (and it did not worked)
I'm still able to enter fastboot mode. So I tried the step 4. with latest nightly build (cm11.0-14-pepper.zip). I've flashed boot.img successfully, but the result is the same (grey screen).
Any ideas what can be done to reanimate the device?
Thanks in advance!
Click to expand...
Click to collapse
Maybe try to hold vol up while "Sony Xperia STE" showing up.
Cwikla said:
Maybe try to hold vol up while "Sony Xperia STE" showing up.
Click to expand...
Click to collapse
Thanks for suggestion!
I've already tried it and it does not help
1) Have you unlocked the bootloader?
2) In the terminal could you try issuing a "reboot recovery" command?
OR
Hold the back button while booting..
Same problem
I have exactly the same problem, also with Cyanogenmod 11.
I'm not able to get in android or recovery, maybe there is a way to fix this in fastboot? (That's the only solution I can think of)
Thanks for your suggestions!
rlvl said:
1) Have you unlocked the bootloader?
Click to expand...
Click to collapse
Yes!
rlvl said:
2) In the terminal could you try issuing a "reboot recovery" command?
Click to expand...
Click to collapse
Could you, please, provide more details when should I run this command?
This is not working with fastboot, and I don't know of other options.
rlvl said:
Hold the back button while booting..
Click to expand...
Click to collapse
Back is "software" button on sola. Nevertheless, I tried holding it but this did not helped.
lvivets said:
Thanks for your suggestions!
Yes!
Could you, please, provide more details when should I run this command?
This is not working with fastboot, and I don't know of other options.
Back is "software" button on sola. Nevertheless, I tried holding it but this did not helped.
Click to expand...
Click to collapse
In adb try the "reboot recovery" command
rlvl said:
In adb try the "reboot recovery" command
Click to expand...
Click to collapse
Unfortunatelly adb is not able to connect to the device. Probably that's because the device does not not reach "far enough" in boot process.
Solution
What you've done wrong is to flash the boot image before the rom. As now the new boot images contain TWRP recovery, it loades after the rom is booted and the rom wont boot because of boot image mismatch. The solution is to use an older boot image which contains the CWM recovery which loads before the rom has even booted. Try THIS rom's boot image then flash the rom and then your new boot image.
HIt like if it helps :fingers-crossed: :highfive:
Solved
INDIAN-MAfIA said:
What you've done wrong is to flash the boot image before the rom. As now the new boot images contain TWRP recovery, it loades after the rom is booted and the rom wont boot because of boot image mismatch. The solution is to use an older boot image which contains the CWM recovery which loads before the rom has even booted. Try THIS rom's boot image then flash the rom and then your new boot image.
HIt like if it helps :fingers-crossed: :highfive:
Click to expand...
Click to collapse
Thank you!
Using AOSX boot.img I was able to get into TWRP recovery. I did not flashed CM11 yet, it's late night right now here.
Another solution is to flash experimental v12 kernel (ensure your version of android matches it!). For me it was 4.0.
This solution was proposed by @pippoaacc here. So, all credits go to him. Also he was very nice to explain me more details regarding the solution (which were not obvious to me).
Using this one I'm able to boot my stock android and use it. However I can't flash any ROM doe to CWM recovery errors.
Anyway. There are at least 2 ways to resolve original problem (gray screen after flashing boot.img from CM11).
So, I believe this thead is solved.
Basicly I tried everything to get into recovery or flash / imstall a new one. Nothing worked so far..
My device is rooted and I can install all apps which need root acces.
I now installed Flashify and when I click on "Recovery image" or "Boot image" it says "Partition not found".
And since I cannot boot into recovery I cant install anything via zip files...
Would be nice if someone could help me.
Best Regards
digausma
Info
digausma said:
Basicly I tried everything to get into recovery or flash / imstall a new one. Nothing worked so far..
My device is rooted and I can install all apps which need root acces.
I now installed Flashify and when I click on "Recovery image" or "Boot image" it says "Partition not found".
And since I cannot boot into recovery I cant install anything via zip files...
Would be nice if someone could help me.
Best Regards
digausma
Click to expand...
Click to collapse
use another method to boot into recovery
like ADB commands
Code:
adb reboot recovery
:good:
If your bootloader is locked, simply use [NUT]'s dual recovery.
If your bootloader is unlocked, install any 4.4.4 based kernel what has recovery built into it. I'm using AndroPlus as I'm running a 4.4.4 ROM as my main ROM.
Well there are severel apps which makes your device boot into recovery. None worked and I think the use the same method?
gamer649 said:
If your bootloader is locked, simply use [NUT]'s dual recovery.
If your bootloader is unlocked, install any 4.4.4 based kernel what has recovery built into it. I'm using AndroPlus as I'm running a 4.4.4 ROM as my main ROM.
Click to expand...
Click to collapse
<- digausma
Thanks I tried that now and everthing went good but I still cannot boot into recovery... it says I have to push VOL-UP or VOL-DOWN when the green led lights up. However I NEVER see a green led and no matter when I press the VOL button it wont boot into recovery...
edit: oh lol forgot I had alrdy an account ^^
Nice.InSane said:
<- digausma
Thanks I tried that now and everthing went good but I still cannot boot into recovery... it says I have to push VOL-UP or VOL-DOWN when the green led lights up. However I NEVER see a green led and no matter when I press the VOL button it wont boot into recovery...
edit: oh lol forgot I had alrdy an account ^^
Click to expand...
Click to collapse
I'm assuming you are using [NUT]'s dual recovery? Did you install busybox before running the recovery installer? If not, install it, then run the recovery installer again. You will see the green LED when the device is showing the SONY logo before the waves bootlogo.
gamer649 said:
I'm assuming you are using [NUT]'s dual recovery? Did you install busybox before running the recovery installer? If not, install it, then run the recovery installer again. You will see the green LED when the device is showing the SONY logo before the waves bootlogo.
Click to expand...
Click to collapse
Well sadly I cannot install BusyBox... Also I am not able to update SuperSU.. And I dont know why -.-
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Hello,
It can get a bit confusing sometimes and people generally expect you to just know lol.
You've not missed a step. Getting into recovery is irritating lol. For as long as I've had it if booted into recovery from the power menu lol xD.
Reboot the Google Nexus 9 by holding the Power and the Volume Down buttons at the same time and wait until the tablet display shows a Google splash screen before releasing the buttons.
If you get a android with an exclamation mark then you've made a boo boo. Dw, even us pros muck up ;]
Go back to your fastboot. Flash twrp like you do. But this time once you've flashed it type
Code:
fastboot boot recovery twrp.img
That should boot your device into recovery after flashing it.
There it should be stuck on there nicely of it takes a while Dw. That's just the fun of owning a N9 lol. That should Do it .
Happy Flashing.
Give us a Thanka if I helped
ChrispyChris said:
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Click to expand...
Click to collapse
If you installed TWRP using
Code:
fastboot flash recovery twrp.img
The only ways I know to get into recovery are to reboot to recovery from the Power menu of your ROM
OR
Boot to fastboot, select HBOOT, then select Recovery. If TWRP is installed as your recovery this will boot TWRP. If it goes to the dead droid screen then you need to install TWRP properly, using the fastboot flash command above.
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Mephisto_POA said:
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Click to expand...
Click to collapse
Are you using the newest TWRP? 3.1.0.0? It's not working for me either, can't boot to recovery. Use 3.0.2.2 or whatever the last version was
I used the 3.1.0.0
the trick was, after installing it, reboot straight back into recovery, so it doesn't get overwritten
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.