Develop Bugs

[Q] Twrp won't install custom rom gives error message

the error message was error flashing zip then it went to updating partition details.should i just continue with it or what?edit:it also shows the 3 buttons that you get at the end of an installation and the rom i was flashing was cyanogenmod 10

Jacobloveskindles said:
the error message was error flashing zip then it went to updating partition details.should i just continue with it or what?edit:it also shows the 3 buttons that you get at the end of an installation and the rom i was flashing was cyanogenmod 10
Click to expand...
Click to collapse
That's a known bug in TWRP. Install a version previous to the one you're using, or install COTR.

safe method of doing that
soupmagnet said:
That's a known bug in TWRP. Install a version previous to the one you're using, or install COTR.
Click to expand...
Click to collapse
my kindle has no system files and i forgot to make a backup.how do i do that in linux

Jacobloveskindles said:
my kindle has no system files and i forgot to make a backup.how do i do that in linux
Click to expand...
Click to collapse
fastboot

soupmagnet said:
fastboot
Click to expand...
Click to collapse
not to sound like a total noob but how do I do it in fastboot

http://forum.xda-developers.com/showthread.php?t=1668159

if i do this will it overwrite my other recovery?
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
If I use your soup kit to change into fast boot can I just install twrp on soup kit and it will downgrade me to an older version?

Jacobloveskindles said:
If I use your soup kit to change into fast boot can I just install twrp on soup kit and it will downgrade me to an older version?
Click to expand...
Click to collapse
Yes, the SoupKit that is posted now has an older version of TWRP. I'm in the process of updating it so you should probably grab it while you have the chance, should you decide to go that route. You could also install Cannibal Open Touch Recovery. All versions of it are quite stable.

confused
soupmagnet said:
Yes, the SoupKit that is posted now has an older version of TWRP. I'm in the process of updating it so you should probably grab it while you have the chance, should you decide to go that route. You could also install Cannibal Open Touch Recovery. All versions of it are quite stable.
Click to expand...
Click to collapse
So if I'm inside twrp and have soupkit up on the PC and have my kindle plugged in and change it to fast boot then hit flash twrp will it do its thing and downgrade me and reboot my kindle into twrp 2.2 and let me install a ROM.

It has been brought to my attention that you may be confused between the KFU (Kindle Fire Utility) and TWRP (Team Win Recovery Project). The KFU is a Windows based utility used to change bootmodes, install custom versions of the recovery and bootloader partition images along with various other tasks. It has no affiliation with TWRP, COTR, or FireFireFire, other than it installs them to your device for you.
However, the "bug" in TWRP mentioned earlier is due to that way it handles the updater scripts in certain ROMS. It has nothing to do with your system files. The reason you have no system files right now, is because you wiped them prior to attempting to flash a ROM. Since the ROM was never successfully flashed, you have no system files in place, therefore nothing to boot to.
Downgrade your version of TWRP, or install a different recovery altogether, make sure you have wiped data (factory reset) and reinstall your ROM. After that, you should no longer have any problems.
I strongly suggest you take the time to read the guides and tutorials available for the Kindle Fire and make sure you understand how everything works before you do something and get yourself in a situation that you can't get out of on your own.

soupmagnet said:
It has been brought to my attention that you may be confused between the KFU (Kindle Fire Utility) and TWRP (Team Win Recovery Project). The KFU is a Windows based utility used to change bootmodes, and install custom versions of the recovery and bootloader partition images. It has no affiliation with TWRP, COTR, or FireFireFire, other than it installs them to your device for you.
However, the "bug" in TWRP mentioned earlier is due to that way it handles the updater scripts in certain ROMS. It has nothing to do with your system files. The reason you have no system files right now, is because you wiped them prior to attempting to flash a ROM. Since the ROM was never successfully flashed, you have no system files in place, therefore nothing to boot to.
Downgrade your version of TWRP, or install a different recovery altogether, make sure you have wiped data (factory reset) and reinstall your ROM. After that, you should no longer have any problems.
I strongly suggest you take the time to read the guides and tutorials available for the Kindle Fire and make sure you understand how everything works before you do something and get yourself in a situation that you can't get out of on your own.
Click to expand...
Click to collapse
There are no tutorials on how to downgrade twrp on kindle fire.look at my previous post its not about kfu its about your soup kit.I checked your thumbnails.it allows me to install twrp but,please I need to know how to downgrade twrp without using the command line.the last time I used the command prompt or typed a command windows gave me a bsod.but now I'm in Linux because of that,anyways,in other words,I don't wanna use a command line.just pleez read my previous post over entirely.

