Database Develop

[CWM] ClockworkMod 6.0.1.2 for Xperia T [UPDATED - 15/10/2012]

This is a CWM recovery for the Xperia T - you need to have unlocked your bootloader at http://unlockbootloader.sonymobile.com/instructions.
I AM NOT RESPONSIBLE FOR BRICKING YOUR PHONE ETC. ETC. ETC. - I'm sure you've heard the rest before.
Steps for installation:
Download recovery from http://goo.im/devs/tilal6991/recoveries/mint/15102012.img
Download fastboot and get it into a place where you can run it - I'm not going to provide instructions how - guides are all over the place
Open a command window in the place where fastboot is
Copy the recovery.img to the fastboot folder
Type fastboot flash boot recovery.img
Type fastboot reboot
You will be in CWM!
Note:
The first time you install a ROM you will need to flash the boot.img of that ROM using fastboot - I'm hoping this restriction can be removed at a future date.
A CM port is also up - compiled by me.
Thanks to:
All the CM guys for having their code on Github - I didn't do anything but compile and figure out the instructions for flashing.

Hmm, so tempting but not sure since you've not tested it on the T. Someone else gonna go first?
EDIT: I am sorry, a bad assumption possibly. Have you tested this on a T?

I have. It's tested and working. I've flashed CyanogenMod and using it as a daily as well.

Will have my T today but I wonder how to access recovery in daily use? (undestood the 1st time access, but not the next accesses...)

backup and restore work？

Switch off phone.
Power on phone with volume down held.
And although I haven't tested there's nothing that indicates backup/restore won't work.
Sent from my Xperia T using Tapatalk 2

Hmm, the recovery just cycle boots into recovery mode. It never boots into system

As I said the first time you flash a ROM you will need to fast boot install the boot mage of the ROM.
Sent from my Xperia T using Tapatalk 2

So then you are forced to flash a rom after installing cwm?
Sent from my Xperia T

Yes. Since you are flashing the boot partition its a pseudo recovery so a ROM needs to be flashed.
Sent from my Xperia T using Tapatalk 2

help
@tilal
im from the arc/s forums and i am in need of some help with compiling CWM 6 for my device
could you gimme a quick tut or something... coz the tut i found on xda was a little vague and difficult to understand
appreciate the help!!

your recovery wouldn't mount sdcard (internal) so i couldn't install cm10. just to let you know, don't know what went wrong, i just used another one i found and all working fine.
thanks, anyway.
Sent from my Xperia T

tumult said:
your recovery wouldn't mount sdcard (internal) so i couldn't install cm10. just to let you know, don't know what went wrong, i just used another one i found and all working fine.
thanks, anyway.
Sent from my Xperia T
Click to expand...
Click to collapse
I hope no one minds the question... but which other did you use? Going to slap the next rev of CM 10 when they post it.

charlatan01 said:
I hope no one minds the question... but which other did you use? Going to slap the next rev of CM 10 when they post it.
Click to expand...
Click to collapse
well maybe it will work for you. i flashed this kernel with included cwm:
http://forum.xda-developers.com/showthread.php?p=32442811
Sent from my Xperia T

New recovery up - quite a few fixes and updated to 6.0.1.5.

tilal6991 said:
New recovery up - quite a few fixes and updated to 6.0.1.5.
Click to expand...
Click to collapse
I flashed this last night successfully. I couldn't get side-loading to work, but it's smooth otherwise. Have not tested backup / restore yet.
Additionally, FWIW, I then flashed the Paranoid Android ROM, and while I've got some issues with it, I didn't have to flash the boot.img from the ROM for the ROM to boot, so I am not sure if that is still required or not... or maybe that's what's causing my issues with the ROM?
Thanks for the recovery!

tilal6991 said:
Type fastboot flash boot recovery.img
Note:
The first time you install a ROM you will need to flash the boot.img of that ROM using fastboot - I'm hoping this restriction can be removed at a future date.
Click to expand...
Click to collapse
So this recovery has to be initially installed on the boot partition, but does it copy itself to the recovery partition on first boot or do you have to reflash it every time you want to switch from running a ROM to running the recovery?
Also, is a stock boot.img available anywhere (so that this recovery can be used for nandroid backups with the stock rom)?

Once I am finished with this recovery how do I turn the phone off?
SOLVED
Hold vol + and - and power button.

CWM on Xperia TX and screen is upside down
Nice work tho.

Is AROMA working in the recovery?
I'm making a rom and I'd like to know it
gregbradley said:
Once I am finished with this recovery how do I turn the phone off?
SOLVED
Hold vol + and - and power button.
Click to expand...
Click to collapse
Vol + and power should do it
Vol - and power is for screenshot in the firmware

