Related
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Make a backup in TWRP, wipe your system partition, Flash the ROM zip and the GAPPS zip, reboot, profit. If anything fails you can roll back to your backup and try again.
Real simple. Download the latest built as well as the latest google apps (gapps)
Reboot to TWRP
Do a backup, so you have a restore point if something happens
Go to wipe->advanced wipe and choose both caches, system and data. DO NOT wipe internal storage
Go to install, choose the ROM and gapps and install them
Reboot
You will now be on the latest. You will have to set your phone up again, and all your text messages, home screen, act will be gone but all your stuff on your sdcard (internal storage) will be untouched.
You can also get real ambitious and make backups with something like titanium backup of all your apps and data and restore it after booting PN, but try to not back up system apps or system data (it should be an option... I dont know, I never use tibu). The main thing you lose without backing up is texts, I usually just deal with it/redownload apps/set up home screen again.
On future updates, unless there are major changes and its indicated by a majority of people in the PN thread, just dirty flash.
That is, backup, wipe caches, install new ROM version( I wouldn't reflash gapps ) this will leave all your apps, settings, ect... But should only be done when flashing the same or a very similar ROM. If you dirty flash and experience problems, go back and clean flash as I first instructed.
So I should not worry about flashing the new 32r radio?
shouldnt this have been one of the first things to learn BEFORE you ever rooted your phone? yea, nice job jumping in before learning your way around. i bet you even used a toolkit to root your device..
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
roy.garlington said:
Everyone's got to start somewhere. And no toolkit here but thanks for your input! And thank you for the helpful responses.
Click to expand...
Click to collapse
no tool kit? ok, your -1 on not learning before rooting has a +1 right by it, for rooting the proper way. you just might earn some respect
Hey there simbo, what do you say about flashing the radio?
Sure. Or don't.
Whatever.
The radio is pretty separate from android. Its basically drivers to tell you phone how to use hardware.
FI has certain requirements for activation that may check what radio you have, but outside of that run what ever works good for you., its not going to for sure be any specific one. Newer may often be better but its not uncommon that an older one may work a little better.
Different apps can help you monitor (I dunno which ones... But I know its a thing ), you can also go into about phone -> status -> sim status and check signal strength where lower dBm is better(well a lower numeric value... Its technically a negative number, so higher is better i.e. -113 is worse then -104). This will vary slightly minute to minute and place to place so just taking a glance once won't really settle it for you
I just use it for a day or two, pay attention to how my signal is (just kinda how often did I have decent # of bars, nothing scientific), and check battery stats clicking on cell standby and looking at % of time with out signal.
roy.garlington said:
Hey there simbo, what do you say about flashing the radio?
Click to expand...
Click to collapse
youre choice. you can try any of the radios, from previous android versions, on any android version. they arent specific. im using the 27R radio. whichever one works best for you, thats whats important
roy.garlington said:
I am new to my Nexus 6 and new to flashing custom roms. I have read the thread all morning long and still don't feel comfortable with what information I have obtained. I'm currently running marshmallow 6.0 rooted with supersu 2.52. How can I flash the latest pure Nexus project 6.0.1 correctly? I do have TWRP recovery installed and I'm running on build number MRA58R
Click to expand...
Click to collapse
Well, it's all very easy if you read a little. Still i will give you one extra tip in case you start flashing all kinds of roms: You unlocked your bootloader. Before doing that you enabled "OEM unlocking" in 'Developer options'. Leave that enabled (this setting is 'sticky'. even when you wipe the device)!!!!. Leaving OEM unlocking enabled will disable "Device Protection" that causes sometimes a 72 hours lock-out from your Google account.
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Strephon Alkhalikoi said:
1. Learn how to use ADB and Fastboot. Toolkits may get the job done, but you learn nothing in using them.
2. If flashing individual images from the system image, NEVER flash userdata.img as it resets your storage to 32GB. Formatting your internal storage using ADB, Fastboot, or in TWRP will restore the missing storage.
3. The system corruption message likely will disappear after you format internal storage and flash the stock images from Google. It will return however if you modify /system by adding files. To permanently remove it requires a custom kernel.
4. This a developer phone. You should be able to root it without losing the warranty.
Click to expand...
Click to collapse
First thanks for your answer!
Oh yes for the 1 and the 4, my precedent phone is a Nexus 4, I know these phones and the steps to root/unroot/flash custom rom/recovery etc.. ^^ (I have made that a looooooot of times on my N4 without any problem, with and without NRT)
And this is for that I am surprised by the bad reaction of my Nexus 6 to this simple actions I request to it. (flashing image files)
I don't make anything I don't know, I am scared to brick my phone because I have made something that I master.
Yes I have forgot this point about userdata.img... But this is not a problem, I have resized my partition after flashing my phone with TWRP =)
The point that are interesting for me is the third point. I want to flash a stock image from Google. It's my goal. (I will flash custom ROM when Google will have stopped the update support)
In fact, my principal big problem is why the OTAs have been failed whereas I just start my phone, out of the box, with no modification and no root.
I'm not a specialist but for me, this is not normal when the phone is out of factory.
I will retry to flash another factory image from Google. This time with the flash-all script.
Thanks =)
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
For the last update, my bootloader have displayed at boot "Your device is corrupted. Blah blah blah..."
I actually make a new OTA update (6.1 I think). But I have an error one more time...
But I have no bootloop this time. The system reboot perfectly but in the old version. And few minutes later, the OTA is notified... Etc etc.
But, if a new system update is available, do you think I will get the same problems?
My system seems to be clean now... But during my multiple trys, my system has been clean too...
Without that, all is good and functionnal. Android, Wifi, LTE, screen, sound..... All!
This is very mysterious... Mostly for a new phone, non-rooted.
I did not want to root it while Google support it, but without root, my phone would still be blocked. That's not normal.
Should I be worried about it?
Thanks everyone!
Click to expand...
Click to collapse
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Kermi78 said:
...
But, if a new system update is available, do you think I will get the same problems?
Click to expand...
Click to collapse
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
I have tried this. Thank you for this tip. I did not know Bootloader and OTAs fail depends of /system state. (I have never modified official google image. If I modify a device, it's with a custom rom like CM for example. Without my problem at the first start I would not have modify anything on my phone)
First, I don't have the bootloader message, that's a half good news
I download actually the MRA58N OTA update. Crossing fingers! =)
NLBeev said:
Flash the latest TWRP 3.0 and the lite stock ROM of @Danvdh. This ROM has all you need, including root and OTA.
Click to expand...
Click to collapse
My goal is to use the official Google Nexus Factory Images with official bootloader, etc.... Exactly the state of a normal Nexus out of the box.
But thank you. In last resort I will think of your tip.
StykerB said:
Next time you flash and go into twrp make sure to select the "leave system read-only" option. Otherwise twrp will patch /system to survive a reboot and any modification to /system will break the next ota.
Click to expand...
Click to collapse
So after my last try of OTA, 2 times, the update has been succeded!
Just thanks a lot! :good:
I notify this thread resolved
Kermi78 said:
My goal is to use the official Google Nexus Factory Images with official bootloader, etc....
Click to expand...
Click to collapse
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
NLBeev said:
Than you can't use layers. You have to live with the white Google ui, battery drain and hurting eyes.
Click to expand...
Click to collapse
Oh no that's good for me, I love Android Stock and I hate layers
For the battery... You see, my last phone was a Nexus 4. So the battery life of Nexus 6 is so wonderful for me!
In all cases, my phone is now stock and functionnal. Just that I want for the moment... I will see later for install other roms on it
I want to be simple things.
Kermi78 said:
(sorry for my bad english I'm french )
Hi everybody,
I have received a new Nexus 6 32GB... No, sorry, a 64GB model (thanks to my resailer.. he make a mistake in the command, so I have won 32GB more! ).
But, I have few software problems with it...
At each OTA update, I get an error (at the robot opened screen). With almost all versions. This error get me a bootloop after update...
So I must to flash the official Google Image manually, partition by partition (else with NRT, I get an error at system writing step... I don't know why).
When I have fixed Android, finally, I have only.... 23.03 GB... With all versions.
So I must resize it in TWRP at each update (OTA or not).
Click to expand...
Click to collapse
DON'T INSTALL THE userdata.img file and this won't happen.
A few week ago I rooted my phone running 7.0 and flashed 7.1 .1 using my PC. Everything worked great and all my desktop folders stayed intact. Today I flashed 8.0 using TWRP without a PC and I lost all my folders. My question is where are these folders stored.? I assumed they were part of the google backup but apparently not. Today when I flashed I did a wipe first. Did that cause them to get deleted?
My concern is that 8.0 rom is WIP so I will probably be updating again soon but I don't want to rebuild my home screen everytime.
Need more info, what did you flash, type of wipe, encrypted or unencrypted etc... Also what do you mean by desktop folders? If you wipe internal storage it will delete all user data, ie sdcard. Wiping everything except internal storage usually keeps all data unless you switch between encrypted and unencrypted(that depends on type of kernel flashed either Inc in rom or separate)
Sent from my Nexus 6 using Tapatalk
Sounds like you dirty flashed from 7.0 to 7.1.1. That means at most you wiped dalvik and cache (and maybe not those).
Going to 8.0 within TWRP, you correctly did a clean flash. Wiping data, dalvik and cache. This is critical between major releases (e.g. 7.x to 8.x). But it also means you will lose your settings including the home screen set-up; which is what I think you mean by "folders".
You probably can get away with dirty flashing future minor updates and not have to do the set-up again. If you develop weird issues after a minor update, you might have to re-flash doing fill wipe again losing settings. This is the nature of flashing ROMs.
I'm guessing you are using the stock launcher. I haven't used that since 5.0 so I can't say if the home screen configuration is backed up to google. I use Nova Prime and Titanium Backup to ease set-up after clean flashes.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Sounds like you dirty flashed from 7.0 to 7.1.1. That means at most you wiped dalvik and cache (and maybe not those).
Going to 8.0 within TWRP, you correctly did a clean flash. Wiping data, dalvik and cache. This is critical between major releases (e.g. 7.x to 8.x). But it also means you will lose your settings including the home screen set-up; which is what I think you mean by "folders".
You probably can get away with dirty flashing future minor updates and not have to do the set-up again. If you develop weird issues after a minor update, you might have to re-flash doing fill wipe again losing settings. This is the nature of flashing ROMs.
I'm guessing you are using the stock launcher. I haven't used that since 5.0 so I can't say if the home screen configuration is backed up to google. I use Nova Prime and Titanium Backup to ease set-up after clean flashes.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thanks, this is very helpful. I will research Nova Prime and Titanium before my next flash.
Hi
So I'm no tech genius but I have a little bit of familiarity with Nexus Root Toolkit and my Nexus 6 is unlocked.
I have factory reset from the OS and started again but the phone is still way slower than it used to be. On top of that I've never had the nerve to try mucking about with alternative kernels and trying to get rid of the encryption.
But now I feel like I have no option. I want to do whatever I can to keep the phone usable for another year or maybe more and it seems like getting rid of encryption will likely help quite a bit!
Any advice on how to go about this as a a newbie with limited tech knowledge?
Cheers
R
ralphaverbuch said:
Hi
So I'm no tech genius but I have a little bit of familiarity with Nexus Root Toolkit and my Nexus 6 is unlocked.
I have factory reset from the OS and started again but the phone is still way slower than it used to be. On top of that I've never had the nerve to try mucking about with alternative kernels and trying to get rid of the encryption.
But now I feel like I have no option. I want to do whatever I can to keep the phone usable for another year or maybe more and it seems like getting rid of encryption will likely help quite a bit!
Any advice on how to go about this as a a newbie with limited tech knowledge?
Cheers
R
Click to expand...
Click to collapse
Quick update.
I found this video "How to Disable Forced Encryption on Rooted Nexus 6!" on Youtube which did a walk-through of using Nexus Root Toolkit to flash the Boot kernel with an img file that unencrypts the Nexus 6.
Problem was my Nexus 6's build is not listed. It's Android 7.1.1 N6F27M
I did a manual search and found a few boot.img files specifically for this build on Android File Host by a developer called bmasephol
Anyway, I downloaded the file from androidfilehost and then manually used the boot.img flash option to select and flash to my phone. It did appear to work but on re-booting the phone stull says it's encrypted under SECURITY.
Any suggestions on how I can either...
a. Get Nexus Root Toolkit to recognise my build or
b. Manually flash the right boot.img file to the phone so that it unencrypts my device?
Thanks for any advice.
P.S. I did think about picking a different boot.img for one of the other recent builds using 7.1.1 listed in Nexus Root Toolkit but I decided that might be adding fuel to the fire. Last thing I want to do is brick my phone!
R
ralphaverbuch said:
...Nexus Root Toolkit and my Nexus 6 is unlocked.
I have factory reset from the OS and trying to get rid of the encryption.
Click to expand...
Click to collapse
NRT installs also TWRP-recovery.
You may wipe the data partition and flash (with TWRP-recovery) a ROM with supersu included.
SuperSu patches the stock kernel. No forced encryption.
https://forum.xda-developers.com/showthread.php?p=74018955
NLBeev said:
NRT installs also TWRP-recovery.
You may wipe the data partition and flash (with TWRP-recovery) a ROM with supersu included.
SuperSu patches the stock kernel. No forced encryption.
https://forum.xda-developers.com/showthread.php?p=74018955
Click to expand...
Click to collapse
Thanks for the tip.
As a bit of a newbie can you just walk me through what I have to do with the file?
I have downloaded it to my Windows PC and have the Nexus 6 plugged in to the laptop with NRT. I have also already got TWRP on the recp]overy partitio. Then....? Not sure how/what I do at that point to get the ROM onto the phone and how do I wipe the data partition?
Apologies for the ignorance. At the limit of my knowledge/skills.
ralphaverbuch said:
Thanks for the tip.
As a bit of a newbie can you just walk me through what I have to do with the file?
I have downloaded it to my Windows PC and have the Nexus 6 plugged in to the laptop with NRT. I have also already got TWRP on the recp]overy partitio. Then....? Not sure how/what I do at that point to get the ROM onto the phone and how do I wipe the data partition?
Apologies for the ignorance. At the limit of my knowledge/skills.
Click to expand...
Click to collapse
Think I worked it out....
ralphaverbuch said:
Think I worked it out....
Click to expand...
Click to collapse
Correction... I managed to install that zip file using TWRP after first wiping the data folder and it all works. But it's still telling me I'm encrypted?
Did I download the wrong one?
N6F27M-Lite-7.1.1-su282sr5.zip
Lite stock rom for the Nexus 6. Prerooted with SuperSU 282SR5 Updated October 2017.
To be unencrypted, after flashing a boot.img (also known as a kernel) that does not force encrypt, you must wipe the internal storage. THIS WILL DELETE ALL FILES, MUSIC, VIDEOS WHATEVER STORED ON THE "SD CARD" DO A BACKUP FIRST!
Of course, just wiping internal storage after a factory reset will probably fix the slow down without anything else needing to be done.
I run my phone encrypted
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
To be unencrypted, after flashing a boot.img (also known as a kernel) that does not force encrypt, you must wipe the internal storage. THIS WILL DELETE ALL FILES, MUSIC, VIDEOS WHATEVER STORED ON THE "SD CARD" DO A BACKUP FIRST!
Of course, just wiping internal storage after a factory reset will probably fix the slow down without anything else needing to be done.
I run my phone encrypted
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Ok so I think I put an unencrypted boot.img on the device already. So wiped the user data with a factory reset and restarted the phone to see if that did the trick...
... Except it bloody didn't!!!
Clearly I'm too thick.
What internal storage do I need to wipe?
adb reboot bootloader
fastboot oem unlock
fastboot flash boot <non forced encrypt boot.img> (suggest using Franco)
fastboot erase userdata
fastboot reboot
Please note; while you probably can do everything through a toolkit, it all happens in the background automatically, so when a problem develops, you don't know enough to resolve it. I don't use toolkits and don't support using them. Fastboot/ADB are not hard and Google had released them as stand alone tools making it easier.
Thanks for the tips. Not 100% confident I know what I'm doing but you never learn if you're not willing to give new things a go!
Cheers
R
I should have commented in the previous post, if your device bootloader is unlocked already, you don't need the "fastboot oem unlock" command.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
OK well I tried and sent it into a repeated bootloop between the google startup logo and TWRP... so whatever I did was plainly wrong! Trying to use NRT to at least get it back and running.... I'm clueless as to the steps I'm meant to take... Ho hum.
Does that mean you can not boot into TWRP?
If you can, do a factory reset, get to a known condition.
Then download Franco's kernel. Flash it in twrp. Reboot. Make sure everything works.
Boot to bootloader (fastboot). Connect to your computer. Type:
fastboot devices
It should come back with your device serial number. If it doesn't, there is a problem with your computer drivers.
Type the command:
fastboot format userdata
This will wipe everything on the "SD card". Reboot. You should now be unencrypted.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
hi my device is nexus 6 running android oreo 8.1
i had tried two rom both 8.1
but they both have the same issue
the device reboots once every day
how to solve it?
thank you all
Tenzinjamyang said:
hi my device is nexus 6 running android oreo 8.1
i had tried two rom both 8.1
but they both have the same issue
the device reboots once every day
how to solve it?
thank you all
Click to expand...
Click to collapse
Let me know the rom names ?
ragulhm said:
Let me know the rom names ?
Click to expand...
Click to collapse
aosip and nitrogen
You might try ABC ROM or Beltz. Both are in the Android Builders Collective thread.
If you still have reboot problems with either of those ROMs, I would wonder if your battery has been replaced.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
before you do this, make sure you have found the oreo rom you want to use. Remember Oreo dont like crackflashing...
1 - Download the latest Google OTA image HERE https://dl.google.com/dl/android/aosp/shamu-ngi77b-factory-5cd75e2a.zip
2 - Use adb or wufresh tools to restore back to stock
3 - Once on stock, install TWRP and ROOT
4 - Reboot to TWRP and format everything, including storage
5 - Now Add the OREO ROM, Gapps, and Root zips to device storage
6 - Flash ROM, Gapps, and Root...NOW FORMAT data, cache, dalvik-cache, and storage (DONT WIPE SYSTEM)
7 - Reboot, PROFIT!!!
I'm not the least bit sure the above is necessary. Without question you should be on the newest bootloader before going to oreo, but returning completely to stock, then rooting, which just gets overwritten by flashing a custom ROM seems excessive.
If you are that nervous about doing an upgrade, then I strongly recommend NOT using a toolkit. Toolkits are great, until something goes wrong and because you're automating the process you'll have no idea what went wrong. Particularly on N6, it is so easy to just use ADB/Fastboot. Those drivers have to be installed anyway for a toolkit to work so you're not gaining anything.
If you follow that advice, please make sure you back up EVERYTHING since the method is directing you to wipe your storage (user data). Of course, if you follow proper return to stock instructions, you'll wipe internal storage (user data) as a function of the -w fastboot switch.
IMHO, it's a mistake to link directly to a factory image release. Here is the factory image page, complete with instructions and checksums for the files. You should ALWAYS verify checksums before flashing a file. The file linked above is the last one listed (newest) in the shamu grouping.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
fkfmfz said:
before you do this, make sure you have found the oreo rom you want to use. Remember Oreo dont like crackflashing...
1 - Download the latest Google OTA image HERE https://dl.google.com/dl/android/aosp/shamu-ngi77b-factory-5cd75e2a.zip
2 - Use adb or wufresh tools to restore back to stock
3 - Once on stock, install TWRP and ROOT
4 - Reboot to TWRP and format everything, including storage
5 - Now Add the OREO ROM, Gapps, and Root zips to device storage
6 - Flash ROM, Gapps, and Root...NOW FORMAT data, cache, dalvik-cache, and storage (DONT WIPE SYSTEM)
7 - Reboot, PROFIT!!!
Click to expand...
Click to collapse
thank you but no work my nexus 6 still reboot (soft reboot) about every 24 hours
Tenzinjamyang said:
thank you but no work my nexus 6 still reboot (soft reboot) about every 24 hours
Click to expand...
Click to collapse
There are many reasons this could happen. An app, a theme, an old battery.
Look to get a log right after the reboot,
adb shell cat /proc/last_kmsg
adb logcat > crash.txt (look for a shutdown thread)
adb shell cat pstore/last_kmsg/serial logs
or if you are running a theme/substratum, remove it for now to see if the problem improves.
If you have mods like custom kernel, exposed, viper, remove them to see if the problem improves.
Delete bootloader logs by rebooting to bootloader, scroll through with volume buttons until reach bootloader log entry, long press power until the phone reboots and immediately fully charge. If the problem improves, it's likely due to the age of your battery.
Try booting to safe mode and see if the problem comes back. Safe mode will not only the minimum necessary for the device to run. It eliminates apps for the most part.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Oreo is far from stable. Samsung S8 had to cancel Oreo release due to rebooting as well
HueyT said:
Oreo is far from stable. Samsung S8 had to cancel Oreo release due to rebooting as well
Click to expand...
Click to collapse
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
do you know any good rom oreo 8.1 for oneplus one bacon? thank you.
Tenzinjamyang said:
do you know any good rom oreo 8.1 for oneplus one bacon? thank you.
Click to expand...
Click to collapse
No? This is a nexus 6 thread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I have never had a reboot on 8.1 ABC for shamu. Beltz is equally stable.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Do the random reboots occur when the device is charging? I had one this morning (running Beltz) while plugged in and fully charged, meaning the battery wasn't being used.
Strephon Alkhalikoi said:
Do the random reboots occur when the device is charging? I had one this morning (running Beltz) while plugged in and fully charged, meaning the battery wasn't being used.
Click to expand...
Click to collapse
I've not had reboots on either Beltz or ABC. Though I have been running ABC pretty much since it was built for shamu.
Back before I replaced my battery, especially towards the end, it would reboot when even when it was plugged in. At its worst, plugging-in would crash the phone.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I've not had reboots on either Beltz or ABCBack
Click to expand...
Click to collapse
I've also a soft reboot once a day. Around 17h. N6 Beltz180314, unencrypted.
That reboot issue started when I installed substratum and black themed layers.
In the Beltz and ABC there's already a dark system theme. Imo this theme works well, but can cause a possible conflict with substratum.
NLBeev said:
I've also a soft reboot once a day. Around 17h. N6 Beltz180314, unencrypted.
That reboot issue started when I installed substratum and black themed layers.
In the Beltz and ABC there's already a dark system theme. Imo this theme works well, but can cause a possible conflict with substratum.
Click to expand...
Click to collapse
I'm still on the "never had a reboot" side [emoji6]
I also use substratum and leave the dark system theme enabled...no reboots. I stand by my opinion that most shamu users with reboot problems need to look at their battery, esp. when it's hours into use.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I'm still on the "never had a reboot" side [emoji6]
I also use substratum and leave the dark system theme enabled...no reboots. I stand by my opinion that most shamu users with reboot problems need to look at their battery....
Click to expand...
Click to collapse
Because my 'once a day reboot' happens in the afternoon I will check the battery charge % when it happens.
But it's a soft reboot; same as when substratum.
I keep an eye on the battery and also on substratum.
I get the once a day reboots also on Oreo ROMs, I would agree with the battery being old theory, but how do you explain no reboots when I go back to PN?
EAK128 said:
I get the once a day reboots also on Oreo ROMs, I would agree with the battery being old theory, but how do you explain no reboots when I go back to PN?
Click to expand...
Click to collapse
Kernel settings maybe? If possible, run the problematic ROM while on charger and see if it reboots.
@NLBeev, I agree that a soft reboot sounds more like theme, or maybe app. I can tell you that I've been running ABC Oreo for N6 since its release. I've been dirty flashing (deleting substratum theme first) each time until last week when I clean flashed.
I don't know if it's possible for you to stay tethered to a PC, but catching a logcat through ADB would probably help. You can store a larger file that way.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
....I don't know if it's possible for you to stay tethered to a PC, but catching a logcat through ADB would probably help.
Click to expand...
Click to collapse
Use my N6 daily
I am suspecting 3 things: battery, substratum and the powersave option of Ex kernel.
It's now evening here and no soft reboot yet.