[wip] htc/vanilla dialer [UPDATED 05/12/10] - Droid Eris Android Development

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

Related

[HowTo] Disable HTC Evo 4G Startup Sound

http://www.youtube.com/watch?v=b7TbLlzFzsU
Wow why is it so hard to embed a Youtube video on here
The startup sound of the HTC Evo 4G is one of the few things I find annoying about the phone. The fact that even plugging headphones into the Evo does not stop the sound is lame. Here's how you can disable it.
Fast and Easy Way for Froyo:
Root your device, use a File Browser (like Root Explorer) and rename the /system/customize/resource/SPC_animation_final.mp3 file.
Requirements
Your phone must be rooted with Toast's method
You must be familiar with ADB and Toast's custom recovery.
If you need more information on Toast's root and recovery, read this {tutorial} how to root \0/ - xda-developers
Disable Startup Sound
Connect your Evo to your computer thru usb and Enable USB debugging on the Evo.
Reboot into recovery. In a commandline do: adb reboot recovery
Start toast's custom recovery by running recovery-windows.bat as Administrator (or the equivalent for Linux and Mac). Do this by right-clicking on the recovery-windows.BAT file and choose Run as Administrator.
Use a different commandline and do: adb shell
Mount the system partition by doing: mount /system
Skip to #9 if you are on 2.2 Froyo
Go into first folder: cd /system/media
rename the mp3 file: mv android_audio.mp3 android_audio.mp3.bak
Go into 2nd director: cd /system/customize/resource
Rename the mp3 file: mv SPC_animation_final.mp3 SPC_animation_final.mp3.bak
You're done! Reboot: reboot
The Making Of
{
"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"
}
Physical split screen.
My "tripod"
The stage
Nice one pingpongboss! Come to think of it, modders can tailor made (if they haven't done so. sorry if they have. i'm a n00b.) this procedure to load their own custom sounds and animation during startup.
joackie27 said:
Nice one pingpongboss! Come to think of it, modders can tailor made (if they haven't done so. sorry if they have. i'm a n00b.) this procedure to load their own custom sounds and animation during startup.
Click to expand...
Click to collapse
Yup, that's right. I think BuglessBeast does that for the Moto Droid. You can also replace these files with your own files manually.
Thanks for the howto! Definitely glad to remove the sound.
thanks! Naive question, though. Why can't you just to rename the files directly in the evo using a file manager? I thought i'd ask before i try and mess things up .
bkofman said:
thanks! Naive question, though. Why can't you just to rename the files directly in the evo using a file manager? I thought i'd ask before i try and mess things up .
Click to expand...
Click to collapse
That is because when you boot into android, /system becomes NAND locked. So you cannot write anything in /system
You can only write to /system in recovery mode.
Does anyone have the stock sprint start up sound SPC_animation_final.mp3 that can upload it here?
I flashed Fresh 0.2 rom and I don't like the startup sound that goes FRESHHHHHHHH. =/
Thank you pingpongboss! It was driving me crazy!
Ketty said:
Does anyone have the stock sprint start up sound SPC_animation_final.mp3 that can upload it here?
I flashed Fresh 0.2 rom and I don't like the startup sound that goes FRESHHHHHHHH. =/
Click to expand...
Click to collapse
Haha I was really scared the first time I heard that sound
yeah so how do you enable it if it's gone???
You can also set your phone sound profile to silent before you shut off your phone and it Disables the HTC Evo 4G Startup Sound.
hotboy8628 said:
yeah so how do you enable it if it's gone???
Click to expand...
Click to collapse
If you did it yourself, then just redo all the steps, but rename all the files back to .mp3.
If your Rom cane with no sounds then you can probably stick your own mp3 into the right folder.
pingpongboss said:
If you did it yourself, then just redo all the steps, but rename all the files back to .mp3.
If your Rom cane with no sounds then you can probably stick your own mp3 into the right folder.
Click to expand...
Click to collapse
it said it was read only when i go to the folder
is this procedure different for froyo?
i get to...
6. Go into first folder: cd /system/media
7. rename the mp3 file: mv android_audio.mp3 android_audio.mp3.bak
Click to expand...
Click to collapse
and the android_audio.mp3 file doesn't exist?
cjohnson said:
is this procedure different for froyo?
i get to...
and the android_audio.mp3 file doesn't exist?
Click to expand...
Click to collapse
Its very well possible that they may have changed the location of the bootup sound. Is the SPC_animation_final.mp3 still there? And does sound go away when you rename that.
Code:
C:\android-sdk-windows\tools>adb reboot recovery
C:\android-sdk-windows\tools>adb shell
/ # mount /system
mount /system
/ # cd /system/media
cd /system/media
/system/media # mv android_audio.mp3 android_audio.mp3.bak
mv android_audio.mp3 android_audio.mp3.bak
mv: cannot rename 'android_audio.mp3': No such file or directory
/system/media # ls
ls
audio
/system/media # find / -name android_audio.mp3
find / -name android_audio.mp3
/system/media # find / -name SPC_animation_final.mp3
find / -name SPC_animation_final.mp3
/system/customize/resource/SPC_animation_final.mp3
/system/media # cd /system/customize/resource
/system/customize/resource # mv SPC_animation_final.mp3 SPC_animation_final.mp3.bak
mv SPC_animation_final.mp3 SPC_animation_final.mp3.bak
/system/customize/resource # ls
ls
BigBen.jpg htc_wallpaper_small_12.jpg
CCInfo.txt htc_wallpaper_small_13.jpg
Colosseum.jpg htc_wallpaper_small_14.jpg
EiffelTower.jpg htc_wallpaper_small_15.jpg
SPC_animation_final.mp3.bak htc_wallpaper_small_16.jpg
SPC_wallpaper.jpg htc_wallpaper_small_17.jpg
StatueOfLiberty.jpg htc_wallpaper_small_18.jpg
bootanimation.zip htc_wallpaper_small_19.jpg
htc_wallpaper_01.jpg htc_wallpaper_small_20.jpg
htc_wallpaper_02.jpg htc_wallpaper_small_21.jpg
htc_wallpaper_03.jpg htc_wallpaper_small_22.jpg
htc_wallpaper_04.jpg m1b586a02.jpg
htc_wallpaper_05.jpg m2dcca705.jpg
htc_wallpaper_06.jpg m43a4ec7b.jpg
htc_wallpaper_07.jpg m43b340e3.jpg
htc_wallpaper_08.jpg m4d5e5f0e.jpg
htc_wallpaper_09.jpg m512d806c.jpg
htc_wallpaper_10.jpg m53b5efe7.jpg
htc_wallpaper_11.jpg m6f42e22c.jpg
htc_wallpaper_12.jpg mbd5dc6f8.jpg
htc_wallpaper_13.jpg mc8a1ff6b.jpg
htc_wallpaper_14.jpg md32a3a14.jpg
htc_wallpaper_15.jpg mdcdc890d.jpg
htc_wallpaper_16.jpg mfac50f3a.jpg
htc_wallpaper_17.jpg mfca3085e.jpg
htc_wallpaper_18.jpg resource
htc_wallpaper_19.jpg s1b586a02.jpg
htc_wallpaper_20.jpg s2dcca705.jpg
htc_wallpaper_21.jpg s43a4ec7b.jpg
htc_wallpaper_22.jpg s43b340e3.jpg
htc_wallpaper_small_01.jpg s4d5e5f0e.jpg
htc_wallpaper_small_02.jpg s512d806c.jpg
htc_wallpaper_small_03.jpg s53b5efe7.jpg
htc_wallpaper_small_04.jpg s6f42e22c.jpg
htc_wallpaper_small_05.jpg sbd5dc6f8.jpg
htc_wallpaper_small_06.jpg sc8a1ff6b.jpg
htc_wallpaper_small_07.jpg sd32a3a14.jpg
htc_wallpaper_small_08.jpg sdcdc890d.jpg
htc_wallpaper_small_09.jpg sfac50f3a.jpg
htc_wallpaper_small_10.jpg sfca3085e.jpg
htc_wallpaper_small_11.jpg
/system/customize/resource #
seems as though they did away with "android_audio.mp3" in froyo on the evo. if you skip steps 6 and 7 (and the bit about toast's recovery in my case since i have amon_ra's installed) everything will work fine.
I would just like to add how I did it.
I rooted using another method but I found a simpler way that works on the EVO 2.2. I downloaded Root Explorer (paid app) for removing bloatware, but I used it to navigate to /system/customize/resource just find SPC_animation_final.mp3 and add .bak to the end of that.
Done and done.
Thanks for the info on which file it was!
chjade84 said:
I would just like to add how I did it.
I rooted using another method but I found a simpler way that works on the EVO 2.2. I downloaded Root Explorer (paid app) for removing bloatware, but I used it to navigate to /system/customize/resource just find SPC_animation_final.mp3 and add .bak to the end of that.
Done and done.
Thanks for the info on which file it was!
Click to expand...
Click to collapse
Is there any free application that can do this? I don't see the directory when I use ES File Explorer. I'm guessing it is hidden somehow?
edit: Nevermind, I found it with ES. No file manager I've tried will allow me to edit the file. What is Root Explorer doing that is so special? Just giving itself superuser? Can't we do that manually?
edit2: I did it via ADB but I'm still wondering the answer to my question above. Also, has anyone noticed if it takes longer to boot? It seems to sit at the white screen for longer than before. Maybe it's spending time looking for the mp3 file before on? Or maybe it's just my imagination.
Minjin said:
Is there any free application that can do this? I don't see the directory when I use ES File Explorer. I'm guessing it is hidden somehow?
edit: Nevermind, I found it with ES. No file manager I've tried will allow me to edit the file. What is Root Explorer doing that is so special? Just giving itself superuser? Can't we do that manually?
edit2: I did it via ADB but I'm still wondering the answer to my question above. Also, has anyone noticed if it takes longer to boot? It seems to sit at the white screen for longer than before. Maybe it's spending time looking for the mp3 file before on? Or maybe it's just my imagination.
Click to expand...
Click to collapse
Sorry for the long delay but it looks like you've figured it out.
IDK what makes root explorer do what it does, but in order to edit anything you have to click the button near the top (once you are in the directory you are working in) that says 'Mount R/W' to make the files read/write instead of read/only. It locks the files as read only by default.
I haven't noticed any longer boot times or anything on mine... dunno.
Blah
This sounds to complicated just turn your volume down before you shut it down.

