Database Users

[Q]Defy+ Custom Roms

Hi guys.
O have a Defy+ phone with Android 2.3.6 onboard
(4.5.1-134_DFP-231)
Pls help me. I cant fully understand how to flash any custom ROM on it?
Root and 2ndinit installed, but i can't install CM9 or AOKP rom for example.
I am booting to 2ndinit, entering recovery, do nandroid backup, do full wipe flash zip from SDcard, flash kernel( from this thread), and finally reboot. And got continious reboots.
What am i doing wrong?

are you wiping cache and dalvik cache after you install the rom? try this and it should boot. Also for CM9 dont install the bootloader. It did not work when I tried to install the bootloader, but fine when I installed without it.
I would try the latest CM7.2 from quartx I have the apr release and its fast, stable and I have had no trouble with it. Well apart from the baseband switcher in the options would not save the changes so had to install the app for it.
here is the link if you are not sure where to get it from
http://quarx2k.ru/cm7-nightly-defy+/?C=M;O=D
just put it on the root of SD card
boot into recovery (2ndinit or CM)
you can back up your data if you want (but sounds like you have done this so the file should still be there)
factory reset and wipe cache and dalvik cache
go to zip from sd and file from sd and zip the new ROM
wipe cache and dalvik catch
reboot.
Oh you can install gapps straight after CM7.2 as well if you want gapps on your phone
here is the latest gapps for CM7
http://goo.im/gapps/gapps-gb-20110828-signed.zip

Thanks, man, i'll try it. Will post a review later.

