Develop Bugs

[Q] Downloading from android market UK.

Has any one got a solution to why the android market will let you download some apps but not others. This problem only happens with certain apps.
Contacted one of the app developers, and he thinks there may be a problem with my data partition.
I'm on stock rom, latest froyo update, and have not rooted. thanks, in advance, for your help.

Do you get an error message?

I just get the message installation unsuccessful

Try resetting ur phone and clear cach or make a different Google account
Sent from my Desire HD using XDA App

region and ROM version also apply

Go to menu/settings/applications/manage applications click the all tab and scroll down to market. Clear data and cache. That should fix it.
Sent from my Motorola Startac running Atari 2600 software!

pwraggcan said:
Go to menu/settings/applications/manage applications click the all tab and scroll down to market. Clear data and cache. That should fix it.
Click to expand...
Click to collapse
+1 for this but if not can you list some example apps so we can see if it's just you (B. East) or not?

The apps i seem to have a problem with are, Cordy the game, storage analyzer, and gun brothers game. I some times have problems with updating from the market. I have to un-install some apps then download them again to update. this happens when the app has been moved to the sd card, but not with all the apps that I have moved to the sd card

B. East said:
The apps i seem to have a problem with are, Cordy the game, storage analyzer, and gun brothers game.
Click to expand...
Click to collapse
No problems here. This is going to be something up with your phone.
B. East said:
I some times have problems with updating from the market. I have to un-install some apps then download them again to update. this happens when the app has been moved to the sd card, but not with all the apps that I have moved to the sd card
Click to expand...
Click to collapse
Not all apps like being on the SD Card. Do all your apps specifically say they have been updated to allow them to be moved to sd card?
You may have to move them to phone if they continue to cause issues (and to be honest, with a 1GB internal memory, putting apps onto a slow sd card really isn't worth doing.
pwraggcan said:
Go to menu/settings/applications/manage applications click the all tab and scroll down to market. Clear data and cache. That should fix it.
Click to expand...
Click to collapse
Did you try this?
If all of the above fails to work you will probably have to factory reset the phone.

I tend to download using wifi, going to try downloading over 3g and see if that makes any difference, if not, will do a factory reset. thanks for the help though.

Before you do that you still haven't said if you cleared the market cache. Did you?

yes, i done that, tried to download again and got a message, "could not install on USB storage or sd card". First time I have seen that message.

Is this whilst trying to update an app or download a new one?
If to update then move the app to the phone first.

this is trying to download a new app.

Had a quick Google and found something to try.
mount the phone so you can access the sdcard.
Set to show hidden files
Go to folder .android_secure
Delete a file in there smdl2tmp1.asec
Then try again.

thanks, I will give it a go. can I use a file explorer to do this, because am not sure how you mount the phone, I am quite new to android, use to use winmo mobiles

you can yes, my favourites are Astro, Linda and ES.

I had a look in android_secure, made sure all hidden files would be visible, and could not find any files at all. checked to make sure that the hidden file visible setting in the file explorer was switched to the correct setting, and could not see any files at all.
Have I lost some files? if i have i have no idea how. do I need to do a factory reset?

B. East said:
I had a look in android_secure, made sure all hidden files would be visible, and could not find any files at all. checked to make sure that the hidden file visible setting in the file explorer was switched to the correct setting, and could not see any files at all.
Have I lost some files? if i have i have no idea how. do I need to do a factory reset?
Click to expand...
Click to collapse
Damn. When I found that possible solution I noticed that as many people said they did have it as said they didn't. I was hoping you would be lucky.
In this case the same file (apparently this is a known bug and has been marked for next version fix) is being stored in the system directory of the phone and without root you can't get access to it.
I'm afraid the only way to clear it (without root) is a factory reset, sorry.

thanks for your help, I will factory reset and see what happens.

[Q] Couldn't capture screenshot. Storage may be in use.

Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?

Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium

msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.

Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.

I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.

4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium

No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.

Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.

Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?

I fixed this deleting the "pictures" folder with RootExplorer.

jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!

bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .

My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.

On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!

Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.

Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0

/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk

Help with endless nested /0/0/0/0 folders

Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks

Bro you need to use a file explorer from recovery. TWRP custom recovery has a built-in file explorer. That should do the trick
Sent from my SGH-T999 using Tapatalk

aussie88 said:
Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks
Click to expand...
Click to collapse
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.

fingolfin14 said:
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.
Click to expand...
Click to collapse
Yep I figured that out the hard way lol. Already upgraded to the latest version of CWM to prevent it from happening anymore. Now to get the files out from down there... :banghead:
Sent from my SGH-T999 using xda app-developers app

On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.

Perseus71 said:
On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.
Click to expand...
Click to collapse
I saw that somewhere and tried that. Doesnt seem to be having any effect. Unless im doing it wrong...
I'm plugging my phone into my computer, accessing the phone section when it comes up, going about 20 0s deep and copying it back to the root. It either crashes my windows explorer, or doesnt seem to be doing anything(i think because its already disconnected itself. i tried making a new folder and it wouldn't let). what am i doing wrong?
PS. how would i access my phones internal SD from DOS?
thanks

