Develop Bugs

Changing file permissions in adb shell

Ok so I:
adb shell
su
cd /system/
cd /app/
rm htcblahblahblah.apk
I get something about it being read only.
This is just an example, I think i actually have full privileges in system/app, but i was messing with something else and i didn't, so how do i change privileges ?

skydeaner said:
Ok so I:
adb shell
su
cd /system/
cd /app/
rm htcblahblahblah.apk
I get something about it being read only.
This is just an example, I think i actually have full privileges in system/app, but i was messing with something else and i didn't, so how do i change privileges ?
Click to expand...
Click to collapse
you need to mount /system as read/writeable. before you shell in, just use
adb remount

ok cool thanks tim

I get remount failed >.> Help? LOL

skydeaner said:
Ok so I:
adb shell
su
cd /system/
cd /app/
rm htcblahblahblah.apk
I get something about it being read only.
This is just an example, I think i actually have full privileges in system/app, but i was messing with something else and i didn't, so how do i change privileges ?
Click to expand...
Click to collapse
Tried chmod?
Example:
Code:
# chmod 0777 This.apk
# rm -f This.apk
EDIT: Also, try sysrw command, if enabled on your ROM or manually remount rw from within adb shell

[Q] Install busybox

Anyone knows how to install busybox?
I've tried to follow some guides but ends up with:
Code:
215:Desktop ricardo$ adb push busybox /data/local
580 KB/s (1083568 bytes in 1.823s)
215:Desktop ricardo$ adb shell
$ su
# cd /system/xbin
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cat /data/local/busybox > busybox
cannot create busybox: not enough memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# dd if=/data/local/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Out of memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# ./busybox cp /data/local/busybox /system/xbin
cp: can't create '/system/xbin/busybox': Cannot allocate memory

same here. cannot write to rw-mounted /system.
sucks

Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.

I have the same problem
ricardoft said:
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
Click to expand...
Click to collapse
What should I do with your files?
Nobody has a solution to this?

I don't think this is a memory issue though, .. added 512mb swap and still it claimed to be out of memory, ..
also I figured maybe hd space .. however when i ln /data/local/tmp/busybox to /system/xbin it had the same error.
I both tried ln from the system and ln from busybox both had same result.

It's not a memory problem! In order to install it you have to be in recovery mode.
Try:
While in recovery mode use adb to connect to our phone. Now transfer the zip file (busybox.zip) to your phone and install it via clockwork recovery -> install zip file -> select my zip file.

can anyone post the proper busybox file cause for some reason the file signature verification failed.
adb push busybox-signed.zip /sdcard/busybox-signed.zip
rebooted phone held down volume button while booting ..
choose recovery, ..
choose install zip from sdcard..
then i see a lot of no and one yes .. so i choose yes but the installation is aborted.

Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.

it has error during installation at line 4 with your busybox.zip
somethinf like can not chmod
(rooted buzz with stock rom)

Elibongo said:
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
Click to expand...
Click to collapse
Do what this guy said.

titanium install in /sdcard busybox, not in /system/bin (xbin) , so it is not usuable by other apps

i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?

kevin2516 said:
Do what this guy said.
Click to expand...
Click to collapse
you have read my mind especially since that isn't free software.

hellysmile said:
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
Click to expand...
Click to collapse
i think you need to create aliases however why install it in xbin anyways then, .. if you need to create aliases or links in bin.. ?
example
$ ln -s /data/local/tmp/busybox ls
$ ./ls
if it is in a path that is included in PATH executing a command will auto look for it in all directories defined in PATH env so basicly you could just create all the directories under /data/local/tmp/bin
and just then append that to PATH env echo $PATH then append :/data/local/tmp/bin to it and busybox should work as well.

Ofloo said:
you have read my mind especially since that isn't free software.
Click to expand...
Click to collapse
titanium backup is free software... look on the market, there's a free version and a donate version.

