Database Users

can someone please help?

I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!

You can use fastboot to erase your current partitions then manually flash the 4.3 stock images.

I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.

chrisbo4 said:
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
Click to expand...
Click to collapse
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.

Rirere said:
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Click to expand...
Click to collapse
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.

chrisbo4 said:
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
Click to expand...
Click to collapse
Install this through device manager.
http://d-h.st/kDu

Username invalid said:
Install this through device manager.
http://d-h.st/kDu
Click to expand...
Click to collapse
Okay, it's installed. I'm not sure what I should unzip though?

chrisbo4 said:
Okay, it's installed. I'm not sure what I should unzip though?
Click to expand...
Click to collapse
You can either flash stock images with fastboot or install TWRP then flash stock zip file.

chrisbo4 said:
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
Click to expand...
Click to collapse
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!

gunner1937 said:
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
Click to expand...
Click to collapse
Thank you for the information, and I'm not offended at all. I spent most of last night reading, and attempting to get adb running on my computer. I experienced issues getting drivers installed, and the computer recognizing the device. Also, trying to find the directories... I'll keep searching to see if I can get this figured out. Thank you again!

Thanks to everyone for helping me through this problem. After a lot of searching, research, reading, and video tutorials, I flashed stock images to the N7 via fastboot. I always thought that adb and fastboot was way too advanced for me (and it probably still is), but at least I got the basics down. Thank you all again.

[q] rooting nexus 4 kitkat 4.4.2? Help!!

hey guys im new to the whole rooting and the whole android world .. anyways im on the latest version of kitkat (4.4.2) on my nexus 4 and i dont know how to root it. can anyone help me please?
also i dont know if its normal but my nexus 4 still looks like 4.3 JB .. any suggestions as to what can be the issue?
all help is greatly appreciated. thanks

The ui looks basically the same except for more white than blue.
Follow the guides on how to root.
Won't lay it all out for you since there a million guides and so on.
But you will need to unlock the bootloader. That will wipe all your data off your device. Everything will be gone.
After that you just need to boot up and put the su. Zip on the device. Reboot into the bootloader again flash a custom recovery. Or just boot it. Then flash the zip you put on the phone with the custom recovery.
That's it. Done. Now stock rooted.
If this don't make sense to you. It probably won't. Read the quides in general.

albundy2010 said:
The ui looks basically the same except for more white than blue.
Follow the guides on how to root.
Won't lay it all out for you since there a million guides and so on.
But you will need to unlock the bootloader. That will wipe all your data off your device. Everything will be gone.
After that you just need to boot up and put the su. Zip on the device. Reboot into the bootloader again flash a custom recovery. Or just boot it. Then flash the zip you put on the phone with the custom recovery.
That's it. Done. Now stock rooted.
If this don't make sense to you. It probably won't. Read the quides in general.
Click to expand...
Click to collapse
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..

zareefpeeroo said:
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..
Click to expand...
Click to collapse
Did you install Android SDK in your PC? It needs to be installed and set up first, and making sure ADB debugging box is checked in Developer Options in your phone. In addition, when you plug your phone into your PC the first time, look in your phone and select Yes when a dialog pop up asking for authorization to remember your phone.

zareefpeeroo said:
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..
Click to expand...
Click to collapse
Adb offline is a different issue. But it's irrelevant. Adb is not needed.
We need to use fastboot. Not adb. You're doing nothing but wasting your time with adb.
You would get adb up and running for what exactly? To issue the command adb reboot bootloader or adb reboot recovery..... Forget adb...

Why are you trying to root? You shouldn't undertake such tasks if you're not 100% educated on the subject.
Sent from my Nexus 4 using xda app-developers app

[Q] Nexus 10 stuck in boot after attempting root

Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?

Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s

Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.

jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.

Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked

Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.

nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom

tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck

Nexus 9 Android N Preview

It seems the n9 is eligible. Anyone has tried or thinking of trying? I might try

Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.

Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.

dictionary said:
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Click to expand...
Click to collapse
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Do we have to be on stock to receive the notification?

I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen

greiland said:
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
Click to expand...
Click to collapse
Same thing happened to me. The ota failed about 1/4 of the way through. Luckily my bootloader was unlocked. After reinstalling the system image and booting up it failed a second time when installing the ota. I think the ota has some definite issues.
Try the Nexus Root Toolkit to return to stock.

mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e

I also went the OTA route and then got stuck in a Google logo boot loop. Boot loader is locked so I am trying a factory reset. Factory reset just finished as I'm typing this. It took about 40 minutes!!!! Once again seems to be stuck on the Google logo.
Edit--
Was able to get into fastboot and install factory image! Used the Nexus Toolkit to unlock the bootloader and so far things seem to be going smoothly.

I got the OTA and it installed fine 2 bugs I have found are if you're watching YouTube and put it in split screen with hangouts and tap the hangouts screen the video will go black until you tap on the YouTube side and the other bug is that the device decided to randomly put itself in airplane mode but over all I am liking it
Sent from my Nexus 5X using Tapatalk

