Develop Bugs

are you rooted already ? (OPPO N1)

hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?

nowy57 said:
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
Click to expand...
Click to collapse
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.

sorry mate
it doesnt work to me
I have tried two times
as you wrote

Harfainx said:
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
Click to expand...
Click to collapse
I have the same issue too. SuperSU installed 3 times. Did the full unroot like you said and reran the install after wiping both the cache. Still no root access.

I think that magic which found us oppo+CM team is missunderstand couse when I first time heard about cooperation this two companies I was so much happy .
by now when I have it I know that maybe couple of hundred is sold this phones and nobody cares about support it .
1.ROM straight from CM/OPPO site doesnt install propely via TWRP( without ingeration for user-script)
2.no root acces yet
this is sad true .
I v got note3 and I see more future with this phone
AOSP/CM is on a way - a lot of android entusiasts is working for free of charge about better and better ROMs
I am dissapointed - no offens to anybody

I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
it is not installed under CM ROM

It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
The exploit method was apparently patched in the official CM release. That exploit doesn't work.

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
i am really confused couse I am pretty sure I am doing good as you said but no succes .

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
If TWRP doesn't work properly how did you root? With the stock recovery?

it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
You can indeed install straight from stock recovery. I did it last night. You have to use the official rom for the n1. Works nicely. I also had root working on cm. I flashed cm from stock recovery then used fastboot to install twrp. After twrp i flashed supersu zip. After i did the fix root or remove or whatever it is in the ap, reinstalled and tested it in titanium. Said i did have access but then went back to coloros to try and fix my mediascanner issue.
Sent from my N1 using XDA Premium 4 mobile app

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
I mean straight flash CM on the stock recovery, not on TWRP. You would have to be on the stock recovery for it to work straight from the CM download. On the stock recovery though, you will not be able to flash SuperSU on it. I do not believe that Omni can be flashed from there either, but I could be wrong (I haven't tried it).
There's a thread in the dev section that has the stock recovery hosted there. You can always fastboot flash back to that at any time.

Okay, I decided to install Cyanogenmod for the heck of it.
I already had TWRP 2.6.3.1 installed,
I downloaded and modified cm-10.2-WPPH50O-n1-signed.zip as per this page's instructions:
http://forum.xda-developers.com/showthread.php?t=2553165
I also downloaded supersu (current version is 1.86).
I entered TWRP and installed it, following that page's instructions.
After the install, I selected 'reboot'.
When I selected 'reboot', It prompted me with:
install superSU now? this will root your device.
I said no, and then rebooted back into TWRP.
Now back in TWRP, I install SUPERSU.
Now reboot again.
Now in CM.
Now run SuperSU, select 'settings', and unclick 'Respect CM root settings".
Now root works for me.
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
2) If, after the CM install, you answer 'install SuperSU' with YES", then it installs SuperSU, and reboots.
When you go back in, and run SuperSU, it says "gee, you aren't rooted, install SuperSU?"
If you answer THAT with yes, then it downloads some version of SuperSU, reboots into twrp, and installs it.
So it's kinda pointless answering YES in the first place, imho.

Are you serious right now?! I was worried unchecking Respect CM root setting would mess things up. But now I have root access. OMG... I unchecked it and it works! ^_^

57 43235953
ChodTheWacko said:
...
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
...
Click to expand...
Click to collapse
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.

hammerandtongs said:
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
Click to expand...
Click to collapse
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank

ChodTheWacko said:
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
Click to expand...
Click to collapse
WOW...so it literally disappeared as I was composing this message.
Cyanogenmod "signed" installed with the oppo bootloader (not rooted as supersu doesn't install successfully through bootloader etc).
Some kind of UI refresh after I changed some home screen settings?
It was persistent through 5-10x reboots and now is gone.
Obviously a glitch since I don't have su and I'm not truly rooted but it WAS there :\
I'd say its a bug to be filed if you are rooted and it's not available.

ColorOS Update 1.2.5i has completely fixed the screen over-sensitivity issues

Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk

It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7

themsubtle said:
It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7
Click to expand...
Click to collapse
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk

rajitsingh said:
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
My root is intact but everything else back to default factory settings and as titanium or the built in backup app don't work I now have to start again, i am really not happy would quite happily sell this phone now

Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!

themsubtle said:
Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!
Click to expand...
Click to collapse
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:

blessingme said:
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:
Click to expand...
Click to collapse
It must have been the update, because I have haven't changed anything else for it to happen, the update has fixed the screen sensitivity too which is good,but I am getting a lot of force closes, from settings app, backup and restore app, and few other system apps.

No issues
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.

jebulol said:
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.
Click to expand...
Click to collapse
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs

No issues here.
Every OTA update has been fine and dandy. I still have root since 1.2.1.

you're not alone.
themsubtle said:
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs
Click to expand...
Click to collapse
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?

scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk

rajitsingh said:
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
hmmm, then I'm not sure.
Her x9006 (Int-EU) is less than a week old and had nothing significant done except OTA (to 1.2.4i) then root before the 1.2.5i OTA was released.

scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version

themsubtle said:
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version
Click to expand...
Click to collapse
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?

scar200 said:
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?
Click to expand...
Click to collapse
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working

themsubtle said:
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
Click to expand...
Click to collapse
Ok, I did multiple tests, and am listing the 2 important ones.
Test 1
1. I reflashed back to 1.2.1i then OTA-ed to 1.2.2i (the next OTA it detected was1.2.5i), flashed TWRP and Update SuperSU 2.02 (to get root) then flashed the x9077-official-recovery-mod.
2. Installed some apps, changed some settings then OTA-ed to 1.2.5i - everything was deleted and I lost root after the OTA - essentially I had to go through the new phone start up menu (language, area, wifi, etc.).
*Initial problem replicated*.
Test 2
I did the exact same procedure again as in Test 1 step 1, but instead of the mod recovery I flashed the Stock Recovery for Find 7/7a (from the thread of the same name in the oppo forums, I used version 0712).
Then I again installed the same apps, changed the same settings and OTA-ed to 1.2.5i.
All the apps and settings remained but the phone lost root.
*Only significant delta between the 2 cases was the recovery version.*
Conclusion
The problem in my girl's case was the x9077-official-recovery-mod.img recovery. OTA-ing using that recovery caused her phone to go through a factory reset. This problem isn't present if the stock recovery direct from Oppo was used. Lesson learnt.
Hope this helps someone. Cheers.

themsubtle said:
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working
Click to expand...
Click to collapse
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.

scar200 said:
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.
Click to expand...
Click to collapse
I can confirm that switching to CWM's Superuser works. When I updated to 1.2.5i I wasn't able to restore my data for ANY of my apps via Rom Toolbox. I decided to replace the Superuser app caused I remembered that worked for me once with a custom rom on the HTC Amaze, and sure enough now my apps' data has been restored. Success. :good:

rajitsingh said:
Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
Hi, regarding the screen touch oversensitivity issue, just one question - are you using any sort of screen protector?
I have a tempered glass screen protector. I tried everything from 1.2.4i to 2.0.1i beta and the screen problem is there. Hearing good news about this 1.2.5i update and need somebody to confirm it works.

How I Installed An Edge ROM and Tricked My Phone Out

I have been asked by several people, on the forums and via PM. I thought that I would offer a step-by-step guide.
Will This Trip Knox? Yes, it will. Installing a custom recovery such as TWRP will definitely trip Knox. From what I have read installing a ROM, even through FlashFire, will trip Knox, as will flashing a kernel.
You Don't Seem To Care About Knox That is correct. To this point the only downside is that I won't be able to use Samsung Pay and I don't plan on that anyway. BUT.....if you do care and Knox matters, stop reading now and stick with stock.
I will also recommend that you grab ODIN and a stock TAR file for your phone. You can always find the latest firmware at SamMobile, but will need to create an account and free downloads are speed capped. It will be SLOOOOW. But you will get a zip with the file that you need inside. Good to have in case of accident. Here is where I got mine: http://www.sammobile.com/firmwares/download/47474/G920PVPU1AOE2_G920PSPT1AOE2_SPR/
That said.....assume that you have a rooted S6. Install TWRP Manager from the Play store, ignore anything it says about an SD card and click on "Install TWRP." The version that you are looking for is "zerofltespr.img." You can also download that from here https://twrp.me/devices/samsunggalaxys6sprint.html and use Flashfire to install. Reboot into recovery (see http://www.androidexplained.com/galaxy-s6-recovery-mode/ for an explanation) and make sure that TWRP is installed. If TWRP doesn't come up, make sure that you used the correct file and try again.) Now you are ready to begin.
1) The ROM that I used is the SAC23 ROM from here: http://forum.xda-developers.com/spr...ment/sac23ram9200srintdeoxedmoddedv1-t3107342 Download that and copy to your phone. You should also grab the "Recent apps fix long press on home" zip file from the bottom of that post.
2) You will also NEED (!!!!!) a kernel that is designed for the S6, otherwise you will bork your phone. I use (and recommend) the Ktoonsez kernel located here: http://forum.xda-developers.com/spr...elopment/kernel-kt-sgs6-ocv-ktweaker-t3093009 Grab that and copy to your phone.
3) For fingerprint recognition and private mode, you will need the Aroma installer from here: http://forum.xda-developers.com/showpost.php?p=60112854&postcount=2 If you use the Aroma installer (and I don't so I have no experience) be sure that those are the only two things that you install.
UPDATE 7/1/2015 Just had a report that fingerprint is working with this kernel: http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-kernel-t3146127
Anyone interested should read all posts for that kernel before flashing.
Once you have those files on your phone, you are ready to begin.
Return to recovery mode. Before you do anything else....Click on "Backup." Accept the default settings and let it do its thing. I always name my backups....calling this Stock is probably a good idea. Once that is done, if you break things, you can return to this.
Okay, now go to Wipe. The old-timers will disagree, but most of the time the default "Factory Reset" is all that you need. If you are paranoid (and who isn't?) after this you can go to Advanced and choose Dalvik Cache, Cache, Data and System. But I rarely do this anymore. Complete guide for using TWRP is here: http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Now go back to the main screen and select Install. You can select multiple zips. Flash the ROM, the kernel and that Recent Apps zip file. Be sure to set the kernel to flash after the ROM. Or you can flash them one at a time.
Once done, reboot phone and if all went well, you will see a new boot animation. First boot will take a while, let her go.
You should have a clean build so remember that you will need to reset Developers options, security (for allow Unknown sources) and other stuff.
With the Ktoonsez kernel, you will have the KTweaker app, very useful. If it doesn't install for you (and it didn't for me) the APK is located inside the zip file that you downloaded at S6\KT-SGS6-LP5.0-TW-G920P-05.28.2015.zip\system\app\ Extract that and install. I use downloaded Profiles a lot.
If all is well, but the fingerprint and private mode settings are things that you use, go back into Recovery and select ONLY those two items. I'll state again, I don't use them, have never flashed the Aroma installer and can't offer any help. I have seen that they work for some people, not for others..../me shrugs. I can't help with that.
I also use the Wicked One Theme from @dazedandconfused who is a master. See http://forum.xda-developers.com/spr...ps/theme-wicked-one-theme-s6-s6-edge-t3129822 for the theme and instructions. Be sure to follow the instructions about having the Urban theme from the Theme Store installed first. But this theme makes me very happy.
That is everything that I know....which goes to show how little I know!
EDIT: Missed a step....DOH!.... if you are using TWRP you should flash the zip file found here to address the Deep Sleep issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Happy ROM-ing.