i have aliases in /system/xbin
they was created after busybox --instal -s
but in system allready exists some commands like ls => i want to use ls from busbox, not from system
and terminal emulator dont anderstand ^[ likes bindings

is there a definitive way to do this. There seems to be no clear way of doing it.

matpol said:
is there a definitive way to do this. There seems to be no clear way of doing it.
Click to expand...
Click to collapse
Maybe this helps:
fang0654 said:
To install:
1) extract and push busybox to your sdcard, reboot into recovery
2) mount /system
3) if you don't have /system/xbin (you should), create it
adb shell:
# mkdir /system/xbin (if necessary)
dd if=/sdcard/busybox of=/system/xbin/busybox
cd /system/xbin
chmod 755 busybox
./busybox --install .
4) reboot and done
OPTIONAL - before rebooting replace the busybox installed by the root process in /system/bin
1) mv /system/bin/busybox /system/bin/busybox.bak
2) cp /system/xbin/busybox /system/bin/busybox
Click to expand...
Click to collapse
from this site: http://forum.xda-developers.com/showthread.php?t=702634

The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.

matpol said:
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
Click to expand...
Click to collapse
You dont have to extract the binary into a folder, just extract the busybox file direct on your sdcard. Than the dd command should work, on my phone it works fine.
But if not, does the command cat in the adb shell work?
If so, try istead of the dd comand:
Code:
mount /sdcard
cat /sdcard/busybox > /system/xbin/busybox
And remember to start your wildfire in the recovery mode, that was the mistake I had done...

[GUIDE] Universal rooting to any ics that you have the stock firmware.

This guide was tested on my samsung galaxy [email protected] gt-B5330 and it worked.
WARNING: this can brick your phone, used on your own risk (both eyes wide open).
The idea behing can be ported on any phone that allows you to upload custom firmware (most samsungs with odin).
The idea is that you escalate to superuser by setting suid on /system/bin/toolbox executable.
By duing that you can run most of the unix commands on android as a superuser.
I is enought for you to copy su utility somewhere where there is not a nosuid option on mountpoint. and make it a suided executable then execute su and get the #.
It's all down hill from here.
I cannot verify for every ics rom out there, but it seems that now ics uses ext4 filesystem for the system partition.
I have made a script that inspects a stock rom firmware isolate the permissions for the toolbox executable and add to them SUID,SUIG.
After that it pachs the firmware back and you can flash it to your device and have a easylly rootable device. (I will post the stept to take to get a standard rooted device).
What you need:
a linux/gnu (it will not work with cygwin because we have to mount the ext4 partition).
simg2img utility (you can get it from xda site it is in ext4_utility packet).
su, busybox and superuser.apk binaries for android (you can take them from a rooting package).
heimdal (for linux) xor odin (for windows and if you cannot flash the firmware on your phone form linux).
I've put all untilities that are not standard into the tar.
just unpack and you have the universal-patch.sh to run over an .tar.md5 firware stock rom.
And post-firmwareUpdate.sh to run after you flash in order to make the root a standard android root.
This was not tested on any other phone (was tested only on GT-B5330) and do it on your own risk.
This rooting does not exploit any weakness (or flaw) in kernel or any thing, it just modifies the stock firmware to make it more flexible so it should be forward compatible with any version of android after ics.

I assume this would exclude HTC's since you meed to be s-off to flash a firmware. I would probably verify that and edit the title if necessary. Other than that, this looks like it could be helpful.

Help to understand the procedure
Hi ETTT,
first of all thanks for your job and effort in finding a solution to this issue.. it has been driving me crazy till now.. but thanx to you i see the light :good: I see it but i cannot really understand the procedure.. Could you please write a step by step explanation of what i need to do. (I am not what we could call a genius with linux).
Thanks in advance.

