Develop Bugs

[Q] 5.0.1 Rooted to 5.0.2 Without Data Loss

For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.

Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps

I'm having the exact same problem. I'm attaching what's appearing on TWRP.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.

I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.

You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.

yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app

^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.

newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx

mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?

(OTA) T-Mobile Lollipop 4.20.531.4 Sense 6.0 Zip

This is the official 5.0.1 Lollipop (4.20.531.4) Sense 6.0 OTA for T-Mobile HTC One M8. (4.20.531.4)
Nothing modified. Just a straight copy. Enjoy!
If you just need the firmware or rom you can download the zip and extract what you need from it. It's pretty simple.
I'll try to get around to extracting everything and posting links for the individual firmware as well. Don't get mad if I don't get around to it though.
Don't do anything with this unless you know what you're doing.
Download Link: https://docs.google.com/uc?export=download&confirm=mOs6&id=0B83tee7zNQDVTTRsTjJ1dzhHeUU

Would it be possible to upgrade to this without having to flash back to stock first?

How to go back to stock and apply OTA.
douglasf01 said:
Would it be possible to upgrade to this without having to flash back to stock first?
Click to expand...
Click to collapse
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad

bradley_e_smith said:
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad
Click to expand...
Click to collapse
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks

douglasf01 said:
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks
Click to expand...
Click to collapse
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad

bradley_e_smith said:
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad
Click to expand...
Click to collapse
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?

douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).

bradley_e_smith said:
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).
Click to expand...
Click to collapse
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?

This is the issue I am presented with trying the CMD with fastboot

douglasf01 said:
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?
Click to expand...
Click to collapse
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.

bradley_e_smith said:
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.
Click to expand...
Click to collapse
I went into the supersu application and there was an unroot option that clears the cache, system, and modifies something. I also flashed the stock recovery back after your last comment, I have never owned an HTC Android device and wasnt aware that was a default. I am going to try the OTA and see if this works out. I will let you know.

I have always just reflashed stock recovery.... Made sure I enabled all of the apps I disabled (like bloatware or whatnot), and then was always able to update. I actually can't recall if unrooting was required.
But I do know that locking the boatloader is not necessary.
---------- Post added at 03:15 PM ---------- Previous post was at 03:14 PM ----------
I am just sad to say goodbye to Xposed....

T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip

douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
When you get the red triangle, hold volume down for a few seconds...you should get a log screen (although it may be volume up, I can't remember, try both)...it will tell you what is wrong.
Also, from my past experiences, if I didn't flash a new stock Rom (but just tried to "clean up" my existing stock Rom), I would run into problems because I had some app on the phone that even if I had deleted it, had originally modified build.prop... And that is one key thing the update checks before proceeding with install. So you have to make sure you have a stock build.prop file.

Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.

douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
You need to rename the recovery file.
Avoid using '+' in files names.
If you have spaces in a file name, ALWAYS put a "quotation mark" around the file name.

DROITURK182 said:
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
Click to expand...
Click to collapse
The link doesn't seem to work.

epsix said:
Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.
Click to expand...
Click to collapse
This is something that always happens with HTC devices. I don't know why.

OfficialLocdoGg said:
This is something that always happens with HTC devices. I don't know why.
Click to expand...
Click to collapse
Yeah, I try changing the sku id in ACC/default.xml to metro pcs, and other carriers it works but not good signal.

Okay, I have got APNs unlocked, root, restriction-free tethering working over IPv6, busybox installed, and a kernel with modified initramfs. Anyone interested in a nice simple debloated stock ROM?

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!

Haven't flashed in over 2 years. Missing anything?

I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.

We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...

Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!

You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.

Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING

ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"

ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html

k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device

Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:

beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS

ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me

Question Bootloop after battery died

Yesterday it happend suddenly: Battery 5% left, just a quick newsarticle before bed and it left me.
At first it didn't even take any charge. Booted in recovery and it's at 40% now.
But booting doesn't work.
OP Logo, bootanimation for around 20 seconds, repeat...
What I tried:
Power off, reboot
changed active slot
Flash the boot image what was last downloaded by me a while ago (semed to be Boot 12.C44_BA, not sure)
Flash the magisk image
Flashed a C47 image
no difference at all, same boot pattern.
A little sidenote:
I have magisk on my op9p, worked fine. a recent ota update failed repeatedly installing in defaulkt way. at boot i had to switch active slot in fastboot a few times. then it booted to current firmware.
I am wondering why i get the same issue independent from the boot.img.
Why did the low battery started this problem at all? How can i be sure to have the right boot.img flashed.
And most important: how can i boot into andoird again?
let me know if you need more information.
Thanks in advance!
edit:
is it possible to install twrp and backup/restore later the important data?

use msm tool and make all new

ChrisFeiveel84 said:
use msm tool and make all new
Click to expand...
Click to collapse
thanks for the hint! I read about this tool. But this means a full wipe of system and user data, right? any chance to avoid this and rescue images before setting up new?

I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?

Speaka said:
I see a few possibilities to get closer:
i can boot twrp via fastboot. wiping data seemed to not help.
mounting userdata doesn't work because it needs a pin code which is not my system code.
maybe i have the wrong boot.img? can i find out which firmware version is installed via twrp and flash the right image afterwards?
Click to expand...
Click to collapse
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?

luckylui said:
TWRP doesn't work with A12 only A11 at the moment.
Have you tried getting your hands on the C.62 firmware to local update?
Click to expand...
Click to collapse
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?

Speaka said:
thanks for pointing that out!
did not try yet. can you please point me to a howto thread?
what would be the way to update if i have no system access?
Click to expand...
Click to collapse
Google search "Tool ALL IN ONE" download it and install. Download the C.62 firmware from one of the threads in the forum. Open the tool you installed earlier select generic device from the pop-up. Click on "advanced options" in the tool and that'll bring you to "adb sideload". I hope that works for you!

This sounds promising. I will try that later. To be sure: This will keep personal data like an usual ota update?
Edit: I'm still stuck. Heres what i do: Boot twrp (not install) from fastboot. in twrp start adb sideload. open the toolaio, generic device, advanced options, select firmware.zip and click flash under sideload. Than it prompts "phone is not in adb or fastboot mode". In the main window it show the device id and "adb sideload".
what am i missing?