Database Users

I just got an update notification for my 3G XOOM for HTK75D

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this all about?? Isn't this just 3.2.1 for the WiFi XOOM? I'm almost afraid to run the upgrade.

Yup. 321 it is. Got it earlier, upgraded, everything is fine.
Sent from my Xoom using Tapatalk

Ok. I just pulled the .zip and all of the files are dated the 25th, which was yesterday. Here is the file.

Why are 3g xooms getting this? Is this a result of downgraded xooms that used that update zip to fix the bootloader baseband?
Sent from my ADR6400L using xda premium

No. I never tried to update using the images from that other thread. I always wait a day or two before trying anything like that to see what happens. Still on stock 3.2. Only thing I've changed is the theme.

This is to bring 3G Xoom users up to the release build for 4G Xooms minus the radio but including all of the new security features present in HLK75D.
It also happens to contain the new 1.50 bootloader.bin which is required for those security enhancements.

Is it safe to add that zip file via cwm to a unlocked & rooted 3G?
I know it is not safe via ota
Or do we re-lock & unroot back to oem HR166 first and just take it via ota
Same update offered here today
?
New to the xoom here, is there a way to add this update while unlock & rooted?
I don't think changing the name to update.zip via cwm will work?
I maybe wrong.
In addition, if i re-lock and all back to HR166, have done it once to take the 3.2 ota update, can i just use the backup within cwm prior and restore settings and apps from that backup after this 3.2.1 update, or will that try to re-store the 3.2 os & boot onto now what would be 3.2.1?

Maybe someone here will be able to provide a walkthrough on how to get this updated. I'm rooted, but will this unroot me? will it lock the bootloader since there's a new bootloader update? I just don't feel like losing all my data and starting all the way back at HR166 again.

Am I likely to get this in the UK? I just checked for updates on my 3G Xoom and nothing shows!

I just said the heck with it and simply re-lock & unroot back to oem stock HR166 "3.0.1"
Then took the 3.1 - 3.2- 3.2.1 updates and started with a clean slate.
I did not have any custom roms and very little software, backed up the apk's and just started from scratch to avoid problems.
Yet I'd be interested in how to apply these ota update zips via cdw if possible for future references.

If my 3G Xoom is on 3.1 would this update take it all the way to 3.2? If so do I need to wait till it appears on my updates screen or is there another way?
Thanks.

Not sure about yours "international or US Verizon?", here in the states with the verizon 3G i went back to stock 3.0.1 re-locked + root, then it offered update 3.1 just over 28MB, then after that update 3.2 was available just over 15MB, took that one, then came update 3.2.1 just over 3.5MB
took that one.
To help it along i went into settings and to the bottom about tablet
Clicked the check update and they were available, once i did not even make it in there when the system told me one was available.
Again, this was on a non international USA Verizon 3G
Total time from start to finish including the re-locking and applying stock 3.01 was maybe 45 minutes in all.
My 3G has NOT been sent in yet for the LTE4G upgrade, hence the 3.2.1 and NOT 3.2.2
adamelphick said:
If my 3G Xoom is on 3.1 would this update take it all the way to 3.2? If so do I need to wait till it appears on my updates screen or is there another way?
Thanks.
Click to expand...
Click to collapse

this update breaks the android market. You cannot update existing apps .. the market constantly force closes.

Try clearing app data for your market

It checks your system first. If you've deodexed or overclocked (modified /system/app, /system/bin, or removed/overwritten files in /system/xbin, as well as the boot image / kernel) it'll abort the install.

I flashed a boot.img that was pre rooted for 3.2. Do I need to reflash a stock boot image first?

I was at Best Buy today checking out the verizon xoom. I went into settings to check which firmare was running. A message popped up saying there was a 4.0 something update available for download. The download file was about 350mb. If that was the ICS update maybe more people will start getting the update within the next few days.

