Database Develop

[Root] Replacing Superuser app with Super SU by CF

Super SU by CF
SuperSU is the Superuser access management tool of the future
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
Who, What Why ? - said by CF
As you may know, I make a lot of apps that use or require root. I also release rooted kernels. I run into a lot of issues with existing Superuser tools. More importantly, a lot of my users run into these issues as well and then email me about it. So I decided to do something about this. Doesn't mean these were problems you have ever seen, or will ever see.
And thus, I have written - pretty much from scratch - SuperSU. I have taken the su binary command line parameter parsing from Superuser, to make sure that is compatible. Aside from that, it is completely rewritten, because how I wanted to do a number of things was incompatible with the existing codebase.
This is not a stab at ChainsDD, or his skills. He has done great work and will no doubt continue to do so, however, I felt the need for some of these changes, and thus made them. This is an early release, so I expect there will be some unforseen issues somewhere.
From now on, all CF-Root and Mobile ODIN Pro (EverRoot) releases will be built around SuperSU.
Please note that SuperSU is not hardened-security-tested or reviewed, and may be exploitable (... as may other solutions ...).
Install :
Flashable Zip v0.93
Market :
Lite
Pro
Note : Pro is key only, you need to install lite version first.
If you install from market, you will have two superuser, remove older one with system appl remover, or any other application can perform same job.
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
Source : http://forum.xda-developers.com/showthread.php?t=1538053

Thanks a lot doc. Gonna give it a try.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Sorry to say but this belongs to General Section.

Nice one, Dr.Ketan.
Perhaps your fine installation instruction could also include this:
"Superuser (the old one) is a system app and should be removed from /system/app/ folder using Root Explorer, ES Eplorer with root permissions, or similar explorer app. Titanium Backup does not show Superuser in its app list, and therefore cannot remove it."
Otherwise you'll be swamped with Titanium questions.

This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..

dr.ketan said:
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
Click to expand...
Click to collapse
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...

grgsiocl said:
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
Click to expand...
Click to collapse
CF says he has fixed that bug in v0.74, and that's the one posted here.

I have no issue with USB debugging ON

Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA

kopitalk said:
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Newbie question here, (sorry) so you don't just download from the market/play store..... open and it will install on it's own?
Sent From my Two Tin Cans & String Device on The Wookie Network

It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market

dr.ketan said:
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
Click to expand...
Click to collapse
Another newbie question... Is there enough of a difference between superuser & supersu for a newbie to risk mucking up their phone?
Thanks!
EDIT : are there instructions as to how to flash with CWM? SORRY!!
Sent From my Two Tin Cans & String Device on The Wookie Network

Superuser v0.75 has been released.
Changelog:
10.03.2012 - v0.75
- Adjustment to OTA survival (better!)
- Slight speedup in Settings
- Fixed native settings update after temp-re-root
- Clear data no longer clears PIN code
- Layout: Prompt: Grant and Deny switch positions (ICS style)
- Layout: AppDetail: Save and Cancel switched positions (ICS style)
- Layout: Added xlarge PIN layout
http://forum.xda-developers.com/attachment.php?attachmentid=940641&d=1331395344
P.S. Dr.Ketan, when I try to download CWM flashable zip from your 1st post I get a 404.

Ya b'coz link replaced by CF with new version
updated now

dr.ketan said:
Ya b'coz link replaced by CF with new version
updated now
Click to expand...
Click to collapse
even mobile Odin is updated with 2.25

Very Slow Boot Up Following Switch to SuperSU Pro
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz

krazman325 said:
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
Click to expand...
Click to collapse
what you said was true...it slows up booting...but what i did was, in supersu app, i selected grant as default and there is no need for prompt...after that, booting as speed up!

I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Sorry for wasting space in this thread!!! Hopefully, anyone else having similar trouble will see this.
kraz

Thanks Doc!flashing now

krazman325 said:
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Click to expand...
Click to collapse
Yeah, this is what CF has to say about it in his original thread:
Chainfire said:
PROTIP:
For extra performance, disable notifications. Logging does not impact performance much.
Click to expand...
Click to collapse

