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.

Restoring Stock boot.img & Stock recovery.img then taking OTA

I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!

AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.

Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.

It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.

AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125

Where can i found the stock boot.image and stock recovery.img

bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...

Thanks

Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!

laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!

AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!

No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!

AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....

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

Installing TWRP

Sorry to beat a dead horse, I come from the nexus forums and haven't used a samsung device in a while. My friend has the Note 4 with MM on it. Is flashing TWRP as simple as just flashing it via odin with his phone as is? Does he need to complete any process first, before being able to flash TWRP via odin?
Thanks all!

Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk

samep said:
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks bud. This was really great!

hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..

CorporalCactus said:
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
Click to expand...
Click to collapse
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk

samep said:
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??

CorporalCactus said:
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
Click to expand...
Click to collapse
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk

samep said:
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected

CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
Did you factory reset and wipe internal memory when restoring the backup?
Put your micro sdcard in a card reader and transfer it. If you're trying to transfer while in recovery, that currently doesn't work.
If you're trying to copy your TWRP backup to micro sdcard, the path should be: TWRP/BACKUPS/(your device s/n recognized by TWRP)/(TWRP Backup folder)
Without proper path, TWRP may not see the backup as official. When saving TWRP backups, the TWRP folder as a whole with desired backups should be saved.
If you can't restore the backup, you can flash a ROM that matches bootloader. Like I said before, factory reset and wipe internal memory and flash the ROM.
Sent from my SM-N910P using Tapatalk

CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
At this point I would just recommend flashing a new ROM man.
Sent from my SM-N910P using Tapatalk

[D5503]Prerooted Customized IN 14.6.A.1.236 Flashable Zip for Sony Xperia Z1 Compact

Hello mates, Here is
D5503_Customized IN_1281-0184_14.6.A.1.236_R3D Prerooted Flashable Zip for Sony Xperia Z1 Compact Locked Bootloader
Made by PRFCreator_v1.3
You need only rooted phone and TWRP
For Root Xperia Z1C : https://forum.xda-developers.com/xperia-z1/general/root-xperia-z1-lollipop-5-1-1-build-14-t3246373
Or you can any well known and safe method for rooting. I have use kingroot 4.5.2.apk, after root I installed Z1C-lockeddualrecovery2.8.26.
For Dual Recovery : https://forum.xda-developers.com/showthread.php?t=2647480
In this creation you will get Stock Sony Rom 5.1.1.{ rooted with SuperSu (2.46) and Z1C-lockeddualrecovery2.8.26 }
How to Install:
1. Download file
2. Copy this zip in your sd card or internal memory( In recovery you can change default storage )
3. Boot to recovery (Use TWRP)
4. Wipe data,Cache and Dalwik Cache
5. install flashable-prerooted-signed.zip
6. Reboot to System
I have flashed on Stock Sony 14.6.A.1.236 in my Xperia Z1 Compact and tested everything is working good. There isn’t any problem in this rom. After installation this rom we can remove System apps, Ringtones etc… which are we don’t use.
In this rom I didn’t added Xposed. So you can install later.I have installed xposed-v84-sdk22-arm after flash rom.
Download Link : https://drive.google.com/open?id=0B2DnyFUiK93lZW1ncXlLd19JSDg
MD5: 3137f4b552a991d8cb8936749b772528
Download Link for Prerooted Zip with Xposed and SU 2.79 : https://1drv.ms/u/s!AqRWEkw4JbcJhBZESlNAZ2S-H0gJ
MD5: a36e3db078d8f8c0b0cca46f675f3259

how to install
How to install including md5?

jmcatamora said:
How to install including md5?
Click to expand...
Click to collapse
How to Install:
1. Download file
2. Copy this zip in your sd card or internal memory( In recovery you can change default storage )
3. Boot to recovery (Use TWRP)
4. Wipe data,Cache and Dalwik Cache
5. install flashable-prerooted-signed.zip
6. Reboot to System
There is no need to including md5, it is for checking purpose is your downloaded file is corrupted or not.

thank you
Can you help me . How to install xpose .??plz show me the download file xposed-v84-sdk22-arm and the framework.