OTA fails for me with message stating "Android Beta Program Verification failed..." after the download. I've registered for the BETA program as normal and got the OTA notification. Same install method worked fine on my 6P. As stated above, looks like the OTA for the 9 has some issues...

USBhost said:
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
Click to expand...
Click to collapse
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.

mikereidis said:
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
Click to expand...
Click to collapse
well Google did release the source for it but... they goofed on it
Check it out https://github.com/USBhost/FIRE-ICE/tree/android-tegra-flounder-3.10-n-preview-1
BTW my kernel works on the N preview

Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?

I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?

naddie said:
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
Click to expand...
Click to collapse
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.

USBhost said:
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
Click to expand...
Click to collapse
So being straight laced and not rooting actually bricked my tablet? What the hell....
I'm a bit surprised there's no way to flash a factory image when the bootloader is locked. If security is a concern why not sign the factory image? Make it something we can sideload like an OTA update.

I am in the same boat!!!
naddie said:
So being straight laced and not rooting actually bricked my tablet? What the hell....
Click to expand...
Click to collapse
I am in the same situation. I figured that the software would be buggy but not actually brick my tablet. If anyone knows of a solution, I hope they post it here!! I would advise against installing this onto a Nexus 9 if anyone reading this is considering this firmware!!!

better33 said:
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
Click to expand...
Click to collapse
No, just wipe everything except internal. You have to extract the last image.sksmsksjssksm whatever zip. Then just fastboot flash each file individually.

Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?

kalinskym said:
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
Click to expand...
Click to collapse
In short, yes. You're basically leaving yourself a backdoor to flash a factory image should the Android N preview OTA takes a dump on you.
As my professor said to us in the laboratory: Do as I say, not as I do.
To be fair, I was hoping to do a no-wipe upgrade so I could experience Android N with all my stuff intact. I knew it was beta, but come on!

New 6P owner, returning to Android after a few years away, seeking recommendations

Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!

GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.

Samuel Holland said:
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.
Click to expand...
Click to collapse
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!

so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.

GunnermanBill said:
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!
Click to expand...
Click to collapse
Here's the link to the unofficial twrp for 6p with f2fs support. Don't forget to check the box in twrp "Use rm -rf instead of formatting" after changing data and cache to f2fs. Make sure your rom and kernel support f2fs with kernel being mandatory for best results. Here's the link:
https://forum.xda-developers.com/nexus-6p/development/unofficial-twrp-3-0-3-x-f2fs-support-t3543450
---------- Post added at 12:27 PM ---------- Previous post was at 12:15 PM ----------
GunnermanBill said:
so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.
Click to expand...
Click to collapse
I'm sure that unlocking the phone with the toolkit is safe. It's the method I used. Also in the link above or in the 6p section it should have any info you may need. You can flash recovery by vol dn & power button into bootloader(fastboot), and once you "cd /path tofolder with recovery image/" & "fastboot devices" to make sure you can see your 6p and drivers are installed correctly, you can rename twrp.img to recovery.img & they command is:
fastboot flash recovery recovery.img
I recommend going to xda 6p section; general, & questions, & answers & reading up on everything just to be on the safe side and very important; make backup at all times just to make sure if there is a "booboo" you can easily restore. If you need adb & fastboot installed, there is a thread here on xda "15 sec adb & fastboot installer".
I hope this could help and I hope you enjoy as much as I have.

Latest ROMs which gives me good performance and battery life are paranoid (still nougat, but always a winner), latest 8.1 with pixel 2 mod and aicp rom with kernvatore kernel.

Buying a 6P for good battery life may have been a mistake...

gman88667733 said:
Buying a 6P for good battery life may have been a mistake...
Click to expand...
Click to collapse
Battery life on stock has been as good as my iPhones 6s. Does charge slower though, even when it's rapid.

GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.

NoobInToto said:
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.
Click to expand...
Click to collapse
Just now finally rooted etc. My issue with stock was it would crash and reboot sometimes when unlocking it while something was playing over bluetooth. Not going nuts with advanced feature roms, but honestly at this point trust the devs here over the crazies that Google hires these days. Just keeping it safe simple and solid.

You should try the SuperXE Custom ROM on 8.0 with the Pixel 2 features/addons. You should also give PureNexus a try, if you're not so satisfied with Oreo just yet. I'm currently running the Android 8.1 developer preview and I love it, the battery life is great and the ROM is fluid with little bugs.

alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?

GunnermanBill said:
alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?
Click to expand...
Click to collapse
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update

knevelsg-j said:
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update
Click to expand...
Click to collapse
I had flashed the super user zip in the wug kit myself while in TWRP but it still didn't stick. I mentioned that previously but i said a lot of other stuff too i'm not suprised you missed it. I guess I'm probably flashing the wrong SU and will look for another.
edit - grabbed the latest stable super user and it seems good now

What's this vendor image that's a thing now? You have to be tethered to a PC to flash most roms due to it nowadays it seems. Radios used to come in zips i could flash in twrp as well, what happened to that?