Now that would be great!!
kosenn said:
I was at Best Buy today checking out the verizon xoom. I went into settings to check which firmare was running. A message popped up saying there was a 4.0 something update available for download. The download file was about 350mb. If that was the ICS update maybe more people will start getting the update within the next few days.
Click to expand...
Click to collapse

kosenn said:
I was at Best Buy today checking out the verizon xoom. I went into settings to check which firmare was running. A message popped up saying there was a 4.0 something update available for download. The download file was about 350mb. If that was the ICS update maybe more people will start getting the update within the next few days.
Click to expand...
Click to collapse
Get back to that best buy, download and dump that update. You would be famous if it was 4.0
Sent from my Xoom using xda premium

al0vely said:
this update breaks the android market. You cannot update existing apps .. the market constantly force closes.
Click to expand...
Click to collapse
al0vely - your mrkt app is probably not fubar'd - HTK75D or HLK75D (update received w/ 4G LTE upgrade) contains an update to the google mrkt. If the app keeps cratering, try going to > Settings > Applications > Manage Applications > All >
Clear the cache & data on the following Apps:
Download Manager
Market
then reboot the device.
If that does not resolve the issue: back up any personal data that would not be backed up to the cloud > reboot into Android Recovery Mode > clear cache > reset to factory defaults > reboot.
That should fix the problem.
Cheers,
Hat.

[TIP/GUIDE] Root + Custom Kernel + Custom Recovery = Device Status Normal + OTA

I'm fully rooted on a self-modified (initramfs/init.d/bootani/build.prop/csc etc²) stock JB 4.1.2 MF2 Rom, with AbyssN2 Kernel 2.5.1 and TWRP Recovery 2.6.0.0. My device status is normal and software update works as intended.
I had these all along since MB2 didn't realise it's working until I was just playing around and stumbled upon accidentally to share this good news :good: 1st of all, the effort is not by me Credits are in red. Please donate to these wonderful peeps! :angel:
Note: This will NOT reset your flash count or whatever you see at download mode to official as long as you have custom kernel/recovery. If you need those cleared before sending to service center, flash stock rom from sammobile.com via pc odin, temporary root, reset the counter using Triangle Away, unroot and finally factory reset. We don't cover these here, there's already lots of guides so please do a quick search if you ever need them...
Please read the guides especially on the links provided:
If you have "Triangle Away" by Chainfire (you need to allow SysScope service to run).
a) make sure you unchecked "Auto reset at boot" (else SysScope will not run properly).
b) make sure you checked "Allow tracker to run" (for Triangle Away 2.37 and below, please upgrade or just uninstall until needed).
c) make sure you unchecked "System modified workaround" (for Triangle Away 2.37 and below, please upgrade or just uninstall until needed).
Confirm that SysScope service is not disabled/frozen. You can check from "Settings, Application Manager, All" or from apps like Titanium Backup. Need not clear its data.
Install and activate the "Xposed Framework" app by rovo89, guide and apk on 1st thread http://forum.xda-developers.com/showthread.php?t=1574401
Install and enabled the "Samsung SysScope Blaster" module by _TB_TB_, apk on the 1st thread http://www.villainrom.co.uk/forum/threads/samsung-sysscope-blaster.5584/. The site has been down for awhile, refer attached for the apk.
Reboot and observe your device status at settings, it should state "Normal". It will change to "Modified" if you use Triangle Away reset feature, or wipe/kill SysScope. It'll then changed back to "Normal" again at reboot..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
** Updates 1st March 2013 **
If you happen to update SuperSU (v1.20) binary using its new CWM/TWRP option, most probably your status will go back to modified. To fix this, uninstall SuperSU via its settings>cleanup>reinstall, reboot, reinstall SuperSU from Google Play Store then open SuperSU. This time, avoid the new CWM/TWRP option and just update the binary normally. And finally reboot, the status will change back to normal.
Note: I noticed the latest SuperSU acts weird after reinstalled. Root required apps will hang awaiting for user prompt. So I temporarily set the default access to grant till further updates.
** Updates 2nd March 2013 **
I noticed the status will also change to modified when the SysScope runs at boot and detects your system fs(FileSystem) is mounted as rw(ReadWrite). Strangely others such as rootfs are not affected. So look out for start up scripts in the init.d folder, if you have, that remount /system as rw(ReadWrite) but didn't set it back to ro(ReadOnly) when the script ends. Some custom kernels does such remount on post init, but they would usually revert it back when done.
busybox mount -oremount,rw system /system
#...scripts having early lines like above should end like below.
busybox mount -oremount,ro system /system
** Updates 11th July 2013 **
Good new, this method seems to be still working on the latest MF2. Personally tested an OTA update on latest TWRP recovery, it works! Need to reroot of course. For AllShare Cast, there has been mix results. Previously tested on someone else's, now I just got the dongle and created this thread [SCRIPT] custom2stock1click-v0.1 (AllShare Cast temporary workaround)