Stuck on bootloader unlocked screen.

Hello,
I yesterday got new at&t Atrix hd with android 4.0.4. I updated to newest 4.1.2 (I think). I rooted it with Motochopper. I tried to install CWM with Myth Tool. Didn't work.
Finally I installed CWM with this method.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Click to expand...
Click to collapse
Then I installed [ROM] CM 10.2 (Android 4.3) for AtrixHD from zip in CWM. Everything was working great till turned Atrix off.
Then it stuck on "bootloader unlocked" screen. Most of the time I was not able to enter CWM but one time somehow I managed to enter CWM, if I use restart option in CWM after restart android loaded successfully. Tried restart again but I was not able to enter recovery and got stuck again. After messing around with volume/power key somehow android loaded again successfully (without enter recovery).
Now it's working but I'm scared to restart or do anything.
What do you think? What should I do? Is it ROM problem, system or what?
Currently there are no install-recovery.sh (or install-recovery.sh.bak) file. Maybe this could be problem?
I would appreciate any help.
Thanks!

mm166 said:
Hello,
I yesterday got new at&t Atrix hd with android 4.0.4. I updated to newest 4.1.2 (I think). I rooted it with Motochopper. I tried to install CWM with Myth Tool. Didn't work.
Finally I installed CWM with this method.
Then I installed [ROM] CM 10.2 (Android 4.3) for AtrixHD from zip in CWM. Everything was working great till turned Atrix off.
Then it stuck on "bootloader unlocked" screen. Most of the time I was not able to enter CWM but one time somehow I managed to enter CWM, if I use restart option in CWM after restart android loaded successfully. Tried restart again but I was not able to enter recovery and got stuck again. After messing around with volume/power key somehow android loaded again successfully (without enter recovery).
Now it's working but I'm scared to restart or do anything.
What do you think? What should I do? Is it ROM problem, system or what?
Currently there are no install-recovery.sh (or install-recovery.sh.bak) file. Maybe this could be problem?
I would appreciate any help.
Thanks!
Click to expand...
Click to collapse
Are you sure the install-recovery.sh file is not installed? Just to make sure, I would install Root Explore to use that to check to make sure.

I don't have root access but I think I should be able to see that file, right?

Do you have root access? You need to install a file manager like Root Explorer so you can easily change the file permissions and rename the file by adding .bak to the end of the file name.
Weird, I don't see it either. I see it in mine though.

No, I don't have root access. I hope it's ROMs issue. CM10.2 doesn't come with root access. There are weird things going on with my phone. I really hope that other ROM will fix that. Thanks for reply.

mm166 said:
No, I don't have root access. I hope it's ROMs issue. CM10.2 doesn't come with root access. There are weird things going on with my phone. I really hope that other ROM will fix that. Thanks for reply.
Click to expand...
Click to collapse
Maybe you could install Root Explorer. Maybe that will allow you to see the file.

I also have problems getting straight into recovery sometimes but if I hold vol up+vol down+power I can select recovery from there. as far root on cm 10.2 flash superuser.zip

Can you tell me what key combinations you use for what purpose? I doubt you make a mistake there...
Sent from my MB886 using xda app-developers app

Just bumping this one
I am pretty desperete now
RSD'ed to Mexican retail
Rebooted fine but I get N/A in every device property value in RSD
When I flash CM 10.2 (wiping cache/dalvik/factory reset/format system and wiping caches/factory reset after) It boots fine the first time and gets stuck in Moto log/Unlocked bootloader when I reboot
I know I missing something but WTF am I missing?

narta said:
Just bumping this one
I am pretty desperete now
RSD'ed to Mexican retail
Rebooted fine but I get N/A in every device property value in RSD
When I flash CM 10.2 (wiping cache/dalvik/factory reset/format system and wiping caches/factory reset after) It boots fine the first time and gets stuck in Moto log/Unlocked bootloader when I reboot
I know I missing something but WTF am I missing?
Click to expand...
Click to collapse
have you tried PAC 4.3 to see if it gives same issue.

frog1982 said:
have you tried PAC 4.3 to see if it gives same issue.
Click to expand...
Click to collapse
it does

I'm having the same problem. Running CM10.2.

[Q] Xperia Z1 is recognized as "togari", Z Ultra

As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?

Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop

HellRoot said:
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
Click to expand...
Click to collapse
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?

Sari95 said:
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Click to expand...
Click to collapse
well..i have never had problems with it being the recovery... what error does it make now?

HellRoot said:
well..i have never had problems with it being the recovery... what error does it make now?
Click to expand...
Click to collapse
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l