Jacobloveskindles said:
There are no tutorials on how to downgrade twrp on kindle fire.look at my previous post its not about kfu its about your soup kit.I checked your thumbnails.it allows me to install twrp but,please I need to know how to downgrade twrp without using the command line.the last time I used the command prompt or typed a command windows gave me a bsod.but now I'm in Linux because of that,anyways,in other words,I don't wanna use a command line.just pleez read my previous post over entirely.
Click to expand...
Click to collapse
I did read your post, entirely.
I'm addressing the fact that you contacted the developer of the KFU, and due to your confusion about things work, gave him the impression that I said something that I clearly haven't.
The "bug" mentioned earlier in this thread has nothing at all to do with the KFU, therefore the developer of that utility is not responsible for it. That being said, the bug in TWRP that prevented you from flashing a ROM has nothing to do with the fact that you don't have system files, as you erroneously assumed.
Even with that, you as the user, assume all responsibility for anything you do to your device, not the developers of this community. This is a community of developers, for developers. This is not a community of developers, for people that don't know what they're getting into, and run into trouble as a result of it.
Now, for your problem at hand...
If you go through this thread carefully, you'll see that I have already answered your question. Go back and pay attention to what's been said and you should be fine.

last question
soupmagnet said:
Yes, the SoupKit that is posted now has an older version of TWRP. I'm in the process of updating it so you should probably grab it while you have the chance, should you decide to go that route. You could also install Cannibal Open Touch Recovery. All versions of it are quite stable.
Click to expand...
Click to collapse
stupid question:do i need to be in fastboot because it says i can do it in any bootmode but of course im gonna be in twrp and downgrading