yeah if you install gapps you can do this straight after the CM7.2 flash
so once cm7.2 says its finished
go back and into install from sd select the gapps zip
install that (only about 9mb so wont take long)
then clear cache and dalvik cache
reboot.
All these ROMS might take upto 10mins to boot first up but thats normal.
if you installed Gapps it will ask you for your account details. Gapps only installs google play app and the google sync for your phone and contacts so it cant resync your contacts (there is a option to sync your apps.
I would choose not to do this as I ended up with 40 apps and most I didnt want lol. If you go into google play and hit the menu button (bottom left on the phone) and select my apps they will have all the apps you have installed and you can select the ones you want instead of having them all install at once then removing the crap ones.
I run V6 supercharger script and have the power control widget on the main screen so I leave everything off and set network to 2g unless I need it and I get 3 days out of the phone easy usually have like 20% left after day 3. So cant complain about battery.

kelbygreen said:
yeah if you install gapps you can do this straight after the CM7.2 flash
so once cm7.2 says its finished
go back and into install from sd select the gapps zip
install that (only about 9mb so wont take long)
then clear cache and dalvik cache
reboot.
All these ROMS might take upto 10mins to boot first up but thats normal.
if you installed Gapps it will ask you for your account details. Gapps only installs google play app and the google sync for your phone and contacts so it cant resync your contacts (there is a option to sync your apps.
I would choose not to do this as I ended up with 40 apps and most I didnt want lol. If you go into google play and hit the menu button (bottom left on the phone) and select my apps they will have all the apps you have installed and you can select the ones you want instead of having them all install at once then removing the crap ones.
I run V6 supercharger script and have the power control widget on the main screen so I leave everything off and set network to 2g unless I need it and I get 3 days out of the phone easy usually have like 20% left after day 3. So cant complain about battery.
Click to expand...
Click to collapse
WOW!Thet's...cool!I'll try to install in in a couple of hours!

yeah not sure if its the script that helps or what. I dont use the phone to much few short calls a day and hook it up to the car stereo when I am driving around. I would get to know the ROM first if you like it mod it further. but always do a nandroid backup first. If something happens then you can always revert back.
CM9 looks good and all but to me the usability of cm7.2 far outweighs the cm9. I have modded mine own theme to so its not like you are stuck with whats installed at first boot.
here are some screens of mine
{
"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"
}

Works great man!thank you! started in 2 minutes.fast smooth and ver-very customizable! Now will deeply explore CM7.2!

glad you like it. Its the best ROM so far I have tried and I been threw ICS, whiterabbit and a few others but all have problems in everyday use and I wanted something that you dont have to keep restarting things coz they freeze all the time.
cm7.2 has worked for everything I have tried so far.

[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...

Xposed Lollipop Modules

I decided to start this thread to share our experience with different modules in exclusive for our Moto X 2014. There is one post talking about Lollipop compatible modules http://forum.xda-developers.com/xposed/xposed-lollipop-compatible-modules-t3032184, but is way to general and sometimes, at least for me, when a module says is compatible and after installed I enter in bootloop and in the worst escenario, I had to flash my system again (5 times by now).
So, if you want to share your experience and different configurations just remember to share your settings, such as:
Settings
Firmware version
Android version
Module and version
If the module is reported as not working but you can make it work, share how you did it.
Anything usefull
My own experience so far.
Android 5.0.2 stock version
Us cellular firmware
None system tweaks or modified
Modules working.
1. Lollipop power menu: Add more options to the power menu. Link. http://repo.xposed.info/module/com.pyler.lollipoppowermenu
2. LPThemer: Working partially, if you try to change "system" colors after a reboot the phone stuck at boot logo, you can solve it by entering recovery and fixing permissions; once you are on the LPThemer menu again, just revert changes. http://repo.xposed.info/module/com.vikas.lollipop.themeLink.
3. Moto XCamera+: Enables the hidden settings for stock motorola camera app. link http://forum.xda-developers.com/showpost.php?p=59174759&postcount=32
4. Amplify. Extend your battery life. Link. http://repo.xposed.info/module/com.ryansteckler.nlpunbounce
5. GravityBox. A bunch of mods for your phone. Link. http://repo.xposed.info/module/com.ceco.lollipop.gravitybox
6. GEL. Hide Google search bar, hide apps from launcher, change grid size of homescreen and app drawer. link http://repo.xposed.info/module/de.theknut.xposedgelsettings
7. Heads up hide. Hides (instead of dismissing) heads up notifications. Link http://repo.xposed.info/module/com.lewisjuggins.headsuphide
8. Lolistat. Lolistat automatically detects the color of an app and turns the status bar color into a slightly darkened one right in the Lollipop style. Link. http://repo.xposed.info/module/info.papdt.lolistat
9. YouTube AdAway. get rid of YouTube ads and branding layers. Link. http://repo.xposed.info/module/ma.wanam.youtubeadaway
Modules Not Working.
1. Amplify. Phone stuck at logo.... Reported as working in Pure edition 5.0
2. AppOpsXposed. Phone stuck at logo.
As @grad061980 says, if your phone enters in bootloop go to the third post to try to solve it.
I will add more modules as I test them or you guys post your experience.
Thanks in advance.

mine
mine

XT1093 US Cellular
Android 5.0.2
Unlocked & rooted
Xposed modules I have active are in the screenshot attached. Only issues I have had is the phone hanging at the carrier boot animation (US Cellular 4g). I've had the issue with all of the modules I have active hanging on first reboot. Two ways to get around the bootloop.
1 ) press & hold the power button until it reboots. If that didn't work, then
2 ) press & hold the power button & when the phone shuts off press power button with volume down to enter the bootloader. You have 2 options here. You can select normal startup & see if the phone boots (it has for me a couple of times) or you can select recovery (TWRP for me) & wipe caches - I do dalvik cache & partition cache & reboot. It has yet to fail to boot after this wipe.
Greenify & X-Blast didn't work the last time I tried.
{
"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"
}

grad061980 said:
XT1093 US Cellular
Android 5.0.2
Unlocked & rooted
Click to expand...
Click to collapse
where did you get the moto x module? I cannot find it
thanks

Latest beta of greenify works

juliospinoza said:
I decided to start this thread to share our experience with different modules in exclusive for our Moto X 2014. There is one post talking about Lollipop compatible modules http://forum.xda-developers.com/xposed/xposed-lollipop-compatible-modules-t3032184, but is way to general and sometimes, at least for me, when a module says is compatible and after installed I enter in bootloop and in the worst escenario, I had to flash my system again (5 times by now).
So, if you want to share your experience and different configurations just remember to share your settings, such as:
Settings
Firmware version
Android version
Module and version
If the module is reported as not working but you can make it work, share how you did it.
Anything usefull
My own experience so far.
Android 5.0.2 stock version
Us cellular firmware
None system tweaks or modified
Modules working.
1. Lollipop power menu: So far, working with out problems. Link. http://repo.xposed.info/module/com.pyler.lollipoppowermenu
2. LPThemer: Working partially, if you try to change "system" colors after a reboot the phone stuck at boot logo, you can solve it by entering recovery and fixing permissions; once you are on the LPThemer menu again, just revert changes. http://repo.xposed.info/module/com.vikas.lollipop.themeLink.
Modules Not Working.
1. Amplify. Phone stuck at logo.
2. AppOpsXposed. Phone stuck at logo.
I will add more modules as I test them or you guys post your experience.
Thanks in advance.
Click to expand...
Click to collapse
Hey Amplify works great for me. I use Amplify, GB, GEL , and LP THemer

ewalk4866 said:
Hey Amplify works great for me. I use Amplify, GB, GEL , and LP THemer
Click to expand...
Click to collapse
Can you share what version of android you are using. Because in 5.0.2 is not working at all.

juliospinoza said:
Can you share what version of android you are using. Because in 5.0.2 is not working at all.
Click to expand...
Click to collapse
Yep I have the pure running 5.0 stock

juliospinoza said:
where did you get the moto x module? I cannot find it
thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=59174759
I ended up just installing the Xposed module & it enabled the extra settings in the stock camera. Plus I can now keep the twist to open the camera.

piccit said:
Latest beta of greenify works
Click to expand...
Click to collapse
Where that apk? I don't see it in the xposed download section.

matt99017d said:
Where that apk? I don't see it in the xposed download section.
Click to expand...
Click to collapse
It's the Greenify app itself. Opt in for the beta in their Google+ community

Did anyone use lpthemer? can we change the white backgrounds of the system apps with it?

Rzr92 said:
Did anyone use lpthemer? can we change the white backgrounds of the system apps with it?
Click to expand...
Click to collapse
Is not working for me. All the others colors are working good but this one.

I can't even makes works xposed where did you get the link?

crisout said:
I can't even makes works xposed where did you get the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3030118
Flash the zip and after the reboot install the apk.

juliospinoza said:
http://forum.xda-developers.com/showthread.php?t=3030118
Flash the zip and after the reboot install the apk.
Click to expand...
Click to collapse
I always get: installation is only possible manually via recovery for now.
And I did what you told me.

crisout said:
I always get: installation is only possible manually via recovery for now.
And I did what you told me.
Click to expand...
Click to collapse
Do you get this screen?
If you see it, although says that message, the frame work is working. No matter the message

juliospinoza said:
Do you get this screen?
If you see it, although says that message, the frame work is working. No matter the message
Click to expand...
Click to collapse
Thank you so much! You have no idea how much I was missing gravitybox ?!

GB alpha 2 made all my quick toggles disappear. Had to roll back to alpha 1 to get them back. Pure 5.0.

diggitydogg said:
GB alpha 2 made all my quick toggles disappear. Had to roll back to alpha 1 to get them back. Pure 5.0.
Click to expand...
Click to collapse
I think you just have to set them up again. I started with alpha 2 and had no problems

Success rooting SM-P900 Knox 0x0 (SuperSU)

I finally managed to root my SM-P900 without tripping knox and it survives a reboot. I'm running the OH2 Lollipop ROM and used the latest PC version of Kingoroot. This installs their own version of Superuser and I have been able to use Titanium Backup to remove Knox and other bloatware. I previously tried and failed with multiple Android versions of Kingroot and Kingoroot.
I'm not 100% happy having the Kingoroot software on my tablet (or my PC for that matter) as I'm unsure about privacy and security issues so I decided to try to install SuperSU instead and remove the Kingoroot files. First of all I tried running Flashfire but it said that the tablet wasn't rooted with the version of Superuser it requires. I then tried running Super Sume but it reported that the tablet wasn't rooted with Kingroot or Kingoroot. Next, I tried installing SuperSU from the app store but it got stuck at downloading the binaries so I removed it. Next, I installed the Kingoroot app and ran it - it reported that the tablet wasn't rooted (!) and when I ran it it then reported it had successfully rooted. I then ran Super Sume again and this time it ran but eventually hung and there was no sign of SuperSU having been installed. Next, I ran Flashfire and this time it obtained root and appeared to run successfully. I attempted to flash the stock OH2 ROM with it and inject Superuser but just ended up with a black screen and non-booting tablet. I then needed to re-flash the ROM with Odin and this obviously removed root.
So I think my next step will be to do a factory reset on my rooted and de-bloated tablet which will give me a sort of satisfactory outcome, i.e. a safe and secure ROM with no Knox or bloatware. But if anyone has any ideas about replacing the Kingoroot Superuser I'm all ears!
EDIT my next step is to try the manual method of running scripts here http://androidforums.com/threads/script-replace-kingoroot-with-supersu.919175/ but this was written for a different device running Kitkat so I'm not sure how it will go.

I've cracked it! The script method above didn't work. Here are the steps I took:
1. Factory reset tablet then allowed it to do an official update to OI1
2. Enabled USB debugging & installation of unknown apps
3. Ran the PC version of Kingoroot (not Kingroot)
4. Installed Titanium Backup then used it to uninstall all Knox software then rebooted
5. Installed & ran Kingroot 4.9 http://www.appsandroidapk.com/tools/kingroot/ and used it to root the tablet again
6. Installed & ran SuperSUme (paid-for app) which removed the Kingoroot and Kingroot SU apps and installed SuperSU
7. Updated SuperSU binaries and rebooted
Remember to turn off automatic updates otherwise your tablet's status will change from Official to Custom.
Screenshots attached!
{
"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"
}

Hello on step 6 SuperSume doesn't seems to progress at all, while all the other steps seems to be fine, I'm using supersume 9.3.8, is it normal or is it like VERY long ?
PS : tried with the exact same versions you used, still the same, the progression bar increase a bit then got stuck at 10% Tried also to uninstall with SuperSu, instant crash...

Ok, I tried and it tripped Knox here...

Sorry about your Knox flag being tripped
It all worked smoothly when I did it on mine, Kingoroot did its stuff in a few minutes and SuperSUme took less than 2 minutes to finish. Not sure what happened with yours. Mine is still running well, rooted and Knox 0x0.

dwl99 said:
Sorry about your Knox flag being tripped
It all worked smoothly when I did it on mine, Kingoroot did its stuff in a few minutes and SuperSUme took less than 2 minutes to finish. Not sure what happened with yours. Mine is still running well, rooted and Knox 0x0.
Click to expand...
Click to collapse
Don't worry it's not under warranty anyway, I guess I left a knox soft before putting twrp and that might be the reason. Now I'm on cm12.1 and running fine. I'm pretty sure, the reseller would give me 100€ for that tablet anyway, so I better keep it for myself !

That explains it, any modded recovery will trip Knox no matter what you do. I still have stock recovery.
Sent from my SM-N9005 using Tapatalk

Im finally ready to root my tablet, Im tired of all of the lag I get and it seems as Samsung has let the 12.2 pro die.
Im running 5.02
Build: LRX22G.P900UEU1COL1
Kernel: 3.4.39-5574008
Knox: 2.3
USA version
Will this root method work without issue for me?

It should do
Sent from my SM-T700 using Tapatalk

I'm curious, will this method work just on P900 or all variances?

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...