[/COLOR]
Sari95 said:
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
Click to expand...
Click to collapse
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.

HellRoot said:
[/COLOR]
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?

Sari95 said:
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.

Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
I had this problem when I try to flash with LB.

HellRoot said:
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Click to expand...
Click to collapse
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help

Sari95 said:
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Click to expand...
Click to collapse
good to hear hope you enjoy the CM.... if you want then please tell me how it is running.. performance, battery, camera etc
have a good day

Broken volume flex

Hi everyone I have a big big problem. My volume buttons are broken, so I can'n navigate through CWM revovery. I have cm10.2 and I want to try the kiktkat ROMs. What should I do? I tried to use goo manager but after I press "flash roms" it reboots in recovery, where I can't do anything unless reboot now. Is there a way to install TWRP touch recovery? I think of installing stock jellybean with ODIN and use a custon kernel through DD command method, but I don't know how to root without using the recovery. Any other solutions? Is there a way to install TWRP directly on cyanogenmod 10.2? Why goo manager doesen't work? Rom manager do the same thing, instead of flashing my rom, it reboots in recovery. Please help me, i'm desperate. Basicaly I want to install ROMs or TWRP recovery WITHOUT USING THE VOLUME BUTTON.

cristinel13 said:
Hi everyone I have a big big problem. My volume buttons are broken, so I can'n navigate through CWM revovery. I have cm10.2 and I want to try the kiktkat ROMs. What should I do? I tried to use goo manager but after I press "flash roms" it reboots in recovery, where I can't do anything unless reboot now. Is there a way to install TWRP touch recovery? I think of installing stock jellybean with ODIN and use a custon kernel through DD command method, but I don't know how to root without using the recovery. Any other solutions? Is there a way to install TWRP directly on cyanogenmod 10.2? Why goo manager doesen't work? Rom manager do the same thing, instead of flashing my rom, it reboots in recovery. Please help me, i'm desperate. Basicaly I want to install ROMs or TWRP recovery WITHOUT USING THE VOLUME BUTTON.
Click to expand...
Click to collapse
I think that we do not have any CM kernel that has TWRP. And you can't install separately recovery from kernel. Maybe you can do this, install CM11 kernel - it has touch CWM. When you swipe up it goes up, when you swipe down... But you must be carefull, and to get 100% working CM11 zip in your recovery, to avoid getting a bootloop. Unpack it on PC and see if zip of it is not broken,
You can install CM11 kernel by getting it from CM11 zip, copy it to the phone and use Universal Kernel Flasher from Play store. After installing it I think that you can't go back to CM10.2 anymore, you will end up with a bootloop. So you must install CM11. And another thing, I am not sure if reboot recovery works well, you will end up with nothing if it does not. So do everything at your risk, do not blame me if you fail...
We do not have working ROM manager or similar thing.

shut_down said:
I think that we do not have any CM kernel that has TWRP. And you can't install separately recovery from kernel. Maybe you can do this, install CM11 kernel - it has touch CWM. When you swipe up it goes up, when you swipe down... But you must be carefull, and to get 100% working CM11 zip in your recovery, to avoid getting a bootloop. Unpack it on PC and see if zip of it is not broken,
You can install CM11 kernel by getting it from CM11 zip, copy it to the phone and use Universal Kernel Flasher from Play store. After installing it I think that you can't go back to CM10.2 anymore, you will end up with a bootloop. So you must install CM11. And another thing, I am not sure if reboot recovery works well, you will end up with nothing if it does not. So do everything at your risk, do not blame me if you fail...
We do not have working ROM manager or similar thing.
Click to expand...
Click to collapse
So I should unpack the CM11 zip and flash the kernel in CM10.2 that I already have? If I will end up with bootloop how should I enter the recovery? The only way to do it is through reboot to recovery option in my rom, if I get stuck in the bootloop I will not be able to do anything. Can you explain one more time, step by step?

cristinel13 said:
So I should unpack the CM11 zip and flash the kernel in CM10.2 that I already have? If I will end up with bootloop how should I enter the recovery? The only way to do it is through reboot to recovery option in my rom, if I get stuck in the bootloop I will not be able to do anything. Can you explain one more time, step by step?
Click to expand...
Click to collapse
I can't guarantee that you can reboot to recovery, because sometimes it does not work. This process is risky... You can't go to download mode too after that.
1. Download CM11 zip, get boot.img from it
2. Install Universal Kernel Flasher and some root explorer
3. Install boot.img with Universal Kernel Flasher
4. Reboot recovery
5. Install CM11, do factory reset, wipe cache, dalvik cache...
I wouldn't try something like this with those risks, I will rather get my volume buttons fixed before trying this. I think chances to fail is greater then not to.