Jacobloveskindles said:
So if I'm inside twrp and have soupkit up on the PC and have my kindle plugged in and change it to fast boot then hit flash twrp will it do its thing and downgrade me and reboot my kindle into twrp 2.2 and let me install a ROM.
Click to expand...
Click to collapse
I'm not an expert on this but let do together. I want to learn something too.
According to the previous post, you asked and soupmagnet already answered that it will install a previous version of TWRP.
Why don't you do that then?
Next question is can you get into TWRP (whatever version you're using now, new or old)?

Jacobloveskindles said:
stupid question:do i need to be in fastboot because it says i can do it in any bootmode but of course im gonna be in twrp and downgrading
Click to expand...
Click to collapse
Just flash this in recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=1204340&d=1342535659

the kindle will boot into recovery
votinh said:
I'm not an expert on this but let do together. I want to learn something too.
According to the previous post, you asked and soupmagnet already answered that it will install a previous version of TWRP.
Why don't you do that then?
Next question is can you get into TWRP (whatever version you're using now, new or old)?
Click to expand...
Click to collapse
because i don't know if it needs fastboot and yes i can get into twrp

that sounds a bit weird
soupmagnet said:
Just flash this in recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=1204340&d=1342535659
Click to expand...
Click to collapse
i flash a recovery in the recovery?lolwut

Jacobloveskindles said:
because i don't know if it needs fastboot and yes i can get into twrp
Click to expand...
Click to collapse
Well, if you can get into TWRP then why not just flash it
What are you waiting for?
Did soupmagnet or someone already say it? flash either the previous version of TWRP or COTR.

Jacobloveskindles said:
i flash a recovery in the recovery?lolwut
Click to expand...
Click to collapse
I can't believe this is still being discussed.
Yes, you can flash recovery in recovery using a flashable .zip (like the one I posted) or via the command line. And SoupKit will install recovery whether you are booted into fastboot, recovery, or a normally booted device.
You're making this way harder than it needs to be. You could have avoided all of this if you would have just read the guides and tutorials available to you from the start.

srry this took so long
soupmagnet said:
I can't believe this is still being discussed.
Yes, you can flash recovery in recovery using a flashable .zip (like the one I posted) or via the command line. And SoupKit will install recovery whether you are booted into fastboot, recovery, or a normally booted device.
You're making this way harder than it needs to be. You could have avoided all of this if you would have just read the guides and tutorials available to you from the start.
Click to expand...
Click to collapse
That was my final thing.just yeah.thanks for staying with me BTW,know how you said the kfu thing wasn't discussed between this page.that was something I discovered I guess the dev thought we discussed that.I'll give you a thanks

[Q] Where can I get CM11 howto on Ouya

Hello
I own Ouya for the month but most of time I use it as media-box for TV (watching movies, etc)
I have already rooted it and installed play market but i hate the stock UI and obsolate android
I saw a video in youtube with CM11 and ouya (android 4.4) and started to google the solution
I already know that it is based on Eternity Project kernel.
I found the way to install bootloader http://www.eternityproject.eu/topic/1114365-eternityproject-tpl-bootloader-for-ouya/ and it is clear
The next step is to install kernel http://www.eternityproject.eu/topic/1114362-eternityproject-kernel-3437-for-ouya-cpu-2ghz-gpu-650mhz/ but it is unclear for me about fastboot command
The next step as I understand is to install CM11 from the CWM
Is it possible to install KitKat without EP kernel?
So If someone have detailed steps or howto on installing CM11 on ouya please give it to this thread
Thanks in advance

I think this is what you're looking for. I'm not sure the EP boot loader is compatible but I'm sure its mentioned in the thread somewhere. Or in the bootmenu thread anyway.
http://forum.xda-developers.com/showthread.php?p=51332165
Sent from my Nexus 5 using XDA Premium 4 mobile app

This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.

quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.

PHYSC-1 said:
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.
Click to expand...
Click to collapse
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.

quepaso said:
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.
Click to expand...
Click to collapse
Just realized cwm is removed,can't install using oneclickrecovery tool either fails says cannot find img etcetc,yet its all there no problems adb is fine and works.Fastboot driver i can't get running although listed yellow exclamation,any ideas?
Fixed it managed to get fastboot going downloaded the required missing dll files and win_usb.inf set up and used ouyatoolbox 1.0.0.0 to rewrite recovery,found i can no longer add the newer 6.0.4.8 recovery zip in update from zip in 6.0.3.2 recovery though? Used to be able to do that. Any way tmore to the point is can someone tell me the step by step process to add cm11 firmware so i don't have to read a load of [email protected] that doesn't end up giving less than nothing in terms of having a clue how,someone in the thread writes about erasing stuff and what oreder but that doesn't tell you how to install or what erase process is or anything detailed and the net has exactly the same misguided tutorials on how to do it.Tellinng a newbie to erase stuff means they will erase all the wrong stuff in all fairness it's good to have a slightly better idea by reading that but it doesn't go in depth or step by step.
All i have found is sites pointing back to the xda pages that do not explain it,it's like your expected to know everything before you have been taught and fill in the gaps off the top of your head.

quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Exactly what he said, I just did these same steps on a 3rd new ouya yesterday and it went off without a hitch. The cm11 thread is long but honestly all the information you need is in the first few posts. If you were able to connect the ouya to USB and run oneclickroot then you're ready to get started.

[Q] formatting to f2fs

I quite fancy trying out a rom that requires formatting to f2fs, but this requires a jaunt into new territory for me. I currently have Philz recovery installed, but after searching, I don't seem to be able to find out how to format using this this. Should I install twrp instead? If so could someone point me to the relevant thread/discussion (again have searched but there are several to chose from) .
Cheers!

westy123 said:
I quite fancy trying out a rom that requires formatting to f2fs, but this requires a jaunt into new territory for me. I currently have Philz recovery installed, but after searching, I don't seem to be able to find out how to format using this this. Should I install twrp instead? If so could someone point me to the relevant thread/discussion (again have searched but there are several to chose from) .
Cheers!
Click to expand...
Click to collapse
I used Captain Throwback's standard TWRP for my sprint m8, but it should work for all m8 variants:
http://themikmik.com/showthread.php...OM-TWRP-Recovery-v2-8-5-standard-TWRP-2-8-6-0
Look under the 3rd post for downloads

westy123 said:
I quite fancy trying out a rom that requires formatting to f2fs, but this requires a jaunt into new territory for me. I currently have Philz recovery installed, but after searching, I don't seem to be able to find out how to format using this this. Should I install twrp instead? If so could someone point me to the relevant thread/discussion (again have searched but there are several to chose from) .
Cheers!
Click to expand...
Click to collapse
Philz recovery hasn't been maintained for some time now. CWM seems to be dying out as well. TWRP is the best choice IMO.

Thanks all, in my ignorance I hadn't realised that philz want actively maintained anymore! So best all round if I switch to twrp.
Another question if I may: it's been a while since I switched recoveries on any device, do I need to push twrp via adb etc. Or can I install it via the app through my phone?

westy123 said:
Thanks all, in my ignorance I hadn't realised that philz want actively maintained anymore! So best all round if I switch to twrp.
Another question if I may: it's been a while since I switched recoveries on any device, do I need to push twrp via adb etc. Or can I install it via the app through my phone?
Click to expand...
Click to collapse
If you haven't done so, you can simply push the TWRP recovery file through adb (just as you did when you first unlocked your bootloader and obtained root, I assume). You can find the latest on twrp's website. I have no experience with the app method, but it should work fine as well.

westy123 said:
Thanks all, in my ignorance I hadn't realised that philz want actively maintained anymore! So best all round if I switch to twrp.
Another question if I may: it's been a while since I switched recoveries on any device, do I need to push twrp via adb etc. Or can I install it via the app through my phone?
Click to expand...
Click to collapse
Since you are already rooted, you can flash TWRP in recovery. But personally, I would flash it in fastboot or hboot.

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!

bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242

1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.

SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.

bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.

Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?

bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1

All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!

You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.

TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!

bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?

have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.

bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.

noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

Installing TWRP over CWM?

Hello,
I am wondering if it is possible to install TWRP over top of CWM? When I initially rooted my phone CWM was installed, however to install a new rom I need TWRP. Is this possible?
Thanks,

Skyty said:
Hello,
I am wondering if it is possible to install TWRP over top of CWM? When I initially rooted my phone CWM was installed, however to install a new rom I need TWRP. Is this possible?
Thanks,
Click to expand...
Click to collapse
Yes. It's been a loong time. Best I can recall, I did the following:
1. Flash'd a ZIP of an old TWRP (couldn't find latest in ZIP file)
2. Rebooted into Recovery
3. Used old TWRP to flash IMG file of new TWRP

Just to make sure I understand (as it's been a while since I rooted a phone or done anything like this).
1.) When you say flashed, do you mean in the TWRP app on the screen where you select your phone model?
2.) So if I flash TWRP (in the manner I described above assuming that's what you meant) and reboot into recovery it will overwrite Clockworkmod and then I'll be in TWRP recovery?
3.) If I do this with the most recent TWRP version I'm assuming this step will be unecessary?
My apologies if I misunderstood what you were trying to say! Thanks for taking the time to respond!