Everything works except I cannot text at all

ScottBroker said:
Everything works except I cannot text at all
Click to expand...
Click to collapse
Are you using the stock messaging app or something else? Did you use the Aroma installer and, if so, was messaging working before?

koop1955 said:
Are you using the stock messaging app or something else? Did you use the Aroma installer and, if so, was messaging working before?
Click to expand...
Click to collapse
I use stock, and I tiried another as well. I did not use the aroma installer
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
ScottBroker said:
I use stock, and I tiried another as well. I did not use the aroma installer
Click to expand...
Click to collapse
I updated the PRL, rebooted and now it works, Thanks

ScottBroker said:
I use stock, and I tiried another as well. I did not use the aroma installer
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
I updated the PRL, rebooted and now it works, Thanks
Click to expand...
Click to collapse
Ah, good to know and thanks for posting the solution here.
Cheers.

koop1955 said:
Ah, good to know and thanks for posting the solution here.
Cheers.
Click to expand...
Click to collapse
Thanks for posting an alternative to the non existant development for the S6.

nice work on this Koop!!!!! I'm running Sacs rom and KToonz kernel smooth and trouble free, privacy mode and finger print scanner work 100%
sent from my S6 using tapatalk

Here's a question. Hope do you use the stock battery icon on Sac's ROM and not one of those gross 3minit or whatever ones? They're all hideous.

