For those of you who may not have taken kindly to Asus' skinning of our beloved Honeycomb OS, you will be happy to know that it's possible to change some aspects of the UI to make it look more "stock". The most notable change that Asus has made, was with the replacement of the stock Honeycomb navigation keys with icons that seem less sleek and frankly, just don't flow with the holographic theme of the OS.
To combat Asus' lack of taste, it's possible, with some hackery, to get the stock navigation icons that you would find on the Motorola Xoom. If you are at all confused of what icons I am speaking of, it's the back, home and multitasking icon located at the bottom left of the screen; they will be changed to look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While I do enjoy the custom Asus widgets that were included in the Transformer, I would much rather prefer the navigation buttons native to a stock Honeycomb OS. I am always "pro-vanilla" when it comes to Android because system updates will most likely be pushed out faster to the user if the manufacturer didn't have to waste more time putting in their little touches to the user interface-I digress.
The procedure is simple but it does require you HAVE ROOT! The easiest way, believe it or not, is to use ADB and the command prompt to effectively change the necessary files. You can install ADB from the official Android development site:
http://developer.android.com
For your convenience, I have already made a backup of the file you will be replacing (see the end of the article) such that, if you ever need to revert to the "stock" Asus theme, then you just need to download the file and use the same procedure below.
Lets get started! All credit goes to XDA member JaiaV. I am simply making a how-to & we are not responsible if you brick your device.
1) Download this file if you are on Android 3.0.1:
Modified SystemUI.apk
Download this file if you are on Android 3.1:
http://dl.dropbox.com/u/2993232/modified/3.1/SystemUI.apk
Prime 1.4
http://db.tt/UI10NAk
Thanks Andrew2511
thanks xformulax
Put this file inside the folder that contains the adb.exe (probably quicker if you just search for it using the native Windows search tool). If you are using the newest version of the developer tools then the folder that contains the ADB.exe should be called "Platform-tools"; put the file in the Platform-tools folder. This way, when you run the ADB command below, the system will know where the file you just downloaded is, which makes everyone's life easier.
2) Enable USB Debugging on your tablet by going into your settings > Applications > Development
3) Plug your Transformer into your Windows machine
4) Launch up your command prompt
5) **REMEMBER, YOU NEED TO HAVE ADB INSTALLED PRIOR TO DOING THIS**
Type in:
Code:
adb devices
you should see your device connected. It should look like this:
6) Once you know your device is connected properly, type in:
Code:
adb remount
7) Next, you just have to type in:
Code:
adb push SystemUI.apk /system/app
8 ) Lastly, to reboot your system quickly, type in:
Code:
adb reboot
If for some reason you would like to go back to stock, its pretty simple. All you have to do is download the file below:
For 3.0.1:
Stock SystemUI.apk
For 3.1:
http://db.tt/eQkoYIk
Then just repeat the procedure above (starting from number 6) and you are all set to go! Just a quick way to make your Asus Transformer look just a bit more awesome!
perhaps this should be in themes...
Sent from my Transformer
www.AsusTransform.com
www.AsusTransform.com/forum
xda doesnt support html.
my mistake, rushed it. fixed
It's pretty easy to do this for yourself for w/e version of the FW you happen to be using. Just adb pull your SystemUI.apk, open it up in your favorite zip/rar application, navigate to the /res/drawable-mdpi folder, and backup the ic_sysbar_home/back/recent/menu images. Should be default/pressed for each. Then move the Xoom/stock images from my SystemUI.apk (made from a deodexed Prime 1.3 SystemUI.apk, thanks to Roach and DC13, I just changed the button images) or a stock Xoom rom into your SystemUI.apk, save. Then push your modded SystemUI.apk into /system/app and you're done.
If you use a rom you can also switch out the modded SystemUI.apk in the zip file you flash, that way if you have to reinstall (or before you install a new image) you don't have to manually move the apk in afterwards. I suggest using the SystemUI.apk that came with the FW version of the rom you're using, as there can be some inconsistencies between a few.
personally i like the icons asus made better, but i don't like that they're white. too bright compared to everything else on the dock.
luckily thats a quick fix once i finally root.
i can adb devices
can someone please help me. i can not get past "adb remount"
gives me an error: "remount failed: operation not permitted"
BBjaiBev said:
i can adb devices
can someone please help me. i can not get past "adb remount"
gives me an error: "remount failed: operation not permitted"
Click to expand...
Click to collapse
You need root.
this doesn't work on 3.1. Any chance of an update?
Sent from my Transformer TF101 using XDA Premium App
mattykellyuk said:
this doesn't work on 3.1. Any chance of an update?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I'd like them on 3.1 too...
djdevine2 said:
I'd like them on 3.1 too...
Click to expand...
Click to collapse
updated! enjoy.
neok44 said:
personally i like the icons asus made better, but i don't like that they're white. too bright compared to everything else on the dock.
luckily thats a quick fix once i finally root.
Click to expand...
Click to collapse
+1, not to harp on the OP, but the Asus Icons (even the Samsung TouchWiz Icons) are much more visually appealing and intuitive to me.
But that's a personal preference. This guide should be useful to anyone looking to make custom icons.
Yep, this thread shows quite nicely that nothing is right for everyone. Me, if there was one thing about the Transformer's styling I would change, it's the stock Google clock font. To me, it looks like cheap and amateurish, and the styling doesn't really fit or match anything else in the OS (other than perhaps the buttons that Asus changed.)
I hope in a future release, Google makes these things user-styleable. I'd much rather have a different font for the clock, which could make it instantly more readable while saving valuable screen space to boot.
But obviously other people are perfectly happy with it...
I flashed the Xoom ones which worked fine but I didn't like them to pushed the original ASUS ones back, however SystemUI.apk force closes constantly and I have lost the status bar. I'm on 3.1 and used the right files.
djdevine2 said:
I flashed the Xoom ones which worked fine but I didn't like them to pushed the original ASUS ones back, however SystemUI.apk force closes constantly and I have lost the status bar. I'm on 3.1 and used the right files.
Click to expand...
Click to collapse
try pushing this file back. thats the original one for 3.1.
http://db.tt/eQkoYIk
ok will give it a shot!
Still force closing..... weird
djdevine2 said:
Still force closing..... weird
Click to expand...
Click to collapse
are you pushing it through adb? Can u try something like root explorer?
ayman07 said:
are you pushing it through adb? Can u try something like root explorer?
Click to expand...
Click to collapse
I've been using root explorer as don't have PC with me at the moment, weird that Xoom worked at first, don't worry too much about it, I'll try with ADB in morning. (It's 10:40 in UK)
djdevine2 said:
I've been using root explorer as don't have PC with me at the moment, weird that Xoom worked at first, don't worry too much about it, I'll try with ADB in morning. (It's 10:40 in UK)
Click to expand...
Click to collapse
make sure you check your permissions.
also, i just skimmed the guide, but i'd probably put a permissions change in the instructions just to ensure everyone has proper permissions on install.
not sure if anyone is interested, but i plan on taking the stock asus and changing just the colors to match honeycomb (versus changing the actual icons)
xformulax said:
make sure you check your permissions.
also, i just skimmed the guide, but i'd probably put a permissions change in the instructions just to ensure everyone has proper permissions on install.
not sure if anyone is interested, but i plan on taking the stock asus and changing just the colors to match honeycomb (versus changing the actual icons)
Click to expand...
Click to collapse
I use root explorer, after i moved it to system/app reboot and work fine.
It doesn't hurt to check permission though. rw,r,r
Edit: I just moved my original systemUI.apk back using root explorer and sems permission
Was changed. I set it to rw,r,r reboot and origin icons are back no FCs
Sent from my Transformer TF101 using Tapatalk
Related
I AM NOT A DEVELOPER
I AM NOT A GRAPHIC ARTIST
I DON'T KNOW IF I DID THIS RIGHT
Version 0.2 -Added CAPS alphebet and improved graphics.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, now that that is out of the way, we can proceed. I've been using hoban_eris's Tainted Vanilla rom ( http://forum.xda-developers.com/showthread.php?t=674134 ) and I really like it. One of the pushes over there is to get away from the HTC dialer, I think just because it's ugly. But because I heavily rely on the smart dial feature, I don't want the Vanilla dialer.
This is the standard HTC dialer from the Tainted_Vanilla rom (and I think the Eris_V3 rom) with some minor graphic changes, to make it resemble the Vanilla dialer. All I did was copy the HTCDialer.apk and Phone.apk out, renamed them to .zip, unzipped the files, found and edited the .pngs, pasted the .png's back to the zipped files (I tried re-zipping the extracted files, but couldn't make it work), then renamed the .zip to .apk, then deleted the apk's under system/apps and copied the new ones over (using Android Commander).
THIS IS A WORK IN PROGRESS! I would like to work on it more, but I'm at my real job and need to do my 'real' work. I'm posting it here to see if anyone finds it useful or has suggestions to make it better. Thanks for looking.
To install- MAKE A NANDROID BACKUP OR BACKUP YOUR APK'S -delete these apk's under system/app and copy the new ones over - NO REBOOT NECESSARY
I'm sure there are other ways of doing this, but I don't know the commands.
Testing out!
Hmm didnt work for me.... force close and then the apps dont show up...
andrew8806 said:
Hmm didnt work for me.... force close and then the apps dont show up...
Click to expand...
Click to collapse
Hmm..... I did a Nand restore to try to duplicate your problem. I'm using Android Commander and when I delete the system files, I get FC's, but after I copy the apks over, they work fine.
Sorry about the trouble, I'm still learning.
yeah even when copy and paste... still FC phone...
Re: [wip] htc/vanilla dialer
We'll just have to see if the other devs will weigh in on this.
-------------------------------------
Sent via the XDA Tapatalk App
btw the remove the dot unerneath the 1, just photoshop and color over the dot with the same color as the dialer. dot gone...
New apk's in the first post!
When u delete files do you get an automatic FC?
When I tried copying and pasting them in the /system/app overwriting the original ones I still get FC
Awesome work!
haha, this is awesome work. I love it. I'll include it in my next tainted vanilla release if you don't mind.
By the way, I had no issues getting it installed with your latest apk's using the following method:
$ adb remount
$ adb shell cp /system/app/Phone.apk /system/app/Phone.apk.bak
$ adb push Phone.apk /system/app/Phone.apk
$ adb shell chmod 644 /system/app/Phone.apk
$ adb shell cp /system/app/HtcDialer.apk /system/app/HtcDialer.apk.bak
$ adb push HtcDialer.apk /system/app/HtcDialer.apk
$ adb shell chmod 644 /system/app/HtcDialer.apk
Nice work jadesdan! Works fine for me. I did the following:
1) sudo ./adb remount
2) sudo ./adb push HtcDialer.apk /system/app
3) sudo ./adb push Phone.apk /system/app
Okay, silly question, as I'm still quite the noob here...
Does this work for Froyo?
I've been reading a lot and recently rooted my Eris, installed several different roms. I'm backed up with Ivan's ROM right now and running KaosFroyo... Customized it pretty well. Dialer One however doesn't have access to my Facebook Photos and it's getting annoying! I think it's got an ugly dialer too... If this works with Froyo, it would be a godsend!
EDIT:
also...
How do you do these command lines... I downloaded the SDK stuff and I haven't figured out which program i'm supposed to use to run the commands... I'm lost on the command running side of things.
avantgarde2 said:
Okay, silly question, as I'm still quite the noob here...
Does this work for Froyo?
I've been reading a lot and recently rooted my Eris, installed several different roms. I'm backed up with Ivan's ROM right now and running KaosFroyo... Customized it pretty well. Dialer One however doesn't have access to my Facebook Photos and it's getting annoying! I think it's got an ugly dialer too... If this works with Froyo, it would be a godsend!
EDIT:
also...
How do you do these command lines... I downloaded the SDK stuff and I haven't figured out which program i'm supposed to use to run the commands... I'm lost on the command running side of things.
Click to expand...
Click to collapse
This won't work with KaosFroyo because it requires the HTC Sense overlay. So far, there aren't any froyo ROMS with sense in them.
To run the commands, open a command window (in windows) and then go to where ever you installed the android sdk. You'll need to be in the tools folder. For my setup, I am in c:\android\tools. Once you are in there, you can run your adb commands. Make sure your phone has USB Debugging turned on in the settings.
magnethart said:
This won't work with KaosFroyo because it requires the HTC Sense overlay. So far, there aren't any froyo ROMS with sense in them.
To run the commands, open a command window (in windows) and then go to where ever you installed the android sdk. You'll need to be in the tools folder. For my setup, I am in c:\android\tools. Once you are in there, you can run your adb commands. Make sure your phone has USB Debugging turned on in the settings.
Click to expand...
Click to collapse
Thanks a lot for the information.
the adb command input stuff kept me from trying the Evil Eris rom. Apparently, in order to fix a few things, I had to run a few commands. I didn't have the ability to do that at the time so I passed on trying it out.
I may go back and give it a try now, thanks!
Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM
nagahtom said:
Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM
Click to expand...
Click to collapse
You could just keep looking at the pics till you see the right one. If your OS allows large thumbnail previews in file browsing that will probably help.
nagahtom said:
Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM
Click to expand...
Click to collapse
I think they are dial_num_1, 2, etc located in Phone.apk\res\drawable-mdpi-finger
Thanks for your responses guys! Appreciate your help!
nagahtom said:
Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM
Click to expand...
Click to collapse
Dialer will be in Contacts.apk res/drawable-mdpi-finger
Phone.apk has the images you see when you are on a phone call. Contacts.apk has the dialer images.
Just so you all know, I've updated this to a Metamorph that does the same thing. It also contains all the pngs and the file pates. You can find it here -> http://forum.xda-developers.com/showthread.php?t=742609
This basic guide was requested by a few users who found the Elite Dev zeppelinrox instructions a little overwhelming, so I found a "little" time to whip this up for you and others.
This guide is written for rooted deodexed SGS3 ROMs only with TW OOM priority above 1 (lower value = higher priority and less likely to be killed off). The patch sets the OOM value of the HOME Launcher to 1.
Use Auto Memory Manager (AMM) to check TouchWiz Home OOM priority >1
Menu > Running Processes > Group by OOM grouping
++ For those using an alternative Home Launcher (eg. Apex), ensure that it is set as "default/home" launcher, so that OOM priority for only the HOME Launcher is changed. Any change to home launcher default will require reboot into CWM recovery and wipe advanced/dalvik. ++
Note: For Apex, I have only checked for OOM priority change, not for redraw.
Below: Unpatched ALF2 TW OOM Priority = 6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWO METHODS POSTED IN THIS GUIDE:
1. Modify your downloaded ROM.zip from Windows PC
2. From running ROM on Device
METHOD #1
* Modify your downloaded ROM.zip from Windows PC
Requirements:
1. 7-Zip
2. Root & CWM Recovery Thanks Chainfire!
3. Deodexed "ROM.zip" : Example = GT-I9300_WanamLite.XXALF2.V1.2.NO-WIPE.zip
4. Nandroid backup in CWM Recovery
1. Using 7-Zip on the PC, extract the services.jar from the ROM.zip system/framework/
a) Right click on ROM.zip > 7-Zip > open archive
b) Open system/framework
c) Extract services.jar to somewhere on the PC you can find it (Do not close 7-Zip system/framework/)
2. Upload the extracted services.jar to ICS OOM Priority Charger , follow the instructions there......
3. Download the patched services.jar to PC (the CWM.zip file may not work as it’ll most likely require the updater-script modified)
4. Naviagte to your patched services.jar, left click (hold) and drag into the open 7-Zip system/framework
5. Close 7-Zip & copy ROM.zip to sdcard
6. Boot into CWM Recovery, Nandroid backup
7. Wipe cache & advanced/dalvik
8. Flash ROM.zip
9. Use AMM app to check TouchWiz Home OOM priority =1
10. Enjoy
METHOD #2
* From running ROM on Device
Requirements:
1. Root
2. Root Explorer app or similar (instructions are for Root Explorer)
3. Deodexed ROM
4. Nandroid backup in CWM Recovery
1. Open up device browser http://android.mimic.ca/
2. File upload > choose file > Root Explorer > phone menu > home > system > framework > services.jar
3. This will exit to the ICS OOM Priority Charger webapp
4. Upload
5. Download > Save As "services.jar" > OK
6. Open Root explore and navigate to /sdcard/Download
7. Long tap services.jar > copy
8. Back > back > system > framework
9. Mount R/W
10. Paste > overwrite
11. Set permissions: long tap services.jar > permissions > rw-r--r--
12. Reboot
13. Use AMM app to check TouchWiz Home OOM priority =1
14. Enjoy
Note: Some widgets (weather) may occasionally redraw as their OOM priority may allow them to be killed off, but you should see reduced TW Launcher redraw.
HUGE THANKS to subvertbeats@XDA for pointing me in the right direction and of course blk_jack@XDA for ICS OOM Priority Charger and especially zeppelinrox@XDA for the services.jar patch instructions.
Added Disclaimer: All your own risk. I am not responsible for anything you may try here. I didn't make you do it, blah blah blah
Just to clarify, reading into the script a little it seems the priority changer changes the priority of the "home launcher", rather than "touchwiz home" itself in services.jar....
Am I reading this correctly?
So if someone were using, say Apex launcher as default home, this will still work as intended, and reduce the redraws on whichever app set as deafult home?
If so thank you VERY much
patchseven said:
Just to clarify, reading into the script a little it seems the priority changer changes the priority of the "home launcher", rather than "touchwiz home" itself in services.jar....
Am I reading this correctly?
So if someone were using, say Apex launcher as default home, this will still work as intended, and reduce the redraws on whichever app set as deafult home?
If so thank you VERY much
Click to expand...
Click to collapse
Just testing for you now.............
AMM > Apex OOM = 5
Set Apex as "home" launcher
Reboot and wipe dalvik
Check with AMM > Apex OOM = 1
YES, I belive it will, should work/help, I will edit my OP
Backup and test and see if theres any improvement in preventing the launcher being killed off, and causing redraw
Where to get ROM.zip?
UpInTheAir said:
1. Using 7-Zip on the PC, extract the services.jar from the ROM.zip system/framework/
a) Right click on ROM.zip > 7-Zip > open archive
Click to expand...
Click to collapse
thanks, where do i get this ROM.zip,can i deodox my stock services.jar and follow these steps?
oyam said:
thanks, where do i get this ROM.zip,can i deodox my stock services.jar and follow these steps?
Click to expand...
Click to collapse
The "ROM.zip" refers to a any custom ROM that is in .zip format used to flash from CWM Recovery.
Example: GT-I9300_WanamLite.XXALF2.V1.2.NO-WIPE.zip
Most custom ROMs are installed this way, so using method #1, you can just replace the services.jar before copying the custom ROM.zip to you sdcard for flashing.
I'll update the OP, again.
UpInTheAir said:
The "ROM.zip" refers to a any custom ROM that is in .zip format used to flash from CWM Recovery.
Most custom ROMs are installed this way, so using method #1, you can just replace the services.jar before copying the custom ROM.zip to you sdcard for flashing.
I'll update the OP, again.
Click to expand...
Click to collapse
Cool, thanks i will give a try
I've been trying this method many times, but to no avail. I'm currently running on the NoSympathy OTA ROM. I've tried both methods, as well as using adb push/pull then copying it to the folder, then fixing permissions, and still nothing. It's like that website for patching the services.jar isn't working. Apex Launcher is still set to 6, no matter what I've done.
Any ideas?
well if you are using Apex why not just tick "keep in memory" option?
I have, but I still get the redraw problems.
jefflikesbagels said:
I've been trying this method many times, but to no avail. I'm currently running on the NoSympathy OTA ROM. I've tried both methods, as well as using adb push/pull then copying it to the folder, then fixing permissions, and still nothing. It's like that website for patching the services.jar isn't working. Apex Launcher is still set to 6, no matter what I've done.
Any ideas?
Click to expand...
Click to collapse
Either your missing a step, ROM not compatible, permissions not set properly etc.
Have you rebooted after patching and wiped dalvik and cache in recovery?
Also, You could try to edit manually, link to zeppelinrox instructions in the OP. This may be a little overwhelming for some though.
Also, try his v6 supercharger script, this may help too. I think this has the option to patch during the setup process (read his thread)
Sent from my GT-P6810 using xda premium
UpInTheAir said:
Either your missing a step, ROM not compatible, permissions not set properly etc.
Have you rebooted after patching and wiped dalvik and cache in recovery?
Also, You could try to edit manually, link to zeppelinrox instructions in the OP. This may be a little overwhelming for some though.
Also, try his v6 supercharger script, this may help too. I think this has the option to patch during the setup process (read his thread)
Sent from my GT-P6810 using xda premium
Click to expand...
Click to collapse
I've tried this about 5 times, so I know I haven't missed a step. Maybe you're right about it not being compatible. I have the Verizon i535 GS3, so maybe there's a difference somewhere.
Thanks for the help though.
Stock Sgs rom
Can the redraw on the stock sgs3 rom be fixed using these same steps
Get Ram Manager from playstore.
Tick "Keep launcher in memory".
Solved the problem for me.
I only get redraws while coming out of games or something. Otherwise no redraw.
Trust me, it works.
That's a scam.
You said it yourself, you get redraws when you come out of a game.... LOL
It's like saying "I never crap until I poop"
zeppelinrox said:
That's a scam.
You said it yourself, you get redraws when you come out of a game.... LOL
It's like saying "I never crap until I poop"
Click to expand...
Click to collapse
Umm..yes..Only if I play games like NOVA or so..
Before that; if I browse for 20-30 mins or even go to playstore for 10-20 mins and hit on Homescreen button; there would be a redraw.
No its not at all.
Sometimes even waking up phone after a long time would cause it.
Now absolutely now. Infact my phone doesn't redraw at all unless I do a very heavy task.
By games I didn't mean Angry Birds.
Give it a try; it really makes things better.
That dev STOLE my OOM grouping fix and calls it lock home in memory.
He used to call it Hard To Kill which was stealing my "brand names" so I had that app pulled off the market until it was changed.
None of it does a single thing for launcher priority.
It's all BS... you get the same thing by lowering your minfrees but that would require you to know what you're doing.
SuperCharge it and then you'll know what's BS and what isn't.
Otherwise, you don't know crap about what is possible.
zeppelinrox said:
That dev STOLE my OOM grouping fix and calls it lock home in memory.
He used to call it Hard To Kill which was stealing my "brand names" so I had that app pulled off the market until it was changed.
None of it does a single thing for launcher priority.
It's all BS... you get the same thing by lowering your minfrees but that would require you to know what you're doing.
SuperCharge it and then you'll know what's BS and what isn't.
Otherwise, you don't know crap about what is possible.
Click to expand...
Click to collapse
If that's the case, he's no "dev" then.
Doesn't take much to take someone's hard work and call it their own. Need to give appropriate credit and if need be, ask first.
Sent from my GT-I9300 using xda premium
zeppelinrox said:
That dev STOLE my OOM grouping fix and calls it lock home in memory.
He used to call it Hard To Kill which was stealing my "brand names" so I had that app pulled off the market until it was changed.
None of it does a single thing for launcher priority.
It's all BS... you get the same thing by lowering your minfrees but that would require you to know what you're doing.
SuperCharge it and then you'll know what's BS and what isn't.
Otherwise, you don't know crap about what is possible.
Click to expand...
Click to collapse
Well I had no idea that he stole your work. Really sorry for that.
I can only tell from a consumer's POV that it actually works; and it's not a placebo.
Earlier if I browsed a page with lots of Images and go to home screen; it would re load.
Now it doesn't. At all.
I should commend you for it; since it's your work.
But it does work and now I'm not embarrassed to hand my phone for show off.
That relaod was crapping on my showoff :laugh:
I already have Touchwiz Home OOM priority set to 1 with ARHD 2.1.1.
eggman89 said:
Well I had no idea that he stole your work. Really sorry for that.
I can only tell from a consumer's POV that it actually works; and it's not a placebo.
Earlier if I browsed a page with lots of Images and go to home screen; it would re load.
Now it doesn't. At all.
I should commend you for it; since it's your work.
But it does work and now I'm not embarrassed to hand my phone for show off.
That relaod was crapping on my showoff :laugh:
Click to expand...
Click to collapse
It moves the launcher down a slot.
That's it.
It still gets killed in the same order as before.
I made the grouping limits more multitasking friendly.
Glad you enjoy getting screwed so much.
Now STFU about it because you still haven't a clue.
The app really is a piece of **** and represents all that is wrong with app development and kanging.
Ok, so I'm going to make a little write up on how to easily install ADB and fastboot on a Mac. It's actually quite simple, and plus you don't have to worry about drivers like in Windows.
Instructions
First, make a folder named "android" (no quotes of course ) You can place it anywhere on your hard drive, it doesn't really matter. Put it somewhere you'll easily remember, because you're going to be using it a LOT. I placed mine on my desktop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, you'll want to download the android SDK from Here. (you won't need to install Java first like you would on a Windows PC, though I would recommend it anyway)
(As pointed out by Wlmeng11, you could skip this step just download a zip that I will have attached at the bottom of the page containing the adb and fastboot files instead of downloading the whole SDK)
When the SDK finishes downloading, Unzip it and the contents of the "android-sdk-mac_x86" folder into your android folder.
Once you have done that, open your android folder. Go into the tools folder inside of it. Double click on the file called "android" (possibly called android sdk) This file is a UNIX executable and will open within a Terminal window.
When it finishes opening, check the folder called tools. Make sure both "Android SDK Tools" and "Android SDK Platform-tools" are selected within the tools folder. Click install and wait for them to download.
When they finish downloading, go into the platform-tools folder inside your android folder, then copy adb and fastboot and paste them into the root of your android folder.
Now that you have adb and fastboot installed, we're going to want to test them to make sure they work.
Go ahead and plug in your android device at this time. Make sure android debugging is enabled in settings. Go into Settings > Apps > Developer and check it there (for Gingerbread 2.3 and lower) or go into Settings > Developer Options and check it there for Ice Cream Sandwich or Jellybean. As of now, there are two ways to access adb and fastboot.
Open a Terminal window (look in Applications > Utilities if you can't find it). Type "cd" followed by the path you saved your android folder to (I'm going to use the Desktop for this demonstration) it should look like this
Code:
cd /Users/<yourusername>/Desktop/android
Press enter.
Now you need to actually execute an adb or fastboot command. To do this, you'll need to type "./adb (or fastboot) <command>" For this tutorial, we will use "ADB devices" since it doesn't actually do anything to the phone. (we won't use fastboot since it requires rebooting to the boot loader which is different for every device)
In the same terminal window as before type the following:
Code:
./adb devices
then hit enter. It should turn up your device's serial number. If it does, proceed to the next step, if not recheck your steps, then leave a post in this thread.
(if it says * daemon not running. starting it now on port 5037 *
* daemon started successfully * that is perfectly normal)
Now, at this moment, ADB and Fastboot are both completely useable. However, it's very annoying to have to CD into the directory and use ./ in front of every terminal command. I'll show you how to add it to your path so you don't have to do any of that.
Open a new Terminal window and type
Code:
nano ~/.bash_profile
it will open a window that looks like this:
(Yours will probably be blank, because I've added a lot of stuff to mine over the years)
Add a line to it that contains the path to your android folder. (again, I'm using Desktop) It should look like this
Code:
export PATH=${PATH}:/Users/<yourusername>/Desktop/android
Once you have added that, press CTRL+X to exit, then Y to confirm the save then press enter. It will close the nano editor. You can close the Terminal window now.
Now we need to verify that it works. Open a new Terminal window and type
Code:
adb devices
If it shows the serial number, then you have set it up successfully and are good to go!
If you have any questions or issues let me know in the thread below.
If this has helped, please press thanks!
Awesome! This made the front page of XDA Thanks guys!
Added screenshots
you won't need to install Java first like you would on a PC
Click to expand...
Click to collapse
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw
wlmeng11 said:
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw
Click to expand...
Click to collapse
Lol I'll fix that. Thanks btw. I'm out today, but I'll give you one tomorrow (too lazy to use my phone)
To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound
wlmeng11 said:
To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound
Click to expand...
Click to collapse
Maybe, I actually use other parts of the SDK . Ill look into that though
AshtonTS said:
Maybe, I actually use other parts of the SDK . Ill look into that though
Click to expand...
Click to collapse
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.
I still prefer linux
I still prefer the linux enviroment, although its handy to have the adb on my macbook for when I'm not at home and have bricked my device :S
I had already got this setup, I just didn't know the ~/.bash_profile bit Now I know had to add my own programs as actual programs and not just aliases XD
First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.
Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.
wlmeng11 said:
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.
Click to expand...
Click to collapse
Indeed, though this method allows you to update your adb and fastboot via Android SDK Manager (ASM). Also, in cases where all you need is adb and fastboot, you can speed up future update checks by going to "Tools"->"Manage Add-on Sites..." in ASM and click on "Disable All" button in "Official Add-on Sites" tab. From there on Android SDK Manager will check only the default repository containing tools and APIs.
visor said:
First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.
Click to expand...
Click to collapse
It could be done that way, but I personally put other stuff in the android folder on my Mac, and also it's a bit quicker to just drag a file into one folder on your desktop than into a folder within a folder
straycat said:
Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.
Click to expand...
Click to collapse
You won't be able to install the SDK, but you can extract the android.zip to a folder named android on your desktop or wherever and use that in place of the SDK step
AshtonTS said:
You bet! this will work on any mac running any OS X (unless Google blocks the install of the SDK, but I have a way around that.
Click to expand...
Click to collapse
Actually, that's a PowerPC Mac, so Intel OSX software will not work.
There is no official support for PowerPC that I know of, but someone on XDA did make binaries for PowerPC.
Sent from my HTC Rezound
Edit: yup, official sdk is x86 only.
BTW, here's the link to the ported binaries.
http://forum.xda-developers.com/showthread.php?t=898744
So many graces, this thing has saved the life because I have not a PC windows, thank you still
varanhia said:
So many graces, this thing has saved the life because I have not a PC windows, thank you still
Click to expand...
Click to collapse
Glad it worked for you
Hi,
Thank you very much. Worked like a charm.
Regards,
Awesome thread. Thanks for taking out the time
DarkSorcerer said:
Hi,
Thank you very much. Worked like a charm.
Regards,
Click to expand...
Click to collapse
nigameash said:
Awesome thread. Thanks for taking out the time
Click to expand...
Click to collapse
Glad it helped you two
Sent from my HTC Sensation
Hi thanks so much for this. Ive been wanting something like this for months/ almost a year.
All the other guides didnt work for me, but this was simple and easy to follow.
Ive encountered one problem and its device specific. My nexus 7 tablet works great with adb, but my htc evo 4g lte doesnt. its rooted, and running cm 10 4.1.2. its debugged any idea how to make it see the device?
UPDATE. so i turned on my usb storage on the device and it now sees the phone. Great work!!!!
Am i going to have to connect storage to mac all the time for this to work on any device?
I'm trying manually install 4.1.2 on my rooted Nexus 7 with CMW.
I downloaded the zip, placed it on my Nexus 7, proceeded regularly to install zip
i selected the zip and it aborted, says Status 7.
Thanks to the community below are solutions to get the update to flash.
EDIT
Thanks to Logic_
You can flash this .zip instead which disables all the checks but do it at your own risk as it can brick your tablet
https://www.dropbox.com/s/isqpvb0w26....1.2edited.zip
This is the update with the checks disabled. I didn't make this, got it off another forum, I just used it because I had moved an update to chrome into my /system and there was no easy way to revert it.
I wouldn't advise using this if you made build.prop modifications, but it is useful if your update is failing over some apps like google wallet.
Once again, I didn't make this and I'm not responsible if you for some reason use this to flash the update over some heavily modded rom
It's from JRO03D btw.
Click to expand...
Click to collapse
EDIT 2
osm0sis method to get the update to work is simpler and possibly risk free.
osm0sis said:
For those who've done some modding and can't remember what they did to pass the OTA asserts, all you need to do is dirty flash the system.img from 4.1.2 factory image in fastboot and eveything should work.
Click to expand...
Click to collapse
Did you try to redownload the zip?
Sent from my Nexus 7 using xda app-developers app
I got a similar error for build.prop file. I had changed it to enable/force auto rotation of the home screen when I was on 4.1.1. When I reverted the build.prop to its original file, it worked for me.
I see the error code is the same in your case as well. Is there a chance that you would have changed BrowserProviderProxy.apk?
mayoor_rao said:
I got a similar error for build.prop file. I had changed it to enable/force auto rotation of the home screen when I was on 4.1.1. When I reverted the build.prop to its original file, it worked for me.
I see the error code is the same in your case as well. Is there a chance that you would have changed BrowserProviderProxy.apk?
Click to expand...
Click to collapse
I didn't edit it which is weird, I don't think this matters but I did sideload aosp browser as I'm not a fan of chrome
Sent from my Nexus 7 using Tapatalk 2
Sebianoti said:
I didn't edit it which is weird, I don't think this matters but I did sideload aosp browser as I'm not a fan of chrome
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It's from the side loading of the browser. I had this too. You have to restore those mentioned browser proxy file(s) to their original state. I also temporarily removed the browser apk from the system/app folder as well, although I'm not sure if this was required. The update installed fine after doing this.
Sent from my Nexus 7 using XDA Premium HD app
nyijedi said:
It's from the side loading of the browser. I had this too. You have to restore those mentioned browser proxy file(s) to their original state. I also temporarily removed the browser apk from the system/app folder as well, although I'm not sure if this was required. The update installed fine after doing this.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Oh okay, how would I restore those files to their original state though?
Sent from my Nexus 7 using Tapatalk 2
I'm having the same problem. I cannot seem to flash the update with CWM. I haven't edited any of the system files or anything like that. Is it the fact that I'm using a different launcher that's causing the problem?
Sebianoti said:
Oh okay, how would I restore those files to their original state though?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'd like to know too. I get the Build.prop error too.
You've made no changes whatsoever? What about the kernel? Worst case just use mskip's toolkit to flash back to stock 4.1.1. Check the lag thread I posted what I did and it worked like butter.
Sent from my Nexus 7 using xda premium
Hi all.....
I'm currently using stock Nexus 7 and did all ways possible here to update and nothing worked, last thing I did was go to setting, backup and restore and hit factory data reset and buala automatically got the update to 4.1.2
Nota: this is not a recommendation but if u wanna try do a Backup and good luck.
Sent from my Nexus 7 using xda premium
I deleted the original browser files in the system/app folder too.
Found them on the rootwiki site here....
http://rootzwiki.com/topic/35089-can-someone-hook-me-up-with-browserproviderproxyapk/
Worked perfectly after
modded build.prob / update problems to 4.1.2
i have similar Problem
Picture
h**p://i49.tinypic.com/w979qt.jpg
i modded my build.prob to Landsape mode. I guess that i corrupt the Md5 hash
(deleting the row with the added contend didnt solve it....)
I tried a factory reste and an Temp Wipe in clockwork. I thought this should solve the problem but i l get the sam error ....
What should i do ?
Flash a facotory Image ?
How do i get back my root, if the factory image is my only option?
Thanks a lot for your help
greets Razzor
I also had the same problem then remembered that I use FullScreenToggle to get rid of the nav bar. I just had to re-enable it and it installed fine.
If you are getting the error on 'build.prop' look in the /System folder with Root Explorer or the ES explorer. If you see a build.prop.bak, that is probably your original file. Rename build.prop to something else and rename build.prop.bak to build.prop. Restart and then try taking the update again.
If you side-loaded the gnex browser so you could use flash, go to the /System/App folder and make sure you have BrowserProviderProxy.apk and BrowserProviderProxy.odex named properly. As stated earlier, rename browser.apk to browser.apk.bak. Restart and then try taking the update again. I had that problem. After getting the OTA installed, I renamed the browserproviderproxy files again, and made it browser bak file browser.apk. Now I have flash working perfectly again on the gnex stock browser.
Okay i managed to fix the browser proxy thing, turns out i had 10.apk at the end of it for some reason
and i renamed browser.apk to browser.apk.bak so that worked,
but now i got the same problem but with wallet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I remember having to jack around with Wallet to get the original update which allowed other credit/debit cards to be added. Some offered a solution where you could download a modified wallet.apk that would work instead of going through the other hoops. If you did that, the apk probably doesn't pass the verification. If you used a modified Wallet.apk did you backup the original one first?
Groid said:
I remember having to jack around with Wallet to get the original update which allowed other credit/debit cards to be added. Some offered a solution where you could download a modified wallet.apk that would work instead of going through the other hoops. If you did that, the apk probably doesn't pass the verification. If you used a modified Wallet.apk did you backup the original one first?
Click to expand...
Click to collapse
I didn't, and i did use a modified APK, but i deleted that, then i downloaded an original but still not working
build.prob error
Fixing steps for build.prob error :
VERY IMPORTANT: You will los all of your data, please make a backup befor you following this stepps ^^
Error Message apply_patch_check("/system/build.prob - "Numbers" , "Numbers")
My way which worked for me
1.)
The only way, if you dont have any backup of the original build prob file youl have to flash a copy of the factory IMAGE.
In my case i used the Nexus Toolkit 3.2 V - with this marvelous tool I copied the Factory Image 4.1.1 on it
2.)
After the factory Image you will lose your root. Install Clockwork or a other custom recovery image. Then its easy too get back your root with the Toolkit (follow the steps)
3.) If your not able to receve the OTA update to 4.1.2, download it and copy the ZIP to your Nexus 7
After this, go back to Fastboot and install the Updates using the up an down Volium buttons to navigate
Now the updating process should go very smooth
greets Razzor
I have the same error when installing from CWM and the ONLY CHANGES I made to my N7 are:
- Unlock
- Root
- CWM
- Battery Icon
Any other ideas? Will installing from ADB and Android own Recovery will work?
EDIT: I tried the update on my SECOND N7, which have all the above EXCEPT the battery icon mod and it works. So looks like the battery icon mod is the issue! Anyone know how to revert back to the original battery icon?
Also, since the first update failed, when I clicked on "Check" under SYstem Update, now my N7 said the system is up to date. How do I force the update to run again?
The system checks are there for a reason and I am in no way responsible if anyone bricks their device with this but...
https://www.dropbox.com/s/isqpvb0w26kqjdx/4.1.2edited.zip
This is the update with the checks disabled. I didn't make this, got it off another forum, I just used it because I had moved an update to chrome into my /system and there was no easy way to revert it.
I wouldn't advise using this if you made build.prop modifications, but it is useful if your update is failing over some apps like google wallet.
Once again, I didn't make this and I'm not responsible if you for some reason use this to flash the update over some heavily modded rom
It's from JRO03D btw.
How to DeOdex YOUR 0A6 Rom.
I would like to note that I appreciate all the work that developers have put forth in creating and maintaining modified Roms. there are some awesome feature rich implementations available. My intentions are not to be critical of any specific Rom or mod. Without the developers we would have nothing.
Firt off, Let me explain why I'm writing this guide of sorts. I've always enjoyed an essentially stock ODEXED rom with a minnimum of tweaks.
When 0A6 arrived with ART support odexing is not currently possible. I attempted to use prepared deoxed varietys but there was always something that was a dealbreaker for me. I have nothing against features but a ROM completely loaded with bells and whistles tends to allow bugs and stability issues creep in. and the requirements to wipe 15 times and do a clean flash while singing a gregorian chant just to get it to boot didn't settle well with me.
Using one of the DeOdexed varietys, I was having problems with duplicate apk's being created in /data/app and erronoius Play store updates compounding this issue. There was also an issue with Private Mode and a variety of FC's. In frustration I reverted to a stock rooted configuration and my phone was rock solid.
BUT, I really missed a few mods that I had grown very accustomed to having namely,
5-Way Reboot
Hotspot Mod
PRL Write
Extra Toggles
So instead of trying to install clean why not create a way for me to Custom DeOdex *MY* rom? and not have to start from scratch everytime allowing a dirty flash without creating some crazy stability issue.
This method is very common knowledge I thought I'd just explain it in an easy to understand way.
Here is what you need.
A stock 0A6 ROOTED configurated phone. Debloat as needed. Set the phone up exactly how you like it with apps and such.
Make sure it's stable. (If you have issues before DeOdexing they will be there afterward!)
Here's the files you may need to make this happen
LBD2.4.zip
7-Zip
Installer template (at end of post)
1> Make sure ADB is working on your computer. USB debugging turned on. Create a folder to store your soon to be download system files and launch a DOS shell from that working folder. Working folder name should NOT contain spaces. With the phone hooked up you should be able to type adb shell and get a prompt.
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
3> Extract and launch LBD2.4 (This is the DeOdexer and is AWESOME). Point it at your recently created "system" folder and let it do it's thing.
I'll assume this will occur without errors as I have never had any.
4> At this point you can manually apply modded apk's to the system folder but I don't really recommend it. They can be applied afterward using the seperate installer zips.
5> with 7-Zip installed open the provided Installer template. Do not Extract it. Just open it in the 7-Zip file browser using the right click context menu in windows.
Drag-Drop the contents of your system folder into the empty system folder in the 7-Zip browser It should be the three folders previously created but now they are Deodexed. Close the 7-zip file manager and select Yes if it asks you to save.
Note: The provided installer template has been modified to only wipe and replace the three system directories.
6. Copy the created installer to your sdcard and install with recovery. Wipe cache and Dalvik before rebooting.
Go have lunch. You will sit at a boot screen for about 10 minutes. Then another 20 to rebuild caches. Time varies.
7. Your system will now be Deodexed! At this point you can install your mods one at a time, I recommend this so you can test your system between installs to determine if a specific mod is creating problems.
This method has so far removed ALL of my stability issues.
The InstallerTemplate is valid for other devices? E.g. Samsung S4.
Thanks.
quinielascom said:
The InstallerTemplate is valid for other devices? E.g. Samsung S4.
Thanks.
Click to expand...
Click to collapse
I, too, would like to know if I can use this on my Note 4 (N910G).
Now I haven't used adb in a while but every time I try to run 'adb pull /system/app app/' it runs for about 4 seconds then quits. Then I try to run any other command and it says the device is offline. I have everything up to date, so I'm at a loss right now.
EDIT: So I couldn't get adb to work right so I pulled the folders using ES file manager then copied them to my PC. When I run the deoxeder I get two errors, Invalid Application Directory -"Application folder and Rom folder should not have spaces" and Error -"Invalid Rom Folder"
EDIT: I had a space at the end of a folder title, currently running, will test, and report back.
stuck
stuck on boot :S s5 g900h
so confused, i dont know what to do
I am on a Sprint Samsung Galaxy S5 running stock lolipop 5.0. I want to deodex my Rom so that I can intall xposed. After 8 hours I am practically in tear because absolutely NO-one can help
I dont know what to do for Rom System Path. I followed alll the instruction to detail and eveytime I click run it tells me that there is no space or something.. Here is the path I have no idea whre to go from here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The rom system path would be what you did in step two:
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
So you would click 'browse' then go to the system folder you made and place the other three folders in.
Pulling files via adb gave me errors, so I downloaded it by root explorer
Now I'm deodexed, thanks a lot
daswahnsinn said:
The rom system path would be what you did in step two:
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
So you would click 'browse' then go to the system folder you made and place the other three folders in.
Click to expand...
Click to collapse
Zhekin said:
Pulling files via adb gave me errors, so I downloaded it by root explorer
Now I'm deodexed, thanks a lot
Click to expand...
Click to collapse
How have you guys replaced back the three deodexed folders???
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
PIRATA! said:
How have you guys replaced back the three deodexed folders???
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
There's an update zip in the OP's first thread. Now that being said I have a Note 3 and haven't tried it yet. Been a little busy but I have a complete deodex'd the three folders w/o errors.
Boot loop. SM-G900M
I got stuck on boot scrren, and my recovery can't format cache partition in the recovery.
daswahnsinn said:
There's an update zip in the OP's first thread. Now that being said I have a Note 3 and haven't tried it yet. Been a little busy but I have a complete deodex'd the three folders w/o errors.
Click to expand...
Click to collapse
Did you pulled with device rooted or not? Is it the same to pull with root or no root?
I am doing that now with no root and I had some skipping special file 'xxxxxxx.so' at the beginning of pulling the /app/ folder.
Is that ok??
PIRATA! said:
Did you pulled with device rooted or not? Is it the same to pull with root or no root?
I am doing that now with no root and I had some skipping special file 'xxxxxxx.so' at the beginning of pulling the /app/ folder.
Is that ok??
Click to expand...
Click to collapse
I couldn't get ADB to pull the folders/files so I used a root file explorer. So, yes I did use a rooted device. I don't know if it's the same as if it weren't rooted but it should be. I would say some files may not get pulled for some reason but I'd retry. I'm not a dev so I'm not much help. I tinker with things until I other break it or make what I what work.
daswahnsinn said:
I couldn't get ADB to pull the folders/files so I used a root file explorer. So, yes I did use a rooted device. I don't know if it's the same as if it weren't rooted but it shouldn't be. I would say some files may not get pulled for some reason but I'd retry. I'm not a dev so I'm not much help. I tinker with things until I other break it or make what I what work.
Click to expand...
Click to collapse
Mmmh.... but I've read that a lot of people does it without rooting.....or not??
About your situation, have you extracted the same exact folder so, right?
Tnx.
tiago.rici said:
I got stuck on boot scrren, and my recovery can't format cache partition in the recovery.
Click to expand...
Click to collapse
I used Root Explorer and did a manual copy of these folders (instead use adb pull). And worked!
Now I'm waiting 1st boot.
---------- Post added at 02:57 PM ---------- Previous post was at 02:49 PM ----------
Zhekin said:
Pulling files via adb gave me errors, so I downloaded it by root explorer
Now I'm deodexed, thanks a lot
Click to expand...
Click to collapse
How long have you waited on boot scrren? I'm about almost 20 minutes and still nothing. :fingers-crossed:
problems with the process on my SM-T530NU with stock 5.0.2 ROM
Hi,
Sorry to bother you, but if its not too much trouble, can you please answer a few questions for me about the deodex process?
I tried to adb pull the 3 system folders, /system/app, /system/framework, and /system/priv-app, but some of the files gave me an error on copying. So I tried copying them with es explorer to my external SD which worked OK.
Next, I tried copying the 3 folders to my PC. I copied the correct amount of files (894), but the amount of directories went down from 1013 to 506. Is this correct?
I then tried running the folders through ldb 2.5. most of the files were successful, but there were a few which failed. (Maps, services, and a few others.) is this OK? Can I still use the output to burn to my Tab4?
Thanks for any help that you can give.
Motisu
motisu said:
Hi,
Sorry to bother you, but if its not too much trouble, can you please answer a few questions for me about the deodex process?
I tried to adb pull the 3 system folders, /system/app, /system/framework, and /system/priv-app, but some of the files gave me an error on copying. So I tried copying them with es explorer to my external SD which worked OK.
Next, I tried copying the 3 folders to my PC. I copied the correct amount of files (894), but the amount of directories went down from 1013 to 506. Is this correct?
I then tried running the folders through ldb 2.5. most of the files were successful, but there were a few which failed. (Maps, services, and a few others.) is this OK? Can I still use the output to burn to my Tab4?
Thanks for any help that you can give.
Motisu
Click to expand...
Click to collapse
I've just ben informed test the correct way should be to extract those folders from a stock firmware downloaded.
Other method but risky, as you could also get extra apps not natively born with your device, is to copy them or pull them from recovery using a file manager like Aroma File Manager or TWRP integrated file manager, or use adb from recovery.
Other "while system is running" methods are not preferred as they could give errors back.
Cheers.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
PIRATA! said:
I've just ben informed test the correct way should be to extract those folders from a stock firmware downloaded.
Other method but risky, as you could also get extra apps not natively born with your device, is to copy them or pull them from recovery using a file manager like Aroma File Manager or TWRP integrated file manager, or use adb from recovery.
Other "while system is running" methods are not preferred as they could give errors back.
Cheers.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
OK, I did exactly as you recommended and got exactly the same result. I used the advanced file manager in TWRP recovery to make copies oof the 3 subfolders and then copied the copies to my PC. I got exactly the same results. still missing folders and getting errors in LBD.
motisu said:
OK, I did exactly as you recommended and got exactly the same result. I used the advanced file manager in TWRP recovery to make copies oof the 3 subfolders and then copied the copies to my PC. I got exactly the same results. still missing folders and getting errors in LBD.
Click to expand...
Click to collapse
Use Total Commander for transferring in Windows ambient.
It's good also for coping from micro-sb to hard-disk.
Enable hidden files!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
thank you
Thank you very much for this well detailed explanation. I am not developer. It took me 2 wks searching, working on how to deodex my rom untill finally found this tutorial. It help me a lot.???