Skyty said:
...
1.) When you say flashed, do you mean in the TWRP app on the screen where you select your phone model?
2.) So if I flash TWRP (in the manner I described above assuming that's what you meant) and reboot into recovery it will overwrite Clockworkmod and then I'll be in TWRP recovery?
3.) If I do this with the most recent TWRP version I'm assuming this step will be unecessary?...
Click to expand...
Click to collapse
Quick answers: No, no, and maybe.
It appears that you may be confusing the TWRP app (which is basically useless bloat) with the actual TWRP recovery. You need to find and download the latest TWRP recovery for your device model. If you can find a ZIP of it, great; because CWM can then install TWRP recovery for you (so that when you reboot into recovery, you'll see TWRP instead of CWM). In my case, there was no ZIP available for the latest TWRP; it was available only as an IMG file. An old version of TWRP recovery, however, was and likely still is available in a ZIP file. So use CWM to install that ZIP of older TWRP, which can then install newer TWRP as an IMG file. I'm just a struggling noob myself, but I'm pretty sure CWM is not able to install an IMG file. Good luck!

MrGoodtunes said:
Quick answers: No, no, and maybe.
It appears that you may be confusing the TWRP app (which is basically useless bloat) with the actual TWRP recovery. You need to find and download the latest TWRP recovery for your device model. If you can find a ZIP of it, great; because CWM can then install TWRP recovery for you (so that when you reboot into recovery, you'll see TWRP instead of CWM). In my case, there was no ZIP available for the latest TWRP; it was available only as an IMG file. An old version of TWRP recovery, however, was and likely still is available in a ZIP file. So use CWM to install that ZIP of older TWRP, which can then install newer TWRP as an IMG file. I'm just a struggling noob myself, but I'm pretty sure CWM is not able to install an IMG file. Good luck!
Click to expand...
Click to collapse
Ahhhh, okay that makes sense. I think I follow. Now in another thread you mentioned that if I need to go back and restore I'd use TWRP to flash CWM, hen I can use CWM to recover my old nandroid backups.
A couple final questions. Will I need to do a wipe when I flash the old TWRP zip (side note, do you know a good place to find those)? If I need to go back to CWM is there any place I can find it to flash with TWRP?
Thanks for all your help!

Skyty said:
... if I need to go back and restore I'd use TWRP to flash CWM, hen I can use CWM to recover my old nandroid backups ...
Click to expand...
Click to collapse
Correct. That is IF you can find TWRP and CWM as ZIP files. I used to switch back and forth frequently, but that was years ago. TWRP is so much more useful, I no longer have anything CWM related nor the ZIPs; and can't even find where I got them. I'm pretty sure they were here on XDA. Spent some time searching, no luck. Then I tried Google. The first snippit nail'd it, here:
https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207
Skyty said:
.... Will I need to do a wipe when I flash the old TWRP zip...
Click to expand...
Click to collapse
I never wiped. I seem to recall that when installing to the recovery partition, one of the steps I saw in the log was a wipe or maybe even a reformatting of that partition taking place along the way.
Skyty said:
.... (side note, do you know a good place to find those)? If I need to go back to CWM is there any place I can find it to flash with TWRP?
Click to expand...
Click to collapse
They're both in the link (above).
Skyty said:
.... Thanks for all your help!
Click to expand...
Click to collapse
That's what the [Thanks] button is for, here on xda.

MrGoodtunes said:
Correct. That is IF you can find TWRP and CWM as ZIP files. I used to switch back and forth frequently, but that was years ago. TWRP is so much more useful, I no longer have anything CWM related nor the ZIPs; and can't even find where I got them. I'm pretty sure they were here on XDA. Spent some time searching, no luck. Then I tried Google. The first snippit nail'd it, here:
https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207
Click to expand...
Click to collapse
I appreciate the link, however, I think those zips are for a different model of phone than mine. However, I think I possibly found versions that will work for me... Is there any real way to confirm?
The serranoltexx CWM Zip
https://forum.xda-developers.com/showthread.php?t=2364980&page=99
The serranoltexx TWRP Zip
https://androidfilehost.com/?fid=24052804347768468
However, I'm not 100% certain either of these will work, and I'm not sure how I'd figure that out.
MrGoodtunes said:
That's what the [Thanks] button is for, here on xda.
Click to expand...
Click to collapse
Done!

Skyty said:
... those zips are for a different model of phone ...
Click to expand...
Click to collapse
OMG! You're right, those are for the Value Edition. I completely miss'd the "ve" in them. Sorry.
Skyty said:
... I think I possibly found versions that will work for me..
The serranoltexx CWM Zip
https://forum.xda-developers.com/showthread.php?t=2364980&page=99
The serranoltexx TWRP Zip
https://androidfilehost.com/?fid=24052804347768468 ...
Click to expand...
Click to collapse
I remember using that very CWM zip version 6.0.5.1, so it should work okay. Good find.
I'm not familliar with that particular TWRP zip. It does clearly indicate being for the i9195 model; I'm just not sure about what "open" means at beginning of zip's filename. Still, worth a try. (If it fails, you can more easily find a TAR file of the most recent TWRP and use Odin to install it.)

MrGoodtunes said:
OMG! You're right, those are for the Value Edition. I completely miss'd the "ve" in them. Sorry.
I remember using that very CWM zip version 6.0.5.1, so it should work okay. Good find.
I'm not familliar with that particular TWRP zip. It does clearly indicate being for the i9195 model; I'm just not sure about what "open" means at beginning of zip's filename. Still, worth a try. (If it fails, you can more easily find a TAR file of the most recent TWRP and use Odin to install it.)
Click to expand...
Click to collapse
So, just thought I'd let you know that I'm up and running with LineageOS and I tested reverting back and forth to CWM and TWRP. Eveything seems in working order! I appreciate you help and have clicked the thanks button on your messages! All the best!

Skyty said:
... I tested reverting back and forth to CWM and TWRP. Eveything seems in working order!
Click to expand...
Click to collapse
That's excellent. It's really amazing how much we can do with this little S4mini device; thanks to the work of devs, several of whom are still providing updates. After all there's never been a more powerful device (other than S4mini VE) that weighs under 4 oz.

MrGoodtunes said:
That's excellent. It's really amazing how much we can do with this little S4mini device; thanks to the work of devs, several of whom are still providing updates. After all there's never been a more powerful device (other than S4mini VE) that weighs under 4 oz.
Click to expand...
Click to collapse
Yeah, its amazing! I've been able to breath new life into my old phone, I'm shocked at how well it runs on the S4; not as well as my newer phones, but better than before. Funnily enough, its actually running a newer version of Android than my S8 and S10e haha. Now onto those phones... been trying to get them both rooted but it's looking like a no go haha.