Hi guys,
so, if you have an unlocked bootloader and have root access, you may apply my following mod. I'll guide you step through step as we got no CWM recovery yet, so you must do it manually.
If you have downloaded this mod previously and everything works, you are fine, but as reported by @geminihc he had no bars (navbar, status bar) after install, so you have to CHMOD the file, I added this to the code you have to enter:
- download your preferred version (BHR = back, home, recent, RHB = recent, home, back) and rename it to SystemUI.apk
- move it to your internal SD card with an explorer or via adb:
Code:
adb push SystemUI.apk /sdcard/
- after that type in the following commands (red lines backup the old files), beware that su wants you to grant root access (SuperSU popup)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
[COLOR="Red"]mv /system/app/SystemUI.apk /system/app/SystemUI.apk.bak
mv /system/app/SystemUI.odex /system/app/SystemUI.odex.bak[/COLOR]
cp /sdcard/SystemUI.apk /system/app/
rm /system/app/SystemUI.odex
chmod 644 /system/app/SystemUI.apk
mount -o ro,remount /system/ /system/
reboot
Done! Enjoy this mod
Reminder: Although this mod was tested on my device, I'll take no responsibility if you damage your system, so just do it if you know what you do!
If we have CWM, I will provide flashable .zip's then.
Thanks for this mod, just ordered my Moto G, will install it as soon as I get it
Just one question, does that also change the 3G icon to a more elegant and minimalistic H and H+ icon like on the Nexus? If not, is it hard to make such SystemUI.apk?
Thanks for this.
Just a quick suggestion: It might be a good idea to add a command that backs up the original SystemUI before overwriting it... It would be easier to restore the original if something goes wrong for someone.
EDIT: also, could you tell us how you managed to achieve this please?
flargen said:
It might be a good idea to add a command that backs up the original SystemUI before overwriting it...
[...]
EDIT: also, could you tell us how you managed to achieve this please?
Click to expand...
Click to collapse
I hope that someone who hacks with the adb console knows how to backup and restore as I said, I don't take any responsibility for damaging your system.
You may copy the original files to a temporary directory for sure before overwriting them:
Code:
cp /system/app/SystemUI.* /sdcard/tmp/
Notice that SystemUI.apk is odexed in original stock ROM, so you have to backup 2 files. When you apply my mod, you copy a DEodexed file to the system directory, so you need to remove the corresponding .odex file as you see in my how-to.
But for your convenience, I attached the original SystemUI.apk (14.71.8) to this post. This is already deodexed, so in case you don't like my mod, simply copy the .apk to /system/app and reboot, just as above. No need to deal with .odex-files.
Manage to achieve "what"? Navbar mod or the carrier label remove?
I edited statur_bar.xml for the carrier, and navigation_bar.xml for the navbar. Both are located in res/layout/
Anyone interested in a semi-transparent status bar?
In my case the launcher is Nova Launcher 2.3beta which supports transparent navbar, but status bar remained black, so I modded the SystemUI again.
shaftenberg said:
I hope that someone who hacks with the adb console knows how to backup and restore as I said, I don't take any responsibility for damaging your system.
You may copy the original files to a temporary directory for sure before overwriting them:
Code:
cp /system/app/SystemUI.* /sdcard/tmp/
Notice that SystemUI.apk is odexed in original stock ROM, so you have to backup 2 files. When you apply my mod, you copy a DEodexed file to the system directory, so you need to remove the corresponding .odex file as you see in my how-to.
But for your convenience, I attached the original SystemUI.apk (14.71.8) to this post. This is already deodexed, so in case you don't like my mod, simply copy the .apk to /system/app and reboot, just as above. No need to deal with .odex-files.
Manage to achieve "what"? Navbar mod or the carrier label remove?
I edited statur_bar.xml for the carrier, and navigation_bar.xml for the navbar. Both are located in res/layout/
Click to expand...
Click to collapse
Yep, I did mean "how to achieve removing the carrier label" Thanks for the info. I guess you're right about people who mess around with ADB in the first place!!
Why they aren't like this by default I do not know. Android dev team do realise our thumbs aren't that long?
theoneofgod said:
Android dev team do realise our thumbs aren't that long?
Click to expand...
Click to collapse
Maybe they are all lefties
shaftenberg said:
Hi guys,
- after that type in the following commands, beware that su wants you to grant root access (SuperSU popup)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/SystemUI.apk /system/app/
rm /system/app/SystemUI.odex
mount -o ro,remount /system/ /system/
reboot
Done! Enjoy this mod
.
Click to expand...
Click to collapse
sorry for a possibly stupid question, where do i enter these commands? I got terminal emulator on android but it doesn't seem to use these commands. thanks,
NVM: i figured i get to get the android SDK. cheers,
sorry to bump this up again, but i did somehting that screwed up my system. when rebooted, it keeps saying "Unforunately System UI has stopped" . when i first did it, i did screw up in that i accidentally closed my command prompt after i did "rm /system/app/SystemUI.odex"
but anyway, I re-did the whole thing again, reboot and that error showed.
So i tried to revert back to original using your backed up Systemui.apk but it is still saying that error. also when i try to do "rm /system/app/SystemUI.odex", it says file not found.
can someone please help? thanks!
update: i also tried fixing permissions via chmod 755 /system/app but still same error.. getting desperate will this help? this is a ls -l listing of my system/app around the systemui.apk . did i do something i'm not supposed to? note that this is using the OP's deodexed modified systemui.apk thanks,
-rw-r--r-- root root 79474 2013-10-26 11:20 SoundRecorder.apk
-rw-r--r-- root root 25704 2013-10-26 11:20 SoundRecorder.odex
-rw-r--r-- root root 28190 2013-10-26 11:20 Stk.apk
-rw-r--r-- root root 77592 2013-10-26 11:20 Stk.odex
-rw-r--r-- root root 264451 2013-10-26 11:20 Street.apk
--w----r-T root root 1966976 2008-08-01 05:00 Superuser.apk
-rwxr-xr-x root root 3099269 2013-12-01 10:44 SystemUI.apk
-rw-r--r-- root root 245294 2013-10-26 11:20 TagGoogle.apk
-rw-r--r-- root root 59251 2013-10-26 11:20 TelephonyProvider.apk
-rw-r--r-- root root 136496 2013-10-26 11:20 TelephonyProvider.odex
-
geminihc said:
update: i also tried fixing permissions via chmod 755 /system/app but still same error.. getting desperate
Click to expand...
Click to collapse
Which ROM? Country? But that shouldn't be a problem.
I'm trying out in mind where your error occurred...
Well, I don't know what you did, but try the following:
download attachment and put the content(!! - not the archive but the .apk and .odex) to your SD card manually or via adb:
Code:
adb push SystemUI.apk /sdcard/
adb push SystemUI.odex /sdcard/
then one after the other:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/SystemUI.odex /system/app/
rm -r /cache/*
rm /data/dalvik-cache/*
mount -o ro,remount /system/ /system/
reboot
this might help.
shaftenberg said:
Which ROM? Country? But that shouldn't be a problem.
I'm trying out in mind where your error occurred...
Click to expand...
Click to collapse
canada, the stock ROM (rooted and unlocked bootloader)
I advise you to copy the lines with crtl-c and insert it into your console just to avoid typing errors.
[edit]
you set the wrong permissions!!
type
Code:
chmod 644 /system/app/SystemUI.apk
chmod 644 /system/app/SystemUI.odex
shaftenberg said:
Well, I don't know what you did, but try the following:
download attachment and put the content(!! - not the archive but the .apk and .odex) to your SD card manually or via adb:
Code:
adb push SystemUI.apk /sdcard/
adb push SystemUI.odex /sdcard/
then one after the other:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/SystemUI.odex /system/app/
rm -r /cache/*
rm /data/dalvik-cache/*
mount -o ro,remount /system/ /system/
reboot
this might help.
Click to expand...
Click to collapse
thank you! it did not fully fix it but at least now it does not keep showing the error loop so i can use my phone, BUT i'm missing the bottom system bar (the back home recent buttons).. lol.. i'm going SOMEWHERE
geminihc said:
thank you! it did not fully fix it but at least now it does not keep showing the error loop so i can use my phone, BUT i'm missing the bottom system bar (the back home recent buttons).. lol.. i'm going SOMEWHERE
Click to expand...
Click to collapse
read my edit, you set the wrong permissions.
shaftenberg said:
read my edit, you set the wrong permissions.
Click to expand...
Click to collapse
i fixed the permissions back, cleared both the cache but still missing bar after reboot. now the listing is:
-rw-r--r-- root root 28190 2013-10-26 11:20 Stk.apk
-rw-r--r-- root root 77592 2013-10-26 11:20 Stk.odex
-rw-r--r-- root root 264451 2013-10-26 11:20 Street.apk
--w----r-T root root 1966976 2008-08-01 05:00 Superuser.apk
-rw-r--r-- root root 2948805 2013-12-01 11:16 SystemUI.apk
-rw-r--r-- root root 695088 2013-12-01 11:16 SystemUI.odex
-rw-r--r-- root root 245294 2013-10-26 11:20 TagGoogle.apk
-rw-r--r-- root root 59251 2013-10-26 11:20 TelephonyProvider.apk
-rw-r--r-- root root 136496 2013-10-26 11:20 TelephonyProvider.odex
is something preventing the systemUI from loading..?
geminihc said:
is something preventing the systemUI from loading..?
Click to expand...
Click to collapse
The only thing I can guess is that the retail SystemUI.apk is not compatible to the canadian version, but I don't think so.
Pretty weird... Have you backed up your SystemUI.apk? Otherwise you have to flash your ROM again as a last resort :/
shaftenberg said:
The only thing I can guess is that the retail SystemUI.apk is not compatible to the canadian version, but I don't think so.
Pretty weird... Have you backed up your SystemUI.apk? Otherwise you have to flash your ROM again as a last resort :/
Click to expand...
Click to collapse
unfortunately i didnt back it up stupid me. but the version should be the 8GB global version (not the US version). i believe there are only 2 versions of this phone.
i realize that the notification bar is also gone, i guess thats part of the systemui.apk
geminihc said:
i realize that the notification bar is also gone, i guess thats part of the systemui.apk
Click to expand...
Click to collapse
Yes, this is part of SystemUI.apk
So sad, sorry
I added a warning to the opening post. Never thought of an incompatibility, but maybe there are language resources missing between german and canadian version.
However, using RSDlite is quite easy, there is a thread here.
Related
Hello,
Now that we have root access it is possible to remove preinstalled apps like :
- Peep
- Stock
- Stock Widget
- Quick Office
- PDF Reader
- etc.
And how it is possible to do this?
Thanks a lot for the futur answers and have a nice day with your rooted HTC Desire!!!
http://forum.xda-developers.com/showthread.php?t=672352
This ROM has those applications removed. If you want to remove them yourself, you can just try mv'ing the APKs out of the way and see if the phone detects them, but I haven't tried this so advice is issued without warranty. If the apps are in /system you'll need to use the recovery + adb shell mount /system to modify it (try in the OS and the phone will just reboot), if they're not in /system or any other protected dirs, you should just be able to mv them straight.
I haven't rooted my phone yet, but I will later on so this is just ideas at this point.
Thanks for the ROM but I want to customize my phone myself^^
Is there a step by step guide that explain what you say because I'm just starting with android.
Thanks for the answer
Sebacestmoi said:
Is there a step by step guide that explain what you say because I'm just starting with android.
Click to expand...
Click to collapse
+1 on that!
I moved to Desire from a Touch HD, and while I never got into ROM cooking for WinMo, I wouldn't mind dabbling a bit with Android, mostly to remove some of the bloatware that comes with the stock ROM. Trouble is... I have no idea where/how to start Such a 'beginner's guide' would be great to get hold of, if anything exists!
EDIT - found these guides here on XDA:
http://forum.xda-developers.com/showthread.php?t=532719 - ADB, Fastboot and Nandroid for Noobs
http://forum.xda-developers.com/showthread.php?t=502010 - ADB for dummies
(I would have expected to see these in the Android section, not in a device-specific forum; oh well... )
And if we delete the .apk and .odex in the "system/app" folder from the "rootedupdate.zip" that Paul from MoDaCo has given to us before flashing?
Does the ROM will flash and work correctly but without these annoying apps?
Sebacestmoi said:
And if we delete the .apk and .odex in the "system/app" folder from the "rootedupdate.zip" that Paul from MoDaCo has given to us before flashing?
Does the ROM will flash and work correctly but without these annoying apps?
Click to expand...
Click to collapse
Try and find out
Personally I would just delete (rename) the odex + apks from your current installation by rebooting into recovering and using a variation of these commands:
Code:
adb shell
At your PC to get a root shell. Then
Code:
cd /system/app/
Code:
mv theapp.apk theapp.bye.apk
Code:
ls
You will need to use a variation of the above commands, "ls" is list files in this directory, "cd" is change directory, and "mv" is rename file.
All the .apk are readonly so I can't uninstall or rename them...
Waht can I do?
The phone has to be in recovery mode in order to get write permissions to the /system partition.
Pretty obvious, I know, but I missed this and I kept banging my head against the keyboard when getting 'read-only' errors (with the phone in USB Disk Drive + debugging)
So I turn on my phone with the "Sound Down" button and I go on the Recovery screen (with red triangle).
Then I connect my HTC Desire to my computer.
But after that I can't go to system partition...
What command are you writing in the shell to load the system partition and do some stuff on it?
I'm sorry I'm very good with Windows but I'm a total noob wit Linux
I have tried the adb shell command (don't know if it's useful for me...) and the computer return me :
- exec '/system/bin/sh' failed: No such file or directory (2) -
and adb remount return me :
remount failed: Invalid argument
Wait... you tried adb with the phone still showing the red triangle?
First you need to bring it to recovery (the screen with green text).
This is how I do it:
- boot off the .iso provided for rooting
- mount the cdrom as described in the guide, but skip ./step1.sh
- put phone in HBOOT (to get the screen with the red triangle) then connect it to the machine
- run 'sudo ./step2.sh' which will push the files needed for recovery to the device - then you'll get the green screen, just like when you flashed the ROM
- then, on the computer:
'sudo ./adb shell' - brings you to the shell prompt of adb
'mount /system' - mounts the protected partition, but you have write permissions
'cd /system/app/' and then delete whatever I want
when done, 'cd /' and 'umount /system' and 'exit'
Clear the cache so that you won't get dead links in the menus later...
Perfect thanks, I had it in recovery mode, but it couldn't locate the app folder under /system/
but after the mount /system it appeared
Tahnk you a hundred times cezarL.
Now I have cleaned my phone from everything I don't need.
For those who are interested by my work I've done the following commands from the recovery screen :
cd C:\AndroidSDK\tools
adb shell
mount /system
cd /system/app/
rm com.htc.NewsReaderWidget.apk
rm com.htc.NewsReaderWidget.odex
rm com.htc.StockWidget.apk
rm com.htc.StockWidget.odex
rm com.htc.TwitterWidget.apk
rm com.htc.TwitterWidget.odex
rm Facebook.apk
rm Facebook.odex
rm Flickr.apk
rm Flickr.odex
rm HtcFMRadio.apk
rm HtcFMRadio.odex
rm HtcFootprints.apk
rm HtcFootprints.odex
rm HtcFootprintsWidget.apk
rm HtcFootprintsWidget.odex
rm HtcRingtoneTrimmer.apk
rm HtcRingtoneTrimmer.odex
rm htcsearchwidgets.apk
rm htcsearchwidgets.odex
rm HtcSoundRecorder.apk
rm HtcSoundRecorder.odex
rm HtcSyncwidget.apk
rm HtcSyncwidget.odex
rm HtcTwitter.apk
rm HtcTwitter.odex
rm MagicSmokeWallpapers.apk
rm MagicSmokeWallpapers.odex
rm Mode10Wallpapers.apk
rm Mode10Wallpapers.odex
rm NewsReader.apk
rm NewsReader.odex
rm PDFViewer.apk
rm PDFViewer.odex
rm PicoTts.apk
rm PicoTts.odex
rm Quickoffice.apk
rm Quickoffice.odex
rm RSS.apk
rm RSS.odex
rm Stk.apk
rm Stk.odex
rm Stock.apk
rm Stock.odex
rm VpnServices.apk
rm VpnServices.odex
rm WidgetDownloadManager.apk
rm WidgetDownloadManager.odex
cd /
umount /system
exit
Then a reboot with a Clear Storage and every app listed above are gone an there is no bug at all with the phone.
Hi can anyone help me try whether the enable flashlight widget in notification drawer is fixed in this apk? I had tried editing the smalis but need a tester because I am no longer using this ROM. Don't worry, it won't screw up your system. Thanks, and I would be grateful for feedback and comments below.(I know the file size is bigger but it should not affect the installation of the apk. If you could help me reduce the size of the apk. Thanks!)
Download link: https://doc-04-00-docs.googleusercontent.com/docs/securesc/uubj7fqvfjf5ec0jql27eda8tuf8buor/0p3fbcmmlesfvj1h7ji0l8d737crl4c7/1373608800000/04484889645328413275/04484889645328413275/0BxwsPruxmr3vZHlGZHRSYkhrbkE?e=download&h=16653014193614665626&nonce=k5np8umoqtbfq&user=04484889645328413275&hash=sl05t2dh68pd6a3bo75r5ndohmuh8b9h
This is a direct link, just click on it and the download will start.
How to install the apk(for those who don't know)
If you don't know how to install it into /system, here's a guide to how to do it.
If you are using Terminal emulator:
1. Type su, then type this:
Code:
busybox mount -o remount, -rw -t yaffs2 /system
2. Then, type this:
Code:
rm /system/app/Settings.apk
3. Then, type this:
Code:
cp /sdcard/<where is the file>/file.apk /system/app
3. Then, type this(Rename the apk to Settings.apk, then do this step):
Code:
chmod 0644 /system/app/Settings.apk
4. Then, type this:
Code:
reboot
5. Your phone will reboot, and after that test the apk out!
If you're using Root explorer(any kind of root explorer):
1. Copy the file to /system/app
2. Set the permissions to -rw -r -r OR 0644
3. Reboot.
4.Your phone will reboot, and after that test the apk out!
THANK you for trying this out! I appreciate suggestions!
I have deodexed the odexed apps and framework jars of Android 4.3 for M Dual.
Now how to move it to /system/ folder with the help of adb?
I tried flash Gordon by making a flash-able zip but it ain't working.
I have a locked boot-loader and I do not want to unlock it.
SArnab©® said:
I have deodexed the odexed apps and framework jars of Android 4.3 for M Dual.
Now how to move it to /system/ folder with the help of adb?
I tried flash Gordon by making a flash-able zip but it ain't working.
I have a locked boot-loader and I do not want to unlock it.
Click to expand...
Click to collapse
This method assumes you have adb set up as an environment variable on windows.
1) Rename the 'app' folder with the deodexed apps to 'done_app' and the 'framework' folder with the deodexed framework to 'done_framework'.
2) Copy both of the folders to the root of your SD Card, basically so when you want them on your phone it is /sdcard1/done_*/ (* being used as a wildcard).
4) Connect your device to the computer with USB debugging enabled.
5) Open up command prompt and then run the following code individually and line by line:
Code:
adb shell
su
stop
mount -o rw,remount /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard1/done_app/* /system/app/
cp /sdcard1/done_frame/* /system/framework/
mount -o ro,remount /system
reboot
This may cause the device to bootloop, just battery pull and restart. Android is upgrading will appear but that is normal.
The reason flash gordon isn't working is because it replaces some framework files and that could cause the device to freeze and then bootloop and it has a safeguard to prevent that.
gamer649 said:
This method assumes you have adb set up as an environment variable on windows.
1) Rename the 'app' folder with the deodexed apps to 'done_app' and the 'framework' folder with the deodexed framework to 'done_framework'.
2) Copy both of the folders to the root of your SD Card, basically so when you want them on your phone it is /sdcard1/done_*/ (* being used as a wildcard).
4) Connect your device to the computer with USB debugging enabled.
5) Open up command prompt and then run the following code individually and line by line:
Code:
adb shell
su
stop
mount -o rw,remount /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard1/done_app/* /system/app/
cp /sdcard1/done_frame/* /system/framework/
mount -o ro,remount /system
reboot
This may cause the device to bootloop, just battery pull and restart. Android is upgrading will appear but that is normal.
The reason flash gordon isn't working is because it replaces some framework files and that could cause the device to freeze and then bootloop and it has a safeguard to prevent that.
Click to expand...
Click to collapse
Thank-you for your quick reply...
I tried this before too but without asking for root permissions and thus it failed each and every time.
Hope it works now.
Will edit the post with the result ones device boots up.
EDIT : IT GOT INTO A BOOT LOOP...
WHAT TO DO NOW?
FLASH THE FTF AGAIN?
EDIT 2 : MY MISTAKE. TRYING AGAIN.
SArnab©® said:
Thank-you for your quick reply...
I tried this before too but without asking for root permissions and thus it failed each and every time.
Hope it works now.
Will edit the post with the result ones device boots up.
Click to expand...
Click to collapse
I used that code for my single SIM and it worked perfectly, just the possible bootloop happened and then I battery pulled and then restarted and it worked. You need su permissions to remount.
gamer649 said:
I used that code for my single SIM and it worked perfectly, just the possible bootloop happened and then I battery pulled and then restarted and it worked. You need su permissions to remount.
Click to expand...
Click to collapse
Yeah I got your procedure.
I made the mistake in copying the deodexed files.
Will report after retrying when I get free.
gamer649 said:
I used that code for my single SIM and it worked perfectly, just the possible bootloop happened and then I battery pulled and then restarted and it worked. You need su permissions to remount.
Click to expand...
Click to collapse
This time I did everything correct yet the same problem...
Here's what I did :
D:\Working Folder\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shel
l
[email protected]:/ $ su
su
[email protected]:/ # stop
stop
[email protected]:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]:/ # rm /system/app/*.odex
rm /system/app/*.odex
[email protected]:/ # rm /system/framework/*.odex
rm /system/framework/*.odex
[email protected]:/ # cp /sdcard1/done_app/* /system/app/
cp /sdcard1/done_app/* /system/app/
cp: /sdcard1/done_app/*: No such file or directory
1|[email protected]:/ # cp /ext_card/done_app/* /system/app/
cp /ext_card/done_app/* /system/app/
[email protected]:/ # cp /ext_card/done_frame/* /system/framework/
cp /ext_card/done_frame/* /system/framework/
cp: /ext_card/done_frame/*: No such file or directory
1|[email protected]:/ # cp /ext_card/done_framework/* /system/framework/
cp /ext_card/done_framework/* /system/framework/
[email protected]:/ # mount -o ro,remount /system
mount -o ro,remount /system
[email protected]:/ # reboot
reboot
Click to expand...
Click to collapse
SArnab©® said:
This time I did everything correct yet the same problem...
Here's what I did :
Click to expand...
Click to collapse
I don't know what is wrong, you have followed the procedure correctly and I have even compared it to my own screencap and it is the same. Are you sure you deodexed properly?
gamer649 said:
I don't know what is wrong, you have followed the procedure correctly and I have even compared it to my own screencap and it is the same. Are you sure you deodexed properly?
Click to expand...
Click to collapse
Leave mate.
Thanxxx for your help.
I think I need to unlock the bootloader and deodex.
SArnab©® said:
I have deodexed the odexed apps and framework jars of Android 4.3 for M Dual.
Now how to move it to /system/ folder with the help of adb?
I tried flash Gordon by making a flash-able zip but it ain't working.
I have a locked boot-loader and I do not want to unlock it.
Click to expand...
Click to collapse
well i have a question to ask how did you deodexed as i am not able to find anything working
deodex error
i try to deodexed xperia m c2004 4.3 by this method
http://forum.xda-developers.com/showthread.php?t=2213235
with compression level 5
result:- "56 apk deodexed" and "0 rar deodexed" (i don't know may be right/wrong)
and then make it cwm flashable zip
then install via cwm
but i got "NFC force close" message
pls give me solution
sorry for my bad english
stalin.sk2 said:
i try to deodexed xperia m c2004 4.3 by this method
http://forum.xda-developers.com/showthread.php?t=2213235
with compression level 5
result:- "56 apk deodexed" and "0 rar deodexed" (i don't know may be right/wrong)
and then make it cwm flashable zip
then install via cwm
but i got "NFC force close" message
pls give me solution
sorry for my bad english
Click to expand...
Click to collapse
In cwm zip, in uodater script add the lines to delete all. odex files.
Flash n your problem wulill be solved.
Sent from my C2004 using Tapatalk
SArnab©® said:
In cwm zip, in uodater script add the lines to delete all. odex files.
Flash n your problem wulill be solved.
Sent from my C2004 using Tapatalk
Click to expand...
Click to collapse
you mean adding this "delete("/system/app/*.odex");" is correct script
and another doubt that 0 jar deodexed when deodex /system/framework will it work?
stalin.sk2 said:
you mean adding this "delete("/system/app/*.odex");" is correct script
and another doubt that 0 jar deodexed when deodex /system/framework will it work?
Click to expand...
Click to collapse
You need to seperately deodex framework files and then flash
also delete the framework odex files
SArnab©® said:
You need to seperately deodex framework files and then flash
also delete the framework odex files
Click to expand...
Click to collapse
Another doubt(may be final question in deodex)
in system/app more than 46 apks are there
in system/framwork more than 35 jars are there
but i deodexed 46 apks and 35 jars only
my question is i need to delete all odex files
or particular i mean delete deodexed odex file in system/app and system/framework
stalin.sk2 said:
Another doubt(may be final question in deodex)
in system/app more than 46 apks are there
in system/framwork more than 35 jars are there
but i deodexed 46 apks and 35 jars only
my question is i need to delete all odex files
or particular i mean delete deodexed odex file in system/app and system/framework
Click to expand...
Click to collapse
Ok.. I am gonna try to be as informative as possible in a short span of time.
There are almost 200 apks in the app folder but most of then are already deodexed.
I have deodexed dual sim firmware and there were 56 apps in total and not 46.
I can't remember the number of jars but ya 35 or near to that.
Now you just need to flash this 56 or 46 apps as per you and those 35 or so jars + 1 framework apk name sony.uxp.something.apk
and delete all the *.odex files in /system/app and /system/framework.
SArnab©® said:
Ok.. I am gonna try to be as informative as possible in a short span of time.
There are almost 200 apks in the app folder but most of then are already deodexed.
I have deodexed dual sim firmware and there were 56 apps in total and not 46.
I can't remember the number of jars but ya 35 or near to that.
Now you just need to flash this 56 or 46 apps as per you and those 35 or so jars + 1 framework apk name sony.uxp.something.apk
and delete all the *.odex files in /system/app and /system/framework.
Click to expand...
Click to collapse
i can't find "sony.uxp.____.apk" where to get and why it need?
stalin.sk2 said:
i can't find "sony.uxp.____.apk" where to get and why it need?
Click to expand...
Click to collapse
Its in framework folder.
There are only 2 apk files and this is one of them.
SArnab©® said:
Its in framework folder.
There are only 2 apk files and this is one of them.
Click to expand...
Click to collapse
in that location 2 apks are there named
1.framework-res.apk
2.SemcGenericUxpRes.apk ( i think you denote this apk)
2nd one already deodexed
am i complete?
stalin.sk2 said:
in that location 2 apks are there named
1.framework-res.apk
2.SemcGenericUxpRes.apk ( i think you denote this apk)
2nd one already deodexed
am i complete?
Click to expand...
Click to collapse
Yup...
Sent from my C2004 using Tapatalk
SArnab©® said:
This time I did everything correct yet the same problem...
Here's what I did :
Click to expand...
Click to collapse
well put the done_app folder in the internal memory card ie sd card
so code will be
adb shell
su
stop
mount -o rw,remount /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
mount -o ro,remount /system
reboot
change sdcard1 with sdcard
happened with me also changing this helped
The T-Mobile One M8 has CarrierIQ.
To remove it you need to be S-off or have a writable booted system. If you haven't made your system writable you can use TWRP's file manager to delete the files.
This also removes HTC logging apps too.
Use a file Manager like Solid Explorer or Root Explorer and go to and delete the following (Make a backup of all if you want to OTA later):
/system/app
QXDM2SD.apk
QXDM2SD.odex
HtcResetNotify.apk
HtcResetNotify.odex
Htcloglevel.apk
Htcloglevel.odex
Smith.apk
Smith.odex
Udove.apk
Udove.odex
/system/priv-app
IQ-tmobile-release-signed.apk
IQ-tmobile-release-signed.odex
IQToggle.signed.apk
IQToggle.signed.odex
MyBreeze.apk
MyBreeze.odex
/system/lib
system/lib/libiq_service_tmobile_2.2.so
/data/data
com.carrieriq.tmobile
com.carrieriq.tmobile.IQToggle
You can use an app like https://play.google.com/store/apps/details?id=com.lookout.carrieriqdetector to check if CarrierIQ is gone (You can use it to check that it's there also).
Viper ROM has it removed
Sent from my HTC One_M8 using Tapatalk
Not everybody wants to flash a custom ROM.
Sent from my HTC One_M8 using Tapatalk
Thank you for posting this, I never knew about carrier iq until now.
Sent from my HTC One_M8 using Tapatalk
What's it for?
Nexus 7
fmedrano1977 said:
What's it for?
Nexus 7
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/CarrierIQ
Thank You!
SmiLey497 said:
The T-Mobile One M8 has CarrierIQ.
To remove it you need to be S-off or have a writable booted system. If you don't I think you can use TWRP's file manager to delete it.
Use a file Manager like Solid Explorer or Root Explorer and go to and delete the following:
/system/app
QXDM2SD.apk
QXDM2SD.odex
HtcResetNotify.apk
HtcResetNotify.odex
Htcloglevel.apk
Htcloglevel.odex
Smith.apk
Smith.odex
/system/priv-app
IQ-tmobile-release-signed.apk
IQ-tmobile-release-signed.odex
IQToggle.signed.apk
IQToggle.signed.odex
/system/lib
system/lib/libiq_service_tmobile_2.2.so
/data/data
com.carrieriq.tmobile
com.carrieriq.tmobile.IQToggle
You can use an app like https://play.google.com/store/apps/details?id=com.lookout.carrieriqdetector to check if it's gone (You can use it to check that it's there also).
Click to expand...
Click to collapse
Thank you! I was having trouble finding the iq it is much different from the lg g2 as I used system tuner to disable carrier iq and was having trouble doing the same on the m8! thanks again!
Technowhiteboi said:
Thank you! I was having trouble finding the iq it is much different from the lg g2 as I used system tuner to disable carrier iq and was having trouble doing the same on the m8! thanks again!
Click to expand...
Click to collapse
NP
Will this work if I don't remove the .odex files? I don't see the .odex files using solid explorer or fx file explorer root.
Love u smiley.U had a great contribution for the g2 now this.
---------- Post added at 03:34 PM ---------- Previous post was at 03:21 PM ----------
How do u like it m8 from the g2
erapmicks said:
Love u smiley.U had a great contribution for the g2 now this.
---------- Post added at 03:34 PM ---------- Previous post was at 03:21 PM ----------
How do u like it m8 from the g2
Click to expand...
Click to collapse
Been pretty good so far.
Thank you! I didn't have the ODEX files, but following your guide removed carrierIQ from my M8.
Worked for me
SmiLey497 said:
The T-Mobile One M8 has CarrierIQ.
To remove it you need to be S-off or have a writable booted system. If you haven't made your system writable you can use TWRP's file manager to delete the files...
Click to expand...
Click to collapse
Thanks for this guide. I was able to use it to remove CarrierIQ from the 4.4.3 T-Mobile version (used the RUU to get a fresh, stock setup first).
At first I tried just renaming the files (adding a "z" to the front of every name), but the phone still loaded some of the services even though the name was different. I ended up doing a chmod 0000 to all the files to stop them from loading.
I did everything from the TWRP file manager because I wanted to make sure I could reverse all my actions in case it failed to boot up.
Good stuff. Thanks OP!
I found I had to restore the CarrierIQ files in order to take an OTA update. To make it easier, I threw these together in order to enable and disable CarrierIQ easily...
It needs to run as root in a shell on the phone. The mount command makes the system partition writable. You should reboot after this for the changes to take effect (and for the system partition to go back to read only).
I take no responsibility. If you don't know what you are doing, don't use these.
Code:
# Disable CarrierIQ
mount -o rw,remount -t ext4 /dev/block/mmcblk0p45 /system
chmod 000 /system/app/HtcLogLevel.apk
chmod 000 /system/app/HtcLogLevel.odex
chmod 000 /system/app/HtcResetNotify.apk
chmod 000 /system/app/HtcResetNotify.odex
chmod 000 /system/app/QXDM2SD.apk
chmod 000 /system/app/QXDM2SD.odex
chmod 000 /system/app/Smith.apk
chmod 000 /system/app/Smith.odex
chmod 000 /system/app/UDove.apk
chmod 000 /system/app/UDove.odex
chmod 000 /system/priv-app/IQ-tmobile-release-unsigned.signed.apk
chmod 000 /system/priv-app/IQ-tmobile-release-unsigned.signed.odex
chmod 000 /system/priv-app/IQToggle_v1.1.3.signed.apk
chmod 000 /system/priv-app/IQToggle_v1.1.3.signed.odex
chmod 000 /system/priv-app/MyBreeze.apk
chmod 000 /system/priv-app/MyBreeze.odex
chmod 000 /system/lib/libiq_service_tmobile_2.2.so
chmod 000 /data/data/com.carrieriq.tmobile
chmod 000 /data/data/com.carrieriq.tmobile.IQToggle
Code:
# Enable CarrierIQ
mount -o rw,remount -t ext4 /dev/block/mmcblk0p45 /system
chmod 644 /system/app/HtcLogLevel.apk
chmod 644 /system/app/HtcLogLevel.odex
chmod 644 /system/app/HtcResetNotify.apk
chmod 644 /system/app/HtcResetNotify.odex
chmod 644 /system/app/QXDM2SD.apk
chmod 644 /system/app/QXDM2SD.odex
chmod 644 /system/app/Smith.apk
chmod 644 /system/app/Smith.odex
chmod 644 /system/app/UDove.apk
chmod 644 /system/app/UDove.odex
chmod 644 /system/priv-app/IQ-tmobile-release-unsigned.signed.apk
chmod 644 /system/priv-app/IQ-tmobile-release-unsigned.signed.odex
chmod 644 /system/priv-app/IQToggle_v1.1.3.signed.apk
chmod 644 /system/priv-app/IQToggle_v1.1.3.signed.odex
chmod 644 /system/priv-app/MyBreeze.apk
chmod 644 /system/priv-app/MyBreeze.odex
chmod 644 /system/lib/libiq_service_tmobile_2.2.so
chmod 644 /data/data/com.carrieriq.tmobile
chmod 644 /data/data/com.carrieriq.tmobile.IQToggle
So if I had busybox installed, I could run these as shell scripts from a root terminal on the phone? [Obviously I would chmod 744 or 755 them first.]
syntropic said:
So if I had busybox installed, I could run these as shell scripts from a root terminal on the phone? [Obviously I would chmod 744 or 755 them first.]
Click to expand...
Click to collapse
I believe that is correct. I'm pretty sure you will need to be S-off in order to write to the system partition.
I use ADB with a root prompt, so you will need to do a su command at the start if you are using this in a terminal.
FreydNot said:
I believe that is correct. I'm pretty sure you will need to be S-off in order to write to the system partition.
I use ADB with a root prompt, so you will need to do a su command at the start if you are using this in a terminal.
Click to expand...
Click to collapse
I would probably opt for using ADB as well, but it would be nice to set up two shortcuts on the desktop that execute these scripts. Something that would su - && run the script, and then back again.
But thanks a lot for sharing them!
anyone know where I can get these files back so I can apply the OTA updates? thanx
Hey... Strangely, I was about to run a bash script with all the chmod commands above. However, I decided to download a few Play store apps that detect it. Each app said I did not have it installed.
I checked the files in the list above and confirmed they were there. Anyone have any idea why CarrierIQ is not present?
About the only thing I have done outside of this which may affect it is that I had disabled the my-t-mobile app since it has that option to monitor your "experience". Since I wanted to avoid this, I just disabled the app.
Could this app be tied to CarrierIQ's functionality??
And then I found this:
http://support.t-mobile.com/docs/DOC-10849
Which seems to confirm my theory above. Of course, as cool as T-Mobile can be, I don't necessarily trust them.
But still, has anyone used an app that has alerted them to the presence of Carrier IQ, while also opting out of allowing T-Mobile to collect diagnostics (which is in the My T-Mobile or My Account app)?
Please let me know.
i think i chose a wrong bootanimation.
i am in bootloop now in this animation.
connected via adb it recognized my stick but have only read rights.
rm not possible.
any tips?
/e: solved with pc version of kingo root.
Xperience Z said:
i think i chose a wrong bootanimation.
i am in bootloop now in this animation.
connected via adb it recognized my stick but have only read rights.
rm not possible.
any tips?
Click to expand...
Click to collapse
If you use the fire stick:
I wouldn't know how to solve your exact problem but im sure my full guide will sort you out:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
sconnyuk said:
If you use the fire stick:
I wouldn't know how to solve your exact problem but im sure my full guide will sort you out:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
Click to expand...
Click to collapse
Code:
X:\>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ cd /sdcard/
cd /sdcard/
[email protected]:/sdcard $ ls
ls
Alarms
Android
DCIM
Download
FireStarterUpdates
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
amazonmp3
backups
[COLOR="DeepSkyBlue"]downgrade.bin[/COLOR]
edid.hex
image_cache
[email protected]:/sdcard $ cp downgrade.bin /cache/
cp downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
1|[email protected]:/sdcard $mv downgrade.bin /cache/
mv downgrade.bin /cache/
mv: /cache/downgrade.bin: Permission denied
1|[email protected]:/mnt/sdcard $ rm -f /cache/*.bin
rm -f /cache/*.bin
[email protected]:/mnt/sdcard $ rm -f /cache/*.zip
rm -f /cache/*.zip
1|[email protected]:/mnt/sdcard $ cp ./downgrade.bin /cache/
cp ./downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
then i tried to delete the bootanimation.zip from /system/media/
Code:
[email protected]:/mnt/sdcard $ rm -f /system/media/bootanimation.zip
rm -f /system/media/bootanimation.zip
rm: /system/media/bootanimation.zip: Read-only file system
it didn't work. fullbrick?
Hi,
Sorry to hear about your bootloop, hopefully you can still recover from it though
Are you sure the device is correctly rooted?
after running the su command it should return:
[email protected]:
and in your logs above it still shows
[email protected]
Also if you do have root and you want to delete the bootanimation.zip file you need to remount the system partition as rw before it will allow it to be deleted.
Xperience Z said:
Code:
X:\>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ cd /sdcard/
cd /sdcard/
[email protected]:/sdcard $ ls
ls
Alarms
Android
DCIM
Download
FireStarterUpdates
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
amazonmp3
backups
[COLOR="DeepSkyBlue"]downgrade.bin[/COLOR]
edid.hex
image_cache
[email protected]:/sdcard $ cp downgrade.bin /cache/
cp downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
1|[email protected]:/sdcard $mv downgrade.bin /cache/
mv downgrade.bin /cache/
mv: /cache/downgrade.bin: Permission denied
1|[email protected]:/mnt/sdcard $ rm -f /cache/*.bin
rm -f /cache/*.bin
[email protected]:/mnt/sdcard $ rm -f /cache/*.zip
rm -f /cache/*.zip
1|[email protected]:/mnt/sdcard $ cp ./downgrade.bin /cache/
cp ./downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
then i tried to delete the bootanimation.zip from /system/media/
Code:
[email protected]:/mnt/sdcard $ rm -f /system/media/bootanimation.zip
rm -f /system/media/bootanimation.zip
rm: /system/media/bootanimation.zip: Read-only file system
it didn't work. fullbrick?
Click to expand...
Click to collapse
Dont look like your properly rooted.
Plug your stick into Windows pc and run Windows version of Kingo root.
When its finished follow the guide I linked you to.
Let me know how you get on.
this was not the first restart.
kingo root und firetv showed rooted.
i gave root with superuser rights for busybox and other apps
Xperience Z said:
i think i chose a wrong bootanimation.
i am in bootloop now in this animation.
connected via adb it recognized my stick but have only read rights.
rm not possible.
any tips?
Click to expand...
Click to collapse
This is why I said on many occasions that it is not recommended to use Xposed modules or mess with bootanimations on your Fire Tv Stick without a working Recovery system, I also semi bricked my Fire Tv 2 box by putting the wrong bootanimation (non working or wrong resolution on it), but because I had a recent back up & a working recovery I was ok, it even wouldn't find my system via ADB so I was lucky. I won't be doing any modding on my stick until I have a Recovery & can backup my System.
deanr1977 said:
This is why I said on many occasions that it is not recommended to use Xposed modules or mess with bootanimations on your Fire Tv Stick without a working Recovery system, I also semi bricked my Fire Tv 2 box by putting the wrong bootanimation (non working or wrong resolution on it), but because I had a recent back up & a working recovery I was ok, it even wouldn't find my system via ADB so I was lucky. I won't be doing any modding on my stick until I have a Recovery & can backup my System.
Click to expand...
Click to collapse
Im just wondering, where has he said anything about xposed?
All he has to do is root with Kingo root on a PC then follow the guide I put up to downgrade/upgrade/same and fix the bootloop.
As the bootanimation package will be replaced with the new system update if im not mistaken.
He didn't.... did you not understand what I said? I did not quote his post I made my own comment which covered Xposed & bootanimations when it comes to modifying the system files any slip ups without a recovery can cause bricks, this is common sense but not always common knowledge to everyone. Believe it or not I am here to help in this forum not to troll or upset anyone, I have always acted politely & try to go above & beyond to help, if you feel I am trolling please report me to the admin, this may have come across as a little abrupt but I feel like I can't mention it could brick forum members devices without someone moaning at me? Sorry for trying to help out
Sent from my SM-G900F using Tapatalk
@deanr1977
I cant understand why you would want to make a comment like that in this thread, when the op is clearly asking for help with an issue caused by changing the boot animation.
I cant see anywhere in your comment that your 'trying to help out'.
Whatever he chose to do with his device he has already done it, wether you explain to him that moddifying system can cause a brick I think he knows that because he has a brick!
If you feel you need to get the message out about moddifying system files why don't you make a new thread explaining this and link your new thread in the guides thats on here?
I for one won't take offence even though I clearly state the obvious in the 2 guides I put together about risks aswell as other guides on here by other members.
Cant say if other users would like that as they might see it as trolling.
Just saying.
funny. unpossible.
kingo root with pc works.
it's unbricked
thanks
weird. after a restart bootloop again because of the wrong bootanimation.
can somebody updoad me /system/media/bootanimation.zip please?
i don't have a backup. but with kingo root (pc) i'll come into the normal system.
i think i can change it.
Xperience Z said:
funny. unpossible.
kingo root with pc works.
it's unbricked
thanks
weird. after a restart bootloop again because of the wrong bootanimation.
can somebody updoad me /system/media/bootanimation.zip please?
i don't have a backup. but with kingo root (pc) i'll come into the normal system.
i think i can change it.
Click to expand...
Click to collapse
Here you go :
Fire Stick bootanimation.zip os version 5.0.5
http://s000.tinyupload.com/index.php?file_id=86378985064921441797
thanks
#unbricked
on my fire tv box i'll install recovery
but no xposed. for what?
on mobile it makes sense
Xperience Z said:
thanks
#unbricked
on my fire tv box i'll install recovery
but no xposed. for what?
on mobile it makes sense
Click to expand...
Click to collapse
Good to hear !!
Glad my advice is helping
Dont quite get what you mean mate. ?
Elaborate..
It's crazy your bootloop was caused by the bootanimation.zip file alone though because I tested plenty of incompatible files and it only showed a blank screen for about 20 seconds and then loaded the Amazon home screen.
I also just deleted the file and this time there was a different boot animation that just said "fire".
I was testing these in case of boot loop risks before I posted my guide and literally couldn't brick it while I was trying them.
Glad you did get it fixed though, I did try and help but I responded to your post on the custom boot guide where you stated you had a bootloop as I figured it may help anyone else who may come across this issue in the future.