Thank you. Worked for me getting my status back to normal.
Sent from my GT-N7100 using Tapatalk 2

OK, nice guide. But does it have any value as far as updates are concerned?
I'm on rooted stock 4.1.1. It was reported "changed" and I couldn't OTA update to 4.1.2.
If I now have "normal" will it update to 4.1.2 through OTA? (I tried and it stared downloading, but will it WORK?)
Will I loose my root?
Is it good idea to update OTA like this ?
Thanx,
D.

Wow, a simple guide that actually works.
Thanks dude.

dalanik said:
OK, nice guide. But does it have any value as far as updates are concerned?
I'm on rooted stock 4.1.1. It was reported "changed" and I couldn't OTA update to 4.1.2.
If I now have "normal" will it update to 4.1.2 through OTA? (I tried and it stared downloading, but will it WORK?)
Will I loose my root?
Is it good idea to update OTA like this ?
Thanx,
D.
Click to expand...
Click to collapse
yes, you will looose the root. i have rooted stock rom with 0 counter and "official". after update with kies i loose my root.

dalanik said:
OK, nice guide. But does it have any value as far as updates are concerned?
I'm on rooted stock 4.1.1. It was reported "changed" and I couldn't OTA update to 4.1.2.
If I now have "normal" will it update to 4.1.2 through OTA? (I tried and it stared downloading, but will it WORK?)
Will I loose my root?
Is it good idea to update OTA like this ?
Thanx,
D.
Click to expand...
Click to collapse
As mentioned by tuksedra previously, yes you would lose root. But rooting back is not a problem. It's a click away using Exynos Abuse app or you can even use SuperSU's survival mode to keep root. Else old school odin method should come in handy.
Personally I hate downloading 1gb of full rom just to upgrade. I have a 200mb fiber connection but hotfile is just too slow. Please let us know if it works for you.
This method should also be working for those who is still having status modified issues even on stock kernel/recovery but rooted. Not sure about kies though (what kies uh?), if anyone can confirm I'll update the OP...

I have seen cases where there is status is modified even device never been rooted, as far as warranty is concern there should not be have issue for status 'modified' once flash counter is 'No'
I have seen many cases of SDS and all i remember have status 'custom' on download mode, though i never read any post where warranty claim rejected for 'custom' status
Here one trick working on Rooted/non rooted device too (without any third party SW)
setting - Appl manager - All - SysScope - clear data
do same with Enterprise SysScope if available
And status will turn to 'Normal'
Another weired phenomenon of OTA is even after doing lots workout and turn status to 'Normal' there is no guarantee you will get OTA updates.(though i have seen cases where OTA successfull even device is rooted)
sometime it needs unroot
sometimes needs unroot + Factory reset
and myself observed 1 time even after unroot + factory reset i didn't get OTA, though update file was downloaded but installation was failed, then i have tried to flash old ROM with Odin and then tried OTA and it was worked, so something there in system can block OTA.