I understand now.. as you said is too risky. Can anyone help me with a method to get root on stock jellybean without using recovery or to use goo manager? I want so bad to try kitkat but I don't want to brick my phone in the process. Thank you Shutdown anyway for the help.

cristinel13 said:
I understand now.. as you said is too risky. Can anyone help me with a method to get root on stock jellybean without using recovery or to use goo manager? I want so bad to try kitkat but I don't want to brick my phone in the process. Thank you Shutdown anyway for the help.
Click to expand...
Click to collapse
I think Goo manager is not working because it is not compatible with our device. Its developer needs to make it work with our phone. So I think there is no other method for rooting except the one we have, zip file and flashing it in recovery.

Why there isn't an odin flashable method for root as for gingerbread? I am sorry for bothering you, but you are of the most experienced dev/user of our device.. My volume flex can't be fixed unless I change the motherboard wich is far too expensive compared with the value of the phone. I also have a very unstable version of cm 10.2 (I installed it like 10 months ago) so my camera doesen't work in video and I have the in call volume bug. If I just could root stock jellybean with other method, I could use twrp and install any 4.4 ROM I want. It is frustrating because I am so close yet so far..

cristinel13 said:
Why there isn't an odin flashable method for root as for gingerbread? I am sorry for bothering you, but you are of the most experienced dev/user of our device.. My volume flex can't be fixed unless I change the motherboard wich is far too expensive compared with the value of the phone. I also have a very unstable version of cm 10.2 (I installed it like 10 months ago) so my camera doesen't work in video and I have the in call volume bug. If I just could root stock jellybean with other method, I could use twrp and install any 4.4 ROM I want. It is frustrating because I am so close yet so far..
Click to expand...
Click to collapse
There is not Odin flashable root method because we got that Recovery method that is easy and does not increase binary count, and devs did not make the one for Odin. Anyway you can't go to download mode too if Volume buttons is not working. You need to press volume up to proceed...

I built a long time ago a CM10.1 kernel with TWRP recovery... CM10.2 CWM is touch recovery.
@cristinel13 Method by shut_down is perfect, but if you aren't not sure to do it do this:
I built this file for you, download it but don't extract, leave as it is
Open Odin and put that file in "PDA"
Open Terminal Emulator on your device and write first su, confirm access then write reboot download
Now your device is in download mode without need to press vol+ to confirm
Press "Start" on Odin
Let the device starts, then open again Terminal Emulator, write again su then write reboot recovery to enter in recovery. Now flash any KitKat ROM that you want

A little help? I flashed it with odin and now my phone is bricked. It boot to the samsung galaxy s advance logo and then it stops. My PC reconise it and I can charge my phone, but I can't start it. How can I enter recovery/download without the buttons? I am pretty scared right now :-s

cristinel13 said:
A little help? I flashed it with odin and now my phone is bricked. It boot to the samsung galaxy s advance logo and then it stops. My PC reconise it and I can charge my phone, but I can't start it. How can I enter recovery/download without the buttons? I am pretty scared right now :-s
Click to expand...
Click to collapse
I think that you need to do factory reset... Can you use ADB? Try to delete data/data folder in root with ADB. You can use this if you need GUI: http://forum.xda-developers.com/showthread.php?t=2105707
You can try with delete of folder data/dalvik-cache.
P.S. I forgot that you flashed just kernel, try adb reboot recovery.

The kernel worked.. I mean the battery logo when I plug it in the PC is like on in kitkat. My phone works but it won't boot up. All I need to do is to enter recovery mode, but I can't without the volume button. Can I enter in recovery with ADB? I red that I can't use ADB with the phone turned off.

cristinel13 said:
The kernel worked.. I mean the battery logo when I plug it in the PC is like on in kitkat. My phone works but it won't boot up. All I need to do is to enter recovery mode, but I can't without the volume button. Can I enter in recovery with ADB? I red that I can't use ADB with the phone turned off.
Click to expand...
Click to collapse
Try. Leave it sometime on that bootloop, and if it is possible it will give you adb access. Use reboot recovery command, like you did for download mode.
Sent from my GT-I9070 using Tapatalk

cristinel13 said:
The kernel worked.. I mean the battery logo when I plug it in the PC is like on in kitkat. My phone works but it won't boot up. All I need to do is to enter recovery mode, but I can't without the volume button. Can I enter in recovery with ADB? I red that I can't use ADB with the phone turned off.
Click to expand...
Click to collapse
Oh right, kernels compiled on 4.4 can't start on 4.2-4.3... Sorry, I forgot that, do you have at least a very little knowledge about hardware? If yes, we can use a "pro" method that will 101% work to enter in recovery
shut_down said:
Try. Leave it sometime on that bootloop, and if it is possible it will give you adb access. Use reboot recovery command, like you did for download mode.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
Unfortunately to have ADB on boot you need to modify default.prop inside boot.img's primary ramdisk, and he can't actually flash again...

