Related
Hi, I would like to De-Odex the rom I currently have on my phone.
Is there an easy way to do this?
I've read:
http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
and
http://www.droidxforums.com/forum/droid-x-themes/4620-how-manually-deodex-your-phone.html (there is also a post about this on here)
The xUltimate tool will not work for me, so I need another option.
Phone: HTC Evo
ROM: Stock 3.29 OTA
Rooted (ofc)
Thanks for the help.
Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App
TheMagicalSock said:
Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I've been switching between roms but I keep coming back to my original stock one. It's still odex'd and I would like to theme the battery icon on the status bar without having to set everything back up on a fresh rom. Since it reads half when 80% of my battery is remaining.
Thanks for the quick response.
Sent from my Evo using XDA App.
and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!
Max_Pain said:
and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!
Click to expand...
Click to collapse
It wasn't that it didn't work.
I just got an error with Java, not sure how to fix it. Some said to re install java, but i've installed JRE and JDK from 5u20 to 6u21 (32 and 64 bit). Everything I tried gave the same error.
I am going to try asking on their forum and see if they can tell me what I did wrong.
I have a feeling it has to do with the 3.29 OTA update. :-/
Good luck and if you get it to work please let me know your setup.
and if you can't run step 3 let me know... that way I am not the only one to seem that crazy.
option 1 and 2 just adb pulls your /system/apps and your framework.
just got stuck starting option 3:
Starting AccountSyncManager.odex
*Deodexing...
Error occurred while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException....
lower it says
at org.jf.baksmali.baksmali.dissambleDexFile(baksmali.java:103)
and it just gives some more errors until i close it down
i was sooo excited to get this done!
Ahhh! I'll see what I can find out on their forums.
Despite the tutorial saying "Manually De-Odex Your Phone" I think it may be just for droid phones. It was posted in the Moto Droid sections of the forums.
Here is the error I was getting:
Code:
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.NullPointerException
at java.util.Properties$LineReader.readLine(Unknown Source)
at java.util.Properties.load0(Unknown Source)
at java.util.Properties.load(Unknown Source)
at org.jf.baksmali.main.<clinit>(main.java:69)
Could not find the main class: org.jf.baksmali.main. Program will exit.
Press any key to continue . . .
dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!
Max_Pain said:
dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!
Click to expand...
Click to collapse
If you want to add anything my post is located:
http://www.droidforums.net/forum/xeudoxus/85223-xultimate-errors.html
Both our problems have "org.jf.baksmali" involved.
Hopefully we'll have some answers soon.
well i ran a test and everything said pass, including the odex and deodex. i installed the latest java, and same problem. i had the phone originally as mass storage, so i tried under charge only, and still same problem.
i really hope we get a solution to this
I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...
Max_Pain said:
I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...
Click to expand...
Click to collapse
Were you able to get it DeOdexed?
I found this after some searching... It seems to be the LONG way to deodex an apk. It was written in 2009 so idk how reliable it will be.
http://androidnetwork.org/forum/viewtopic.php?f=11&t=55
Edit: Link to Avabox: http://forum.xda-developers.com/showthread.php?t=697459
[UPDATE] I tried Avabox and it de-odexed all of the files that I adb pulled. I copied the De-Odexed files back to their respective folder on the /system/, and deleted "rm /system/app/*.odex" (Removing all the .odex files) and rebooted.
I got stuck on the white "HTC Evo 4G" screen and could not get passed it.
I am not sure what I messed up. Maybe I need to resign the files? I'll try that tomorrow.
Let me know how your attempt went. :]
When I left for school I left the script deodexing my app folder...it seems to have done the job and there were no errors. It's doing the process for the framework files now.
Once I move it over to the phone we 'll see if it worked...
I'll update here when I find out...
Swyped from an HTC Evo on MetroPCS...
i just tried that too and i got stock in a bootloop.
the avabox script does deodex all the app files. it doesn't do that for the framework files...it seems it'll only deodex .apk files.
anyways, i deleted everything from my /system/app folder and then pushed over the deodexed apks...i also did this for the two apk files from system/framework and the phone did the bootloop thing. so i put back the original /system/framework files, effectively only leaving changed the contents of /framework/app/ and still, bootlooping.
i'm restoring right now...i'll try it some more at another time.
let me know if you figure it out!
I was reading some of the comments on this thread(http://forum.xda-developers.com/showthread.php?t=598026) They we're saying about problems with de-odexing the framework.
Do we need to resign system apps before we push them back?
I am optimizing my apks now, going to batch resign then try putting just the apks back on.
Well I messages avalaunchmods asking the same thing...if anyone knows it should be him...
Update if you get it working please!
Swyped from an HTC Evo on MetroPCS...
Unfortunately, I still don't have any good news. :[
I tried resigning the de-odexed apk's and replacing the ones on my phone.
This got stuck at the white HTC Evo 4G screen.
This failed
Then I optimized, signed, and zipaligned.
This threw me into an actual boot loop. (I was excited... It's the first boot loop i've gotten.)
This failed.
Here is some semi-less-bad news.
I used http://circle.glx.nl/ to make a flashable update.zip for theme-ing. I Flashed it with success and was able to get to the lock screen. Sense UI along with just about every other system app kept force closing.
But I was able to successfully (even though I got FC's) theme and boot using that kitchen.
I am going to mess around with the different settings there and see if I can atleast theme my phone.
Any luck with your attempts?
i was at school all day - no news from me. this is very discouraging though.
i'm surprised nobody else has chimed in! considering how many people are making and releasing roms, some people must know what's going on here
Good news (kinda)
I was able to theme my framework-res.apk without any errors or FC's.
I didn't do anything to De-Odex it but it accepted the theme when I manually edited it.
There must be an xml that scripts how the battery is displaying %'s
since I have 89% of my battery remaining but the themed battery is showing 80%.
I'll dig around and see where it is and add it to my next framework recompile.
We're you interested in just themeing or the whole de-odexing (apps & framework)
If you want to theme it i'll write up a decent tutorial on what I did.
If not I'll write up a quick tutorial for the next root newbie who wants to theme.
Going to test run it and make sure I didn't mess much up.
Edit3: The bad, it would appear that you can't modify the .xml's of the framework. You can only change the pictures.
So the battery wont be able to have the exact %.
Modifying of any .xml leads me to a boot loop.
Tips are appreciated on fixing this.
I'll keep trying.
so here is what i've learned.
i had modified both .com.htc.resources and framework-res before. those files, at least in my rom, are not odexed. everything else in the framework folder is a mix of files, .jar files and other formats, including services.jar, which is odexed. that's why if we change the services.jar file, without the phone being deodexed, it wont work.
that's why i want to deodex my rom. i have too many changes already and dont want to re-do them in another, deodexed rom.
my main interest in deodexing the rom is to have the working battery percentage on top (which used to work on THIS rom before, without deodexing???) and to have a transparent notification tray.
and from there being able to make any other changes as they come up...
i'll see when i have some more time to try out other options, but chances are you will have time before me, so keep updating!
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
Hey everyone!
I am rooted and bootloader unlocked. Inexperienced at flashing roms and don't have the time to experiment right now. I am getting the over the air V9 update nag and it is really starting to piss me off! I found this site that claims to have found a way to stop the nag for the OTA by faking the phone into thinking it already has it. Its for an older version of Android but I was wondering if the concensus thinks it will work and if someone can post an image of what the updated build prop should say so I can try this method out.
I have less then 10 posts so I cant post a link or a pic of what Build Prop looks like
Thanks,
Mark
This is from rootzwiki
It seems like I was able to find an interesting OTA notification kill method:
I have a GC FE 2.0 setup I like to use sometimes, and the OTA was annoying the balls out of me. Note that the new update hasn't rolled out to me yet. But on GC FE 2.0, the methods you guys described above did not work. I could not not an update file in cache. Instead, I did the following steps as described below and I have no update notification anymore. All the other threads regarding the GC FE 2.0 OTA update notification just turned into a "install GB, FE sucks" fest. :/
Here is what should work:
Open Root Explorer, browse to /system, mount R/W, long press build.prop, and select Open in Text Editor.
Find the line:
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/EP4:user/release-keys
Change this line to whatever the new ROM's equivelent build.prop's line is. I suspect that just "EP4" needs to be changed to "FP1".
Save the changes to the build.prop file.
Restart twice or more. I had to restart 3 times to get data back.
Disclaimer: Since I actually haven't tested this method with the new update, I don't know if it will work. Somebody will need to find what the line in build.prop for the new FP1 update is. You should be able to pull the build.prop from the new ROM or find somebody that has taken the update to get you the value of that line. Also, if puppies die because you did this, it's not my fault.
Dr. Mark said:
Hey everyone!
I am rooted and bootloader unlocked. Inexperienced at flashing roms and don't have the time to experiment right now. I am getting the over the air V9 update nag and it is really starting to piss me off! I found this site that claims to have found a way to stop the nag for the OTA by faking the phone into thinking it already has it. Its for an older version of Android but I was wondering if the concensus thinks it will work and if someone can post an image of what the updated build prop should say so I can try this method out.
I have less then 10 posts so I cant post a link or a pic of what Build Prop looks like
Thanks,
Mark
This is from rootzwiki
It seems like I was able to find an interesting OTA notification kill method:
I have a GC FE 2.0 setup I like to use sometimes, and the OTA was annoying the balls out of me. Note that the new update hasn't rolled out to me yet. But on GC FE 2.0, the methods you guys described above did not work. I could not not an update file in cache. Instead, I did the following steps as described below and I have no update notification anymore. All the other threads regarding the GC FE 2.0 OTA update notification just turned into a "install GB, FE sucks" fest. :/
Here is what should work:
Open Root Explorer, browse to /system, mount R/W, long press build.prop, and select Open in Text Editor.
Find the line:
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/EP4:user/release-keys
Change this line to whatever the new ROM's equivelent build.prop's line is. I suspect that just "EP4" needs to be changed to "FP1".
Save the changes to the build.prop file.
Restart twice or more. I had to restart 3 times to get data back.
Disclaimer: Since I actually haven't tested this method with the new update, I don't know if it will work. Somebody will need to find what the line in build.prop for the new FP1 update is. You should be able to pull the build.prop from the new ROM or find somebody that has taken the update to get you the value of that line. Also, if puppies die because you did this, it's not my fault.
Click to expand...
Click to collapse
not to burst your bubble but someone already figured a way to stop it lol
http://forum.xda-developers.com/showthread.php?t=2098477
javskies said:
not to burst your bubble but someone already figured a way to stop it lol
http://forum.xda-developers.com/showthread.php?t=2098477
Click to expand...
Click to collapse
Not sure what you mean about bursting my bubble but thanks fot the link, it worked!
Dr. Mark said:
Not sure what you mean about bursting my bubble but thanks fot the link, it worked!
Click to expand...
Click to collapse
i was being really lazy and didnt feel like reading your entire post so i thought it was a how to lol. no prob!
Could someone hook me up with an untouched copy of lg framework apk and framework apk por favor??
C'mon someone else besides me has to be still running stock.. It is a very easy copy and upload, please help a brother out.
Im sorry, I tried to be patient. I am pretty sure Ive helped more than a few people out around here. All Im asking for is about 5mins or less for someone to copy and upload these. I didnt screw anything up, just want to remove some mods I flashed a long time ago in which I no longer have a copy of.
Swizzle82 said:
Im sorry, I tried to be patient. I am pretty sure Ive helped more than a few people out around here. All Im asking for is about 5mins or less for someone to copy and upload these. I didnt screw anything up, just want to remove some mods I flashed a long time ago in which I no longer have a copy of.
Click to expand...
Click to collapse
Idk what your currently running, if its bone stock or what but you should be able to rip what you need from a rom download/. I unfortunately am running aosp or else I would help you in a heartbeat. There are alternate methods though!! good luck... also just came to mind, try pulling it from a nand or twrp backup.
Yeah I flashed these so long ago I dont have that backup anymore. Im pure stock as far as rom goes Im on 10m. I found some from 10c but its the framework and one thing you most definetly need the matching version of. I dont have my computer for a while so I cant return to stock and start over.
Thanks for the reply though.
Downloaded and extracted from zone rom.. All good now.
Ok let me be really specific i have flashed stock firmware through odin, i have done clean wipes, i have done every possible thing in my power but still experience horrible tablet preformance i get app stops and restarts everytime even after i have flashed on odin no one here has been able to help me they tell me to do the same thing over and over download stock firmware and flash, do a clean wipe iv'e done it all please help i know someone can i think its a file in the screenshots i enclosed that is corrupted but i have no idea which one is it. its not the system or the kernel it is something deeper please help i am begging you developers
k,
no offense, but your post is wildly disrespectful. [frowny face]
you are basically putting the proper ownership of your error off on others.
to be fair, in your ignorance you flashed a firmware without first doing some research on the topic.
a noobish mistake, it happens, i've done it.
there were plenty of threads created prior to your experience warning of new samsung releases
overwriting bootloaders and how to navigate the issue.
from my interaction with you, i think i am accurate in saying you did not do the aforementioned research.
i for one took time to describe a way to "fix" your issue. You chose not to attempt it, which is fair. It is risky.
Cool.
However, lots of the users you've interacted with on xda have a fair to expert handle on how to get things done.
they do what they can to help, they cannot be expected to compensate for another's impatience, lack of attention
to detail and/or incompetence/ineptitude.
m
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
kgalv419 said:
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
Click to expand...
Click to collapse
hmm,
okay, different approach.
http://m.youtube.com/watch?v=JmvCpR45LKA
just a refresher.
now,
screenshots of directories are next to useless.
what's needed is , at the very least a logcat.
to get that or anything else moving you need,
custom recovery installed.
root.
busybox.
adb setup properly on pc.
the ability to describe you problem in words other than my thing doesn't work.
the sense not to keep creating thread after thread concerning the same issue.
if you are that insistent on undoing what you have done, my previous suggestion to you is probably the best bet.
if you want "Professional" help then seek a repair service.
Savvy?
m
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
kgalv419 said:
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
Click to expand...
Click to collapse
k,
okay, cool. sorry for being so rough on you.
i am downloading a copy of 4.4.2 firmware though linking me to the firmware
you initially flashed would be good.
what would be better is if you still have the firmware file crack it open with 7zip and get me a list
of the files [.img, .bin] inside.
run logcat after you boot up. attach to post as text file
then run your routine to where you get your issue, fc's etc and run logcat again and post as text [2]
m
okay it looks like i am not going to be downloading the 4.4.2 firmware.
downloads break from the one source i found
and i have no interest in joining the other site. that's bull****.
so if you can get me the list of files contained in the realease that would be helpful.
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
kgalv419 said:
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
Click to expand...
Click to collapse
k,
dude, where's my car ? [log ?] :silly:
m
Here bro
kgalv419 said:
Here bro
Click to expand...
Click to collapse
k,
i am going to guess you are trying to run a battery/governor tweaker ?
i am going to guess when you type getenforce in terminal
your output will be enforcing.
i am guessing when you resend your logcat you will do so after
typing su
and then
logcat -d > /sdcard/logcat.txt
if my guesses as to the app and selinux are correct you;
a- need to let the app go into the dustbin of history
b- need to look for a tutorial on dumping/unpacking/customizing/repacking/reflashing your boot.img
in order to disable selinux and make it stick.
if my guesses are wrong it is because;
the log you posted is super-lame [sorry] use your terminal, not a catlog app.
you have yet to tell me what app are giving you your headache. in which event is an issue between you
and the app's developer.
lastly you should be question the developer of the rom.
m
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
kgalv419 said:
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
Click to expand...
Click to collapse
k,
okay, this ---> android.permission.INTERACT_ACROSS_USERS_FULL is the ballbuster.
it's connected to , from what i've read so far , a maybe faulty root and multiuser.
what version supersu are you using ? unroot and then reroot trying from version 1.97 maybe to 1.99.
kill multiuser and clear out any suspect accounts in settings. will post back if i find something more conclusive.
you can jump in as well by searching the error i mentioned.
android.permission.INTERACT_ACROSS_USERS_FULL
m
@kgalv419
edit after rooting set actions to auto grant permission and trust system
EDIT - disable xposed modules - xprivacy if you're running it.
QUESTION - THIS IS A JELLYBEAN ROM ? seems to be a jellybean issue...
EDIT-EDIT i found this... http://forum.xda-developers.com/gal...card-app-data-to-extsdcard-tw-t2178863/page16
read that page looking specifically at the portion concerning /system/etc/permissions/platform.xml
you may need to add/edit the line for
android.permission.INTERACT_ACROSS_USERS_FULL
with the proper uid [user identification] meaning the right number/symbol for root,shell,ewok, etc.
the entry looks something like this;
<assign-permission name="android.permission.INTERACT_ACROSS_USERS_FULL" uid="shell" />
and remember to reset the file's permissions correctly - 644
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
kgalv419 said:
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
Click to expand...
Click to collapse
In a situation like this thinking is guessing = no good.
re-read previous post. search, test, verify. Don't guess [think].
m
Yes bro trust me I'm trying
Are you able to flash CWM and root your device ?
I will advise what is next to be done....
Sent from my SM-T211 using XDA Free mobile app
Yes I already have it rooted with philz touch recovery
Wipe format every single partition that you see remove 1st your ext sd card this will empty all folders then redo tne Odin part
Sent from my SM-T211 using XDA Free mobile app
By every single partition you mean including those folders like acc, and others in the device?