disable encryption? - Nexus 6 Q&A, Help & Troubleshooting

im on shamu 7.1 kernal 2.19.40-g54336ba and my device says encrypted? how do i turn it off? someone said by flashing a kernal? for this phone xt1103 and rom which kernal is it? thanks

leo5111 said:
im on shamu 7.1 kernal 2.19.40-g54336ba and my device says encrypted? how do i turn it off? someone said by flashing a kernal? for this phone xt1103 and rom which kernal is it? thanks
Click to expand...
Click to collapse
So basically most custom kernels list forced encryption as disabled. Really what you need to do is flash a custom kernel and then format your userdata. The way I do it is using fastboot with the command "fastboot format userdata" do this AFTER flashing the custom kernel. 2 of my favorite kernels are either elite kernel or elementalx, but there are many many more! Let me know if you have more questions!

format user data means i have to reinstall apps again?

Yes, you will lose all of your apps and data including photos and videos. Make sure you backup before you wipe user data.

if i Titanium backup my apps will formatting user data wipe out my backups? and can i just wipe in TWRP?

leo5111 said:
if i Titanium backup my apps will formatting user data wipe out my backups? and can i just wipe in TWRP?
Click to expand...
Click to collapse
No it needs to be formatted. Wiping won't do it. Do you have a PC? Backup your stuff to a PC and then format the userdata.

how do i backup to pc? i allways had phones with a sd card before so i would just do it there

DONE where it used to say encrypted it offers to Encrypt if i want

Why do you need to remove encryption? The benefits aren't that big... Slightly faster R/W and a few seconds faster booting time.

Didgeridoohan said:
Why do you need to remove encryption? The benefits aren't that big... Slightly faster R/W and a few seconds faster booting time.
Click to expand...
Click to collapse
more then a few seconds boot time, there was like 3 or 4 articles all said same thing, it benchmarked ALOT better with it off, benchmarks arent everything i know, but they represent how snappy using/switching between apps the system will be :good:

leo5111 said:
...... but they represent how snappy using/switching between apps the system will be :good:
Click to expand...
Click to collapse
The OTA's can be a spoiler. OTA's install a boot.img with forced encryption.
Today I forgot to change the boot.img before booting........ encrypted again.[emoji37]

the difference to almost EVERYONE I know with this phone is so small, its not worth the hassle..

Related

CM11 Snapshot to Snapshot Install