You cand explain the method to enter in recovery, I will give it a shot.

cristinel13 said:
You cand explain the method to enter in recovery, I will give it a shot.
Click to expand...
Click to collapse
In terminal emulator get superuser request nd then type 'reboot recovery' then u r good to go...........

kamalnath93 said:
In terminal emulator get superuser request nd then type 'reboot recovery' then u r good to go...........
Click to expand...
Click to collapse
I don't know why usually someone doesn't read previous messages in a thread. He can't actually boot his ROM, so no terminal emulator

Using XModGames on Tab S2

Hey guys, I am trying to use an application called XMODGAMES on my Samsung Tab S2. If you are not familiar with the application it is used with games to make them automated (i.e. perform tasks that would if done manually waste hours of your time).
Yesterday, I was able to root my device using the following techniques: I downloaded odin, cf_autoroot, and t810 5.1.1 boot. This actually ended up boot-looping my device so I used odin to flash to a stock firmware, installed twrp, and then installed SuperSu (yay root). Then I downloaded XMODGAMES and it is failing to work with the device, upon troubleshooting I found that there is an issue with "Enforcing" with Samsung devices that causes the application to not work. There are a few workarounds (given by XMODGAMES) that I attempted but I can not get it to work so I am looking for your advice and help.
This is the link to their workaround and videos: http://www.xmodgames.com/faq/64.html
TLDR: You use Lucky Patcher and SD2LINK to move the XMODGAMES application to the system/app directory and use ODEX as well as a few more actions. The issue that I am having is when I move it to the system directory the app icon disappears and I can no longer open or remove it. When I go to the local storage I can see the folder for the app but I cannot access it.
Seeking your expertise, and a HUGE thank you in advance.

I think I know what u problem is... u can either flash a different Kernel with Permissive SElinux or Search XDA for an app called SElinuxChanger that will allow to modify ur stock kernel on the fly, also I think U might need to install busybox not sure though.. I would Install it anyway but it seem u might have it already since u are using lucky patcher.. please let me know if it worked.

Mr_Jay_jay said:
I think I know what u problem is... u can either flash a different Kernel with Permissive SElinux or Search XDA for an app called SElinuxChanger that will allow to modify ur stock kernel on the fly, also I think U might need to install busybox not sure though.. I would Install it anyway but it seem u might have it already since u are using lucky patcher.. please let me know if it worked.
Click to expand...
Click to collapse
I downloaded SElinuxChanger but whenever I change the mode to Permissive it does not last long before it is reverted back to Enforcing. I have also tried to reboot several times and the mode does not stick. When I rooted my device yesterday I followed these rooting instructions: http://forum.xda-developers.com/tab-s2/general/guide-root-tab-s2-t3205019
I thought I already flashed a permissive kernel, I am not sure why it would still show enforcing? When I downloaded the stock firmware would it overwrite the kernel? Can I simply flash the kernel from the root guide again and will everything work properly? Or will that total mess everything up?

Maybe @ashyx and/or @DeeXii can help, they know their stuff.

mbducati said:
I downloaded SElinuxChanger but whenever I change the mode to Permissive it does not last long before it is reverted back to Enforcing. I have also tried to reboot several times and the mode does not stick. When I rooted my device yesterday I followed these rooting instructions: http://forum.xda-developers.com/tab-s2/general/guide-root-tab-s2-t3205019
I thought I already flashed a permissive kernel, I am not sure why it would still show enforcing? When I downloaded the stock firmware would it overwrite the kernel? Can I simply flash the kernel from the root guide again and will everything work properly? Or will that total mess everything up?
Click to expand...
Click to collapse
upon reading u OP I notice u encounter the same issues I did and then rooted the same way I did, and to answer ur question yes u need a new kernel with SElinux Permisive since using odin to flash stock does overwrite everything now I dont know if that kernel is good for ur build... since u came across the same Issue as me I'm guessing that u're currently on PB1 build which is the latest correct? so at least for now stay away from now.. I use that app as well and I'm working on getting it to work as we speak as Soon as I get it working I'll share my method with ya..

