Database Users

Market on Stock TNT Rom Gtablet

Market on stock Gtablet Rom
After alot of research i got this to work.
Try at your own risk!!!
First root with Z4 root. This is totally reversable.
Next find and download gtab_tnt_lite_v2.00 and unzip to your computer. Go to update, system, app and copy the files below to your gtablet. Go to ES file explorer and install the apps listed below manually in the order they are numbered. Then reboot . Pick setup wizard after reboot and follow instructions for google.
1. GoogleServicesFramework.apk
2. OneTimeInitializer.apk
3. SetupWizard.apk
4. Talk.apk
5. Vending.apk
6. Gmail.apk
7. Maps.apk
Next
- Get a copy of Titanium Backup and sideload it (free version is fine).
- Make sure the Market is working with your Google ID, of course.
- Go into Settings -- Applications -- Manage Applications and Force Stop both the Market and Google Services Frameworks apps.
- In Titanium Backup, go into "Backup/Restore", look for "Google Services Framework 2.2", click on it and then choose "Wipe Data". Then go back to the home screen.
- Run the Market app. You should get an error (that's a good thing, as that's what we want. If you don't get an error, re-try the steps above until you do).
- Reboot, and wait at least a minute after the OS is up to let things stabilize.
- Run the Market again. You should see an immediate difference.
Enjoy

http://forum.xda-developers.com/showthread.php?t=842590
Post #1

duplicate post

Well this is just for the folks that dont want to have to mess with having to flash through recovery.

frankie_pr1 said:
Well this is just for the folks that dont want to have to mess with having to flash through recovery.
Click to expand...
Click to collapse
You get the most up to date gapps from the link provided. You can extract the same files from that zip.
You are less likely to have problems using the current gapps and installing through recovery than manually copying and pasting files.
There are several existing threads that cover this process already.
http://forum.xda-developers.com/showthread.php?t=889659

Closed, as there are already multiple threads that cover this subject.

Still can't delete stock apps

Followed this guide to downgrade: http://android.modaco.com/content/h...-r4-htc-legend-rooting-guide-now-with-1-31-x/
And then loaded this ROM: http://android.modaco.com/content/h...o-rom-for-the-htc-legend-with-online-kitchen/
Looking for a free method to delete stock apps.

Taking a stab in the dark here and saying because you flashed a Sense UI ROM you won't be able to delete them as they're integrated into the system. Try another ROM which isn't Sense based. I suggest CM7 RC2, which you can find by exploring cyanogenmod.com.

segphault said:
Taking a stab in the dark here and saying because you flashed a Sense UI ROM you won't be able to delete them as they're integrated into the system. Try another ROM which isn't Sense based. I suggest CM7 RC2, which you can find by exploring cyanogenmod.com.
Click to expand...
Click to collapse
Oh... I'm loading CM6 just now.

Alrighty. Make sure you flash the gapps package from the cyanogenmod wiki too if you want google apps integrated into your system. Flash it right after you've flashed the CM6, while still in recovery.

segphault said:
Alrighty. Make sure you flash the gapps package from the cyanogenmod wiki too if you want google apps integrated into your system. Flash it right after you've flashed the CM6, while still in recovery.
Click to expand...
Click to collapse
Oh I was past that stage on my last post.
Anyway, I still can't remove things through adb shell - tried removing the Voice Dialer as a test, but it said "directory not empty".

In which case I'm stumped. Someone else will know.

As long as you have root access it doesn't really matter what ROM you're running, you should still be able to move and/or remove system apps, just keep in mind that some of them are essential for the system to run properly. Even if you are using a Sense based ROM, you can still removed many system apps such as widgets and things like friendstream, flickr, footprints, etc.
There are two (or probably more) simple ways of going about removing system apps. The easiest, if you have successfully flashed S-OFF, is to use Root Explorer and simply move or delete whatever app you want.
If you're not S-OFF, you can use adb shell to move a system app to data partition (or anywhere else you want to push it to), and to delete a system app if that's what you're looking to do.
To remove an app in adb, you must first mount /system partition, then you can use the command "ls /system/app" to show a list of all apps installed in the system partition. To remove an app, follow the syntax "rm /system/app/AppName.apk" (obviously replacing AppName.apk with whatever app it is you're trying to remove.
To move an app from /system/app to /data/app use the following syntax:
"mv /system/app/AppName.apk /data/app/AppName.apk"

I wasn't in recovery mode to do my deletes.
This should be stickied: http://android.modaco.com/content/h...apps-from-the-htc-desire-with-adb-in-windows/

[Script]New "Low Storage" Notification fix

Here we go !
Starting point is from CyanogenMod Captivate forum and some improvement were added here and there. Credits are recalled and came from this thread : [SCRIPT][CM7/9] /datadata/ low storage notification lagless fix - init.d script.
Background :
CyanogenMod (CM) based roms on our I9000 (and brothers) uses a small and fast flash chip to store application datas. This make the rom smooth and sweet ... This chip is mounted as /datadata and is about 170Mo.
With a lot of apps (or apps storing lots of stuff there) we faced a "Low storage" notification and our phone becomes laggy.
The first idea was to move this /datadata to /data (about 2Go) whose have a lot of free space. This works but the phone became laggy.
Then some others devs think about moving back to /datadata frequently accessed files (sqlite database and xml preferences files). First as scripts part then as flashed zip file. The phone becames smoother but not like a "vanilla" CM rom. This is the 1103 datafix in thread linked previously.
An xda user suggested to let on /data only library files and move back all other stuff to /datadata. These lib files are only accessed (when used by users) in read mode so the ext4 /data partition is efficient in this way and phone becomes smoother as "vanilla" CM roms. This is the 2903 datafix I made and post in previously linked xda thread.
But with this latest datafix, applications cache are stored in /datadata and recent Google apps (like Chrome) fulfilled it quickly : the "Low storage" notification is back !
Next solution :
Like 2903 datafix, only libraries ("lib" and "libs" subdirectories) stay on /data by default.
BUT unlike it you could choose which apps will also store their cache in /data. And this is REVERSIBLE : if one of selected app becomes laggy you could move back its cache onto /datadata
How to use it :
Make a nandroid backup
Just grab the zip file and flash it in recovery
At reboot, it will revert previous datafix (if there is one) and apply this one. So first boot could take more time (5 minutes max) than "normal" boot.
It also creates a "datafix" directory in /data/local with two files : "move_cache.txt" and "skip_apps.txt".
Just edit the first file (root needed) to add apps whose cache will go back to /data at next boot :
Code:
com.android.chrome
org.mozilla.firefox_beta
will put Google Chrome and Firefox Beta cache on /data. All others apps cache will go to /datadata.
If you want Firefox cache to go back on /datadata, just remove its line in the file and reboot.
In the "skip_apps.txt" file, just put apps you want to fully stay on /data/data. If apps was previously moved to /datadata by the datafix it won't apply; you have to add its name in "skip_apps.txt" file after installing it and before rebooting the phone. On the other hand, if you remove the apps name from "skip_apps.txt" file all but libraries will be moved to /datadata at next reboot.
Requirements :
Samsung Galaxy S based phone (GT-I9000, Vibrant, Fascinate, Captivate, etc.)
CM based rom (including CM7/9, MIUI and maybe ao(k)sp etc.)
Kernel that supports init.d scripts (latest CM9 nightly support it)
Busybox installed
A fresh nandroid backup
FAQ :
Q : There is 2 zip files, who's the good one ?
A : It depends of your kernel. With stock CM9 kernel use the Datafix20120521. With others like Devil etc., use the SDatafi20120521. The only difference is between the script name : 30datafix or S30datafix. Some recent kernels add a "S" before the init.d script name. Why ? No idea !!!
Q : Will this wipe my phone ?
A : No, it should not delete any data on your phone. But as it's not tested with every phone xda user have it's a good idea to have a fresh nandroid backup
Q : Do I need to reflash the zip file ? When ?
A : The datafix will be erased each time you upgrade/change your rom (including Nightly Builds) or your kernel (many of them "clean" the init.d directory). But if you don't install lots of apps after upgrading you don't really need to install the datafix again : without full wipe, a nandroid restore or an Odin full installation te datafix will stay on.
Q : Is there something to do when backuping my apps ?
A : Nandroid should work without specific option; Titanium Backup users should tick the Preferences > Troubleshooting settings > Follow all symbolic links option. I don't use other backup apps ...
Q : Can I use this on Samsung based rom ?
A : No ! And it's irrelevant cause Samsung roms don't have the "Low storage" issue !
Q : I'm using Slim ICS rom, do I need some busybox fixer etc. ?
A : I don't use SlimICS but all commands in my script call busybox directly so it should work. Let me know if there is still a problem with this !
Q : Why do you change naming of the zip file ?
A : Cause I want ! And it's listed directly in chronological order in terminal (or recovery) in this way.
Q : How can I know which apps use most space on /datadata :
A : Just run as root (in adb or terminal) :
Code:
du -s /datadata/*|sort -n
Downloads :
Box : https://www.box.com/s/6783d86f3840c02db911
Dropbox : https://www.dropbox.com/sh/rwibb0r0fhhyvh6/KaoBoC1BtB
Please don't mirror this.
I put the shell script in attachement here. Just grab it on your sdcard, remove the ".txt" extension and you could run it using Scripter or equivalent (root needed). Please post here if something gone wrong when using it.
Donations :
As I spent some time (and coffee) for this (and april datafix for those following previous xda thread) I think about a donation button. Give me your advise on that please ...
Link for donations
But just a little "Thanks, it works great !" would be great !

Reserved.
(ten chars)

Thanks for this. I kept wondering why I would run out of storage all the time. Well, now I know and you fixed it!
Sent from my GT-P7510 using XDA Premium HD app

awesome using chrome was causing me FC every once in a while

Hi,
Nice work.
Something I don't understand - how should I choose which apps I have their cache go to the /data partition? Apps that I frequently access? Apps that take a lot of space?

Wendigogo I've previously had an old datafix posted that moved all the files to /data/data and I've only had issues when Chrome filled the cache so Ive ran your script but now /datadata is filled and everything is FC Chrome's cache seems to be in /data/data though
any ideas?

Er.. is my datadata folder meant to be empty after applying this patch ? Phone is definitely slower.. forgot to do a nandroid too argh.
As per the other fixes.. doubt this is reversible ?
Sent from my GT-I9000 using Tapatalk 2

Wendigogo said:
Q : Can I use this on Samsung based rom ?
A : No ! And it's irrelevant cause Samsung roms don't have the "Low storage" issue !
Click to expand...
Click to collapse
Just a stupid question.
Why Samsung Roms dont need it ?
How works the solution of Samsung?
Thanks!

Very good script. Whats your future plans for this?
It would be really good if this was made into an app that let u select the apps cache you want on /data or /datadata rather than having to edit a text document.
Sent from my GT-I9000 using XDA

I've flashed this and now my /datadata partition is empty...
Enviado desde mi GT-I9000 usando Tapatalk 2

Something went wrong for me too
I wasn't previously using datafix,flashed it and checked my /datadata a very little time after reboot that was 128Mb free.Seemed a lot of free space comparing to the only-libs 2903 version.For the same initial configuration/apps installed i usually get about 88Mb of free space after flashing 2903.
Just a little while later i noticed a datadata folder in /datadata and free space was now 66Mb...I reboot and /datadata ended full.
Note:Users of Devil or MnIcs get after each boot a user.log (+ a .bak of the previous boot) that describe among others things init.d process,it could help to paste it here

Seems to work for me... but can someone tell me what the following folders are for and if I need them or if they're remnants of some past datafix?
/data/data.new
/data/data2
Thanks.

TheeWolf said:
Hi,
Nice work.
Something I don't understand - how should I choose which apps I have their cache go to the /data partition? Apps that I frequently access? Apps that take a lot of space?
Click to expand...
Click to collapse
None would be the best choice.
Moving their cache out of /datadata can potentially make them laggy. However, some apps have massive caches (Flipboard, Chrome, Google Music, etc.); as such, these apps are unusable unless you do move their cache (or unless you have very few apps installed).

I wonder why so many people are having troubles. I'll give the script a try soon. It looks good! Thanks for your monumental contribution, Wendigogo.

Wendigogo said:
Donations :
As I spent some time (and coffee) for this (and april datafix for those following previous xda thread) I think about a donation button. Give me your advise on that please ...
But just a little "Thanks, it works great !" would be great !
Click to expand...
Click to collapse
My vote is that you SHOULD put up a donation button, I am happy to contribute to your coffee fund (so long as you don't drink Starbuck's ;-) But since you're French, you surely have better taste than that!)

After upgrade to ver.0521 from 0329, I have the following problems:
1. There is a data.new folder, I wonder if it can be removed.
2. new installed apps haven't been moved to datadata
3. removed apps haven't been removed from datadata
I'm on cm9 0520 with devil 0.56 kernel, busybox updated to 1.20.
By the way, the scripts run well under scripts manager.

curl66 said:
Just a stupid question.
Why Samsung Roms dont need it ?
How works the solution of Samsung?
Thanks!
Click to expand...
Click to collapse
I GUESS it is easy to manage across all devices for the cm team without having to write specific code for different devices.

basily said:
Seems to work for me... but can someone tell me what the following folders are for and if I need them or if they're remnants of some past datafix?
/data/data.new
/data/data2
Thanks.
Click to expand...
Click to collapse
+1. Why do we need those folders to be kept in data? But when I tried to delete data.new I got FC's for all of my apps. Seems that data.new has replaced data/data folder.
And one more. I wanted to move com.android.email to data/data completely and edited skip_apps.txt. But when I check datadata folder with Disk Usage app - com.android.email still remains there.
What have I done wrong?
Sent from my SGH-I897 using xda premium

I find that 0521 version uses busybox for copy /move /mkdir operation, which is different from old versions.

After 3 reboots /datadata is still empty...
Enviado desde mi GT-I9000 usando Tapatalk 2

[ROM] (Almost) Stock Debloated 10.1.1.A.1.307 CWM ZIP LB v8

This is the ROM i use myself, but I post it here in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you. That said, these ZIP files and procedures have been tested by myself and a few others and seem to work quite well.
FLASH THIS AT YOUR OWN RISK.
Requirements:
Sony Xperia Z.
Only tested on LB, but should also work on UB.
Ability to flash ZIP files via recovery.
Features:
Based on Xperia Z_10.1.1.A.1.307_Unbranded BE.ftf (file uploaded by Psicao).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned.
No reboots when mounting system r/w.
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Call recording.
18 Toggles.
36 dpi softkeys.
Changelog:
v8
Added 18 Toggles.
Switched to 36 dpi softkeys.
v7
Added WeatherWidget back due to popular demand.
More robust and less intrusive way to ensure that mounting system r/w doesn't cause a reboot.
v6
Based on 10.1.1.A.1.307
Removed 18 Toggles since it is not compatible with 1.307 yet.
Delete the ric daemon early in the boot process.
v5
Added 18 Toggles.
Applied a few WiFi tweaks to get a (hopefully) more stable WiFi connection.
v4
Removed duplicate notification sound 'vega' (bug in original ROM).
Increased volume a bit.
v3
Created all symlinks found in the original FTF file.
Changed all file and directory permissions to match those in the original FTF file.
Added a more robust script to stop ric.
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.307_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Reboot again once NFC firmware has been upgraded (only needed if upgrading from 1.434 or earlier).
Note regarding unlocked bootloaders: This ROM is designed for LB. If using this on UB flash the following ZIP after installation to remove the CWM recovery for LB: C6603_10.1.1.A.1.307_UBPATCH.zip
Clear data?
If NFC is not working and you're upgrading from a 1.434 ROM, I recommend that you clear your userdata by flashing C6603_10.1.1.A.1.307_ClearData.zip.
You do NOT need to clear user data if you are already running a ROM based on 1.253 or 1.307 and everything is working fine.
MD5 hashes:
2f8fe013da90987447a04c0e5f405998 (C6603_10.1.1.A.1.253_DEBLOAT.zip)
3bba6ffb3cd9bdf7535c5e4b722223d5 (C6603_10.1.1.A.1.253_ClearData.zip)
b889d474290d9b924acbf011277d58e3 (C6603_10.1.1.A.1.307_UBPATCH.zip)
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel and baseband from the original FTF via Flashtool in order to get the full 1.307 experience.
Preventing reboots when mounting /system read-write
This ROM uses my own little utility called RICHunter to prevent reboots when mounting /system read-write. If you want to use it yourself in your own ROM you can download it here:
0c766dc58cc909693f5d669264d78f4a (richunter.zip)
Included in the ZIP file is a README.txt that explains how to use it, but you can also read it here:
RICHunter by Carceri @ XDA
1. What is this?
On the Xperia Z Sony have added a small program called ric which
monitors mount options on filesystems and reboots the system if
they deviate from their default values. This causes the system
to reboot e.g. when the /system partition is mounted read-write.
In short, this programs stops this daemon and replaces it with a
dummy version that doesn't do anything, thereby disabling ric.
2. How do I use it?
Just put the file richunter somewhere on your system, for example
/system/bin/richunter, make it executable (chmod 755) and run it
as the root user. This needs to be done every time the system is
restarted.
This can be achieved by putting the following lines in a file
called /system/etc/install-recovery.sh:
#!/system/bin/sh
exec /system/bin/richunter
Another way is to make a wrapper to /system/bin/ctrlaltdel and
call richunter from there:
#!/system/bin/sh
exec /system/bin/richunter
exec /system/bin/toolbox ctrlaltdel "${1}" "${2}" "${3}" "${4}"
Choose either one, or a 3rd solution to automatically run it.
Remember to make the files executable.
3. How does it work?
On the latest kernel, the ric daemon is restarted whenever it
is killed. Therefore the following steps are taken by this
program to stop it without giving it time to reboot the system:
1) The programs runs as a daemon waiting for up to 60 seconds
for ric to start.
2) It detects which CPU ric was last scheduled on, and forces
ric to always run on that CPU in the future.
3) It forces itself to run on the same CPU as ric and sets its
scheduling priority to real-time. This prevents anything
in that CPU from running, including ric.
4) It mounts the rootfs read-write and replaces ric with a
dummy version that just sleeps forever. Finally it kills
the ric process and remounts rootfs read-only.
5) The daemon now exits. When ric is restarted the dummy
version is started instead.
4. What about unlocked bootloaders and custom kernels?
On custom kernels ric has either been removed or not installed
at all. Therefore this is only needed on locked bootloaders.
5. Can I use it in my own ROM?
Sure. Use it as you want.
6. How do I compile it?
You need to have the Android NDK installed. Then set the
correct paths in the included Makefile and run:
1) make prep
2) make
That's it. When you want to recompile you can skip step 1).
7. What license is this released under?
It is UNLICENSED software. See http://unlicense.org/

Hi, i have not tested this exact zip, but the rom i am using now is based on a previous version you posted in another thread.
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
As i said, this happens on the first zip you uploaded, i don't know if this was already solved on newer versions.
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions. This step could also be added to the main flash script, no user data is lost and i think all NFC related problems would be gone
Thanks for sharing your work.

RoberM said:
There is a little issue with your "debloating", you removed "Notes" app, so when you go to "small apps" drawer and choose notes or voice recording, an error pops out, so you have to remove the icons and forget about stock notes or voice recording as they are apps not available on the market to download separately.
Click to expand...
Click to collapse
I have added the Notes app back in this zip.
RoberM said:
If NFC is not working, there is still hope to keep user data intact, just delete /data/usf on your phone, take usf folder from your userdata.tar, and put it in your phone in the same place where the older was with same permissions.
Click to expand...
Click to collapse
That was actually the first thing I tried and it didn't work for me. It might work for some and if someone is interested I'll be happy to provide a zip file that just restores this directory and keeps everything else under /data intact.

How do you enable call recording btw? Thanks.
Sent from my C6603

The link is down!! :crying:

mandarjoshiin said:
The link is down!! :crying:
Click to expand...
Click to collapse
Link is back up. I were just in the process if uploading v2

vibranze said:
How do you enable call recording btw? Thanks.
Click to expand...
Click to collapse
Press the menu button during a call.

Carceri said:
This is the ROM i use myself, but I posted this in case other people also want a clean (almost) stock ROM with root and recovery. It works for me, but I provide no guarantee that it will work for you, so FLASH THIS AT YOUR OWN RISK.
Requirements:
- Sony Xperia Z with locked bootloader.
- Ability to flash ZIP files via recovery.
Features:
Based on the first version of the ZIP posted by wawyed on this thread.
...which was based on C6603_Unbranded_10.1.1.A.1.253.ftf (original file uploaded by prakka).
Removed bloat and other apps you can download from Google Play.
Installed CWM recovery 6.0.2.8 for locked bootloaders v4.
Odexed and zipaligned
Pre-rooted with Koush's Superuser App.
Busybox v1.20.2 installed.
Enabled call recording.
Changelog:
v2
Fixed reboot issue when mounting system r/w.
Added Notes and NoteWidget back.
Reodexed and zipaligned.
v1
Initial release.
Installation:
Enter recovery.
Flash C6603_10.1.1.A.1.253_DEBLOAT.zip.
Clear user data OPTIONAL STEP - SEE BELOW.
Reboot.
Say not to "Disable recovery flash" if asked.
Possibly reboot a second time once NFC firmware has been upgraded.
I had problems with NFC not working if I didn't clear user data the first time I upgraded from a version < 1.253. In order to clear user data follow this step:
Flash C6603_10.1.1.A.1.253_ClearData.zip.
These ZIP files and procedures have been tested by myself and a few others and seem to work. However, some people have also experienced issues, but since I don't know their exact setup it is impossible for me to pinpoint the source of these errors. FLASH THIS AT YOUR OWN RISK.
Upgrade kernel and baseband:
Once the ROM is working you might want to flash kernel, fotakernel and baseband from the original FTF via Flashtool in order to get the full 1.253 experience.
Click to expand...
Click to collapse
hello I used your guide and everything works to perfection thanks:laugh:, I invite other people to use this guide to those who want to update your phone with the root installed.:good:
ps. sorry if I use a translator.
ciao ho usato la tua guida e funziona tutto alla perfezzione grazie, invito altri utenti ad usare questa guida per chi vuole aggiornare il telefono con il root installato.

Great, this is the first one deodexed and zipaligned, i am sure a lot of people will be interested.
EDIT: Ok, i didn't read well, it says Re-Odexed

Sorry, i'm a little confused, is this rom odexed or deodexed?
Sent from my C6603 using Tapatalk 2

secondkai said:
Sorry, i'm a little confused, is this rom odexed or deodexed?
Click to expand...
Click to collapse
In changes for version 2 reodexed is written. Attentively read an original post.

Carceri said:
Press the menu button during a call.
Click to expand...
Click to collapse
Thanks, but what I meant was how to incorporate call recording into the ROM, is it something that can be done easily, e.g. editing build.prop, etc or any other method?
Cheers.
Update: I got the answer. Thanks.

picasa album sync is missing in google accounts and album view, is this due to bloat removal ?

jimsey said:
picasa album sync is missing in google accounts and album view, is this due to bloat removal ?
Click to expand...
Click to collapse
I don't think so. Is that feature available on a normal Xperia Z stock ROM?
I think that the original Gallery app installs the required sync adapter. Also if you have Google+ installed it is replaced by Photo Sync.

hello Carceri would like to upgrade to v4 there some procedure to be performed?

fabbiotto said:
hello Carceri would like to upgrade to v4 there some procedure to be performed?
Click to expand...
Click to collapse
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.

Carceri said:
If you have installed this ROM before you just need to flash the new ZIP file to get the latest version.
Click to expand...
Click to collapse
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?

fabbiotto said:
s now the v2 if I install the v4 just that I do not clear user data to not lose my data?
Click to expand...
Click to collapse
Just flash the new ROM. No need to clear data.

Carceri said:
Just flash the new ROM. No need to clear data.
Click to expand...
Click to collapse
thank you very much:good:

hello v4 does not work well with the DoCoMo Status Bar and the Task Switcher sony disappears, you can take a look please?
by the time I come back to v2

[GUIDE] Get Xposed working on your deodexed TouchWiz based Lollipop ROM! 2015/08/17

DISCLAIMER
The process of flashing a custom recovery/kernel/firmware may and will trigger your device's Knox Counter. Neither XDA nor I can be held responsible for your actions. Proceed with caution. During this process you will lose all your settings and apps. As long as you follow the instructions, your device's storage, internal and external, won't be touched​
Still not compatible with x64 systems! Not compatible with Samsung 5.1.x (sdk22) ROMs!
Hello, Ladies and Gentleman
Many people seem to have a hard time to understand how all of this here on XDA works. I constantly get PM's from users, asking how to do the most basic stuff like flashing a .zip or stock firmware via Odin. Usually, I don't even read them and just hit delete. I know it's not ok to deny people help, so I decided to show you how you can get Xposed working on your TW based stock or custom ROM since it's the most frequently asked question I get.
It's nothing you couldn't do if you'd just....
We're going to use @arter97's customized Xposed Framework as the one made by @darkera13 needs the user to manually modify and replace files which may be too complicated for some.
Preparation
-READ EVERYTHING OVER AND OVER AGAIN.
-A custom recovery System like TWRP or CWM (PhilZ or Stock)
-A deodexed ROM. It's the only way to go. YOU NEED A DEODEXED ROM. If your ROM is not deodexed and you flash the framework, you'll end up in a bootloop. To deodex your existing ROM carefully follow Post #2
Here are a few made by XDA Senior Member @_alexndr
Stock deodexed for SM-N9005 Galaxy Note 3 International Qualcomm.
Stock deodexed for SM-G900F Galaxy S5 International Qualcomm
-And the framework itself from here
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
-Flash a custom recovery system of your choice. This is listed under preperation on purpose since this guide is about getting Xposed on your TW Lollipop device. A guide on how to get a custom recovery system is most certainly available in your device's forum.
-Store the ROM and the Framework in an easy to find folder, which we're gonna call "folder x". It doesn't matter where you store it (ext. SD or int. SD)
The Fun Part
-Boot into your custom recovery and make a full wipe:
TWRP users: "Wipe>Advanced Wipe> Tick System, Data, Cache, Dalvik Cache> Slide to format.​CWM users: "Mounts and Storage> hit Format /System; hit Format /Data; hit Format /Cache.​
-Still in recovery system, install, or flash the files we put in folder x;
TWRP users: "Install> Navigate to folder x and choose the ROM file first> Add Zip> now choose the Xposed Framework from folder x> Slide to flash.​CWM users: "Install Zip> Choose zip from /sdcard if folder x is on internalt storage or /storage/sdcard1 if folder x is on ext. storage (SD-Card)>​choose the ROM file first> -Yes - install ROMXY.zip.​Do the same with the Xposed Framework zip file.​
-Still in recovery system, reboot device and wait for it to boot. It can take up to 20 minutes. Enjoy Xposed on your Samsung TouchWiz Lollipop ROM.
-Stuck in a bootloop? Try this and repeat the process.

XDA Senior Member @Honzze kindly pointed out to keep following in mind; You have to start JoelDroid Lollipop Batch Deodexer with Admin permissions. Otherwise this error might return "path variable" of Java "is not set".
Deodexing your existing ROM without having to flash an entire ROM
As the title says, with this awesome guide by XDA Senior Member @townsenk you don't have to reflash an entire new ROM to your device. Instead, youll just deodex those parts of your System which need to be modified in order to get Xposed working. You don't necessarily have to perform a full wipe if you do it this way. But if you encounter fc's or end up in a bootloop, you know what to do
Guide for this guide:
Regarding point 1: "...launch a DOS shell..." just means, you need to open the so called "CMD" programm in Windows. To "launch a DOS shell" or CMD from within a folder, you simply have to hold down the shift key and right click in that folder. The context menu will show an entry "open command window here". And that's it! (Windows XP users may have to search the internet for another solution)
For Galaxy S5 and Note 3 users: If ADB returns "device offline" or an empty line after "List of devices attached" make sure your using a USB 2.0 data cable on a USB 2.0 port
townsenk said:
How to DeOdex YOUR (...) Rom.
I would like to note that I appreciate all the work that developers have put forth in creating and maintaining modified Roms. there are some awesome feature rich implementations available. My intentions are not to be critical of any specific Rom or mod. Without the developers we would have nothing.
(...)
This method is very common knowledge I thought I'd just explain it in an easy to understand way.
Here is what you need.
A stock (...) ROOTED configurated phone. Debloat as needed. Set the phone up exactly how you like it with apps and such.
Make sure it's stable. (If you have issues before DeOdexing they will be there afterward!)
Here's the files you may need to make this happen
LBD2.4.zip
7-Zip
Installer template (at end of post)
1> Make sure ADB is working on your computer. USB debugging turned on. Create a folder to store your soon to be download system files and launch a DOS shell from that working folder. Working folder name should NOT contain spaces. With the phone hooked up you should be able to type adb shell and get a prompt.
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
3> Extract and launch LBD2.4 (This is the DeOdexer and is AWESOME). Point it at your recently created "system" folder and let it do it's thing.
I'll assume this will occur without errors as I have never had any.
4> At this point you can manually apply modded apk's to the system folder but I don't really recommend it. They can be applied afterward using the seperate installer zips.
5> with 7-Zip installed open the provided Installer template. Do not Extract it. Just open it in the 7-Zip file browser using the right click context menu in windows.
Drag-Drop the contents of your system folder into the empty system folder in the 7-Zip browser It should be the three folders previously created but now they are Deodexed. Close the 7-zip file manager and select Yes if it asks you to save.
Note: The provided installer template has been modified to only wipe and replace the three system directories.
6. Copy the created installer to your sdcard and install with recovery. Wipe cache and Dalvik before rebooting.
Go have lunch. You will sit at a boot screen for about 10 minutes. Then another 20 to rebuild caches. Time varies.
7. Your system will now be Deodexed! At this point you can install your mods one at a time, I recommend this so you can test your system between installs to determine if a specific mod is creating problems.
This method has so far removed ALL of my stability issues.
Click to expand...
Click to collapse

Since I no longer own this device, I'm retiring from this thread as of now. Hope I could help you.

Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.

omg brilliant @nitrous² ! thanks so much! its been days i keep trying to deodex with others tool...

Sachitoge said:
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
Click to expand...
Click to collapse
Same happened to me.... Did you solved this problem?

Maurizio1953 said:
Same happened to me.... Did you solved this problem?
Click to expand...
Click to collapse
Nope, i ended up using CM12 (at that time, right now i got cm13 update).
Well i had to deodex apps to get xposed on TouchWiz, but i failed and didn't get headache because of the Xposed modules being not really well compatible on TouchWiz, so i jumped to CM, i find it more stable, and the CM13 is insane because it saves so much battery at stand by, compared to lollipop, the Android 6.0.1 Marshmallow is the biggest update in android history, that saves hell lot of battery (it can be also maybe because i don't have Xposed Framework in recent rom).
Anyway, im tired of it, and i don't need to hassle with Link2Sd because of Android Marshmallow offering to mount the SD Card, in the end, all my needs are being offered in this (for me) huge, best android update, being Marshmallow.
Try it i would say, so amazing.

Ok i would like to go to cm13 as you but i stil need the support to the gear s smartwatch so i decided to stay with touchwiz without xposed.