[Updated][How-To] Xoom Navigation Icons on Asus Transformer

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

[Boot Animation]Droid Prime

Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and have been waiting patiently ever since. I posted about it already now its ready for the wild.
I did not create this. I have only edited the desc.txt so it will run on our phones. All credit goes to BootAnimator on RootzWiki. Again I did not create this so please thank the creator BootAnimator on RootzWiki
.
{
"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"
}
Unzip the file then follow the instructions below.
http://www.mediafire.com/?7tmnb3u7axbu2u0
Root Explorer method:
1. Rename your bootanimation to bootanimation (if not already named this)
2. Put it on your SD card
3. Open Root Explorer and copy bootanimation.zip to /system/media. This will replace the existing boot animation
4. Reboot your phone
ADB method:
1. Make sure you have downloaded android sdk
2. Put android sdk in C:\
3. Set the directory of command prompt to C:\android-sdk-windows\platform-tools. Click here for a video tutorial.
4. Rename your boot animation to bootanimation and put it in C:\android-sdk-windows\platform-tools
5. Open cmd
6. Type in order:
-adb remount
-adb push bootanimation.zip /system/media/bootanimation.zip
-adb reboot
Click to expand...
Click to collapse
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
Originally Posted by hockeyfamily737
0. It's recommended to do a nandroid backup first!
1. Download the "bootsnd.sh" file and put it on the root of your sd card.
2. Using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media
3. Open Terminal Emulator and type the following commands using the stock keyboard. Press enter after each line:
su
cd /sdcard
sh
sh bootsnd.sh
reboot
4. As the device boots up you will hear the transformers sound bite sound. You are now free to replace the android_audio.mp3 file in /system/media with any .mp3 file you like as long as you rename it to "android_audio.mp3"
5. DO NOT ATTEMPT TO OUTSMART THESE DIRECTIONS OR YOU WILL BE RESTORING YOUR NANDROID BACKUP!
6. Enjoy
Click to expand...
Click to collapse
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Here is how to fix it.
Make sure you are mounting in r/w mode on each of these steps.
Using a app like root explorer, goto /system/bin and delete the file bootsound.
Back out to /system now open build.prop in text editor mode, look for this text.
Code:
ro.config.play.bootsound=1
Delete it from the build.prop and save and exit.
This is optional but recommened.
Reboot phone.
Verify no sound is playing.
Now run the script again and reboot.
You should have a boot sound again.
Click to expand...
Click to collapse
Sent from LGE XDA phone
eollie said:
Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and have been waiting patiently ever since. I posted about it already now its ready for the wild.
I did not create this. I have only edited the desc.txt so it will run on our phones. All credit goes to BootAnimator on RootzWikiAgain I did not create this so please thank the creator BootAnimator on RootzWiki
Unzip the file then follow the instructions below.
http://www.mediafire.com/?7tmnb3u7axbu2u0
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Click to expand...
Click to collapse
Umm... It never work... I tried this for 7 times...
Sent from LGE XDA phone
Do this plug your phone in via the usb and open adb window.
Type "adb shell bootanimation".
It will say "mmap failed:errno 19 no such device" and play the animation on your phone screen.
If it says anything else post it here and I can figure out what the problem is.
Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk
lekhwani said:
Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
+1 Same... 40 times I tried ur method...
Sent from LGE XDA phone
lekhwani said:
Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
dax4182 said:
+1 Same... 40 times I tried ur method...
Sent from LGE XDA phone
Click to expand...
Click to collapse
Im sorry its probably your phone. I see dax is using a P500. Some phones just wont play the boot sound.Ive seen it happen on the V no reason just refuses to play.
eollie said:
Im sorry its probably your phone. I see dax is using a P500. Some phones just wont play the boot sound.Ive seen it happen on the V no reason just refuses to play.
Click to expand...
Click to collapse
But on the official ginger is able to play the bootsound as is original manfacturered...
Sent from LGE XDA phone
DaxElectro said:
But on the official ginger is able to play the bootsound as is original manfacturered...
Sent from LGE XDA phone
Click to expand...
Click to collapse
Where is the bootsound located on the official gingerbread release?
I only say some phone just wont play it because Ive tried to help several people on android central get it working and their phone just wont play it no matter what we did. Im sure somebody with more knowledge than I have on this would be able to figure it out, however Im not sure why it wont work. I was told that on CM rom the kernel was trimmed and bootsound was removed that is why you have to run the script I link to.