Mr_Jay_jay said:
upon reading u OP I notice u encounter the same issues I did and then rooted the same way I did, and to answer ur question yes u need a new kernel with SElinux Permisive since using odin to flash stock does overwrite everything now I dont know if that kernel is good for ur build... since u came across the same Issue as me I'm guessing that u're currently on PB1 build which is the latest correct? so at least for now stay away from now.. I use that app as well and I'm working on getting it to work as we speak as Soon as I get it working I'll share my method with ya..
Click to expand...
Click to collapse
Hey Jay, why does Samsung have to be so difficult? Ahh! I'm sorry to hear that you're in the same boat as me but it is somewhat relieving to know that I am not in this alone. I will have to look at what build I have when I get home and get back to you. Getting this app to work is very important to me, so important that I will return the tablet if I cannot get it to work in the next 10 days and get something compatible. I'd love to help in any way that I can to get us both up and running. Please let me know!

mbducati said:
Hey Jay, why does Samsung have to be so difficult? Ahh! I'm sorry to hear that you're in the same boat as me but it is somewhat relieving to know that I am not in this alone. I will have to look at what build I have when I get home and get back to you. Getting this app to work is very important to me, so important that I will return the tablet if I cannot get it to work in the next 10 days and get something compatible. I'd love to help in any way that I can to get us both up and running. Please let me know!
Click to expand...
Click to collapse
It's weird bud I had never came across this problem, til now not only that I was having difficulty keeping root while on Stock rooted, but anyway to what's important I got the app to work yesterday after experimenting with kernels and what not, I couldn't get it to work on stock rooted so I move to flashing roms that is how I go it working. So flash this rom http://forum.xda-developers.com/tab-s2/development/rom-neked-nook-oj1-5-1-1-710-t3317823
follow this instructions:
1- Full wipe
2- Flash rom and Flash second file
3- reboot, here's where it gets tricky most likely u will encounter the same issue I did u gonna get a distortion on ur screen and blinking screen don't panic just let it boot once u are in the language selection screen turn it off now boot into recovery.
4- Flash last kernel.
5- Wipe cache/dalvik
Profit. Good luck.. let me know how it goes.

Mr_Jay_jay said:
It's weird bud I had never came across this problem, til now not only that I was having difficulty keeping root while on Stock rooted, but anyway to what's important I got the app to work yesterday after experimenting with kernels and what not, I couldn't get it to work on stock rooted so I move to flashing roms that is how I go it working. So flash this rom http://forum.xda-developers.com/tab-s2/development/rom-neked-nook-oj1-5-1-1-710-t3317823
follow this instructions:
1- Full wipe
2- Flash rom and Flash second file
3- reboot, here's where it gets tricky most likely u will encounter the same issue I did u gonna get a distortion on ur screen and blinking screen don't panic just let it boot once u are in the language selection screen turn it off now boot into recovery.
4- Flash last kernel.
5- Wipe cache/dalvik
Profit. Good luck.. let me know how it goes.
Click to expand...
Click to collapse
That is awesome news! Congratulations. I am very excited to do this when I get home tonight. I am sorry for my newb-ness (I do not do these types of things often) but I just want to make sure I don't mess something up. I am assuming that when I flash all of these files I am just booting into download mode, using Odin, selecting the files for AP and hitting start (please correct me if I am wrong). Can you please answer the questions in the bullets below?
follow this instructions:
1- Full wipe
Is this just a hard factory reset or do I have to wipe a specific way? Using TWRP?
2- Flash rom and Flash second file
Is this the proper order from this link? http://forum.xda-developers.com/tab-s2/development/rom-neked-nook-oj1-5-1-1-710-t3317823
1) Neked_Nook-710/810 - 810 users MUST flash this ROM and the file below after installing this ROM and BEFORE rebooting.
2) Neked_Nook-810-file-2 - 810 users MUST flash this- Flash this file AFTER flashing the ROM and BEFORE rebooting
3- reboot, here's where it gets tricky most likely u will encounter the same issue I did u gonna get a distortion on ur screen and blinking screen don't panic just let it boot once u are in the language selection screen turn it off now boot into recovery.
When I boot into recovery, am I booting into TWRP? Or did the full wipe clean this out? How do you flash from recovery as I would think it would be done in download mode + Odin.
4- Flash last kernel.
Do I flash this kernel? Permissive-OJ1-kernel-810.zip It was the first response in the thread. https://www.androidfilehost.com/?fid=24421527759882106
5- Wipe cache/dalvik
Do I wipe cache/dalvik before I reboot or can I do this after I reboot using SD2LINK or any app?
Again, I am sorry for my newbness but I just want to make sure I don't mess something up by accident. Thanks in advance.