Moving from Snapshot M10 to a newer Snapshot M11, need always to reset data on CWM? or is not needed?
Lot of time to setting all again every month, Thanks in advance
I don't know the answer but have you tried updating without wiping /data? Seems like you've nothing to lose trying...
Erik FX8 said:
Moving from Snapshot M10 to a newer Snapshot M11, need always to reset data on CWM? or is not needed?
Lot of time to setting all again every month, Thanks in advance
Click to expand...
Click to collapse
No you don't need to wipe /data. However, wiping /cache, dalvik-cache and /system is a good practise!
TechnoSparks said:
No you don't need to wipe /data. However, wiping /cache, dalvik-cache and /system is a good practise!
Click to expand...
Click to collapse
I'm new to this so just wanted to confirm something if you wouldn't mind. I'm using MrSteve's CM port for LBL and he says to just flash the new ROM over the old when updating versions. I can only assume he knows best but is the above some voodoo that is recommended anyway, even if unnecessary?
Thanks.
ricodredd said:
I'm new to this so just wanted to confirm something if you wouldn't mind. I'm using MrSteve's CM port for LBL and he says to just flash the new ROM over the old when updating versions. I can only assume he knows best but is the above some voodoo that is recommended anyway, even if unnecessary?
Thanks.
Click to expand...
Click to collapse
In this case this depends on the developer. It seems that if MrSteve555 said to do so, then I believe it is best to follow his words. Well if you notice, I said it is a good practise to do those wipes.
If you don't do system wipe, a new zip will flash the new files and replace the old one. There are no disadvantages on doing this. But some ROM do recommend wiping the system first.
Above all, wipe the system as it might keep troubles away unless stated otherwise by the respected developers
Thanks, TechnoSparks. And the same goes for /cache, dalvik-cache too? I don't mind waiting the few extra minutes it takes to wipe these too if there's any benefit.
ricodredd said:
Thanks, TechnoSparks. And the same goes for /cache, dalvik-cache too? I don't mind waiting the few extra minutes it takes to wipe these too if there's any benefit.
Click to expand...
Click to collapse
Yes its optional too but widely recommended across the forums. I am not so sure about the benefits. But let's just assume that your device will be a lot fresher if those wipes are performed. And just maybe, when I will have to flash a ROM in the future, I will try to ignore the wiping of cache and dalvik-cache and see if they do some negative impacts on the ROM.
Wiping the dalvik-cache only took 0 to 2 seconds in my experience. Wiping the /cache partition only took about 4 seconds. So it doesn't take so much time to be obvious
TechnoSparks said:
No you don't need to wipe /data. However, wiping /cache, dalvik-cache and /system is a good practise!
Click to expand...
Click to collapse
Hi,
I have flash CM11 snapshot M11 from cwm recovery. Previously I was on CM11 nightly build.
Do I need to flash the boot.img after flashing the M11 snapshot?
Thanks.
xdagops said:
Hi,
I have flash CM11 snapshot M11 from cwm recovery. Previously I was on CM11 nightly build.
Do I need to flash the boot.img after flashing the M11 snapshot?
Thanks.
Click to expand...
Click to collapse
No, you don't have to flash the boot.img anymore.

Still confused about encryption!