How To Fully UnRoot HTC Evo

Credits/Disclaimer
Code:
[U][B]
This is not my guide, you dont have to thank me for this.
Thanks to Ocnbrze over at AndroidForums for this.
we are not responsible if your device(s) cause(s) a nuclear war[/B][/U]
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Please read thru this guide once or twice before actually taking steps !
Your phone MUST be on a stock sense rom so go get that installed now !
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Before you do anything else, your phone MUST be on a stock sense rom !
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
{
"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"
}
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!​
XenonV said:
First things first- Not my guide, You are fully responsible for whatever happens. It is not XDA's fault, its not my fault, its all on you.
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Now lets begin
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!​
Click to expand...
Click to collapse
I've actually been dealing with this most of the day trying to unroot and go back 100% stock and have had no success. It was suggested elsewhere that I need to be on a stock rom? I'm dl'ing one now to try as I am currently on an ics rom.
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
XenonV said:
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
Click to expand...
Click to collapse
Perhaps a good bit of info to add to the op
Relentless D said:
Perhaps a good bit of info to add to the op
Click to expand...
Click to collapse
already on it, thanks
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Captain_Throwback said:
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Click to expand...
Click to collapse
i dont know who the original writer is, which is why. if i know then i always list that info :good:
XenonV said:
i dont know who the original writer is, which is why. if i know then i always list that info :good:
Click to expand...
Click to collapse
Where did you get it from, then?
It looks strikingly similar to this guide:
http://androidforums.com/evo-4g-all-things-root/526575-guide-unrooting-gingerbread-2-3-5-a.html
In fact, the inordinate number of exclamation points and the use of my command prompt screenshot makes me think it originated over there.
Captain_Throwback said:
Where did you get it from, then?
Click to expand...
Click to collapse
somebody PM'd me the guide on another website (the tech game) , just the text, no link
XenonV said:
somebody PM'd me the guide on another website (the tech game) , just the text, no link
Click to expand...
Click to collapse
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Relentless D said:
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Click to expand...
Click to collapse
problem solved thanks :good:
and yes this is my guide. however, you do not need to be on stock sense, just not on ics roms for this to work. just throwing that out there.
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
Are you running a rooted ROM? You need to have root access for this to work. Try typing "su" at the prompt and see if it changed to a #.
thanks
Can this be done using a Mac?
XenonV said:
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
Click to expand...
Click to collapse
i have tried that and it still doesnt work, any help!?
im running a brand new computer like seriously out of the box, windows 7 ultimate and it wont give the #
Chirpout said:
Can this be done using a Mac?
Click to expand...
Click to collapse
yes, i believe the guide states something about that..not exactly sure, you can also use google for more help
Hi, I know this is really out of date, but I have to send my phone back because the screen is cracked (inner touch screen) and I wanted the phone to be completely stock. I never rooted the phone. I only unlocked the bootloader. I found this thread hoping I could relock the bootloader to make it look like I never unlocked it in the first place. Of course once I reached Step 7, I don't get the # sign. I get the $ sign and I don't know what to do :/

[HOW TO] DeOdex YOUR lollipop Rom

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

Categories

Resources