dr.ketan said:
I have seen cases where there is status is modified even device never been rooted, as far as warranty is concern there should not be have issue for status 'modified' once flash counter is 'No'
I have seen many cases of SDS and all i remember have status 'custom' on download mode, though i never read any post where warranty claim rejected for 'custom' status
Here one trick working on Rooted/non rooted device too (without any third party SW)
setting - Appl manager - All - SysScope - clear data
do same with Enterprise SysScope if available
And status will turn to 'Normal'
Another weired phenomenon of OTA is even after doing lots workout and turn status to 'Normal' there is no guarantee you will get OTA updates.(though i have seen cases where OTA successfull even device is rooted)
sometime it needs unroot
sometimes needs unroot + Factory reset
and myself observed 1 time even after unroot + factory reset i didn't get OTA, though update file was downloaded but installation was failed, then i have tried to flash old ROM with Odin and then tried OTA and it was worked, so something there in system can block OTA.
Click to expand...
Click to collapse
Hi dr.ketan!
I rooted my Note II yesterday using your Method 1 and used TA to reset counters and this is what i did and noticed:
Note: Did almost workaround, yours, other posts and mine. Geee... read more than 100 pages, rebooted nth times!
1. After rebooting and setup/updates, checked my device status and it is still normal.
2. Recheck again via reboot and download mode, Binary DL: No, Binary: Official & Status is official also.
3. Reboot and check Device, status again normal.
4. Install Avast, do 2 & 3.
5. Configure Avast Firewall, SuperSU prompted and granted.
6. Do 2,.
7. Do 3, but status is modified now.
8. Reflash stock ROM DMB2 Philippines via PC ODIN and back again to stock unrooted phone.
Again, refer to NOTE above.
Any additional workaround Sir or anyone?
For me, Device Status Modified is an eye sore.
Also, I want to say THANK YOU VERY MUCH for all the guides and posts Sir!!

dr.ketan said:
Another weired phenomenon of OTA is even after doing lots workout and turn status to 'Normal' there is no guarantee you will get OTA updates.
Click to expand...
Click to collapse
What about if
1) I have some frozen apps (suppose this is no big deal)?
2) I have integrated some updated apps into ROM?
3) I have added some user apps to system?
Will this be lost/changed after OTA?
D.

Really difficult to say anything regarding OTA
Thogh even you get OTA
- frozen application should remain as it is if OTA doesn't have same application
- user application pushed to system should remain as it is
Sent from my GT-N7100 using xda premium
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
wyndcryst25 said:
Hi dr.ketan!
I rooted my Note II yesterday using your Method 1 and used TA to reset counters and this is what i did and noticed:
Note: Did almost workaround, yours, other posts and mine. Geee... read more than 100 pages, rebooted nth times!
1. After rebooting and setup/updates, checked my device status and it is still normal.
2. Recheck again via reboot and download mode, Binary DL: No, Binary: Official & Status is official also.
3. Reboot and check Device, status again normal.
4. Install Avast, do 2 & 3.
5. Configure Avast Firewall, SuperSU prompted and granted.
6. Do 2,.
7. Do 3, but status is modified now.
8. Reflash stock ROM DMB2 Philippines via PC ODIN and back again to stock unrooted phone.
Again, refer to NOTE above.
Any additional workaround Sir or anyone?
For me, Device Status Modified is an eye sore.
Also, I want to say THANK YOU VERY MUCH for all the guides and posts Sir!!
Click to expand...
Click to collapse
If you mean you are having unrooted stock rom with device modified
Then try
Setting - application manager - all - sysscope - clear data
Same with enterprise sysscope
It may turn to normal
Otherwise factory reset also works
Sent from my GT-N7100 using xda premium

dr.ketan said:
If you mean you are having unrooted stock rom with device modified
Then try
Setting - application manager - all - sysscope - clear data
Same with enterprise sysscope
It may turn to normal
Otherwise factory reset also works
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yes after factory reset or clearing all syscope, it turns normal.
I have done that also Sir, but after installing avast, rebooted - normal status, configure firewall, status is back to modified. Done it many times and tried to workaround.
Anyway, I'm back to stock right now and will do a rooting rematch later after office. Any more advice Sir on rooting procedure?
I know, you will direct me to your posts but perhaps there is other way to do it basing from your experience...