I think it would have been better to just link to chainfires thread rather than repost what he posted.

[ROM][NANDROID-BACKUP] minusculeShield 1.0

minusculeShield 1.0
So after some time, I decided that the 4.3 update is worth doing slight modifications, even without the native Shield Services and PC Streaming able to be done remotely. I have gotten used to using Limelight anyways, so I decided to update my basic modified stock Shield ROM
First, I updated to the latest OTA 68, then went from there, the features are as follows:
- Two versions of the ROM, one with OTA and one without
- Includes a alternative Calculator (RealCalc), Zeam Launcher, Adblock, Xposed Framework (Along with an Xposed Module for adding a Play Store link to App info, and GravityBox for various system tweaks), MX Player, and ES File Explorer
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.3 Minimal Gapps
- Koush's Superuser/Superuser Binaries pre-installed
Same installation process as 0.5, excluding need to select Advanced Restore, you can restore like a normal Nandroid without specifying partitions
As always, make sure you wipe System, Data, Cache, and Dalvik before installing
If you have problems with the OTA-exempt version trying to OTA, if it prompts you, it will do it once, and once you "apply" the update (which it will never actually apply) the notification will go away
minusculeShield 0.5[Nandroid-Backup]
So, this is not really a ROM, but a Nandroid backup of my system without any partition but "/system."
This is almost as stripped down as the stock Shield ROM you can get. I have removed all but literally the most essential apps, and also removed the OTA functionality.
The idea for making this was that I couldn't stream remotely anymore since OTA 63, which I promptly set out to fix. I soon realized it was a problem with the Android side of things, as using it on 4.1.2 or 4.2.2 with their respective apps for that release seemed to work fine. OTA 63 (and 64, which is basically the same release, just for those who couldn't install 63) made the local streaming much less productive, as I immediately noticed lagspikes and a load of other problems, which I had never encountered before.
So, in a basic sense, this backup after installed, keeps the ability to stream remotely without troubles of performance or re-connection problems, uses a much more lightweight version of Gapps (Slimrom's version to be exact). It is based on agrabren's TweakerROM 1.1.0, which is a 4.2.2 base, and uses the original TegraZone Dashboard. It again removes OTA, so updating is not an option.
So, when you do install this backup, your internal "/sdcard" storage should no longer need the "nvidia" and "shield" folder, and you can delete those. They will most likely be recreated by some Shield services.
So on to installing and basic rundown in-case you past the above message and just want a bulleted list:
Installation:
Assumes the following:
1. Unlocked Bootloader
2. CWM installed
Installation procedure:
1. Download attached ZIP, extract to your internal SD card ("/sdcard") using the folder structure of "/sdcard/clockworkmod/backup/<extract contents of ZIP here>"
2. Boot into CWM and select backup and restore
3. Choose advanced restore
4. Choose minisculeShield, then "system"
5. Factory reset, wipe cache, data, and dalvik
6. Reboot and enjoy
Information on changes to original 4.2.2 ROM and other info:
- Removes OTA system
- Improves performance of streaming using original Dashboard, Shield Services, and Shield PC Streaming applications
- All but the most essential "system" apps are removed
- All "Gapps" are using Slimroms 4.2.2 Build 8 version
- Koush's Superuser/Superuser Binaries pre-installed
Download:
Version 0.5
Version 1.0 (OTA Enabled)
Version 1.0 (OTA Removed)

This is great. Will give this a shot today or tomorrow. Thanks!

themichael said:
This is great. Will give this a shot today or tomorrow. Thanks!
Click to expand...
Click to collapse
I'm glad, I thought people would be trampling each other to get a hold of some sort of fix to the remote streaming issue. I guess not. I know I was SUPER disappointed by the latest update for that exact reason.
Let me know if you have any problems, questions, or concerns. I am very new here, but I have been working with Android for almost as long as it came into existence. I started with Android 2.1, so I have learned a lot. I'm also a Unix (mainly the Linux variety) guy, so that goes hand in hand with Android.

I still get notification prompts for ota.

themichael said:
I still get notification prompts for ota.
Click to expand...
Click to collapse
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such

jarjarfinks said:
This prompt is a one-time thing, if you attempt the install it will fail and never prompt again. I attribute this to a probably data not being cleared for the actual OTA I removed before doing the Nandroid, but I assure you, I have never gotten it again, and never had to install it past that. Basically, if you attempt the install, it will not restart, but rather just disappear, and even upon restart will just boot normally. Let me know if you've tried that what happens, as I still am using this Nandroid, and since I did indeed attempt (and fail) installing that OTA, it has never prompted again, and stayed where it was during Nandroid in terms of system apps and such
Click to expand...
Click to collapse
Seemed to work. I'll let you know if anything changes.

same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can

milk070 said:
same here , ive been on the evo 3d for a long time and learned alot , ill keep you posted as much as i can
Click to expand...
Click to collapse
Is it me, or does the new GFE render the PC running it as "Busy" regardless of the version of the Android side? It was working prior to the GFE update 1.7.1.0, I just had to use the version of the PC Streaming, Dashboard, and Nvidia Shield Services apps in this Nandroid. It seems Nvidia has found a way to render it "Busy" the same problem I had before, no matter what ROM you use
Please test, and let me know, as I will have to find another way

[Discussion] NULL_ROM Official Q/A - FAQ- General Discussion thread

This is place where you can come and ask questions regarding support as well as any other general discussion for the Null rom. Please keep the development thread to just that DEVELOPMENT. The developer of this rom is here to develop and not here to answer your questions because you can't take the time to figure out the answer yourself. This will be a community driven thread. Therefore, if you feel something needs to be added to the OP please mention me in a post and I'll take a look
If you need to download the rom free to stop by the dev thread to download. However, if I see you ask a question in here and then go to that thread to ask the same question I will be handing out infractions. Please consider this your only warning.
On a side note, I'll be transferring the OP of this thread to a person with this device in due time. However, for the moment this needed to be created. If you are willing to take the OP from me please feel free to send me a PM. The only requirement that I would have is that you keep it updated properly.
FAQ / IT DOESNT WORK ! WAH
INTERNET ACCESS
GO INTO "FULL SETTINGS -> BLUETOOTH -> SELECT YOUR PHONE SETTING ICON (ON THE RIGHT OF PHONE NAME) -> TICK INTERNET ACCESS".
ENSURE BLUETOOTH TETHERING IS ENABLED ON YOUR PHONE BEFORE HAND OBVIOUSLY.
*NOTE* ENSURE YOUR MOBILE DEVICE SUPPORTS TETHERING, US VARIANT PHONES HAVE RESTRICTIONS INPLACE. REFER TO THE US INTERNET TETHERING THREAD.
*NOTE 2* BLUETOOTH TETHERING DOES NOT AUTO RECONNECT, INSTALL THIS THIRDPARTY SOLUTION ON YOUR GEAR TO ENABLE AUTO RECONNECT.
PLAYSTORE / GOOGLE ACCOUNT MANAGER HAS STOPPED..
VERIFY YOU HAVE A BLUETOOTH INTERNET TETHERING CONNECTION ESTABLISHED BEFORE ATTEMPTING TO ADD A GOOGLE ACCOUNT.
MUST NOT BE USING THIRD PARTY TETHERING, EG. PDANET.
HOW DO I FULL WIPE?
BOOT INTO RECOVERY MODE AND SELECT THE "RECOVERY" OPTION. DO THIS AFTER FLASHING THE ROM
UNABLE TO WAKE GEAR WHILE IN PHONE CALL
THIS IS CAUSED BY THE HOME BUTTON REMAP MOD, THE HOME BUTTON MUST BE PRESSED IN ORDER TO WAKE THE GEAR UP IN THIS STATE.
ONLY WORK AROUND IS TO EITHER USE THE WRIST WAKEUP GESTURE OR DISABLE THE HOME BUTTON REMAP MOD.
*NOTE* BY DISABLING THE HOME BUTTON REMAP MOD, THIS WILL DISABLE THE ABILITY TO MANUALLY LOCK THE SCREEN WHILE USING A CUSTOM LAUNCHER.
DOUBLE TAP BRIGHTNESS/SOUND TOGGLE HAS DISAPPEARED
THIS IS CAUSED BY USING THE FULL SYSTEM UI, SIMPLY PUT IT REPLACES THE DOUBLE TAP WINDOW WITH THE NOTIFICATION SHADE. BY USING GRAVITYBOX YOU CAN ADD ADDITIONAL TOGGLES LIKE BRIGHTNESS & SOUND TILES TO THE FULL NOTIFICATION SHADE.
OTHERWISE SIMPLY REFLASH THE ROM WITH THE FULL SYSTEMUI OPTION UNTICKED.
SCREEN FLICKERING/GITTERING
THIS IS CAUSED BY THE INITIAL BOOTUP, REBUILDING THE CACHE AND INITIALIZING ALL THE APPS. GIVE YOUR GEAR A FEW MINUTES TO SETUP AND RESTART.
SCREEN UNLOCKS TO NOVALAUNCHER PAGE PREVIEW?
GO INTO "NOVA SETTINGS -> GESTURES -> HOME BUTTON -> NONE".
ENABLE DEVELOPER SETTINGS / USB DEBUGGING
GO INTO "SETTINGS -> GEAR INFO -> ABOUT GEAR", TAP SOFTWARE VERSION 10 TIMES.
ENABLE UNKNOWN SOURCE APK INSTALLATION
GO INTO "FULL SETTINGS -> SECURITY -> TICK UNKNOWN SOURCES".
ENABLE MTP
GO INTO "FULL SETTINGS -> STORAGE -> MENU BUTTON (TOP RIGHT OF SCREEN) -> USB COMPUTER CONNECTION -> MEDIA DEVICE (MTP)".
WATCH STYLER NOT WORKING
ENSURE ITS SELECTED AS THE DEFAULT WATCHFACE IN GEAR MANAGER.
IF CLOCK FACE DOES NOT UPDATE UPON CHANGING, RESTART GEAR.
DOUBLE CLICK HOME BUTTON DOESNT WORK ON TOUCHWIZ LAUNCHER !
*NOTE* DO NOT DO THE FOLLOWING IF YOU ARE USING NOVALAUNCHER, YOU WILL NOT BE ABLE TO MANUALLY LOCK YOUR GEAR.
*NOTE 2* YOU CAN SIMPLY REFLASH THE ROM WITHOUT WIPING AND DISABLE THE HOME BUTTON REMAP MOD.
NAVIGATE/PULL THE FOLLOWING FILE FROM YOUR GEAR: /SYSTEM/USR/KEYLAYOUT/GPIO-KEYS.XML
EDIT IN A TEXT EDITOR SO IT LOOKS LIKE THE BELOW:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 116 POWER WAKE
[B]key 172 HOME WAKE[/B]
​

edit

Amazing. This thread is very much needed song as how the dev thread keeps getting cluttered with posts that wouldn't be there if some one would have read
sent from my Note 3 or Galaxy Gear

Yeah this thread is an awesome idea to leave the general discussion and support issues out of the other thread.

Whenever I select "recovery" it doesn't give me an option to install the rom?
I followed the steps for the root and the add the .zip to my SD card on the phone. When I select the option for recovery it just does a system restore on it. Any help?

You need to flash twrp first
sent from my Note 3 or Galaxy Gear

feature request
[what about to include support fpr AquaMail client?
I'm using it and I think it is the better at the moment
The developer could be interesting....

Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.

Pepski said:
Just a quick (somewhat noob) enquiry about the Gear and what this ROM can do for it, as I'm thinking of picking up a Note3 + Gear from work (Vodafone), as the watch is free.
Firstly, I hate Touchwiz with a passion! I don't wish for anyone to read that in an angry way, but I'm really not fond of the colours, themeing, etc. of that particular UI. I much prefer vanilla Android and, as such, would look to root the Note3 and install CM or an equivalent on it.
Would I then lose any functionality of the Gear? Can the GearManager APK be installed on a non-TW ROM?
I'll need a bit of an idiot's guide for the whole thing, but it's nothing I can't research.
Click to expand...
Click to collapse
No. Sadly not.
Or at least not with all the bells and whistles working.

I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11

ktetreault14 said:
I actually am testing CM11 on my note 3 as I type. I was wondering if someone could link me to the latest gear manager so I could test how it works.
Sent from my Note 3 w/ CM11
Click to expand...
Click to collapse
Here's 2 versions. The latest and the previous one, a lot of people are having problems with the latest, and even Samsung supposedly admitted it was bugged and they were going to release a new one. The previous version seems to work fine for people, and there's no real functional updates on the latest one anyway, so you might prefer it.
Latest version - 1.5.121601
Previous version - 1.5.120903

I couldn't get cm11 to download the necessary apks for gear manager so I restored a tw backup and backed up the apks themselves. When I went to restore them the only ones that would not restore were the weather and svoice. It is paired now with gear manager running in the notifications. Still testing out what works and what doesn't
Sent from my Note 3 w/ CM11

Running 16, removed Ms. Pac-Man for running too slow on the Gear, everything's running smooth.
Sent from Spaceball One.

I have nexus 5 rooted and running null16, could anyone please point me out how to make gear manager to work?has anyone made notifications work? so far i can just make calls from it and syncs the time.I have read everywhere but nothing works so far and i can't seem to find a reliable sorce of information. If we could make something like an app and null to be modified to work with that so we lose gear manager dependency i belive that would be a game changer . Fomey i will donate something pretty soon as i allways apreciate work from people creative like yourself .
EDIT: 15 AUD for you Fomey, thank you for your work !

reboot after install of null_16
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.

ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Read.

ernie36564 said:
i have attempted several times now to install the null_16 on my galaxy gear. after each time i attempt to go into the recovery mode to actually install it, it reboots and resets the device. i have read numerous times to flash the null_03_TWRP2.7.tar.md5 file and i have done this with odin and received a pass at the top left of the odin program and then it reboots the galaxy gear. i then install the null_16 file on the root of the sd card directory with wondershare mobilego (left zipped as noted in several videos i have watched) after this i remove device from charging device and this is when i try to go to recovery modeto install. after getting to recovery and holding power button for approximately 3 seconds and release this is when it reboots and has reset itself. any help would greatly be appreciated and yes it is rooted with supersu. I am sure i am doing something wrong but not sure what.
Click to expand...
Click to collapse
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears

OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
eroracing said:
Download mk7 for your country.... I don't care if you are already on it just do it! Flash with Odin then flash twrp recovery..... Use adb to boot to recovery....... Trust me it works!
Sent from my Note 3 SM-N900A rooted by Designgears
Click to expand...
Click to collapse
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
almulder1092 said:
Installing Null_ TWRP: (Version as of this tutorial is Null_ 03 TWRP)
Thanks to fOmey for this Null_ TWRP
Installing Null_ TWRP:
Preparation:
Download Null_ TWRP - fOmey
READ THE NULL_ TWRP Original Post
Installation:
Put your Gear into Download Mode
Connect your Gear to you PC.
Open Odin
Click on the PDA Button
Locate the Null_ TWRP file and select it. (It should be a .md5 file, if it is zipped, then unzip it)
Press Start
Once it is completed it will reboot the gear.
Null Quote:
If you find the recovery is not sticking & your Gear wipes when attempting to access recovery after flashing, you must root your Gear prior to installing TWRP again & Run the following commands in ADB:
*NOTE* You will gave to accept a supersuser request popup when executing "SU" command
*NOTE 2* Probably a good idea to run this prior to first installation (To save time)
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
ADB stands for Android Debug Bridge
If needed "ADB" can be found here on xda - Thanks to shimp208​​
.[/CENTER]
Click to expand...
Click to collapse

gypsydigi said:
OMG i got it running!
thanks so much for all the work done with this rom... Everything seems to be running perfect...
At first i couldn't get it to flash properly... I was trying everything. Took hours to initially get the recovery going. It ended up being a driver issue and after a lot of reading and troubleshooting i was finally able to get it up and running.
One question that i have that i couldn't find the answer too... Is there any way to have the watch widget (either the stock clocks or watch styler) appear as a full screen widget without the launcher or the status bar at the top... yet keep the status bar and launcher on the other pages? I am assuming that i can't do it after reading countless of pages... Because i do like the full screen watch face.
Thanks again for all the hard work!
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
I had to follow this step in order to get the recovery to stick. No matter what i did including flashing the stock recovery then flashing twrp i couldnt get it going until i did this:
Click to expand...
Click to collapse
You cannot do what you are asking.... But you can set clock widget. Use Nova settings to hide notification bar, dock and scroll indicators then use gesture and button settings to create gesture to accommodate just about anything! I have swype down to open notification bar..... Swipe up open notification app.... Double tap opens app drawer and 2 finger Swipe up opens my dialer! Just set widget long press and resize to full screen. You may have to adjust colums and rows in Nova settings to accommodate whatever widget you are using in order to center properly. Hope this helps!
Sent from my Note 3 SM-N900A rooted by Designgears

On the newest release (16) there is support for custom boot animation and includes the null boot animation. Is that a part of the aroma installer or is the custom null boot animation a part of the rom that you cannot remove? I'd rather stick with the stock if you don't mind.

Schiziodd's ROM flavors for HTC desire

in the subsequent posts below, you will find all the info you need for not only the device but the ROMs I have had my hands in.
each person who I pulled the files from will get a thanks in the posts as necessary

NonSense 1.04
Disclamer: these files are meant specifically for the HTC Desire 510. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures. what has been included in this tutorial is for the HTC Desire 510
You have been warned.
note: from now on CRI signifies cricket, and B-S signifies sprint/boost if those signifiers aren't used, it applies to both type of this phone
now to the goodies.....
List of supplies:
1. Phone (HTC Desire 510)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. the zip files from this location. click here
4.1 there are 2 different versions of the same ROM, but the *1.04-lean.zip is US only (refer to changes to see why).
4.2 CRI for cricket/att, B-S for boost/sprint
5. read these instructions completely before attempting
before we get started make sure you have supersu (which can be downloaded from here), and NonSense1.04.zip copied to the root of your external SD card
NETWORK UNLOCK (I.E. switching services)​
as this phone is LTE compatible, it takes a SIM card no matter the service to receive calls and data. so it stands to presume all you need to do is network unlock the device (Sprint calls it UICC unlock, others it's the Network Unlock Code)
the phone needs to be network (SIM) unlocked in order to switch it from cricket to sprint, or from sprint to virgin mobile, etc.
to network unlock the phone:
1. make sure you are on stock ROM (the one that came with the phone, not the one listed in this post nor CM)
2. call the respective original service provider of the phone (i.e. cricket, sprint, etc.) and tell them that you are leaving the country (like to Australia) and you want to unlock the SIM so you can use your device for service down there.
2.1 if you bought the phone second-hand or don't have service on it, you will have to find a reputable unlock service online
2.2 for sprint customers, your account HAS to be at least 6 months old before they will give you the UICC(SIM unlock) code
2.3 for boost customers, your account HAS to be at least a year before they will give you the UICC(SIM unlock) code
3. once you have the SIM unlock code, pull battery from phone, remove the original SIM, put your services respective SIM in (i.e. originally a cricket phone now running a T-Mobile SIM), put in battery, boot phone, and enter the unlock code where it asks.
4. once your back into device, you'll notice you will have no data.
4.1 what needs to be done is to program the APN (google will be your best friend here - for example sprint lte apn settings, or T-Mobile lte apn settings).
5. now that you have the APN settings, you can program them into the phone.
5.1 APNs can be found in the device by going to settings, then mobile data, clicking on access point names. in there in the upper right hand corner should be 3 dots that are verticle. click on that and then on new APN.
5.2 add the respective settings, click save and then make sure it has a green dot next to it.
6. sit back and enjoy the fruits of your labor
APNs for this device can only be written once the phone has been UNLOCKED and the original (cricket) service providers SIM is NOT inserted, and your using another service Provider ( sprint, T-Mobile, etc.) SIM.
UNLOCKING BOOTLOADER​
1. for the drivers, use the ones contained here in the HTCDrivers.zip and extract them to the desktop
1. extract and use the file contained in adb.zip to flash unlock token
2. follow this tutorial and choose all other supported devicess when it asks about device.
INSTALLING TWRP AND KERNEL​
in the adb file you should notice a file called recovery.img. that is TWRP recovery for the device
there is also a file called boot.img. this will allow read/write permissions at the System level once root is obtained
if you have either the sprint, boost or another service provider's variety of this phone, try flashing their respective kernel after you install the ROM or before you root (no guarantees that flashing the respective kernel will work. as I have the cricket variety of this phone, I am only developing for that one)
1. from home screen, go to settings and scroll down to power and then scroll all the to the bottom of that and uncheck "fast boot"
2. shut down phone completely
3. go back into fastboot (vol down + power)
4. Select fastboot from the menu list and press the power button.
5. open command prompt and use the CD command to get it to the root of the adb folder (CD C:/users/sky/desktop/adb).
6. plug in device and wait for it to say fastboot USB
7. type in command prompt "fastboot flash recovery recovery.img' (should complete within 4 seconds)
8. in the same command window type "fastboot flash boot boot.img" (should complete within 4 seconds)
8.1 step 8 can be skipped if your just flashing *NonSense1.04*.zip
9. pull battery once that is completed and put it back in.
10. power device on (skip this step if rooting)
OBTAINING ROOT (can be skipped if installing NonSense1.04 as it's already rooted)​
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the supersu update package.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load
INSTALLING NonSense 1.04​
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the NonSense1.04.zip.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
3.1 beware, it may take a bit to install. just be patient, it's working.
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load. be forewarned, it may take about 15 minutes to load
CHANGES​
CRI versions
1. DEODEXed the ROM
2. added external SD support into the ROM
3. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
4. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
5. added more stable kernel to flash file.
6. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, and Viper4android (DSP/equalizer)
6.1 all apps that have been listed in 6 can be uninstalled without the need for root
7. root and SU have been added and are up to date in this rom as of 11:45PM MST on 3/1/215
8. added apns-conf.xml from CyanogenMod
9. got native APP2sd support thanks to pattyboi's kernel
B-S versions
1. mostly DEODEXed the ROM
2. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
3. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
4. added more stable kernel to flash file.
5. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, Wifi Tether, and Viper4android (DSP/equalizer)
5.1 all apps that have been listed in 5 can be uninstalled without the need for root
6. root and SU has been added
*1.04-lean
list of removed apps
1. Dropbox (can be found in playstore)
2. Google plus (can be found in playstore)
3. Hangouts (can be found in playstore)
4. HTC Dot View(can be found in playstore)
5. keyboard language packs for Arabic, Chinese, English UK, French, German, Greek, Italian, Portuguese, Russian, and Spanish (not in play store) if needed, flash language.zip found here
6. VPN dialogs (not in play store) if needed, flash missing.zip found here
7. HTC Zoe (can be found in playstore)
BUGS​
CRI versions
1.USB internet pass-through not working
2.WiFi direct (miracast) not working
3. want to get rid of annoying volume too loud warning
B-S versions
1. native hotspot says internet when connected to win 7 machine, but will not allow it to go through. Have included wifi tether as a workaround until the issue can be resolved
THANKS​
CRI versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing a more stable kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, CraviingCritic for providing the original ROM in which this wouldn't be possible
B-S versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing the current kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, LarryBoyG for providing the original ROM in which this wouldn't be possible
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.
I will also be keeping the links updated for as long as I own the device (being that my HTC Desire 510(Cricket) is network unlocked, that may be a long time - or until I get a better device).
UPDATES​
for those of you who have downloaded the ROM since first release, I will include an CRI_NSupdate.zip or B-S_NSupdate.zip file found here. it will include the changes I have made to the rom since it's initial upload.
the file by the name of NSupdate.szip will include update that pertain to both the CRI and B-S ROMS
to install the updates, just put the update file onto the root of the SD card, reboot into recovery, choose install, pick the update file, swipe the blue button on the bottom, reboot and enjoy.
EDITING THE BOOTUP​
location of files mentioned is in /system/customize/resource
to change boot animation
1. find your favorite boot animation
2. rename it to AIO_bootup.zip
3. copy/move and overwrite the original with a root explorer to /system/customize/resource
to change the boot sound
1. find a sound file you like and want to hear every time the phone boots (can be changed at any time)
2. convert it to wav (the file has to be wav in order for the phone to recognize it)
3. rename it to CRICKET_LOGO_24bit28k_STEREO.wav
4. copy/move and overwrite the original with a root explorer to /system/customize/resource
reboot and enjoy...
THINGS NOTICED WHILE CREATING ROMs​
1. both (cricket and boost/sprint) phones are exactly the same except for the boost/sprint ones contain a CDMA chipset.
1.1 the only things I had to change from the cricket rom to the boost rom was apns.xml in framework-res, apns-conf.xml, and the preferred network type in build.prop.
2. all kernels work for both (US) versions
3. the same recovery is used on both (US based) devices
so essentially, if we develop for the boost/sprint version of the device, change a few things, it will be ready to roll for the cricket version as well
TO FIX NATIVE TETHER ON B-S VERSIONS​
1. Install Script Manager – SManager app from the Play Store.
2. Open the app and grant it root access when prompted.
3. Now, navigate to /system/etc/init.d and tap “tether” script.
4. Click on SU and Boot (Android skull and gear icons, respectively)
5. Click on Run and Save options.
The issue should be fixed now. Reboot and enjoy!
thanks goes to qwerty6532 and LarryBoyG for the fix. now to add that permanently to the ROMs and then they'll be absolutely stable enough for me to be happy and start working on CM11

CM11
I will be building CM11 for the device for both the cricket and boost models. look for the info here as I update it a I need
****edit**** ok so I figured out some of the issue with CM11 not wanting to install apps. I got the internal memory pulling the 1.1 gbs but now I need to symlink the external memory where it goes.
****edit**** so I have figured out what needs to be done...... the kernel for CM11 needs to be built from the ground, up (or one needs to be built that is compatible with it). i'll upload the current one that fixes the memory error (look in downloads).

reserved
so as i have not been actively developing on the phone i will no longer supply updates. all flash files are up to date as of 8 months ago and should be working with out an issue.

again, reserved
same to you...

This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.

Burtrum57 said:
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Click to expand...
Click to collapse
if I had a 64-bit version for this device, I would have it out as soon as I could. and thanks

Great job. Off and running now

I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app

Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.

CSP III said:
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
Click to expand...
Click to collapse
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot

qwerty6532 said:
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Well it's added to it. It just needs to be activated for now until I can figure out how to add it to automatically start from the first run of the Sprint/boost ROM

schizoidd said:
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
Click to expand...
Click to collapse
Sorry, not following "wipe the system partition" ???

CSP III said:
Sorry, not following "wipe the system partition" ???
Click to expand...
Click to collapse
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset

schizoidd said:
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
Click to expand...
Click to collapse
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.

CSP III said:
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
Click to expand...
Click to collapse
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine

schizoidd said:
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
Click to expand...
Click to collapse
Right on buddy. I'll take you at your word on it. I've never had to do that before so it naturally made me a little nervous. Not that I couldnt have just restored a backup, but still . Many thanks.

Problems
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.

schizoidd said:
I
for those of you that build the kernels, do you think u can build one that is AOSP and compatible with the device for android 4.4.4?
Click to expand...
Click to collapse
we cant really do a "aosp" kernel because of htc's modifications to the board and pins,and they have their own dtb issues...im 99% sure mine works with android 4.4.x because of larry using it in gpe,just repack the ramdisk the zimage and it should be okay

Bobby060 said:
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
Click to expand...
Click to collapse
If you're going from bone stock to this, you need to do a factory data reset. Just make ssure you back up your data and use nandroid manager to pull it data back into the new ROM

Fix dec 2016/jan 2017: Snapchat on rooted android device running xposed.

POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.

Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.

Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.

It didn't worked. S7 edge exynos (6.0.1)

Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.

hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?

Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.

AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.

Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?

Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.

Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.

Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.

immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!

Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.

just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)

ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?

Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily

Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.