twiztid907 said:
Here's a question. Hope do you use the stock battery icon on Sac's ROM and not one of those gross 3minit or whatever ones? They're all hideous.
Click to expand...
Click to collapse
I have to say that it is really popular mod, but not to my taste either. Here is what I run for battery:
GSam Battery Monitor (also lets you customize the battery icon, but I don't)
Greenify and Wakelock Detector
With Ktoonsez, I have the Ktweaker installed. Click on the 3 dots upper left. Scroll down to KTweaker Shop Profiles and then pick from Conservative, Balanced or Performance (or grab some of each.) I am using the Conservative Profile "Dead By April." I love that name!
Average Per Complete Charge (now this is with light usage) 2 days 0 hours, with screen on 1 hour 41 minutes.
Not expecting to get the same battery life when I am traveling or with heavy usage, but that is still pretty remarkable.

koop1955 said:
With Ktoonsez, I have the Ktweaker installed. Click on the 3 dots upper left. Scroll down to KTweaker Shop Profiles and then pick from Conservative, Balanced or Performance (or grab some of each.) I am using the Conservative Profile "Dead By April." I love that name.
Click to expand...
Click to collapse
while I'll admit I haven't explored the KToonz settings much, I was wondering how you accessed profiles, this is good info, I'm trying out dead by April as I type this out lol
sent from my S6 using tapatalk

Missed a step
I edited the original post, but let me add this.
If you are running TWRP, you should flash the zip file found here to address the "No Deep Sleep" issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56

Hello, thank you for this great write-up! I PM'ed you the other day, and you helped me get my phone flashed and all.
However, I am still having issues with the Fingerprint scanner. If any other users do use the Fingerprint scanner, could you explain the steps in which you flashed each file? After using the Aroma installer to fix Fingerprint, I keep getting "Unfortunately, Fingerprint has stopped working." I just can't seem to get it working even with the Aroma installer. Maybe I am flashing files in the wrong order?
Thanks for any advice!

Android Attack said:
Hello, thank you for this great write-up! I PM'ed you the other day, and you helped me get my phone flashed and all.
However, I am still having issues with the Fingerprint scanner. If any other users do use the Fingerprint scanner, could you explain the steps in which you flashed each file? After using the Aroma installer to fix Fingerprint, I keep getting "Unfortunately, Fingerprint has stopped working." I just can't seem to get it working even with the Aroma installer. Maybe I am flashing files in the wrong order?
Thanks for any advice!
Click to expand...
Click to collapse
did you do a factory reset or dirty flash?
sent from my S6 using tapatalk

Another ROM Option
This is also an option for anyone having issues: http://forum.xda-developers.com/spr...ebloated-rom-samsuing-galaxy-s6-edge-t3126661
@Electronical Updates reminds all S6 users to flash the Ktoonsez kernel.
I hope to try this out this weekend.

scott_0 said:
did you do a factory reset or dirty flash?
sent from my S6 using tapatalk
Click to expand...
Click to collapse
I have tried both. I first wiped system, data, cache, dalvik and tried that. Then, I tried dirty flash from stock, flashing the ROM, kernel, and fingerprint fix, then wiped caches, and nothing. :/
Could you start the aroma installer, and on the first slide it tells you the version. Could you tell me which version you have? Maybe we have different versions, that could be the problem.. Thank you!
Edit: I also tried the other debloated ROM you mentioned, but it did not work with nor without the Aroma installer. If anybody wants to work with me to get this working, I can provide logs and information and test out whatever is needed. Thanks!

Thank you for this write up...glad to learn there is dev'ing going on for the edge.
Was hoping you could help; tried flashing twrp via odin, per instructions--root manager shows that I have TWRP 2.x.x. installed but when I try to boot into recovery I just get this crazy bright white screen. Was able to reboot normally the first time, but then tried booting into recovery with flashify and now stock on that bright white screen. I do have success with getting connections with odin, twrp flashing successfully. But now trying to flash back to stock firmware to get my recovery back and I have mixed results. PLEASE any help would be very much appreciated...might have borked my brand new s6 edge...but hope not.
Thanks in advance.

Unsuccessful
koop1955 said:
I have been asked by several people, on the forums and via PM. I thought that I would offer a step-by-step guide.
Will This Trip Knox? Yes, it will. Installing a custom recovery such as TWRP will definitely trip Knox. From what I have read installing a ROM, even through FlashFire, will trip Knox, as will flashing a kernel.
You Don't Seem To Care About Knox That is correct. To this point the only downside is that I won't be able to use Samsung Pay and I don't plan on that anyway. BUT.....if you do care and Knox matters, stop reading now and stick with stock.
I will also recommend that you grab ODIN and a stock TAR file for your phone. You can always find the latest firmware at SamMobile, but will need to create an account and free downloads are speed capped. It will be SLOOOOW. But you will get a zip with the file that you need inside. Good to have in case of accident. Here is where I got mine: http://www.sammobile.com/firmwares/download/47474/G920PVPU1AOE2_G920PSPT1AOE2_SPR/
That said.....assume that you have a rooted S6. Install TWRP Manager from the Play store, ignore anything it says about an SD card and click on "Install TWRP." The version that you are looking for is "zerofltespr.img." You can also download that from here https://twrp.me/devices/samsunggalaxys6sprint.html and use Flashfire to install. Reboot into recovery (see http://www.androidexplained.com/galaxy-s6-recovery-mode/ for an explanation) and make sure that TWRP is installed. If TWRP doesn't come up, make sure that you used the correct file and try again.) Now you are ready to begin.
1) The ROM that I used is the SAC23 ROM from here: http://forum.xda-developers.com/spr...ment/sac23ram9200srintdeoxedmoddedv1-t3107342 Download that and copy to your phone. You should also grab the "Recent apps fix long press on home" zip file from the bottom of that post.
2) You will also NEED (!!!!!) a kernel that is designed for the S6, otherwise you will bork your phone. I use (and recommend) the Ktoonsez kernel located here: http://forum.xda-developers.com/spr...elopment/kernel-kt-sgs6-ocv-ktweaker-t3093009 Grab that and copy to your phone.
3) For fingerprint recognition and private mode, you will need the Aroma installer from here: http://forum.xda-developers.com/showpost.php?p=60112854&postcount=2 If you use the Aroma installer (and I don't so I have no experience) be sure that those are the only two things that you install.
Once you have those files on your phone, you are ready to begin.
Return to recovery mode. Before you do anything else....Click on "Backup." Accept the default settings and let it do its thing. I always name my backups....calling this Stock is probably a good idea. Once that is done, if you break things, you can return to this.
Okay, now go to Wipe. The old-timers will disagree, but most of the time the default "Factory Reset" is all that you need. If you are paranoid (and who isn't?) after this you can go to Advanced and choose Dalvik Cache, Cache, Data and System. But I rarely do this anymore. Complete guide for using TWRP is here: http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Now go back to the main screen and select Install. You can select multiple zips. Flash the ROM, the kernel and that Recent Apps zip file. Be sure to set the kernel to flash after the ROM. Or you can flash them one at a time.
Once done, reboot phone and if all went well, you will see a new boot animation. First boot will take a while, let her go.
You should have a clean build so remember that you will need to reset Developers options, security (for allow Unknown sources) and other stuff.
With the Ktoonsez kernel, you will have the KTweaker app, very useful. If it doesn't install for you (and it didn't for me) the APK is located inside the zip file that you downloaded at S6\KT-SGS6-LP5.0-TW-G920P-05.28.2015.zip\system\app\ Extract that and install. I use downloaded Profiles a lot.
If all is well, but the fingerprint and private mode settings are things that you use, go back into Recovery and select ONLY those two items. I'll state again, I don't use them, have never flashed the Aroma installer and can't offer any help. I have seen that they work for some people, not for others..../me shrugs. I can't help with that.
I also use the Wicked One Theme from @dazedandconfused who is a master. See http://forum.xda-developers.com/spr...ps/theme-wicked-one-theme-s6-s6-edge-t3129822 for the theme and instructions. Be sure to follow the instructions about having the Urban theme from the Theme Store installed first. But this theme makes me very happy.
That is everything that I know....which goes to show how little I know!
EDIT: Missed a step....DOH!.... if you are using TWRP you should flash the zip file found here to address the Deep Sleep issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Happy ROM-ing.
Click to expand...
Click to collapse
I have the SM-G920P Sprint variant I downloaded all necessary zip files even the "deep sleep"zip, backed up my stock rom, wiped and installed well at least I tried. Loaded the SAC23 ROM zip, swiped to flash but the screen just went black and I found myself back at TWRP recovery screen. Tried repeatedly and to no avail. Wondering what I missed if anything.