Rooting rematch started...
Question Doc, after wipe data/factory reset, do i need to re-install Triangle Away to allow tracker to run?
Just finished factory reset, configure setup and updated SuperSU, Currently my Device Status is Normal.

I think there is no meaning to keep on tracking, whenever you need just clear data for sysscope that's it.
Sent from my GT-N7100 using xda premium

dr.ketan said:
I think there is no meaning to keep on tracking, whenever you need just clear data for sysscope that's it.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thanks Sir!
After enabling USB Debugging, device status turns modified. followed your advice then rebooted and now status is back to normal! :good:
I'll update once setup and all installation are completed. :fingers-crossed:
Again, thank you very much!

If one need continue normal status then try method described in op
Otherwise reset manually whenever you need (like for ota)
Sent from my GT-N7100 using xda premium

dr.ketan said:
If one need continue normal status then try method described in op
Otherwise reset manually whenever you need (like for ota)
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yeah, I will Sir!
I'll take one step at a time.
Thanks!

Mine has gone back to modified. Tried a few things, but no luck as to get ir back to normal.
Installed both apps and clearing the data before didn't help as well. Did the uninstall and clean app from within xposed installer. Rebooted and reinstalled and status still modified.
Any suggestions ?
Sent from my GT-N7100 using Tapatalk 2

Did you installed, updated or performed anything recently? Mine is custom kernel/recovery (just flashed latest TWRP 2.4.2.0) and wifey's rooted(older 4.1.1) but stock kernel/recovery, till now both status is still normal.
What I noticed is that it will change to modified, if you clear SysScope data or kill'em, use TA to reset counter or prevent SysScope tracker to run normally at boot...

Worked fine after twrp install. There was a supersu update that I installed and after that it went to modified.
Sent from my GT-N7100 using Tapatalk 2

I had supersu updated too, didn't really checked the status... I remember only choosing to update su binary normally instead of the new option via cwm/twrp. I just rebooted and the status is still normal now. You might wanna try clearing both ent/SysScope then reboot...

IS Private Mode NOT Working for you after Rooting? - Try This... - LOLLIPOP

Thread Updated - This Thread is now about Private Mode in LOLLIPOP
What is Private Mode?:
http://www.androidcentral.com/how-use-private-mode-samsung-galaxy-s5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OLD KITKAT REFERENCE/SOLUTION BELOW
Is Private Mode working after you rooted your Note 4?
If the answer is no... try this flashabe zip:
Private Mode Fix
I have already demonstrated that Private Mode can continue to work after rooting/tripped Knox:
See post #24...
http://forum.xda-developers.com/not...-configure-fingerprint-scanner-t2919478/page3
Please, post results here...

If i understand correctly, it wont work for stock rooted. U have to use an rom

I can confirm this works on DynamicKat 1.2, but the quick setting did not show up. I am still glad that private mode is working now. Thank you TEKHD!

It's working for me using an Xposed module called XSecureStorage

Confirming that this works on a stock rooted deodexed rom on the Sprint Note 4.
Thanks!

OK I may have figured out another piece of this puzzle. Maybe someone more knowledgeable than me can use it to get to the bottom of it. Some background:
I was running stock, rooted. I made two complete nandroids in TWRP. The first directly after rooting. The second after a few mods but before installing Xposed framework and Wanam Xposed. I knew Xposed might kill my Private mode and indeed it did!
Removing the XsecureStorage module did not fix it, nor did uninstalling Wanam and the Xposed framework, nor flashing the Private mode fix listed in this thread. Unfortunately neither did restoring the second nandroid and that really puzzled me since Private mode was working when I made that nandroid. I tried all these things more than once to be sure. It seemed like nothing would get back my Private mode which upset me since I had a file there I really wanted back!
Then I did a complete wipe and restored the first nandroid and finally Private mode was working! Unfortunately the file I wanted was only in the second nandroid. When I restored the second nandroid again (this time just system & data) Private mode stopped working so I figured it could be one of the mods I'd installed before making that second backup. Finally I traced it to the 4 way reboot mod which alters android.policy.jar. I believe quite a few mods alter this file.
So maybe Private mode locks up when that file is altered (though there may be other conditions which also breaks it). Anyway, my advice is make nandroids - lots of them! And beware! Like me you may install some mods and be sailing along with Private mode working, only to find that when you restore a nandroid, it no longer works because of something you installed. Why this should be the case I don't know.
Sorry for the long post but I hope it helps
someone who can test this further and figure it out!
Sent from my SM-N910T using XDA Free mobile app

