Related
Ok, I'm completely self taught as far as this whole arena of technology is concerned. So please bear with me. I rooted using kindle water and clockwork mod was installed as my recovery. But, I need twrp to install any of the 3.0 kernels. Can I install twrp with clockwork mod still on my device our do I need to remove it somehow? Any advice would be great.
No, I don't think it's even remotely possible.
There are several methods you can use to install TWRP; fastboot, script, KFU, depending on whatever you're most comfortable with.
Before you do so I'd highly suggest you read and understand what is laid out in this guide: http://forum.xda-developers.com/showthread.php?t=1552547 (first, second and third posts)
It'll save you a lot of trouble when things "go bad".
Thanks for the reply!
Stage said:
Ok, I'm completely self taught as far as this whole arena of technology is concerned. So please bear with me. I rooted using kindle water and clockwork mod was installed as my recovery. But, I need twrp to install any of the 3.0 kernels. Can I install twrp with clockwork mod still on my device our do I need to remove it somehow? Any advice would be great.
Click to expand...
Click to collapse
Actually, if you wanted to have a completely wacky setup...
They are all boot images, so you can leave CWMR on your recovery partition and flash your boot partition with TWRP. Then you would "normally" boot into TWRP and selecting recovery will take you to CWMR as it did before. If you ever want to boot ICS, you can "fastboot boot" the ICS boot.img file and it should boot into the system for you. This is just all in theory, I've never done anything this insane, but it should work if you wanted.
Now, for a more practical approach....
You can leave CWMR on your recovery partition and just "fastboot boot" the TWRP image. That would get you a "per boot" access to TWRP without ever flashing it onto your device. If all you want to do is flash ICS with it, then this is a doable setup and would just require the extra step of booting directly from the TWRP recovery image with fastboot.
Well I'm on CM9 by hellfire right now so ICS is definitely possible. Just wanted to get HWA going.
Just to piggyback on the OP and maybe a more direct question.
I currently have CWMR installed. Can I simply use KFU to replace it with TWRP by choosing option 3?
dferrey said:
Just to piggyback on the OP and maybe a more direct question.
I currently have CWMR installed. Can I simply use KFU to replace it with TWRP by choosing option 3?
Click to expand...
Click to collapse
That would answer my question add well. Anyone?
dferrey said:
Just to piggyback on the OP and maybe a more direct question.
I currently have CWMR installed. Can I simply use KFU to replace it with TWRP by choosing option 3?
Click to expand...
Click to collapse
Stage said:
That would answer my question add well. Anyone?
Click to expand...
Click to collapse
KFU's TWRP installer is either broken or will install TWRP 2.0.0 (broken reboot) and FFF 1.0 (4 generations old) together. You can either tinker with its run.bat file or learn to use fastboot if you want the latest stuff installed. The latter makes more sense to me...
http://forum.xda-developers.com/showthread.php?t=1552547
The fastboot section is in post #3.
kinfauns said:
KFU's TWRP installer is either broken or will install TWRP 2.0.0 (broken reboot) and FFF 1.0 (4 generations old) together. You can either tinker with its run.bat file or learn to use fastboot if you want the latest stuff installed. The latter makes more sense to me...
http://forum.xda-developers.com/showthread.php?t=1552547
The fastboot section is in post #3.
Click to expand...
Click to collapse
Dang, reading for comprehension is not my strong suit sometimes. I read that guide yesterday and it specifically addresses my question and also says I can play with images without installing them way cool.
Thanks for pointing me in the right direction.
what is the real difference between cwm and twrp besides the interface? I like twrp but i also like to use rom manager when on another rom besides stock....also im using bootmanager for my tri-boot needs... What is the problem with cwm and 3.0 kernel?
I believe that Hashcode updated CWM to support 3.0 ROMs (Check the dev section).
I started with TWRP then CWM. Then I wanted to flash 3.0 ROMs so I used KFU to flash TWRP (Hope that helps someone).
I have not tested the new CWM yet as this old version of TWRP does what I need it to.
hgigh said:
I believe that Hashcode updated CWM to support 3.0 ROMs (Check the dev section).
I started with TWRP then CWM. Then I wanted to flash 3.0 ROMs so I used KFU to flash TWRP (Hope that helps someone).
I have not tested the new CWM yet as this old version of TWRP does what I need it to.
Click to expand...
Click to collapse
I believe that CWM is more streamlined in that it can work with ROM Manager as well, whereas TWRP requires you go to recovery in order to flash anything. However, I like to stick with TWRP for its ability to compress backups, since there isn't much free space on the Fire. I'll probably switch over to CWM eventually, but, like you, TWRP does just what I need.
YayILikePie said:
I believe that CWM is more streamlined in that it can work with ROM Manager as well, whereas TWRP requires you go to recovery in order to flash anything. However, I like to stick with TWRP for its ability to compress backups, since there isn't much free space on the Fire. I'll probably switch over to CWM eventually, but, like you, TWRP does just what I need.
Click to expand...
Click to collapse
I agree completely! Not much space at all. ROM Manager is cool but I have had more problems than solutions using it (G2X) so I am used to going into recovery to flash (CWM included).
thanks for the help. Im used to using rom manager/cwm on my indulge so im not really used to having to go into recovery for everything. but as stated earlier with the limited space on the kindle ill still with twrp then so i can compress my backups. also stated rom manager will have some problems untill they can find a way to link cwm for kindle fire to rom manager otherwise you will run into the same issues that happens when you use it with twrp....it boots into recovery and then does nothing else. lol
Alright so I tried installing TWRP via goo manager. I downloaded the app and installed the openrecoveryscript. It shows that it's installed, yet whenever I tried and reboot into recovery it still boots into clockwork... I have gone as far as trying to delete Rom Manager app from my phone and I tried installing the openrecoveryscript again. Any suggestions on how I should go about fixing this. I`m currently running 11.0-installerXNPQ02R.
I did read the "similar threads" and read them.
I am wondering If I wanted to replace TWRP with CWM what is the exact process. Also is there a way to have a dual recovery so you can choose which one you want to use?
electrojas said:
I did read the "similar threads" and read them.
I am wondering If I wanted to replace TWRP with CWM what is the exact process. Also is there a way to have a dual recovery so you can choose which one you want to use?
Click to expand...
Click to collapse
You can over write TWRP with CWM by flashing CWM with ROM Manager. Or Terminal Emulator. You can not use 2 at the same time because recovery resides in a specific memory slot that can only contain 1. There is nothing stopping you from quickly flashing back to whichever recovery you want though. These instructions will show you a way to switch back and forth at will. It works for both TWRP and CWM. You just need the appropriate recovery.img. http://forum.xda-developers.com/showthread.php?t=2170635
Thank you
BCSC said:
You can over write TWRP with CWM by flashing CWM with ROM Manager. Or Terminal Emulator. You can not use 2 at the same time because recovery resides in a specific memory slot that can only contain 1. There is nothing stopping you from quickly flashing back to whichever recovery you want though. These instructions will show you a way to switch back and forth at will. It works for both TWRP and CWM. You just need the appropriate recovery.img. http://forum.xda-developers.com/showthread.php?t=2170635
Click to expand...
Click to collapse
This is exactly the information that I have been wondering. Thanks for the quick reply and link. Peace.:good:
Keep in mind that backups are specific to the recovery that they are done with. If you backup with CWM you must restore with it also. If your latest is with CWM and then you funk your phone up, TWRP will not help you restore unless you can find a flashable CWM.
Another option?
BCSC said:
You can over write TWRP with CWM by flashing CWM with ROM Manager. Or Terminal Emulator. You can not use 2 at the same time because recovery resides in a specific memory slot that can only contain 1. There is nothing stopping you from quickly flashing back to whichever recovery you want though. These instructions will show you a way to switch back and forth at will. It works for both TWRP and CWM. You just need the appropriate recovery.img. http://forum.xda-developers.com/showthread.php?t=2170635
Click to expand...
Click to collapse
I keep flashing CWM with ROM Manager but TWRP still shows up on my Recovery, and i'm not confident enough to use the Terminal Emulator option. Is there another way to go?
Flash CWM from TWRP. Just make sure you find a version of CWM that is flashable.
Here is a link to the tar version of Philz that I use: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
PauloScalon said:
I keep flashing CWM with ROM Manager but TWRP still shows up on my Recovery, and i'm not confident enough to use the Terminal Emulator option. Is there another way to go?
Click to expand...
Click to collapse
The terminal method is quite simple and a guarantee to work. You only have to type exactly what you see in the instruction. I understand you may be nervous about using codes to change the inner workings of the ROzm but believe me as long as you type it correctly its not possible for something to go wrong.
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.
Hey All,
Model: HTC One M8 - 0p6b160
CID: TELUS0001
Got a HTC One M8 the other day, I have already dev unlocked it via HTC, but I'm looking to have root and if possible s-off but stay on the stock image.
I've been wanting to backup the recovery image (since there seems to be very little resources for the TELUS001 CID) but from everything I've read this can only be done once you have root using adb and dd. To get root I need to install TWRP or PHILZ.
What I'm not clear about:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Thanks
felix2000 said:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Click to expand...
Click to collapse
1 and 3. You can backup stock recovery by booting into custom recovery that is located on your computer, instead of flashing custom recovery to the phone. This is already what you have described in Item 3. Is your phone in fastboot mode? The TWRP file is located in the same folder as fastboot.exe? Are you sure you have fastboot connectivity? To check this, type "fastboot devices" (with no quotes) and see if your device ID comes up.
Also, a great many stock recoveries are already posted here: http://forum.xda-developers.com/showthread.php?t=2701376
This thread also describes the process of backing up stock recovery via fastboot.
2. Not sure what you are asking. But yes, recovery can't backup something that isn't there (just current installed state).
4. Having custom recovery will prevent install of OTA, if that is what you mean. But return to stock recovery and restore any system files altered by root allows install of OTA. Or you can just install a custom ROM based on Android L when it comes out, as custom ROMs are sure to come quickly after L is available. Maybe even sooner than your version's OTA.
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!