The First said:
Hi ETTT,
first of all thanks for your job and effort in finding a solution to this issue.. it has been driving me crazy till now.. but thanx to you i see the light :good: I see it but i cannot really understand the procedure.. Could you please write a step by step explanation of what i need to do. (I am not what we could call a genius with linux).
Thanks in advance.
Click to expand...
Click to collapse
If you are refering to the procedure that the script is doing here is the version of step by step (with-out the script):
http://forum.xda-developers.com/showthread.php?t=1956653
If you want to know the step by step with the script, here (I will not respond to more basic than this, like how to boot ubuntu and stuff.):
mkdir -p /tmp/foo
sudo mkdir /mnt
cd /tmp/foo
tar -xzf universal-patch.tar.gz
export PATH=./:$PATH
{get the firmware here and unzip it, it should have a file with .tar.md5 suffix}
./universal-patch.sh {the name of the firmware including the .tar.md5 suffix}
wait a while. you should have by the way about 10 times the size of the zip as free space.
if all goes well you will have a myfrm.tar.md5 rady for flashing.
flash the firmware, and after boot enable usb debuging, hook the phone to pc
sudo adb devices
./post-firmwareUpdate.sh
you should have a rooted phone.
you cannot go any more basic than that.
Have fun.

Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app

The file after qa
phyxar said:
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
Thanks for testing and input.

phyxar said:
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
XWALH3 i've produce from your universal-patch cannot being flashed to my phone, odin crash each time open those files

phyxar said:
XWALH3 i've produce from your universal-patch cannot being flashed to my phone, odin crash each time open those files
Click to expand...
Click to collapse
I'm puting the xdelta to the XWALH3
here are the md5s for the original and patched firmware.
cfe3ca545c4a2c8d453e02cd549655a1 B5330XWALH3_B5330OJVALH1_B5330XXLH4_HOME.tar.md5
624f63943bff54941e4042a39d7928f2 myfrm.tar.md5
Now I have some question in order to debug:
does the patching you have done yeild the same file as I have here?
have you use the same imput? (that's why I've give you the md5 of my imput).

Hey you have rooted you b5330 then do you notice any performance upgrade
Sent from my GT-B5330 using xda premium

Can I patch the firmware using windows??
Because I'm on win
I don't really understand using linux
Or can you make single click batch file that I can use it to patch my firmware???
I really appreciate it if someone provide it
Thanks
Sent from my GT-B5330 using xda app-developers app

byboyz said:
Can I patch the firmware using windows??
Because I'm on win
I don't really understand using linux
Or can you make single click batch file that I can use it to patch my firmware???
I really appreciate it if someone provide it
Thanks
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
I don't know windows that much to make a batch clone of the script. so you need linux.
But you can use a live cd (maybe from ubuntu) to run the script.

ETTT said:
I don't know windows that much to make a batch clone of the script. so you need linux.
But you can use a live cd (maybe from ubuntu) to run the script.
Click to expand...
Click to collapse
Thx for ur reply
How can I open XWALH3.patch that u give earlier??
Bcause I don't know anything about linux
Sent from my GT-B5330 using xda app-developers app

byboyz said:
Thx for ur reply
How can I open XWALH3.patch that u give earlier??
Bcause I don't know anything about linux
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
that patch is an xdelta patch.
There is an xdelta application on windows, don't know if it works, but it should work.

