Develop Bugs

[Q] Reset to Stock ICS/Unroot/etc. (Boot Issues)

So I've found a lot of threads on here giving me great info on how to handle various situations, but given what I'm looking to do with my phone, I'm not sure what order to do everything in and what tools are best. Currently, my T989 is on ICS 4.0.3 (UVLE1), rooted, with CWM installed. When I originally upgraded to ICS, something got messed up that caused my phone to hang on "Goodbye" anytime I try to turn it off/reboot. I've read that Darkside's Cache Wipe can fix that issue, but basically I'd like to wipe the device, start fresh with a stock build and get everything right from the start. I will likely root it again later, but I'd at least like to get it reset to stock and have everything working correctly first.
What I'm looking to do:
Unroot and uninstall CWM
Wipe the phone clean (all data, cache, partitions, etc.)
Clear the phone entirely back to stock OS/stock recovery/stock everything
Upgrade to the latest stock OS (if necessary)
I'd like to do all this while also fixing whatever caused the hang while shutting down/rebooting. I'd also like to use a stock OS image from Kies instead of downloading one from other places if at all possible (I'm a tad paranoid/OCD when it comes to stuff like that). I've seen two Darkside tools-- cache wipe and super wipe, and I'm not sure if I need one or both of them to help with clearing off the device/fixing my reboot issue.
So with all that in mind, what's my best route to take? I'm just looking for what tools to use and in what order, there are enough great guides on here on how to use the various tools that I can figure out the rest from those. In other words, "Use X to clear blah, uninstall Y while choosing yadda, install Z" etc. I hope that's not too tall of an order Thanks to all for your help!

Edit Oct 17, 2014 - Encrypt your device/phone with custom ROM

Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
If you don't agree ... stop reading and move on...
Background: Our phone has access to so much personal information that its scary if it fell into wrong hands. The only way to fix this is to encrypt phone. I did lot of research and here is a working solution that works for me - try at your risk.
Download Links:
a) Tested with ROM Stock 4.4.4 NH7 Galaxy S4 M919/Jfltetmo by @ShinySide
b) Tested with ROM |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
c) stock recovery AT&T S4 works with M919
d) Philz/CWM custom recovery
Encrypting with custom rom
1) Assume you are on custom recovery. - Backup everything first. Create a nandroid backup
2) Do a full wipe and install one of the two roms linked above (I have tested with few other roms ... none worked). Start the phone and set it up the way you want. Install all apps etc.
3) ODIN Stock recovery. See #c under download above. Its AT&T stock recovery but works for me. You need to know how to ODIN - find out. Doing this wrong will permanently damage your phone
4) Start your phone and turn on encryption. You will need to set lock type = password and will need to connect to charger and have 80% charge.
- Phone will do blank and stay blank for 20-30 minutes. Do not do anything. Encryption is happening behind the scenes.
- You might have to do this twice or thrice if it did not encrypt first time. For me the phone went blank first time and after 25 minutes it restarted but device was not encrypted. I redid the same steps and worked second time.
- If you interrupt the encryption process (battery pull or power up) you will see error message (encryption failed, reset device)
5) If all goes well you now have a password protected encrypted phone with custom rom!!! Check in Settings -> Security
6) You may install custom recovery ... but I don't see the point because you will need stock recovery to decrypt
To install another ROM
1) Reboot into stock recovery, then wipe data and cache (this removes encryption).
2) install your recovery of choice and install ROM using recovery. Philz/CWM
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
Tronicus said:
How to Flash a rom on an encrypted Android phone (specifically this one, the I9505 SGH-I337).
The Problem: Once encrypted, you can't decrypt it easily. When encrypting the phone android will tell you you can only decrypt it using a factory reset. Naturally you assume it's talking about the "Factory Data Reset" option found in Settings --> Backup and Reset. But noooo, Android is lying through its ****ing teeth. Then you'll assume you have to wipe everything from your custom recovery mod (CWM, TWRP, or one of those). Wrong again! You'll get beautiful "can't mount /data" messages and more bull****. I read about a workaround that required installing the new rom using ADB, but I had ingeniously disabled USB debugging prior to wiping everything, so I only got so far with that option (plus it's tediously long if you haven't installed all the necessary software already and don't feel like bricking your phone because you made a typo in the command line). So, apparently the only other way to really format that partition free of its encryption is to use a stock recovery. So:
Short Version for Godlike users who know automatically how to do all this **** without any help (mimicking how most help posts are finely detailed on this site): Flash stock recovery, wipe everything, flash your custom recovery and install your new rom.
Long version for us mortals who don't know everything and haven't already downloaded already every single bit of software on earth:
Backup all the stuff you want to save. This process will truly wipe EVERYTHING. You can do it manually, or you can use an app like Titanium Backup Pro to help you (find it on Google Play Store). Here's a nice guide which recommends what to restore and what not to restore: http://forum.xda-developers.com/showthread.php?t=1480343
Flash the stock recovery using Odin. You can download a stock recovery from here: http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3 It's the link called "I337MK2stockrecovery.tar.md5" In case you don't know how to flash it with Odin, this short guide will help: http://forum.xda-developers.com/showthread.php?t=1506697
In step 6 replace "recovery.tar.md5" with the stock recovery you downloaded.
Wipe everything from the Stock recovery console. This little ****er will **** up the encryption all those sissies couldn't touch. You're welcome. You boot into recovery mode from a turned off phone by pressing simultaneously the volume up key + the home key + the power key until you see blue text appearing in the top left corner of your screen.
Reinstall your custom recovery. In my case I had installed the rom BEFORE flashing in the stock recovery (apparently it works, you just can't boot because of the encryption), so I was able to boot into the new rom before I returned to my custom recovery. Weird. Anyways, I recommend CWM. You can pick it up from this link: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
For some weird reason they call the I337 version the "jflte" version. It's bonkers. Click there, and download the latest version that ends with .tar.md5. This version is upgradable via Odin, which we already used. Use the same instructions used as when you upgraded the stock recovery rom.
Boot into your recovery mod and flash your rom like you usually do.
A word about TWRP: it cost me many hours of work and I don't recommend it. Its website is outdated, and recommends using GooManager (which is no longer mantained) and doesn't work anymore for this. GooManager suggests using a new, different app, which doesn't have the option of installing TWRP. Then I tried using their TWRP Manager app from play store and the image file wouldn't download. Then I tried manually selecting the image file in TWRP manager that I downloaded from their site for use via the ADB method, and it bricked my phone... twice (using two different methods the app sugested). I tried so much because in theory TWRP has the ability to decrypt android's 4.4 encryption, but after looking at their github site I noticed it was filled with people's reports (including people with the S4) on how it wouldn't work decrypting squat. So I gave up, and installed CWM in 30 seconds.
Click to expand...
Click to collapse
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk

cnewsgrp said:
One of the things I needed was the ability to encrypt my phone (device only not external SD) for security purpose. Our phones today gives access to lot of information that I would rather not fall in wrong hands. I did lot of research and here is a working solution.
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
The quote looks long however it is really very simple. To install another ROM
- Install and reboot into stock recovery, then wipe data and cache (this removes encryption).
- Then install your recovery of choice and install ROM using recovery. Philz/CWM
This has been tested working on |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
This did NOT work on a Touchwiz ROM by same developer
I have not tested any other ROM
Click to expand...
Click to collapse
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app

lordcheeto03 said:
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tested stock recovery on M919 .. it works

Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...

p-hil said:
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
Click to expand...
Click to collapse
Yeah Encryption does not seem to work on TWZ roms. I tried on G Eye without luck.

I have updated op. Please check

Encryption will slow down your phone quite a bit. More battery usage + more CPU usage + slower phone = not worth it unless you've got some very private stuff you don't want being shared. Otherwise, 3rd party apps that lock a lot of files, can encrypt certain files, and hide others will do the trick perfectly well.'
Not trying to bash fully encrypting your phone, but I've tried it before and although I am very pro privacy, I had to eventually take it off due to all the extra hassle it created.

Don't know about slowing down. I am not seeing it. I feel differently about security.

[Q] Loading ROM's

Good Morning,
I've searched through the forums and so far haven't had any luck. I apologize if this is a topic that's been covered to death, which it likely has, but I haven't found a solution to my particular problem.
Galaxy Tab Pro 10.1.
I was having problems with TouchWiz crashing, usually 2 to 3 times per day. Sometimes it would lock up the unit, requiring me to reboot. Sometimes it would just come back after 5 or so minutes. Whatever the case, I decided, since I was already interested, that I would try to root the device, clear up some memory, maybe even flash a new ROM to take care of the issue.
First, I successfully rooted the device, no problem. Surprisingly easy, actually, following steps from this website.
I loaded SuperSU, Titanium Backup, Greenify - but still had (more rare) instances of TouchWiz crashing, and even the entire unit rebooting itself occasionally. So, I decided to take a stab at Cyanogenmod 11.
After attempting to load Cyanogenmod using Heimdall and Odin, and having issues I'll add, I finally realized that (theoretically) I could just use ROM Manager to load the file. Cool! So I loaded the zip file for CM11 onto the top level of my SD Card, created a recovery, and attempted to load the new ROM. The first problem I had was that the unit wouldn't just load the ROM like I expected, but it put me into recovery mode. I suspect that's not right, but I attempted to go ahead and use the menu picks to load the ROM anyway. I wiped data/factory reset, them wiped cache partition. Then, I selected "apply update from external storage". I selected the zip file for CM11, which was right where I left it, hit select, and had the following problem.
I got the following errors, two times, in red text (with other yellow text messages surrounding);
E:footer is wrong
E:signature verification failed
So...what do I need to do here, folks? Worst case scenario, obviously, I just keep using TouchWiz, as I haven't managed to brick my device yet, and I would still be able to utilize root access apps. But I have to be close, aren't I? Does anyone have the patience to help out a guy who only knows enough to be dangerous?

You need to use custom recovery to flash custom ROMs. It sounds like you are trying to use stock recovery.

redpoint73 said:
You need to use custom recovery to flash custom ROMs. It sounds like you are trying to use stock recovery.
Click to expand...
Click to collapse
Thanks for the reply. I'm not sure what I did wrong, but I decided to give TWRP recovery a shot, and was getting an error on the CM11 zip file. I re-copied over the zip file, tried again, and that did the trick. I guess I either had a bad zip file, the wrong recovery, or both.
Thanks!
Robb

Sometimes I had problems flashing zips from external storage, appeared as corrupted, never a problem when zip was in internal storage . Did you try that?

thdervenis said:
Sometimes I had problems flashing zips from external storage, appeared as corrupted, never a problem when zip was in internal storage . Did you try that?
Click to expand...
Click to collapse
No, I did not try that, as simply recopying the zip file onto the SD card did the trick.
I spent all evening playing with the settings, trying out themes, setting up my apps - and my unit didn't crash one time. Pretty slick!
Now I just need to learn how to use Titanium Backup to store settings so I can play with different ROM's.

[Solved] Issues activating SGS3 SPH-L710 on Sprint with Custom ROM + lots of problems

Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.

This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.

I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.

Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!

afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good

Recover, Root disappearing, WiFi breaking.

Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.

I have found that to get TWRP to stick I have to flash the zip and whatever else I'm flashing, then boot into my rom, then boot back into fastboot TWRP and flash the TWRP zip again, then boot back into the rom.
Root is tricky on this phone. Nobody can really answer what's going on there without knowing what month bootloader you are using, what app and what version of the app you are trying to use to root.
The other problems really sound Rom related. If you want to go from a truly fresh start with no chance of any corruption on either partition you might want to run flash-all.bat of the Google factory image separately to partition a and then to partition b. That cleared up problems for me in the past but I'm not sure why.
You might also consider running stock and seeing if the WiFi or status bar problems persist.

xxxtncxxx said:
Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.
Click to expand...
Click to collapse
This has been a real challenge with this phone (but I'm enjoying it). Anyway, the way I got a good stable set up is flashing the factory image to both slots (a/b), then adb/fastboot to twrp.img and flash ROM, then boot up. Then again the twrp.img and flash the twrp.zip and boot up. Then do the root and boot up , then go back and do the kernel (since it's EX and I want the gestures, I boot it up rooted before I flash EX). This works for me although I'm using Pure Nexus ROM. Hope this helps you, looks similar to what was posted by jhs39.