jmcatamora said:
Can you help me . How to install xpose .??plz show me the download file xposed-v84-sdk22-arm and the framework.
Click to expand...
Click to collapse
Thanks to rovo89 for xposed support .
This is the link for download xposed framework
http://dl-xda.xposed.info/framework/sdk22/arm/
Detailed instructions for installation go to this link
https://forum.xda-developers.com/showthread.php?t=3034811

Thanks a ton for this! Worked awesome!
Since I went from stock 5.0.2 -> 5.1.1 ... I tried not wiping data and it seems everything still works fine! My apps, settings and data are all there =) ... so far w/o bugs.
I installed cyberian 7.1 camera(primary reason for my attempt at the upgrade) ... and seems to be working 100% w/o issue =)

GenTarkin said:
Thanks a ton for this! Worked awesome!
Since I went from stock 5.0.2 -> 5.1.1 ... I tried not wiping data and it seems everything still works fine! My apps, settings and data are all there =) ... so far w/o bugs.
I installed cyberian 7.1 camera(primary reason for my attempt at the upgrade) ... and seems to be working 100% w/o issue =)
Click to expand...
Click to collapse
Happy to know it is working on without wiping data.

PARESH AHAR said:
Happy to know it is working on without wiping data.
Click to expand...
Click to collapse
An update, its still working amazingly bug free!!! (w/o data wipe)
Also, *I think* battery life has much improved ... but that may be because I wiped cache and also turned off Stamina mode after reading it sucks battery life rather than help it lol!
I did run into some battery level quirkiness within the first few days of install, but hoping it was just some learning curve the OS had to do w/ battery ... time will tell =)
I do have a question tho, just noticed you state the bootloader/recovery is "locked"? Does this overwrite my previous "unlocked" state and its relocked now? Or does an unlocked state persist? Thanks

GenTarkin said:
I do have a question tho, just noticed you state the bootloader/recovery is "locked"? Does this overwrite my previous "unlocked" state and its relocked now? Or does an unlocked state persist? Thanks
Click to expand...
Click to collapse
No,this doesn't overwrite your unlocked bootloader. your unlocked state is persist.You can check by dialing *#*#7378423#*#* /Service info/Configuration/Rooting status:

Sad update, seems my phone has fallen victim to the "LP upgrade & damaged battery" coincidence =( ... I know its not a fault of ur ROM. Phone works fine from 100% to 50% then a 50% it rapidly drops to 1% and shuts off =/
That being said, ordered a replacement battery kit + back door + NFC tag. Hopefully normal battery functionality will be restored after its replaced =)
Seems to be a widespread problem =/ Its weird because I had LP 5.0.2 on it previously.

Battery replacement went well, back to full expected usage time!

blank screen after sony logo what should i do i have an unlock bootloader TWRP 3.0.2 on FotaKernel

nhicko95 said:
blank screen after sony logo what should i do i have an unlock bootloader TWRP 3.0.2 on FotaKernel
Click to expand...
Click to collapse
Bro I have tried locked bootloader. But I think GenTarkin installed on unlocked bootloader successful. First you should flash stock.ftf and after go further as first post.

Dirty flash I love you dirty flash blahblahblah
Thanks for this, just what I needed without the hasle as Gen said I just flashed over the rom I was using (mx 8.5), wiped dalvik and that other thing but kept data and now my phones overheating has stopped, installed xposed and my tweaks reinstalled themselves... Because of the dirty flash some of the apps needed updating but apart from that its ask good... Nice one

Update Zip
Zip is updated with Xposed and SU 2.79
Download Link : https://1drv.ms/u/s!AqRWEkw4JbcJhBZESlNAZ2S-H0gJ

Is there an Arabic language?

azoga said:
Is there an Arabic language?
Click to expand...
Click to collapse
Stock languages

There is a problem with Facebook and Messenger app (normal, not lite versions). When my girlfriend is trying to run these apps the screen just is just blinking (black&white) every 0,5 of sec. and nothing else is happening. Reinstalling those apps does not solve the problem.

watchoutbehindyou said:
There is a problem with Facebook and Messenger app (normal, not lite versions). When my girlfriend is trying to run these apps the screen just is just blinking (black&white) every 0,5 of sec. and nothing else is happening. Reinstalling those apps does not solve the problem.
Click to expand...
Click to collapse
You need to install an older version of facebook.

14.3.b.0.310
Can i flash this rom from stock rom 14.3.b.0.310?