king_ricardo said:
I have the SM-G920P Sprint variant I downloaded all necessary zip files even the "deep sleep"zip, backed up my stock rom, wiped and installed well at least I tried. Loaded the SAC23 ROM zip, swiped to flash but the screen just went black and I found myself back at TWRP recovery screen. Tried repeatedly and to no avail. Wondering what I missed if anything.
Click to expand...
Click to collapse
First off. please edit your post to not include the entire Original Post. It is both bad form and makes it difficult to find your question.
The first thing that I would do if I were you is to make sure that I had a good download of the SAC23 ROM. That is most likely where your problem is. I will check my download later and post the MD5, but you should re-download.
I checked MD5 using WinMD5 Free (shouldn't matter, there are several MD5 checkers)and the MD5 should be 3bb8163e902769f564a2f3adb3a1b7e6. Try checking that.

Android Attack said:
I have tried both. I first wiped system, data, cache, dalvik and tried that. Then, I tried dirty flash from stock, flashing the ROM, kernel, and fingerprint fix, then wiped caches, and nothing. :/
Could you start the aroma installer, and on the first slide it tells you the version. Could you tell me which version you have? Maybe we have different versions, that could be the problem.. Thank you!
Edit: I also tried the other debloated ROM you mentioned, but it did not work with nor without the Aroma installer. If anybody wants to work with me to get this working, I can provide logs and information and test out whatever is needed. Thanks!
Click to expand...
Click to collapse
Came here to say I had the same problem. The original ROM posted here was a Deodexed ROM, and the aroma tool posted was an odex version. There's an aroma installer for Deodexed Roms that works perfectly fine, just gotta use that. I'd post the link but I've been up all night and I have work in an hour lol. Have fun, the ROM is pretty nice!

@koop1955 @scott_0 have yuo guys flashed SacsROM v3?! It seems effin' amazing!! I'm verrryyy tempted to try it lol.

Stock Rom D851-20G Flasheable Zip (07 Oct)

D85120G-Untouched_Stock_Restore.zip
Flash Full Stock (system/kernel/modem/recovery) No Root, No Mods, 100% Stock

Thanks.

Since this is the full rom, not OTA, has anyone successfully twrp from stock rooted 20e and then SuperSU and kept root? Will TiBu frozen system apps stay frozen as well? TIA

What exactly is this rom?

cenwesi said:
What exactly is this rom?
Click to expand...
Click to collapse
The name of the zip file and first post tells you what it is.
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5

do we flash it through TWRP? or any other custom recovery?

Yes, just as you would w/ any other ROM. Perform a full wipe beforehand, excluding both internal and external storage. And if you want to retain root and recovery, make sure to flash those immediately after (add them to the queue in TWRP).

Just flash this rom.. Everything works fine..
Sent from my A1-840FHD using XDA Free mobile app

This may be a stupid question but I flashed this and it says I'm still vulnerable to stagefright, isn't this suppose to patch it.
Sent from my LG-D851 using Tapatalk

I flashed the same 20g ROM, and according to the Lookout Stagefright Detector app, my device is not vulnerable to Stagefright.

works but
Followed these instruction using twrp
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
I had to reset phone after flashing and setting up. Because the phone was no functioning correctly.
Unfortunately Stagefright CVE-2015-6602 is still vulnerable according to
Zimperium Stagefright detector app.
Lookout Stagefright Detector will not detect the latest Version 2.0 vulnerabilities of Stagefright and make it clear in there app description.
"This app does not support detection of Stagefright 2.0 vulnerabilities. "
So here we go again in the waiting game.
Wouldn't it be better if google took Stagefight out of the rom, so it can could be updated in play store?

painless
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!

Works Great
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3

fc3211 said:
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
Click to expand...
Click to collapse
Thanks for the two links. Very helpful

Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.

skipaaa said:
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
Click to expand...
Click to collapse
I landed here because I tried the 20e to 20g update and got the "unexpected version" error via twrp. Responding to my own post cuz I got bold and did it anyways.
...So, I had TWRP 2.8.7.0 D851 installed. Did full backups with Titanium paid version and TWRP. Started with STOCK rooted d85120e, left it rooted, and used TRWP to install
1) STOCK d95120g from top of this thread,
2) TWRP d851 2.8.7.0 found elsewhere (above link is 2.8.6.0), and
3) the SuperSU zip from link found just above.
Rebooted system without any wipes. A few minutes to update apps on first reboot and mostly good to go. Had to update SupserSU binaries via normal mode, and reinstall busybox. Busybox froze on black screen on multiple attempts during it's startup check, so on next attempt, I didn't let it finish the check, just told it to install, and has been bliss all day. So far, so stable. Better have the backups and not need them than need them and not have them. Settings show D85120G and Lookout shows NOT vulnerable to stagefright.
Sitting pretty. Hope this helps others who couldn't use the 20E to 20G update method to keep stock roms with optional root.