Dumbo53 said:
OK I may have figured out another piece of this puzzle. Maybe someone more knowledgeable than me can use it to get to the bottom of it. Some background:
I was running stock, rooted. I made two complete nandroids in TWRP. The first directly after rooting. The second after a few mods but before installing Xposed framework and Wanam Xposed. I knew Xposed might kill my Private mode and indeed it did!
Removing the XsecureStorage module did not fix it, nor did uninstalling Wanam and the Xposed framework, nor flashing the Private mode fix listed in this thread. Unfortunately neither did restoring the second nandroid and that really puzzled me since Private mode was working when I made that nandroid. I tried all these things more than once to be sure. It seemed like nothing would get back my Private mode which upset me since I had a file there I really wanted back!
Then I did a complete wipe and restored the first nandroid and finally Private mode was working! Unfortunately the file I wanted was only in the second nandroid. When I restored the second nandroid again (this time just system & data) Private mode stopped working so I figured it could be one of the mods I'd installed before making that second backup. Finally I traced it to the 4 way reboot mod which alters android.policy.jar. I believe quite a few mods alter this file.
So maybe Private mode locks up when that file is altered (though there may be other conditions which also breaks it). Anyway, my advice is make nandroids - lots of them! And beware! Like me you may install some mods and be sailing along with Private mode working, only to find that when you restore a nandroid, it no longer works because of something you installed. Why this should be the case I don't know.
Sorry for the long post but I hope it helps
someone who can test this further and figure it out!
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I have been looking into this... I think it's actually the file:
system/framework/android.policy.odex
Flashable zip: (odex injection)
Can anyone with Jovy's ROM try this fix: (in order to verify if this fix makes Private Mode work with Jovy's ROM)
http://tek.serveftp.net/xda/Private_Mode_for_jovy_Fix_N4_tekhd.zip
If this works... All credit goes to you @Dumbo53
Quick Instructions...
1. Deactivate Xposed Framework
2. Reboot into recovery and flash file above...
3. Reboot... and see if Private Mode is working...

I'm on firekat v4 not jovy's rom, but I lost my private mode along the way. I thought it was when I tripped knox rooting with the temporary recovery cf autoroot uses.
This fixed my issue.
Rocking private mode currently. Hadn't been able to use it since the day I started rooting and flashing.

I've been trying to install the Xposed module for secure storage. However it says waiting for download for over 20 minutes now. Any ideas on this because I'd really like to use this feature of my phone. Thanks.
Sent from my SM-N910T using XDA Premium HD app

Ok the server for Xposed was down last night. It is back up now. I installed the Xsecurestorage module and private mode is working.
So for those of you with the Xposed framework installed, that's probably the easier route over installing a flashable zip file.
Sent from my SM-N910T using XDA Premium HD app

not sure whats different but im on stock rooted and neither wanam nor xsecure fixed my private mode. IDK

Did you try the flashable zip in the op?

flash did not fix on stock rooted rom. No Xposed installed yet

i was going to try flashing that file but if you say it doesnt work...
When updating my phone yesterday via odin, i flashed the update...checked private mode. (it worked)
Flashed root file and checked private mode...(it worked) Told SuperSU to not disable Knox. Checked private mode again...(it worked)
Installed Xposed...checked private mode.(private mode failed). I have tried the xsecurestorage and wanam module and neither worked. S health works fine. Just not private mode. Was pretty excited about being able to use this. My only other option i suppose is to go with a deodex rom that stays closest to stock i guess.