Hello...I'm new to the nexus phone. I am still confused about "encryption" . I'm Stock rooted encrypted, if I flash a new rom what would be my procedure? Normally I wipe data, dalvik, system. But reading the threads here on nexus forums "data" seems to mean something else(user data). If I flash a rom with kernel included( encrypted kernel), then I would lose all my settings and my internal sdcard. Phone would be like new out the box. How can I flash from TWRP without losing my internal sdcard when I'm not near my computer?
Do I need to look for a rom without encrypted kernel? Seems like that would keep my user settings intact?
you would flash any rom just like you would normally flash any rom. if a kernel allows for decryption, then you would have to format data to decrypt(after flashing that kernel, or you will lose it out of your storage after decrypting). if you dont format data, then you will stay encrypted.
simms22 said:
you would flash any rom just like you would normally flash any rom. if a kernel allows for decryption, then you would have to format data to decrypt(after flashing that kernel, or you will lose it out of your storage after decrypting). if you dont format data, then you will stay encrypted.
Click to expand...
Click to collapse
So is "wipe data" the same as "format data"? I normally wipe data unless I'm dirty flashing. And do I have to flash a "radio" every time I flash? I thought that I read that roms don't include radios . This nexus stuff seems confusing coming from other phones. I'm on sprint if that makes a difference.
kwdan said:
So is "wipe data" the same as "format data"? I normally wipe data unless I'm dirty flashing. And do I have to flash a "radio" every time I flash? I thought that I read that roms don't include radios . This nexus stuff seems confusing coming from other phones. I'm on sprint if that makes a difference.
Click to expand...
Click to collapse
roms dont include radios, so they wont touch the one that youre currently using. its in a different partition. you dont need to flash radios when flashing a rom, ever, on a nexus. carrier also makes no difference. and wipe data and format data are two different thing. wiping data itll just clear the user data. formatting data will clear the whole partition and reformat it.
kwdan said:
So is "wipe data" the same as "format data"? I normally wipe data unless I'm dirty flashing. And do I have to flash a "radio" every time I flash? I thought that I read that roms don't include radios . This nexus stuff seems confusing coming from other phones. I'm on sprint if that makes a difference.
Click to expand...
Click to collapse
**NINJA'D
Radios are part of the firmware, and are not touched by flashing a rom. They will stay on your device, unaffected by flashing or normal wiping procedures.
Wipe data = clearing out app data, settings data, etc., created during normal use of an os.
Format data = completely wipe out the data partition of your phone, meaning anything and everything you ever save to your device will be deleted. This is what is needed in order to decrypt.
Hope that helps clear things up.
Sent from my Nexus 10
So.... I had similar questions.. As long as I flash whatever ROM and kernel I want first, I can go ahead and format data. I will then boot intro android, unencrypted, running my desired ROM and kernel, but will have lost anything in my storage? Correct?
And there's no way to decrypt without data wipe?
trickster2369 said:
**NINJA'D
Radios are part of the firmware, and are not touched by flashing a rom. They will stay on your device, unaffected by flashing or normal wiping procedures.
Wipe data = clearing out app data, settings data, etc., created during normal use of an os.
Format data = completely wrong out the data partition of your phone, meaning anything and everything you ever save to your device will be deleted. This is what is needed in order to decrypt.
Hope that helps clear things up.
Sent from my Nexus 10
Click to expand...
Click to collapse
Yes.. That makes since to me. It's just that there is a "Sprint radio.Zip" floating around that you have to flash if you lose signal. That would be a "radio" so how does it get wiped when flashing? I was going to try the "Pure Shamu" rom. That's what brought all the questions.
Ok.. Seems like any kernel change will wipe internal storage
If I'm encrypted, stay encrypted and internal storage is safe. Change kernels and internal storage is wiped...
kwdan said:
Yes.. That makes since to me. It's just that there is a "Sprint radio.Zip" floating around that you have to flash if you lose signal. That would be a "radio" so how does it get wiped when flashing? I was going to try the "Pure Shamu" rom. That's what brought all the questions.
Ok.. Seems like any kernel change will wipe internal storage
If I'm encrypted, stay encrypted and internal storage is safe. Change kernels and internal storage is wiped...
Click to expand...
Click to collapse
I haven't had to deal with the Sprint radio issues because I'm on Verizon. But i believe that is a patch to the rom to make sprint data work.
Changing kernels does not automatically wipe internal storage. The kernels are "decryptable", meaning if you format data, you will be decrypted. If you do not format data, you will be as you were, encrypted. If you were already decrypted, you will still be decrypted.
I believe there was one rom or kernel , don't remember which, that automatically decrypted, but I know that was stated in their OP.
Sent from my SinLess Shamu
9wire said:
And there's no way to decrypt without data wipe?
Click to expand...
Click to collapse
I dont think its possible now.
I had to factory reset after formatting data, but after that all is smooth.

[Q] Twrp flashing order check?