mbducati said:
That is awesome news! Congratulations. I am very excited to do this when I get home tonight. I am sorry for my newb-ness (I do not do these types of things often) but I just want to make sure I don't mess something up. I am assuming that when I flash all of these files I am just booting into download mode, using Odin, selecting the files for AP and hitting start (please correct me if I am wrong). Can you please answer the questions in the bullets below?
follow this instructions:
1- Full wipe
Is this just a hard factory reset or do I have to wipe a specific way? Using TWRP?
2- Flash rom and Flash second file
Is this the proper order from this link? http://forum.xda-developers.com/tab-s2/development/rom-neked-nook-oj1-5-1-1-710-t3317823
1) Neked_Nook-710/810 - 810 users MUST flash this ROM and the file below after installing this ROM and BEFORE rebooting.
2) Neked_Nook-810-file-2 - 810 users MUST flash this- Flash this file AFTER flashing the ROM and BEFORE rebooting
3- reboot, here's where it gets tricky most likely u will encounter the same issue I did u gonna get a distortion on ur screen and blinking screen don't panic just let it boot once u are in the language selection screen turn it off now boot into recovery.
When I boot into recovery, am I booting into TWRP? Or did the full wipe clean this out? How do you flash from recovery as I would think it would be done in download mode + Odin.
4- Flash last kernel.
Do I flash this kernel? Permissive-OJ1-kernel-810.zip It was the first response in the thread. https://www.androidfilehost.com/?fid=24421527759882106
5- Wipe cache/dalvik
Do I wipe cache/dalvik before I reboot or can I do this after I reboot using SD2LINK or any app?
Again, I am sorry for my newbness but I just want to make sure I don't mess something up by accident. Thanks in advance.
Click to expand...
Click to collapse
At this point I'm assuming u have root and twrp installed, You will not need Odin at this point unless something goes wrong.
Before u start anything make sure u have all files inside ur tablet before wiping anything, also don't forget to make a back up of ur current Rom.
1-Everything is done in trwp recovery full wipe is System, cache, Dalvik, Data NOTHING ELSE DO NOT WIPE INTERNAL.
2- yes follow those instructions, FLASH THE ROM DO NOT REBOOT N THEN FLASH FILE 2. once that's done reboot. You will encounter a very glitchy system, don't panic wait til it fully reboots and then turn it off now boot into recovery again.
3- the full wipe will not erase TWRP u can't loose that unless u Odin stock. To boot into recovery just hold down Vol up+ home button+power when Tab s2 screen appears release after 2 or 3 secs now u will be in recovery. Once there u do what I already explained, flashing will be done with the install tab.
4- yes flash that kernel
5- Wipe after kernel finish flashing to avoid issues..
Good luck. Let me know if u have anymore questions

Mr_Jay_jay said:
At this point I'm assuming u have root and twrp installed, You will not need Odin at this point unless something goes wrong.
Before u start anything make sure u have all files inside ur tablet before wiping anything, also don't forget to make a back up of ur current Rom.
1-Everything is done in trwp recovery full wipe is System, cache, Dalvik, Data NOTHING ELSE DO NOT WIPE INTERNAL.
2- yes follow those instructions, FLASH THE ROM DO NOT REBOOT N THEN FLASH FILE 2. once that's done reboot. You will encounter a very glitchy system, don't panic wait til it fully reboots and then turn it off now boot into recovery again.
3- the full wipe will not erase TWRP u can't loose that unless u Odin stock. To boot into recovery just hold down Vol up+ home button+power when Tab s2 screen appears release after 2 or 3 secs now u will be in recovery. Once there u do what I already explained, flashing will be done with the install tab.
4- yes flash that kernel
5- Wipe after kernel finish flashing to avoid issues..
Good luck. Let me know if u have anymore questions
Click to expand...
Click to collapse
Awesome job! It works! Woohoooooo! I really appreciate our journey on getting us there , even thought you did all of the work. Thank you so much. I have a few more questions if you don't mind.
1) Samsung devices play games in low resolution so I downloaded Gamer Tuner (to max the res) but it says that the device is unsupported or not a Samsung device. I'm not sure what I can or cannot enable without confusing the system. I can't find a similar app out there either.
2) Now that my device is a Nook, lol. How do I get rid of all of the Nook stuff? Can I just start deleting stuff without consequence? Especially the main Nook page and preferable all of the buttons that say NOOK on them.
Again though, you did it and you're the man! Thank you good sir!