Wiped everything as stated and flashing reboots TWRP, anyone know why this happens?

Thank you! Works - rooted 20e to 20g
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
I was on rooted 20e and did what you said. Works like a charm, I have 20g now without any problems. Thank you everyone! :]

I finally came out of lurk mode to say thanks. This untouched ROM has saved me from 2 soft bricks. Works flawlessly.

it has no sound please help

Uninstall Root on Cm13?

I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks

Isn't root enabled via settings? Maybe turn it off in the settings or reflash and don't enable root?

I tried that but the system is still seen as rooted
Sent from my SGH-T999 using XDA-Developers mobile app

Shack70 said:
I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Click to expand...
Click to collapse
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"

mrrocketdog said:
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
Click to expand...
Click to collapse
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app

Shack70 said:
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
hmmmmm well just for something to try , how about reflasing superSU then see if it will open. idk. just something to try
"err on the side of kindness"

CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install SUHide v0.54
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will hide your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
-Test Pokemon Go. You should have no problems!
6. Need a GPS spoofing app? I use Fake GPS (well worth the $2.99). It allows you to pin favorite locations (I bounce quickly between spots where I can hit multiple lured PokeStops at once), and has settings to randomly move within a radius at whatever intervals and speed. They also have a GPS Joystick and Routes app that I have not yet tested since they don't offer a trial or free version. I'll update on that if they do offer a trial.
I have fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
**UPDATE 10/7/2016 ** - edited to use updated suhide v0.54