I'm trying to flash chroma rom onto phone with leankernel/hells core and verizon 5.1 radio. May someone confirm this is the correct order? I'm currently on latest chroma with franco kernel. (i don't like dirty flashing )
1. Wipe everything but internal sd
2. Flash latest chroma
3. Flash latest leankernel/hellscore
4. Flash Gapps
5. Flash verizon radio 5.1
Should i also include Supersu in the steps?
Also, if my internal memory is getting a bit cluttered from apps and other random stuff, is there a way I can reset my phone to a rooted, bootloader unlocked, unencrypted state without doing a full reset to stock then doing everything over?
Raymondlikesroot said:
I'm trying to flash chroma rom onto phone with leankernel and verizon 5.1 radio. May someone confirm this is the correct order? I'm currently on latest chroma with franco kernel. (i don't like dirty flashing )
1. Wipe everything but internal sd
2. Flash latest chroma
3. Flash latest leankernel
4. Flash Gapps
5. Flash verizon radio 5.1
Should i also include Supersu in the steps?
Also, if my internal memory is getting a bit cluttered from apps and other random stuff, is there a way I can reset my phone to a rooted, bootloader unlocked, unencrypted state without doing a full reset to stock then doing everything over?
Click to expand...
Click to collapse
first off, why would you have to go back to stock???
secondly, the radio can be flashed at any time, no order involved in that.
thirdly, when you wipe data(everything but the SD storage), thats a factory reset. so, wipe data/system, flash chroma, flash the gapps, flash SuperSU(for root), then flash your kernel and reboot.
As long as you flash ROM first, doesn't matter about the order
simms22 said:
first off, why would you have to go back to stock???
secondly, the radio can be flashed at any time, no order involved in that.
thirdly, when you wipe data(everything but the SD storage), thats a factory reset. so, wipe data/system, flash chroma, flash the gapps, flash SuperSU(for root), then flash your kernel and reboot.
Click to expand...
Click to collapse
Sorry, a clean sd card is simply one of those weird things I like(It might be ocd or something xD). When i had my s4, i would do a full reset to stock every time I flashed a rom because I didn't want any residual files left over. That being said, is there any simpler process to reset or clean the internal memory between flashing roms besides stock reset? What I'm talking about is some way to set or "reset" the nexus 6 to a unlocked, rooted, unencrypted, and twrped state but otherwise stock.
Raymondlikesroot said:
Sorry, a clean sd card is simply one of those weird things I like(It might be ocd or something xD). When i had my s4, i would do a full reset to stock every time I flashed a rom because I didn't want any residual files left over. That being said, is there any simpler process to reset or clean the internal memory between flashing roms besides stock reset? What I'm talking about is some way to set or "reset" the nexus 6 to a unlocked, rooted, unencrypted, and twrped state but otherwise stock.
Click to expand...
Click to collapse
Make a backup in TWRP of your device when it's in that state. Then flash that backup whenever you want to return to that state.
Raymondlikesroot said:
Sorry, a clean sd card is simply one of those weird things I like(It might be ocd or something xD). When i had my s4, i would do a full reset to stock every time I flashed a rom because I didn't want any residual files left over. That being said, is there any simpler process to reset or clean the internal memory between flashing roms besides stock reset? What I'm talking about is some way to set or "reset" the nexus 6 to a unlocked, rooted, unencrypted, and twrped state but otherwise stock.
Click to expand...
Click to collapse
just do a full wipe in twrp, itll clean out your storage. but move all the files that you want to save to your computer or they will be gone.
Evolution_Tech said:
Make a backup in TWRP of your device when it's in that state. Then flash that backup whenever you want to return to that state.
Click to expand...
Click to collapse
Wouldnt I have to full wipe beforehand?
simms22 said:
just do a full wipe in twrp, itll clean out your storage. but move all the files that you want to save to your computer or they will be gone.
Click to expand...
Click to collapse
After I full wipe, I can use mtp to transfer the rom and gapps in twrp right? Or do I have to use adb ?
Raymondlikesroot said:
After I full wipe, I can use mtp to transfer the rom and gapps in twrp right? Or do I have to use adb ?
Click to expand...
Click to collapse
Either
danarama said:
Either
Click to expand...
Click to collapse
Thanks! I would give you a thanks but I'm limited to 8 per day lol
Raymondlikesroot said:
Thanks! I would give you a thanks but I'm limited to 8 per day lol
Click to expand...
Click to collapse
No worries. I'm not bothered about them. Really they're to be used in development threads to prevent flooding them with useless "thanks".posts

Most stable ROM for Galaxy S5 mini

Hi
I'm searching for a custom ROM for my mom's gamaxy s5 mini. Touchwize is very buggy on her devices, so i'm looking for a stable ROM.
I'm not specific looking for a ROM that has a lot of features but they are always welcome.
What ROM do you guys suggest?
Thanks
stock rom with custom kernel
Dev!n said:
stock rom with custom kernel
Click to expand...
Click to collapse
+1
Custom roms for the S5 Mini are still on BETA stage. They have some bugs, an higher battery drain and some features are unsopported. Stock rom with a custom kernel and ROOT os the best way. Also, don't forget to format the Data and Cache partitions into the F2FS filesystem.
Andrea224 said:
+1
Custom roms for the S5 Mini are still on BETA stage. They have some bugs, an higher battery drain and some features are unsopported. Stock rom with a custom kernel and ROOT os the best way. Also, don't forget to format the Data and Cache partitions into the F2FS filesystem.
Click to expand...
Click to collapse
What kernel do you suggest?
And how do I format data and cache partition into F2FS filesystem? And before I do that, in what filesystem are they formated originally?
titan1655 said:
What kernel do you suggest?
And how do I format data and cache partition into F2FS filesystem? And before I do that, in what filesystem are they formated originally?
Click to expand...
Click to collapse
I suggest this kernel: http://forum.xda-developers.com/galaxy-s5-mini/orig-development/kernel-custom-kernel-t3130662
You can format the two partitions into the TWRP 3.0.0 recovery. Normally, on every phone, they are formatted into the ext4 filesystem (you can also read it before formatting)
Andrea224 said:
I suggest this kernel: http://forum.xda-developers.com/galaxy-s5-mini/orig-development/kernel-custom-kernel-t3130662
You can format the two partitions into the TWRP 3.0.0 recovery. Normally, on every phone, they are formatted into the ext4 filesystem (you can also read it before formatting)
Click to expand...
Click to collapse
Last question.
Why only format the Data and Cache partitions into the F2FS filesystem? And not the other partitions?
titan1655 said:
Last question.
Why only format the Data and Cache partitions into the F2FS filesystem? And not the other partitions?
Click to expand...
Click to collapse
Because only these two partitions have this possibility.
What custom kernel would you recommend for G800H? And what is the advantage of formatting the partitions into F2FS?
morcio said:
And what is the advantage of formatting the partitions into F2FS?
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/F2FS should tell you why you want this (It's a FS designed especially for mobile devices that use flash memory for storage).
Sm-g800h or sm-g800f???
Info: model SM-G800F, baseband G800FXXU1BPC4
I had the same question as TS and listened to the advice of @Andrea224 by flashing the custom kernel mentioned in this thread.
I started with the stock 5.1.1 ROM.
- First I flashed the kernel using Odin3.
- Then I flashed TWRP 3.0.0 recovery using Odin3.
- Then I re-formatted \data and \cache F2FS booting in TWRP.
All went well.
When I boot in Recovery I got the question to mount read/write and the warning about not able to receive OTA updates.
When I exit Recovery I get the question to install SuperSU.
Coming from a long line of HTC devices the above questions are new to me.
What do they mean? I once did choose to install SuperSU. Is my phone rooted now? Or should I still flash the CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5 file?
Also in TW I get the questions about not having an original software installed. Is this about Knox? How can I disable this?
Concluded: Have I done all the correct steps to have a stable system?
bakmanhans said:
Info: model SM-G800F, baseband G800FXXU1BPC4
I had the same question as TS and listened to the advice of @Andrea224 by flashing the custom kernel mentioned in this thread.
I started with the stock 5.1.1 ROM.
- First I flashed the kernel using Odin3.
- Then I flashed TWRP 3.0.0 recovery using Odin3.
- Then I re-formatted \data and \cache F2FS booting in TWRP.
All went well.
When I boot in Recovery I got the question to mount read/write and the warning about not able to receive OTA updates.
When I exit Recovery I get the question to install SuperSU.
Coming from a long line of HTC devices the above questions are new to me.
What do they mean? I once did choose to install SuperSU. Is my phone rooted now? Or should I still flash the CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5 file?
Also in TW I get the questions about not having an original software installed. Is this about Knox? How can I disable this?
Concluded: Have I done all the correct steps to have a stable system?
Click to expand...
Click to collapse
Now, I will explain to you how to get it work properly:
- Boot your phone in download mode and flash the latest update of the TouchWiz for your country with Odin. (If you are on CM13, into TWRP: 1- Do a backup of your data; 2- In Wipe -> Advanced Wipe select Dalvik, Cache, System, Data and wipe these partitions; then select Cache and Data and format both to ext4; 3- After all, flash TWwith Odin)
- Boot your phone in download mode and flash SuperSU with CF-Auto-root.
- Boot your phone in download mode and flash the TWRP 3.0.0 with Odin.
- When you are into recovery: 1- Tick the option for never show this message on every reboot into recovery and then swipe to allow modification; 2- Do a backup of your Data; 3- Flash the custom kernel; 4- Format Data and Cache to F2FS; 5- Restore the backup of your Data; 6- Reboot the phone and DO NOT allow to install SuperSU if it ask to you. (If after the reboot, the phone says that your device isn't rooted, flash another time CF-Auto-root)
- With the kernel and root installed, now is time to delete some apps: 1- Download and install RootExplorer; 2- Go into "system" -> search SecurityLogAgent.apk into the folder called "app" or "priv-app" (I don't remember in which folder is it) and delete it. Naturally, you have to grant root access to the app.
Now you have a good and stable rom. Also, if you want to debloat the stock rom, you can use this ZIP -> http://forum.xda-developers.com/galaxy-s5/development/mod-urwsoft-barebone-cleaner-t3043479 (this is for the S5, but it's compatible with the S5 Mini) or you can delete manually some apps through RootExplorer. If you have some problems, contacts me.
With Root Explorer you mean the payed version?
Verstuurd vanaf mijn SM-G800F met Tapatalk
bakmanhans said:
With Root Explorer you mean the payed version?
Verstuurd vanaf mijn SM-G800F met Tapatalk
Click to expand...
Click to collapse
Yes, just search on Google the apk.
Did all the steps above except for the URWsoft BareBone Cleaner. I had to reflash both Autoroot and TWRP through Odin twice. Weird. By removing SecurityLogAgent.apk I was finally able to enjoy my device without being warned all the time. Nice!
I have noticed that after every reboot my Wifi connection settings are lost. Anybody else experienced this?
bakmanhans said:
Did all the steps above except for the URWsoft BareBone Cleaner. I had to reflash both Autoroot and TWRP through Odin twice. Weird. By removing SecurityLogAgent.apk I was finally able to enjoy my device without being warned all the time. Nice!
I have noticed that after every reboot my Wifi connection settings are lost. Anybody else experienced this?
Click to expand...
Click to collapse
It's a bug, it appears when you flash a custom kernel. To fix it, go here -> http://forum.xda-developers.com/showpost.php?p=65568464&postcount=10
I'm sorry for restoring such an old thread but my question is the same.
Which is the best rom for G800F?
Custom roms I see that have still many known bugs
Stock rom ok, but how about debloating it? I haven't found a debloated version, nor a guide/script to debloat it automatically.
And what about the kernel? Which is the best kernel for stock rom? And for custom roms?
Thank you
Alefello said:
Stock rom ok, but how about debloating it? I haven't found a debloated version, nor a guide/script to debloat it automatically.
Click to expand...
Click to collapse
I use Root Package Disabler from play store, it has in-built bloatware list that you can disable/freeze.
Very convenient and effective.
How about Resurrection Remix MM? It's marked as stable and it seems that everything is working in the changelog and comments.
Or LOS 13 too seems everything is working (but I can't find confirmation in comments)
I'm using this one
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-resurrection-remix-n-5-8-2-t3562523
It's 7.1.2 RR. It's perfection. I'm not even kidding I've used it for 3 months and it's stable as hell. On top of that it has million features that come with RR roms. Battery life is really good too.

upgrading to Nougat, trouble replacing old kernel

Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip
jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Try reverting to stock
Install stock firmware using adb
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.
Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here
Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.

Categories

Resources