mbducati said:
Awesome job! It works! Woohoooooo! I really appreciate our journey on getting us there , even thought you did all of the work. Thank you so much. I have a few more questions if you don't mind.
1) Samsung devices play games in low resolution so I downloaded Gamer Tuner (to max the res) but it says that the device is unsupported or not a Samsung device. I'm not sure what I can or cannot enable without confusing the system. I can't find a similar app out there either.
2) Now that my device is a Nook, lol. How do I get rid of all of the Nook stuff? Can I just start deleting stuff without consequence? Especially the main Nook page and preferable all of the buttons that say NOOK on them.
Again though, you did it and you're the man! Thank you good sir!
Click to expand...
Click to collapse
For ur nook app problem this is the solution
If you DO NOT want the BNN interface/apps, you'll need to use a rooted explorer and delete /system/app/NookAMV. Then got to App Manager and uninstall Nook.app.
For the game tuner app do you get a gameservice error? I think the solution for ur problem lies in the apps that were removed if go back to the thread there are two zips that u need one is removed appso and the add+apps flashable. U need to pick from the removed appso zip and placed them into the add+apps flashable zip into the right folder and then flash it in twrp.
As for me is not that big of the deal either app since I play on my phone, and i'm glad u got it working just giving back to the community as they have given to me.

Mr_Jay_jay said:
For ur nook app problem this is the solution
If you DO NOT want the BNN interface/apps, you'll need to use a rooted explorer and delete /system/app/NookAMV. Then got to App Manager and uninstall Nook.app.
For the game tuner app do you get a gameservice error? I think the solution for ur problem lies in the apps that were removed if go back to the thread there are two zips that u need one is removed appso and the add+apps flashable. U need to pick from the removed appso zip and placed them into the add+apps flashable zip into the right folder and then flash it in twrp.
As for me is not that big of the deal either app since I play on my phone, and i'm glad u got it working just giving back to the community as they have given to me.
Click to expand...
Click to collapse
Thanks for the quick reply as always. Everything you said worked like a charm! I added the GameOptimizer app back and it allowed me to use the Samsung Game Tuner app to fix the resolution. You're the man! Last thing that seemed a little weird was when I restart - the tablet does not automatically connect to my home WiFi, I have to manually re-enter the password and connect. I am wondering if I need to add more apps back. I'll play with it more tomorrow but thanks again for your time and help!

mbducati said:
Thanks for the quick reply as always. Everything you said worked like a charm! I added the GameOptimizer app back and it allowed me to use the Samsung Game Tuner app to fix the resolution. You're the man! Last thing that seemed a little weird was when I restart - the tablet does not automatically connect to my home WiFi, I have to manually re-enter the password and connect. I am wondering if I need to add more apps back. I'll play with it more tomorrow but thanks again for your time and help!
Click to expand...
Click to collapse
I'm having minor issues with WiFi as well I don't know if it's kernel related or what best option is to ask in the ROM'so original thread... me having to put the WiFi password is yet to annoy me.. plus I'm not staying in this rom for long. Good luck to ya.. sorry I don't have the answer to this one.

Mr_Jay_jay said:
I'm having minor issues with WiFi as well I don't know if it's kernel related or what best option is to ask in the ROM'so original thread... me having to put the WiFi password is yet to annoy me.. plus I'm not staying in this rom for long. Good luck to ya.. sorry I don't have the answer to this one.
Click to expand...
Click to collapse
Hey Jay, I flashed the kernel (and wiped cache+kalvik) from this thread and it resolved my WiFi issue. Why did you say you didn't want to stay on this ROM?

mbducati said:
Hey Jay, I flashed the kernel (and wiped cache+kalvik) from this thread and it resolved my WiFi issue. Why did you say you didn't want to stay on this ROM?
Click to expand...
Click to collapse
Thanks for the Kernel info u beat me to it. Reason I'm moving is because since there isn't much development for this tablet yet (I'm staying optimistic that it will pick up) I much rather stay close to stock as much as possible.

mbducati said:
Hey Jay, I flashed the kernel (and wiped cache+kalvik) from this thread and it resolved my WiFi issue. Why did you say you didn't want to stay on this ROM?
Click to expand...
Click to collapse
Can I ask a favor from you? Can u check if ur tablet's microphone is working.. mine isn't I wanna know if it's the tablet or the ROM.. thanks in advance

Mr_Jay_jay said:
Can I ask a favor from you? Can u check if ur tablet's microphone is working.. mine isn't I wanna know if it's the tablet or the ROM.. thanks in advance
Click to expand...
Click to collapse
This appears to be a ROM issue, my microphone did not work in a video.

mbducati said:
This appears to be a ROM issue, my microphone did not work in a video.
Click to expand...
Click to collapse
Thanks bud just what I needed it to move out of this rom... thanks again...

Mr_Jay_jay said:
Thanks bud just what I needed it to move out of this rom... thanks again...
Click to expand...
Click to collapse
Please dm me and let me know where you go. I want to get on something without these issues as well, lol.