Try ADB FileExplorer that should not time out on Windows. I have also tried Android File Manager with success. If that does not work, I will look up other options.

Well i tried android file manager. Im not 100% sure exactly how these programs work, but either way its saying i dont have root access. I do and i also have chainfires adbd insecure app which should give me full root access, but its still not working.
I looked at ADB FileExplorer too, but i didnt really get it and it kept saying it couldnt find my phone and something about an incorrect path.

With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.

Perseus71 said:
With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.
Click to expand...
Click to collapse
It never asked for root on my phone. I've tried all the changes and everything else that people have recommended, but im still not having any luck. I guess im too much of a noob for all this lol :crying:

Try Re-mounting internal SD in Recovery and then connect to PC.

nope, still no luck. Its still saying no root and no supersu request is coming up. I guess im missing something....
EDIT: I seem to somehow be "losing" root every time i try to connect to the android file manager. i open an app that requires root and it says i dont have root. I have to reboot my phone to get root to work again. It's weird though, because SuperSU opens fine...

open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card

Lieu10ant said:
open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card
Click to expand...
Click to collapse
If only it was that easy. its behind 400 nested folders. Windows cant go that deep. it freezes and FC's after about 200.
Im giving my phone in to get my power button repaired, so i guess ill ask the software tech there if he can figure it out. But thank you Perseus for all your help last night. :good:

I also have this problem guys, how do i update my custom recovery please?

[stock 4.4.2] SD card write fix.

The first thing that bothered me after updating to stock 4.4.2 is the lack of SD card write for media.
Well here i fixed that, (ROOTED users only)
using your root explorer, navigate to /system/etc/permissions/
now look for "platform.xml" back up this file somewhere in case anything goes wrong.
now replace this file with the modified file attached, set correct permissions and reboot!
In case anyone is wondering what change is in the modified file, it is a permission added to write media to sdcard, ( "<group gid="media_rw" />" under external storage)
unzip the attached file (it should read platform.xml), and do leave the feedback.

is it same wtih this program?
https://play.google.com/store/apps/details?id=nextapp.sdfix
is it possible to change the directory of SD card just like previous OS
in kit kat directory is "storage/sdcard1"
in previous OS is ""storage/removeable/sdcard1"
because of this some of my app couldn't detected the data

raitokun said:
is it same wtih this program?
https://play.google.com/store/apps/details?id=nextapp.sdfix
is it possible to change the directory of SD card just like previous OS
in kit kat directory is "storage/sdcard1"
in previous OS is ""storage/removeable/sdcard1"
because of this some of my app couldn't detected the data
Click to expand...
Click to collapse
havent tried the app, but then again why would you want to keep an extra app for something that can be fixed
This doesnt change the directory, only allows the apps to write to sd card.

raitokun said:
is it same wtih this program?
https://play.google.com/store/apps/details?id=nextapp.sdfix
is it possible to change the directory of SD card just like previous OS
in kit kat directory is "storage/sdcard1"
in previous OS is ""storage/removeable/sdcard1"
because of this some of my app couldn't detected the data
Click to expand...
Click to collapse
xyge said:
havent tried the app, but then again why would you want to keep an extra app for something that can be fixed
This doesnt change the directory, only allows the apps to write to sd card.
Click to expand...
Click to collapse
install app, run app, uninstall app. solved with no user interference between and safe from bootloops. also, on JellyBean the sdcard direcotry was the same as KK (storage/sdcard1)

xkeita said:
install app, run app, uninstall app. solved with no user interference between and safe from bootloops. also, on JellyBean the sdcard direcotry was the same as KK (storage/sdcard1)
Click to expand...
Click to collapse
Well part of the reason why I prefer Android is the learning and understanding that comes with messing around with it, so I prefer modifying the system as per my needs
With that said, if the app doesn't require to be kept after fixing the issue it's definitely a good option for the ones who don't want to go with all the trouble.
Sent from my C6502 using Tapatalk