FuNKSioN said:
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install suhide v0.53
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will spoof your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
Test Pokemon Go. You should have no problems!
***UPDATE***
I have just fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
Click to expand...
Click to collapse
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.

Shack70 said:
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Click to expand...
Click to collapse
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.

FuNKSioN said:
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
Click to expand...
Click to collapse
Wow! Thanks I appreciate it.

Shack70 said:
Wow! Thanks I appreciate it.
Click to expand...
Click to collapse
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.

FuNKSioN said:
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
Click to expand...
Click to collapse
Thanks for your help. I updated yo the newest nightly build, did a full factory reset and deleted the 2 su files. After rebooting i re-downloaded the newest version of Pokémon and installed it. Game is working fine.
I don't use root much so I'll see how it goes without root and if I need root i can put the su files back(I made copies and put them in Dropbox) or try superSU/hideSU.
I know the s3 is slow but I'm putting off an upgrade until i have to upgrade. Until i upgrade I won't really realize how slow my phone is
Sent from my SGH-T999 using XDA-Developers mobile app

Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.

FuNKSioN said:
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
Click to expand...
Click to collapse
Yeah i get this is a temporary solution. Thanks for all your help. You've really gone above and beyond
Sent from my SGH-T999 using XDA-Developers mobile app

no problem man!

Thanks!
FuNKSioN said:
no problem man!
Click to expand...
Click to collapse
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.

romehu2 said:
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
Click to expand...
Click to collapse
Glad to help. I was in the same boat: so much info in all directions and none of it seemed to work. I keep up with ChainFire's G+ account. He had a few posts linked directly back to XDA. Those few posts had everything needed. I just put it in simple steps. All thanks to him really

Sigh
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?

romehu2 said:
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
Click to expand...
Click to collapse
reflashed CM13 + GApps, used ADB to rename system/xbin/su & system/bin/su to /su-off, and SafetyNet is happy (and thus, so is PoGo). but now, of course, phone isn't rooted.
---------- Post added at 05:18 AM ---------- Previous post was at 05:05 AM ----------
on the plus side, CM13 comes with File Manager which allowed me, without root, to install the v39.1 PoGo apk that I downloaded last week.

Sit back and wait for an SU update... It's only been a hot minute.