Just used this trick again. Firekat v5.
I think I lost private mode when I tripped Knox with cf autoroot:
Nice to have it back. Although, I'm going to need a more exciting life before I need it.

This actually soft bricked my phone. Stock but rooted and stuck at the tmobile scree.

Just used this trick again. Infamous 2.3:

Working for me on Infamous 2.2
Sent from a mobius strip

Hey guys.
I started another threat but TEKHD requested i put this here as well. I found a method that worked for the 910f and worked for myself.
In data/system/secure_storage delete the personalpage folder
In data/system/users delete privatemode_edk_1000.
This got it working on my phone. Still using Xsecurstorage in xposed and haven't tested yet with it not on.
http://forum.xda-developers.com/note-4-tmobile/general/how-fixed-private-mode-t2985441

This Fix didn't work for me, but, the one mentioned by @avengethis1 at THIS POST worked for me on my T-Mobile Note 4 N910T with Stock ROM and TWRP Recovery

Cant get snapchat working on custom ROM

Hi all. I've read through a few threads here and I've followed their instructions regarding getting Snapchat working.
I don't know what I'm doing wrong but i cannot get the app to work. I'm currently using the "On the edge" ROM and i have tried removing xposed framework via recovery and also unrooted however still no joy I'm afraid. Also i did try the root cloak module through xposed however that didn't work for me either [emoji20]
Any insights would be great!
Sent from my SM-G935F using XDA-Developers mobile app

Flame_Beard said:
Hi all. I've read through a few threads here and I've followed their instructions regarding getting Snapchat working.
I don't know what I'm doing wrong but i cannot get the app to work. I'm currently using the "On the edge" ROM and i have tried removing xposed framework via recovery and also unrooted however still no joy I'm afraid. Also i did try the root cloak module through xposed however that didn't work for me either [emoji20]
Any insights would be great!
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
What does it do? My Snapchat stopped working today... idk what's wrong, can't connect to server.
Sent from my SM-G935F using Tapatalk

This is the error I get.
This after removing root and unflashing xposed through recovery. Although, it was the same error I got with root cloak too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anyone able to help?
Sent from my SM-G935F using XDA-Developers mobile app

Bump
Sent from my SM-G935F using XDA-Developers mobile app

Rydah805 said:
What does it do? My Snapchat stopped working today... idk what's wrong, can't connect to server.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Did you manage to get yours working?
Sent from my SM-G935F using XDA-Developers mobile app

Uninstall Xposed Simples
Snapchat detects the XposedBridge, and when detected fails to let you login.
Uninstall Xposed, Sign in.
Reboot and reinstall xposed.
As long as you are signed in, it will work with xposed, the issue is attempting to sign in for the first time,.
If removing Xposed did not work, Was Xposed pre done on the ROM.
Could have files or Data still lurking around.
Am on Stock, i have the Same Error message and i can overcome it by simply removing Xposed.

I ended up getting a new phone due to a flaw it had and it works on this one.
Sent from my SM-G935F using Tapatalk