xyge said:
Well part of the reason why I prefer Android is the learning and understanding that comes with messing around with it, so I prefer modifying the system as per my needs
With that said, if the app doesn't require to be kept after fixing the issue it's definitely a good option for the ones who don't want to go with all the trouble.
Sent from my C6502 using Tapatalk
Click to expand...
Click to collapse
I know bro, I'm usually doing things with android modifying stuff here and there but sadly most users won't even do a single search after getting into a problem and that's kinda irritating after some time...

[Q] Hating Kitkat 4.4.2. Need help finding work around for Dropsync or else...

Since updating to Kitkat 4.4 I've lost the ability to sync files and folders on my MicroSD card.
There is a work around provided by the dropsync developers where you put your files in the /Android/data/com.ttxapps.dropsync/files folder on your microSD card and you're supposed to be able to sync there. However I don't have the 'com.ttxapps.dropsync/files' folder in my microSD card. In fact there is nothing in there that appears to be associated with dropsync. I even tried uninstalling and reinstalling dropsync to see if those folders would be generated but they were not.
So I tried creating those folders in there myself and dropping my folders and files to be synced in there as well. When I tried to set the sync settings through dropsync it says that those folders cannot be two-way synced.
Does anyone have some advice for me? I really don't want to root because I don't want to void my warranty, but if there is absolutely no other way of resolving this issue that I may end up doing so.
Does anyone think android will change their minds about this and let apps write to the microSD card in a later update?

gina$zanboti said:
Since updating to Kitkat 4.4 I've lost the ability to sync files and folders on my MicroSD card.
There is a work around provided by the dropsync developers where you put your files in the /Android/data/com.ttxapps.dropsync/files folder on your microSD card and you're supposed to be able to sync there. However I don't have the 'com.ttxapps.dropsync/files' folder in my microSD card. In fact there is nothing in there that appears to be associated with dropsync. I even tried uninstalling and reinstalling dropsync to see if those folders would be generated but they were not.
So I tried creating those folders in there myself and dropping my folders and files to be synced in there as well. When I tried to set the sync settings through dropsync it says that those folders cannot be two-way synced.
Does anyone have some advice for me? I really don't want to root because I don't want to void my warranty, but if there is absolutely no other way of resolving this issue that I may end up doing so.
Does anyone think android will change their minds about this and let apps write to the microSD card in a later update?
Click to expand...
Click to collapse
Did you used a system file manager app to create the folder (file manager app build in with the O/S)? you can't create with a third party file manager. Give it a try. If that's not working then you need....ROOT!!!

buhohitr said:
Did you used a system file manager app to create the folder (file manager app build in with the O/S)? you can't create with a third party file manager. Give it a try. If that's not working then you need....ROOT!!!
Click to expand...
Click to collapse
I used the "My Files" app which was already installed on the device. I'm pretty sure it's androids thing.

gina$zanboti said:
I used the "My Files" app which was already installed on the device. I'm pretty sure it's androids thing.
Click to expand...
Click to collapse
yep that's the system file manager. Tell you the truth, if your sync app already installed before you upgrade then you may have a chance, but if you install the app after the 4.4 upgrade then, most likely it's not going to work...just my observation.

buhohitr said:
yep that's the system file manager. Tell you the truth, if your sync app already installed before you upgrade then you may have a chance, but if you install the app after the 4.4 upgrade then, most likely it's not going to work...just my observation.
Click to expand...
Click to collapse
It was installed and set up to sync all my files before the upgrade. It was working perfectly until I updated to Kitkat. Now it's all gone to hell and I'm about ready to root. This irritates me so much.

gina$zanboti said:
It was installed and set up to sync all my files before the upgrade. It was working perfectly until I updated to Kitkat. Now it's all gone to hell and I'm about ready to root. This irritates me so much.
Click to expand...
Click to collapse
BTW, what model of your device?

buhohitr said:
BTW, what model of your device?
Click to expand...
Click to collapse
SM-P600. It's the 16gb wifi.

Would downgrading my firmware void my warranty?

gina$zanboti said:
Would downgrading my firmware void my warranty?
Click to expand...
Click to collapse
With the p600, your warranty will be voided if you try to root and you can't not downgrade.

buhohitr said:
With the p600, your warranty will be voided if you try to root and you can't not downgrade.
Click to expand...
Click to collapse
Ugh... I'm completely updated with the stock firmware (installed the 103mb update earlier today). Will this tutorial still work for it?

gina$zanboti said:
Ugh... I'm completely updated with the stock firmware (installed the 103mb update earlier today). Will this tutorial still work for it?
Click to expand...
Click to collapse
Yes the link is good, but the files are not up to date here is mine;
1) Download this file https://dl.dropboxusercontent.com/u/...ixx-smp600.zip then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here https://goo.im/devs/OpenRecovery/lt03wifiue/
That's all!