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.

Modified OTA2 Updates for Installation in ClockworkMod Recovery

I have modified several of the updates to be installed in ClockworkMod Recovery so that it will not overwrite CWM Recovery and should also preserve root. I still recommend protecting root using Voodoo OTA Rootkeeper in case something goes wrong and it is always a good idea to make a nandroid backup in ClockworkMod Recovery before installing any update. Also after updating Titanium backup said that my su had the wrong permission and it wanted to correct it (I allowed it to fix it). I am not sure why this happened as I thought I set the permissions properly in the update but go ahead and run Titanium after updating and let it fix it for you if there is a problem. These updates will still check all of your system apps so you need to restore them (copying and pasting them back into the /system/app folder and setting the proper permissions with Root Explorer is one of the easiest ways to do this). You can also make your own modifications to the update and remove the checks if you like (some people have done this with no problems but one guy reported that android wouldn't boot after updating with no checks so I leave it up to you to decide for yourself). I posted instructions for modifying the update here. The changes I made to the update were to remove the Indigo check (because it was giving me an error) commented out the lines that delete the current recovery and install the new recovery, removed the line that deletes Superuser.apk, added an su file to the update so that it reinstalls su after deleting it, and finally added lines to symlink and set permissions for the su file.
Install instructions:
Protect root with Voodoo OTA Rootkeeper (just in case)
Copy the proper update.zip to your external sdcard (if you are US or WE you must install 086 before 089)
Make sure your battery is well charged (having your battery die during the update would be very bad)
Turn off TpT and boot into recovery by turning on and repeatedly pressing the volume up key
Wipe cache partition
Make a nandroid backup (not necessary but highly recommended)
Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
Let the install run and then choose reboot system now in the CWR main menu
The first boot will take a long time, don't worry this is normal (if it takes more than 30min you may want to hold power to turn off and reboot again)
ThinkPadTablet_A310_02_0037_0076_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
ThinkPadTablet_A310_02_0039_0089_US_CWR.zip
ThinkPadTablet_A310_02_0039_0086_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0089_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0087_UK_CWR.zip
ThinkPadTablet_A310_02_0039_0089_ROW_CWR.zip
ThinkPadTablet_A310_02_0039_0089_SC_CWR.zip
ThinkPadTablet_A310_02_0039_0090_JP_CWR.zip
Flash at your own risk! I am not responsible if this totally bricks your tablet, breaks your root, or creates any other problems for you! Make sure that you install the correct version for your region.

Worked great for me. Thanks!

Is it also necessary to temporarily unroot before applying the update? Thanks again.

I don't believe I needed to do a tempory un-root to apply the updates. I just followed the instructions. I did have to power down during the first installation since it stayed in .. rebooting.. mode for 20 to 25 minutes. After powering down and rebooting, _86 was installed.
I did have to re-install Busybox to get LUKS Manager to work after the installation of 86 and 89.

Thanks, but I got in trouble with OTA2 by not unrooting first, and the OP is the one who helped me with it. I need to make sure before I make a move.

It should not matter, the update deletes and reinstalls su.

Thank you. I'll give it a try later today.

great thanks.
a sticky would be great

I just applied OTA 2.5, now my market consistently force crashes. Anybody else having this issue?

try to download and install new "Play Store"

mandrsn1 said:
I just applied OTA 2.5, now my market consistently force crashes. Anybody else having this issue?
Click to expand...
Click to collapse
My market is working fine on OTA 2.5. Maybe you have two versions of the same app installed after updating (for example if you removed FlexT9 in system and installed the full FlexT9 keyboard from the market and then restored the system app to update). It could also be a problem due to the change over to the new Play Store as quyTam suggested. If all else fails a factory reset would likely fix the problem but then you will have to set everything up again.

jhankinson said:
My market is working fine on OTA 2.5. Maybe you have two versions of the same app installed after updating (for example if you removed FlexT9 in system and installed the full FlexT9 keyboard from the market and then restored the system app to update). It could also be a problem due to the change over to the new Play Store as quyTam suggested. If all else fails a factory reset would likely fix the problem but then you will have to set everything up again.
Click to expand...
Click to collapse
Nope, i unfroze apps before i updates and made sure there were no replaced system apps when I installed.
I have tried stock market, 3.4.4 (honeycomb 3.2 market) and 3.4.6 (Play store) and they all force crash. Sounds like a factory reset may be needed.

mandrsn1 said:
Nope, i unfroze apps before i updates and made sure there were no replaced system apps when I installed.
I have tried stock market, 3.4.4 (honeycomb 3.2 market) and 3.4.6 (Play store) and they all force crash. Sounds like a factory reset may be needed.
Click to expand...
Click to collapse
Something else must be messed up. I factory restored and still am having issues.

I got an error message after trying to install file from SD Card. It said
"Installing: /sdcard/ThinkPadTablet_A310_02_0039_0089_ROW_CWR.zip
Finding update package...
Opening update package...
Installing update...
Verifying Current system...
assert failed: apply_patch_check("/system/app/FlexT9ChineseIME.apk", "222668fd99a68916eb4d6784c3795801ea0698bd" , "8c4feb3af89ec0ff3791c0d5acf30bad168b4600")
E:Error in /sdcard/ThinkPadTablet_A310_02_0039_009_ROW_CWR.zip
(Status 7)
Installation aborted.
I'm currently using 0074ROW
Could someone advise how to fix this?

Put back the system file indicated - FlexT9ChineseIME.apk.

toenail_flicker said:
Put back the system file indicated - FlexT9ChineseIME.apk.
Click to expand...
Click to collapse
Thanks but where can I found it?

That depends on what country you're from. There's a couple of system dumps here on xda.

same here can't ota update coz i deleted some of the apps so can anyone know where can find the dump for the 0074 row dump? or could someone please provide the dump here?
thx for the help!!!

You can also go to the Lenovo download page to find your previous download file, unzip it, and find the file to put back.

toenail_flicker said:
You can also go to the Lenovo download page to find your previous download file, unzip it, and find the file to put back.
Click to expand...
Click to collapse
thx for the help. just asking are you referring to this:
download.lenovo.com/slates/think/tablet1
the worse thing is i deleted the drmprovider.apk and the odex as well which i couldn't see that apps in those zip.
so could anyone help here?
thx!!!

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

[Q] How to integrate Apps/Updates to system

Hi,
I would like to know if there is a way to integrate/push Apps into System Partition beside using flashable ZIP file? For a long time Link2SD, LP and Titanium Backup did the trick, but now they all don't work.
Pushing an update (for example Play Store App) to system will just add the APK and not replace old one, so you have the App twice.
Pushing an installed User App to system will make it disappear, while it is wasting space in system partition. It's just not recognized by Android.
Right now (MM/6.0.1 ROM), the only working method I know of doing it is flashing ZIP file in Recovery or Flashfire. Is there any other working method? Preferably a script or an App that is still working on G900F with MM Stock ROM?

zombie system apps

Hi XDA. Hope someone can offer some help here. Ive just updated my OP5 to the latest OOS build. I am rooted, latest TWRP & Magisk.
I am having issues deleting unwanted apps from /system. Every time I attempt in Titanium Backup, it appears successful, but when rebooting the app is back.
Also have tried manually removing the directories and associated from /system/priv-app, however every time I try root explorer i get a "Delete Failed" message.
The only way I have been able to do this successfully is from the TWRP file manager, however its a PITA tracking which friendly app name corresponds to what folder in priv-app.
Any suggestions?

so figured this out. Permissions or something must have been messed up. Completely wiped system, data, everything using twrp and did a fresh install.
Working as expected now