Okay, with the multiple reports of it not working.
I deleted Snapchat, Removed any old files. Cleared Cache.
Reinstaleld Snapchat (With Xposed enabled) And i got the same message as above.
Rebooted into Recovery, Uninstalled Xposed, Cleared Cache, Waited about 20 minutes for Android to rebuild its Database.
Booted up, and attempted to login (Worked first go)
Rebooted, Installed Xposed, Still logged in.........
Problems with CustomRoms.
Install Stock, then Xposed and make the Rom via Mods (I find it no different from a Custom ROM, other than you know for 100% what has been changed)
(I always keep a Titanium Backup of Apps like this, You can restore them at any point, And you can carry on where you left off (As you are not prompted to login when restoring the app, You can use it with Xposed)
Of course you need to ensure you backup the App, after you have logged in

This is a known thing. If you are not logged into Snapchat before Xposed is installed, you will not be able to login. Uninstalling Xposed, logging into Snapchat, and re-installing Xposed will fix the issue and let you stay logged in - just do not log out. No idea why they do this dumb ****. It's not like it prevents people from using anything. Just makes it a hassle...

Cant erase FOTA via fastboot, update snuck through

Hey gang, I doubled checked and couldn't come up with an answer but somehow Android System Update got past my frozen FOTA & Update Center (few others) as well as having system updates unchecked in Dev Options. I haven't installed the update & would love to stay on 10D.
So I boot into fastboot, run the fastboot erase fota and get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As most can spot I'm definitely in fastboot as the fastboot getvar all and fastboot reboot function just fine. I tried defrosting the fota & others and that also didnt work.

Which phone do you have?

androiddiego said:
Which phone do you have?
Click to expand...
Click to collapse
Tmob,
I moved the Update.zip from Cache and the otacerts.zip from system/etc/security to my SD card and then went to settings/app [enable show system]/Update Center and cleared data and cache to remove the notification. I think I cleared the cache on Google Play Services as well the 1st time around but the notification came back on restart.
Side note: I had the update center frozen & it still was during clearing the data & cache. I've rebooted a few times and notification is still gone..hope it stays away. Still curious why the fast boot commands didnt work.

2muchspl said:
Tmob,
I moved the Update.zip from Cache and the otacerts.zip from system/etc/security to my SD card and then went to settings/app [enable show system]/Update Center and cleared data and cache to remove the notification. I think I cleared the cache on Google Play Services as well the 1st time around but the notification came back on restart.
Side note: I had the update center frozen & it still was during clearing the data & cache. I've rebooted a few times and notification is still gone..hope it stays away. Still curious why the fast boot commands didnt work.
Click to expand...
Click to collapse
I'm on tmo also.
Ok, here's what I did. It's the old Sammy trick. As you did, delete or move the update.zip file from /cache directory. You will have to unfreeze the update center to get the notification again.
I selected the update notification from notifications and then selected to install it. See the attached. It said rebooting. It won't reboot because the necessary file is gone. Wait 10 seconds and touch the recents home key and close the window. Done!
I rebooted the phone and no nag.
I'm on OvrDrive's 10j base now so it doesn't matter, but if you want to stay on 10d and stop the nags, this will work. Once the update fails, it won't try anymore.

androiddiego said:
I'm on tmo also.
Ok, here's what I did. It's the old Sammy trick. As you did, delete or move the update.zip file from /cache directory. You will have to unfreeze the update center to get the notification again.
I selected the update notification from notifications and then selected to install it. See the attached. It said rebooting. It won't reboot because the necessary file is gone. Wait 10 seconds and touch the recents home key and close the window. Done!
I rebooted the phone and no nag.
I'm on OvrDrive's 10j base now so it doesn't matter, but if you want to stay on 10d and stop the nags, this will work. Once the update fails, it won't try anymore.
Click to expand...
Click to collapse
These are great instructions, Im keepin them handy if my notification returns. How do you like OvrDrive's rom? I've traditionally stayed rooted stock but lately been curious about trying one out for a test drive.

2muchspl said:
These are great instructions, Im keepin them handy if my notification returns. How do you like OvrDrive's rom? I've traditionally stayed rooted stock but lately been curious about trying one out for a test drive.
Click to expand...
Click to collapse
I hope this worked for you. I was afraid to try this even though it used to work on all my sammy phones, but I bit the bullet and it worked. @OvrDriVE 's ROM is great. I do a lot of lurking watching what is going on with each rom and I feel that Ovrdrive has the best. That's not to say anything bad about the other guys. They are very involved and actually help people out in rom threads that aren't even theirs. We have a great group of folks here. With that said, OvrDrive's I believe has the least complications and he is very responsive. I believe he came from a Note 4 which is where I came from and his reputation on the Note 4 was excellent.