I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
barry123 said:
I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
Click to expand...
Click to collapse
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
deleted cache, dalvik, wiped entire phone, yes
LeftHandedWave said:
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
Click to expand...
Click to collapse
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
I've done that too in my initial flashing
flashback7 said:
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I've done that too in my initial flashing
Click to expand...
Click to collapse
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
flashback7 said:
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nope, I did a fresh install of all my apps
one7dchevy said:
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
did a hashcheck [md5] of all files as I usually do. Now I'm even having problems flashing new ROMs since in the last hour or so. I've made a backup of Pure Nexus ROM, so I know I'm able to use it, but might have to do other things here in the next couple of days to get rid of it
LeftHandedWave said:
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
flashback7 said:
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
Click to expand...
Click to collapse
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Using TWRP 2.8.7.2 wiped everything u mentioned above but unable to attach log files, no attachment box is available to me here
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
did everything u mentioned above. I've flashed my old Nexus 4 many times over the past couple of years
Use pastebin and include a link to your logs.
dodgerslim said:
Use pastebin and include a link to your logs.
Click to expand...
Click to collapse
<script src="//pastebin.com/embed_js/NHEvqKc9"></script>
BTW I've installed CM 13 and minimalistic text works flawlessly on it, no hiccups no crashes, weird!!
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
PKFR4Life said:
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
Click to expand...
Click to collapse
LOL! I've done that a few times reverting to stock and going from there. I'v had to do that in the past to get out of trouble. But seeing how I've done this countless of times over the past few years and the last phone was also a Nexus [albeit quite a change from Lollypop to Marshmallow], the rules are the same for flashing. One thing I was concerned with initially was that the vendor.img file for Pure Nexus was MMB29P but I'm on MMB29T. I don't know if that's an issue. I'm using 6.0.1 Android.
I may try it again in a few days mind you and re-flash. Will def post something if it's a positive change!!
Related
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
phermey said:
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
Click to expand...
Click to collapse
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
yes if rooted. lots of people are stock and running franco.
phermey said:
yes if rooted. lots of people are stock and running franco.
Click to expand...
Click to collapse
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
phermey said:
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
Click to expand...
Click to collapse
wouldn't hurt to wipe anyway. ill stop wiping and see if i notice a difference though, so far i dont notice any. so id probably just skip out on wiping as it does seem useless because my phone still feels the same
Hi all,
Issue with TWRP and restore. I've got a backup, but when I tried to restore it, it would crash and reboot while restoring the /data partition. I try wiping the /data partition (I have my backup on a server, too) and it crashes midway through that, too. Just reboots and returns to TWRP.
What should I do?
Thanks,
Ben
Wipe cache, dalvik cache, fix permissions, then restore.
Sent from my EVO using xda app-developers app
freshlysqueezed said:
Wipe cache, dalvik cache, fix permissions, then restore.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Tried that, no luck
I'm currently restoring the factory 4.2.2, then installing TWRP and adb'ing the files back over to try restoring again. Hopefully this works.
Thanks,
Ben
Fmstrat said:
Tried that, no luck
I'm currently restoring the factory 4.2.2, then installing TWRP and adb'ing the files back over to try restoring again. Hopefully this works.
Thanks,
Ben
Click to expand...
Click to collapse
This issue is mentioned over in the official TWRP forum under "Original Android Development" The Dev acknowledged it, saying he needs to fiddle with it... Might not be bad if you poked your head in there with any other information you could add...
*fingers crossed* Hope they get it patched up soon... I'm a little restore shy now. Up until I encountered this, I was swapping ROMs on a nearly daily basis... No anymore.
I started over again, like you, and it works ok now. But I don't know when/if the problem will rear its ugly head again, so holding off until I hear more.
DefinityX said:
This issue is mentioned over in the official TWRP forum under "Original Android Development" The Dev acknowledged it, saying he needs to fiddle with it... Might not be bad if you poked your head in there with any other information you could add...
*fingers crossed* Hope they get it patched up soon... I'm a little restore shy now. Up until I encountered this, I was swapping ROMs on a nearly daily basis... No anymore.
I started over again, like you, and it works ok now. But I don't know when/if the problem will rear its ugly head again, so holding off until I hear more.
Click to expand...
Click to collapse
I'm having the same problem with 2.5.5.0. Happens probably 30% of the time and always during the data restore. It completes on the second go-round, but I'm constantly holding my breath. I was under the impression that this was taken care of in this latest version.
Sent from my Nexus 10 using Tapatalk HD
mine crashes when I do simple wipes
on latest
happens about 30% of the time too
I had that happen a lot, I just 2.3.3.0 now and it is perfect.
http://techerrata.com/browse/twrp2/manta
Rom Toolbox app will let you install it too.
stonebear said:
I had that happen a lot, I just 2.3.3.0 now and it is perfect.
http://techerrata.com/browse/twrp2/manta
Rom Toolbox app will let you install it too.
Click to expand...
Click to collapse
Oh, good, I'll do that. Thanks.
Edit (5 min. later): Wow, that was easy, lol. Thanks again.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Oh, good, I'll do that. Thanks.
Edit (5 min. later): Wow, that was easy, lol. Thanks again.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Enjoy a recovery you can have faith in, lol.
stonebear said:
Enjoy a recovery you can have faith in, lol.
Click to expand...
Click to collapse
Ain't it the truth.
So I just tried doing the same with my phone and the installation failed, something about illegal instruction. I'm running CM 10.1 on an unlocked, S-OFF HTC Vivid.
Any ideas?
Sent from my Vivid 4G using Tapatalk 2
bruce7373 said:
Ain't it the truth.
So I just tried doing the same with my phone and the installation failed, something about illegal instruction. I'm running CM 10.1 on an unlocked, S-OFF HTC Vivid.
Any ideas?
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
Are you using Rom toolbox? If not, you aren't trying to flash the manta version are you?
Sent from my Nexus 10 using Tapatalk HD
stonebear said:
Are you using Rom toolbox? If not, you aren't trying to flash the manta version are you?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
No, I tried with RomToolbox, same method as with the N10. I choose 2.3.3 0 from the list, so I assume it was the Holiday version. The first time I tried, it claimed I didn't have permission, but I think that was because it was the first time I was using Rom toolbox since flashing CM so the permission popup came after the fact. I rebooted and that was when the message changed to invalid instruction.
Edit: Tried again with 2.4.1.0. Same result. But I located the files and they are holiday, so I can just flash with fastboot, I guess.
Sent from my Vivid 4G using Tapatalk 2
bruce7373 said:
Edit: Tried again with 2.4.1.0. Same result. But I located the files and they are holiday, so I can just flash with fastboot, I guess.
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
Yea that should work. Must be a Rom toolbox problem, I would think.
Sent from my Nexus 10 using Tapatalk HD
Hi everyone, I am having an issue whenever I install a touchwork rom that it will inevitably randomly reboot, or crash then reboot at least once a day. I am not going to mention any specific roms here because it has happened consistently with several of the most popular touchwork roms on this forum. I also considered the possibilty of a rogue app causing these problems, however yesterdayI installed one of my favorite roms and did not install a single third party application, to rule out that possibility. Today it just rebooted again this morning out of nowhere.
Caveat is that when I tried a 4 day trial on a AOSP rom, i had no such issues, even though i TB'ed my apps and restored everything.
Now I know an easy solution is to just stay on a non TW rom, but I happen to like several TW features and can't seem to figure out whats going on here.
Any ideas?
I'm assuming you have an i337m. I'd Odin the stock firmware and see if you have the reboot issues on it. If you don't it's most likely the rom that is causing the issue our the way you're flashing them
Sent from my Nexus 5
jd1639 said:
I'm assuming you have an i337m. I'd Odin the stock firmware and see if you have the reboot issues on it. If you don't it's most likely the rom that is causing the issue our the way you're flashing them
Sent from my Nexus 5
Click to expand...
Click to collapse
US version
theraker007 said:
US version
Click to expand...
Click to collapse
So you're on mdl firmware? Are you doing full wipes, system, data, cache and dalvik, when you're installing the roms?
Sent from my Nexus 5
jd1639 said:
So you're on mdl firmware? Are you doing full wipes, system, data, cache and dalvik, when you're installing the roms?
Sent from my Nexus 5
Click to expand...
Click to collapse
every single time. Again, this is only happening with TW roms. I've also tried stock and KT kernel with same roms.
Hi Everyone,
Im using an att LG G2 with Paranoid Android installed; I bought the phone at release I am pretty sure and through att. I believe it to be PA version 3.4 and Android version 4.3.1 from looking af the about phone settings. Basically Ive had this phone on loan to someone for about a year and it is just bogged down with shovelware. Netflix wont even load. I was comfortable playing around with ROMs before but ive been in the Ios scene lately and am out of practice. I have some recoveries but I'm concerned with having not played around on the phone's root for several years now so I'd rather not use something that may be incomplete.
My main concern is having the phone back to its speed from before, getting rid of all of the apps, and starting fresh. Id like to keep PA, hopefully upgrade to the latest version, but if i can just factory reset that works too. I'm pretty sure i could reinstall PA starting from scratch with a clean phone. I've been through the forums different times and I really do find that the info is all consolidated well. I hope I don't come accross as lazy or unwilling to search, I just had a bad experience flashing my Galaxy S2 so whenever I'm not certain on the process I try to consult with people more involved.
Thank you all for your time,
Andrew Rapp
Forgive me but I've had this phone on the shelf for a bit and am seeing now that paranoid Android is relatively dead. That'd be unfortunate since I really dug the interface! But if it really is no longer being supported would anyone have a suggestion on a ROM upgrade? Thanks again!
Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk
Treboeth said:
Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I had CM back on my s2! I could get down with checking it out again. Going through their website is a lot of helpful information, however, most of it seems to be garnered at first time users. I'm using this guide here:
https://wiki.cyanogenmod.org/w/Install_CM_for_d800
and I'm curious if I can skip the first half (installing a custom recovery); because I'm pretty sure I have one installed already from when I flashed PA. How would I go about checking?
Just reboot into recovery to check the version.
But it would be best to update to TWRP 2.8.73 (latest version).
Sent from my LG-D802 using Tapatalk
So once I've updated TWRP (which I do have installed) I can skip that first half and just do the second part? Thanks for the help btw; really trying to bring the phone back to life since I love the screen and size
If you have flashed Roms before you know the rule, read the first post then read it again then read it a third time
Make sure you have the correct bootstack, I suggest the official CM ROM to start with by Drastic then you can always try the others AICP,Bliss,ResurrectionRemix and Crdroid.
I like AICP for the customisations been on it for a couple of days to try out.
Sent from my LG-D802 using Tapatalk
I know, being cautious to a fault here >_< I just ended up using flashify to update twrp; that was easy enough. I'll use the app to make a back up I believe and then try following instructions on the website! Thanks for all your help, hopefully I won't need to return XD but still keeping the topic open just in case!
Nope! I get an error when trying to install the CM zip file. In red it says:
E: Error executing updater binary in zip '/sdcard/cm-12.1-20151117-SNAPSHOT-YOG7DAO1KI-d800.zip'
I was able to get in what appears to be a broken CM installation, which fortunately includes file system exploration and messaging. Accessing the phone from the computer is no problem either. Any idea what the issue here may be?
Bump!
Not sure to be honest,if you have followed the steps in the OP post up in the thread by @drastic and I am sure the more knowledgeable will help you solve the problem.
Sent from my LG-D802 using Tapatalk
I'm sorry, which thread is that?
Totalrapture said:
I'm sorry, which thread is that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3264508 Cm13 [emoji6]
Sent from my LG-D802 using Tapatalk
Ahhh thanks! Yeah I'd been doing the 12.1 downloads from the CM site but yeah that process seems to be the same. Could it be possible that my something weird had been done with the person I loaned the phone too? He liked to tinker and I wouldn't put it passed him to have done something funny with it, or even I before having loaned it. Coud the bootstack be an incorrect? Is there a way I could check?
Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk
Treboeth said:
Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I was thinking that'd be the best option; just to start everything over. Would that process be extensive? I'm on a work computer so I can use recovery and get the files on my phone but anything too complex or needing me to use installers I'll probably have to wait until tomorrow
http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk
Treboeth said:
http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll probably wait until my next day off and then try to run through it all
My hat goes off to hauwei and Google for building this handset.
I have been using a galaxy s6 for the past year rooted and tweaked to the best of my knowledge and what could be mustered with the closed source and exynos7420. I have been using the 6P for two days and honestly I'm considering something I thought I wouldn't try...... Stock no root. I have always rooted my devices and played round with them built a popular rom back in the gt540 days but this phone this beast I'm actually considering stock.
So my question currently cyanogenmod shows nightly builds but no stable builds, so unofficial at best and it looks to be the same for a lot of other roms as cm seems to be the major base for 90% of roms now, so what are currently the advantages of these builds or the builds based off stock?
Obviously there is adaway and Xposed and viper4android but in terms of build performance battery life and stability is it worth moving off stock atm?
Sent from my Nexus 6P using Tapatalk
Bump[emoji14]
Sent from my Nexus 6P using Tapatalk
Danzano said:
My hat goes off to hauwei and Google for building this handset.
I have been using a galaxy s6 for the past year rooted and tweaked to the best of my knowledge and what could be mustered with the closed source and exynos7420. I have been using the 6P for two days and honestly I'm considering something I thought I wouldn't try...... Stock no root. I have always rooted my devices and played round with them built a popular rom back in the gt540 days but this phone this beast I'm actually considering stock.
So my question currently cyanogenmod shows nightly builds but no stable builds, so unofficial at best and it looks to be the same for a lot of other roms as cm seems to be the major base for 90% of roms now, so what are currently the advantages of these builds or the builds based off stock?
Obviously there is adaway and Xposed and viper4android but in terms of build performance battery life and stability is it worth moving off stock atm?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
CM definitely isn't the base for most (or even a small percentage) of ROMs on a Nexus, most ROMs are based on the official aosp source. Most ROMs that I've tried are as stable as stock. What are the advantages? Added features. You're probably better off of gaining extra features via a custom ROM with those features built in, than gaining them by adding Xposed modules to the stock ROM. If you need instructions on unlocking/flashing/rooting this device I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
PS. As per the rules, please only bump a thread once every 24 hours, it had only been exactly 94 minutes in this case.
Heisenberg said:
CM definitely isn't the base for most (or even a small percentage) of ROMs on a Nexus, most ROMs are based on the official aosp source. Most ROMs that I've tried are as stable as stock. What are the advantages? Added features. You're probably better off of gaining extra features via a custom ROM with those features built in, than gaining them by adding Xposed modules to the stock ROM. If you need instructions on unlocking/flashing/rooting this device I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
PS. As per the rules, please only bump a thread once every 24 hours, it had only been exactly 94 minutes in this case.
Click to expand...
Click to collapse
I'm confident in the nexus development I was just unsure if the pros out weighed the cons as things currently stand vs stock
I will have a look at that thread though, I mean it is a nexus so if a hardware fault rears it's ugly head i can always return to stock.
Does the nexus line have any kind of flash counter yet or is it still safe I heard qualcomm was putting something in place awhile back. Sorry got to catch back up on things
Sent from my Nexus 6P using Tapatalk
Danzano said:
I'm confident in the nexus development I was just unsure if the pros out weighed the cons as things currently stand vs stock
I will have a look at that thread though, I mean it is a nexus so if a hardware fault rears it's ugly head i can always return to stock.
Does the nexus line have any kind of flash counter yet or is it still safe I heard qualcomm was putting something in place awhile back. Sorry got to catch back up on things
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, Nexus devices do not have any sort of flash counter. Though, during the first 1-2 months of the 6P release, rumor had it that the phone has a blowable QFuse, which would be irreversible if you unlock the bootloader.
However, later on the skepticism was wiped away, and it was clarified that nothing as such exists. Yes, the QFuse exists, but its completely unrelated.
Danzano said:
I'm confident in the nexus development I was just unsure if the pros out weighed the cons as things currently stand vs stock
I will have a look at that thread though, I mean it is a nexus so if a hardware fault rears it's ugly head i can always return to stock.
Does the nexus line have any kind of flash counter yet or is it still safe I heard qualcomm was putting something in place awhile back. Sorry got to catch back up on things
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No flash counters or anything like that on the Nexus, never has been and probably never will be. It is first and foremost a development device, it just happened to catch on in the mainstream too. If you have any questions don't be afraid to ask, we have a great community of people helping out in the guide thread.
DJBhardwaj said:
No, Nexus devices do not have any sort of flash counter. Though, during the first 1-2 months of the 6P release, rumor had it that the phone has a blowable QFuse, which would be irreversible if you unlock the bootloader.
However, later on the skepticism was wiped away, and it was clarified that nothing as such exists. Yes, the QFuse exists, but its completely unrelated.
Click to expand...
Click to collapse
Qfuse thats the one I remember reading about thankyou DJ
Heisenberg thankyou for your answer this is my first nexus device so any help is appreciated. I saw there was a couple of all in one tools in the dev forum, do you think these work well or better just to use sdk and manual commands? I ask because im all for shortcuts when they work ;P
So far though this phone has been awesome so be interesting to see what some of these roms are like I'll be using just nexus devices from now on thanks again guys.
Danzano said:
Qfuse thats the one I remember reading about thankyou DJ
Heisenberg thankyou for your answer this is my first nexus device so any help is appreciated. I saw there was a couple of all in one tools in the dev forum, do you think these work well or better just to use sdk and manual commands? I ask because im all for shortcuts when they work ;P
So far though this phone has been awesome so be interesting to see what some of these roms are like I'll be using just nexus devices from now on thanks again guys.
Click to expand...
Click to collapse
My advice: don't use a toolkit. They can make things easier sometimes but easier isn't always a good thing. They've been known to cause issues, and there's really no substitute for ensuring things go right by doing it yourself. Plus, if you're going to be modifying your phone, you really need to have a good working knowledge of fastboot, especially on a Nexus. That's what will get you out of trouble if it arises.
If you're looking for a pretty stock-like experience but with some great features added I'd recommend trying out Pure Nexus, it's a rock solid ROM with useful extra features. I have links to all ROMs (and basically anything useful for this device) in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
Heisenberg said:
My advice: don't use a toolkit. They can make things easier sometimes but easier isn't always a good thing. They've been known to cause issues, and there's really no substitute for ensuring things go right by doing it yourself. Plus, if you're going to be modifying your phone, you really need to have a good working knowledge of fastboot, especially on a Nexus. That's what will get you out of trouble if it arises.
If you're looking for a pretty stock-like experience but with some great features added I'd recommend trying out Pure Nexus, it's a rock solid ROM with useful extra features. I have links to all ROMs (and basically anything useful for this device) in my index:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
Click to expand...
Click to collapse
Fantastic thread mate ill be getting my study pants on haha used to use fastboot with my one x and the g2 but havent in awhile so ill go make sure im all up to date before I pull the trigger
One last question if ive already downloaded my whole spotify playlist 8GB can I pull that from the phone with adb backup and restore it so i dont have to re download everything pretty sure its encrypted so not sure it can be done.
Danzano said:
Qfuse thats the one I remember reading about thankyou DJ
Heisenberg thankyou for your answer this is my first nexus device so any help is appreciated. I saw there was a couple of all in one tools in the dev forum, do you think these work well or better just to use sdk and manual commands? I ask because im all for shortcuts when they work ;P
So far though this phone has been awesome so be interesting to see what some of these roms are like I'll be using just nexus devices from now on thanks again guys.
Click to expand...
Click to collapse
Depends entirely on your choice. If you want to learn more about your device and how things work on it, you can perform things by yourself. Doing it manually also helps you keep a track of things that are going on, so if somehow your device is stuck, or not functioning as it should, you can always track back the source of the issue. And since you performed it yourself, you will know it better.
On the other side, toolkits have their own benefits. If you just want to perform procedures without much hassle and automate everything, you can go for them. All the toolkits here is the 6P section have proved useful to many users. You can try all of them, and see which one works better for you and your phone.
I for once have tried SKIPSOFT Android toolkit, offers a lot of functions. At the same time, there is Squabbi's Nexus 6P Toolkit, which has a more user-friendly interface, and much simpler to use.
Personally, I don't prefer toolkits, they could be buggy, at times. And have never suited my purpose.
Danzano said:
Fantastic thread mate ill be getting my study pants on haha used to use fastboot with my one x and the g2 but havent in awhile so ill go make sure im all up to date before I pull the trigger
One last question if ive already downloaded my whole spotify playlist 8GB can I pull that from the phone with adb backup and restore it so i dont have to re download everything pretty sure its encrypted so not sure it can be done.
Click to expand...
Click to collapse
That depends, is it just stored in a folder on your internal storage or is it stored as app data?
Heisenberg said:
That depends, is it just stored in a folder on your internal storage or is it stored as app data?
Click to expand...
Click to collapse
I believe its stored as app data because even with root explorer on the S6 I couldnt find it but if I looked at the app size in the S6 app manager it didnt show the music as part of the apps usage if that makes sense.
Ill try pull data and see if it works if it does ill be sure to post it as it could be a life saver for others who once they start flashing wont stop
Danzano said:
I believe its stored as app data because even with root explorer on the S6 I couldnt find it but if I looked at the app size in the S6 app manager it didnt show the music as part of the apps usage if that makes sense.
Ill try pull data and see if it works if it does ill be sure to post it as it could be a life saver for others who once they start flashing wont stop
Click to expand...
Click to collapse
Well it'd only be an issue right now due to the bootloader unlock process wiping your internal storage. It isn't necessary to do so when flashing ROMs so the data would remain intact through ROM flashes.
Heisenberg said:
Well it'd only be an issue right now due to the bootloader unlock process wiping your internal storage. It isn't necessary to do so when flashing ROMs so the data would remain intact through ROM flashes.
Click to expand...
Click to collapse
If I have developer options enabled on stock could i not adb pull all data?
If not ohwell just means my connection will get another day of thrashing lol
So dirty flashes are not a big issue on the nexus roms? or you mean backup data in twrp and restore after the rom flash?
Danzano said:
If I have developer options enabled on stock could i not adb pull all data?
If not ohwell just means my connection will get another day of thrashing lol
So dirty flashes are not a big issue on the nexus roms? or you mean backup data in twrp and restore after the rom flash?
Click to expand...
Click to collapse
Yes you should be able to use adb pull to grab the data. What I meant was that'd only be necessary if your entire internal storage is about to be wiped, like prior to unlocking the bootloader.
And no, definitely don't dirty flash when changing ROMs, and definitely don't restore the /data portion of a nandroid backup on a different ROM. Both will cause major issues. What I meant about that was sometimes some of the data (your playlist for example) is not stored as a part of the app, but is instead stored in the internal storage. Because the internal storage itself isn't wiped during a wipe preceding a ROM flash (a clean flash involves wiping system, data, cache, dalvik cache) the playlist would still be present on your storage after flashing the new ROM.
Anyway, the whole point was in response to your comment about it being useful to frequent flashers, when in reality it (adb backup) is only really ever needed once (before your storage is wiped during the bootloader unlock). Sorry if I'm not making sense, I don't feel like I am haha.
Heisenberg said:
Yes you should be able to use adb pull to grab the data. What I meant was that'd only be necessary if your entire internal storage is about to be wiped, like prior to unlocking the bootloader.
And no, definitely don't dirty flash when changing ROMs, and definitely don't restore the /data portion of a nandroid backup on a different ROM. Both will cause major issues. What I meant about that was sometimes some of the data (your playlist for example) is not stored as a part of the app, but is instead stored in the internal storage. Because the internal storage itself isn't wiped during a wipe preceding a ROM flash (a clean flash involves wiping system, data, cache, dalvik cache) the playlist would still be present on your storage after flashing the new ROM.
Anyway, the whole point was in response to your comment about it being useful to frequent flashers, when in reality it (adb backup) is only really ever needed once (before your storage is wiped during the bootloader unlock). Sorry if I'm not making sense, I don't feel like I am haha.
Click to expand...
Click to collapse
That makes sense almost got all the updated sdk tools now so will get to backing up then rooting just wanted to double check on the backing up because i have to nuke the internal storage when i unlock the bootloader
On pure nexus now with elementalx kernel well worth it
Sent from my Nexus 6P using Tapatalk
Danzano said:
On pure nexus now with elementalx kernel well worth it
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nice
Unlocking bootloader.
Quick question regarding unlocking bootloader on 6p.
I understand that unlocking will trigger the software verification warning when starting the phone. If I return completely stock at a later date and re-lock the bootloader will the verification warning be disabled?
I'm not new to the rooting/flashing thing and have modified all of my previous Androids, but there are conflicting reports as to whether this is the case. A couple of videos on YouTube make it appear that the message is disabled after a return to stock.
Chipbutty.80 said:
Quick question regarding unlocking bootloader on 6p.
I understand that unlocking will trigger the software verification warning when starting the phone. If I return completely stock at a later date and re-lock the bootloader will the verification warning be disabled?
I'm not new to the rooting/flashing thing and have modified all of my previous Androids, but there are conflicting reports as to whether this is the case. A couple of videos on YouTube make it appear that the message is disabled after a return to stock.
Click to expand...
Click to collapse
Yes, the message will disappear if the bootloader is relocked. That's the only way to remove it. Not sure if you need it but I have a detailed unlock/root/flash guide for our device here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928