ETTT said:
If you are refering to the procedure that the script is doing here is the version of step by step (with-out the script):
http://forum.xda-developers.com/showthread.php?t=1956653
If you want to know the step by step with the script, here (I will not respond to more basic than this, like how to boot ubuntu and stuff.):
mkdir -p /tmp/foo
sudo mkdir /mnt
cd /tmp/foo
tar -xzf universal-patch.tar.gz
export PATH=./:$PATH
{get the firmware here and unzip it, it should have a file with .tar.md5 suffix}
./universal-patch.sh {the name of the firmware including the .tar.md5 suffix}
wait a while. you should have by the way about 10 times the size of the zip as free space.
if all goes well you will have a myfrm.tar.md5 rady for flashing.
flash the firmware, and after boot enable usb debuging, hook the phone to pc
sudo adb devices
./post-firmwareUpdate.sh
you should have a rooted phone.
you cannot go any more basic than that.
Have fun.
Click to expand...
Click to collapse
hi there, I'm stuck at last point/step: ./post-firmwareUpdate.sh
my terminal respond many error about busybox
the code like this:
2684 KB/s (91980 bytes in 0.033s)
4016 KB/s (996704 bytes in 0.242s)
4491 KB/s (1085140 bytes in 0.235s)
.//busybox: 1: .//busybox: Syntax error: word unexpected (expecting ")")
.//busybox: 1: .//busybox: Syntax error: word unexpected (expecting ")")
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nolonger with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
cd /system/xbin
for k in
nt/obb/su # copy the su binary to a place that can be sudoed <
/mnt/obb/su: cannot open for write: Permission denied
1|[email protected]:/ $ chown 0.0 /mnt/obb/su # modify the owner
Unable to chmod /mnt/obb/su: No such file or directory
10|[email protected]:/ $ chmod 6755 /mnt/obb/su # set SUID flag.
Unable to chmod /mnt/obb/su: No such file or directory
10|[email protected]:/ $ /mnt/obb/su # becomes root !!
/system/bin/sh: /mnt/obb/su: not found
# remount the system partition as readwrite. <
mount: Operation not permitted
/system/xbin/su #copy su in path <
/system/xbin/su: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory
10|[email protected]:/ $ chmod 6755 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory
# close the security hole (toolbox is nolonger with SUID) <
Unable to chmod /system/bin/toolbox: Read-only file system
er.apk of=/system/app/Superuser.apk # copy the superuser application <
/system/app/Superuser.apk: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
10|[email protected]:/ $ chmod 666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
10|[email protected]:/ $ #now this is done for busybox
10|[email protected]:/ $ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/ $ chmod 755 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/ $ cd /system/xbin
[email protected]:/system/xbin $ for k in
Click to expand...
Click to collapse

smhybrid said:
hi there, I'm stuck at last point/step: ./post-firmwareUpdate.sh
my terminal respond many error about busybox
the code like this:
Click to expand...
Click to collapse
Ok it seams busybox has a thing against ")" in comments.
Here is the script without comments, so try this.

ETTT said:
Ok it seams busybox has a thing against ")" in comments.
Here is the script without comments, so try this.
Click to expand...
Click to collapse
no good, it's still have same error...
maybe the problem is in busybox?
and i don't know why I'm unable to do chmod

smhybrid said:
no good, it's still have same error...
maybe the problem is in busybox?
and i don't know why I'm unable to do chmod
Click to expand...
Click to collapse
give this command:
adb shell ls -l /system/bin/toolbox
and let's see if the toolbox has suid.

ETTT said:
give this command:
adb shell ls -l /system/bin/toolbox
and let's see if the toolbox has suid.
Click to expand...
Click to collapse
what i get is
-rwxr-xr-x root shell 99068 2012-08-09 11:59 toolbox
how to get suid?

smhybrid said:
what i get is
-rwxr-xr-x root shell 99068 2012-08-09 11:59 toolbox
how to get suid?
Click to expand...
Click to collapse
have you flash the patched firmware?

ETTT said:
have you flash the patched firmware?
Click to expand...
Click to collapse
well, I've just do all of Your step, except this:
flash the firmware, and after boot enable usb debuging, hook the phone to pc
Click to expand...
Click to collapse
because I don't know the meaning of flash the firmware. How to do that?
So I skip that and hook the phone to pc with usb debugging enabled
i'm new at linux, but I want to try this method for my galaxy chat

[MOD] Remove CarrierIQ

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.

[SOLVED] Bootloop after Bootanimation

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.