Related
I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!
That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App
Wait. I have a normal reboot. Maybe mine is messed up?
Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.
Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer
jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse
I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...
Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App
Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.
I would like it if someone could tell me how to get/use a custom rom boot cause I really want one and haven't the slightest idea cause I'm tired of seeing the sprint 4g start up lol.
Sent from HTC EVO 4G via xda app
Well if you are rooted, then go donwload one of the many custom boots on this site. Download the bootanimation.zip (and sound file if its included) to your phone. Then go grab a program like astro or root explorer and copy and paste the 2 files into /system/media. I've done it this way a few times and have never had a problem. Next time though you should use the search feature im pretty sure theres a whole thread dedicated to it.
I searched for help first but they didn't explain it the way you did. I'm going to try your method. I hope it works, I wonder if someone could make one for me..
Sent from HTC EVO 4G via xda app
I'm lost, I can't really find the boot roms I saw before, I feel dumb but I am a noob lol.
Sent from HTC EVO 4G via xda app
Here you go http://forum.xda-developers.com/showthread.php?t=708173
Do a search for UOT Kitchen they have boot options and they have flashable zips
Sent from my PC36100 using XDA App
I got a boot but I dont know where to put it and how to use it...
Sent from HTC EVO 4G via xda app
jacoballen22 said:
I got a boot but I dont know where to put it and how to use it...
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
Have you tried adb? or do you know how to push the files?
To be honest I done know either....
Sent from HTC EVO 4G via xda app
jacoballen22 said:
To be honest I done know either....
Sent from HTC EVO 4G via xda app
Click to expand...
Click to collapse
Then you shouldn't be messing with your phone in the first place if you don't know at least ONE of those.
I haven't tried either, all I know is that one uses the computer and the other has something to do with terminal and a bunch of codes, which is easier and I rooted my phone just fine, I'm learning..
Sent from HTC EVO 4G via xda app
it all depends on what you have I have the evo with froyo 2.2 android on it and was told it cant be rooted but i followed a video on youtube and got mine rooted you don't actualy have to flash the whole rom to get a new animation booted... just root your phone depending on what you have... i used the unrevoked method follwing a youtube video of course with windows i had to install the hboot usb thing on my evo anyways i got it rooted and the unrevoked site is just one click i got the software from unrevoked dot com... download the unrevoked 3 for whatever operating system your running on your PC... hook it up to your PC watch the youtube video tutorials they will help... don't just watch one though i spent a whole 2 weeks reasearching everything i could to root it... just incase i failed i knew how to undo it from my research... the unrevoked method worked for me... and i havn't been limited to anything i got the free tethering got full premissions i have custom lock screen and boot screen.. anyways go to the site download that theres several other files you will need like the hbooter software if your rooting the evo.. i'm not giving a tutorial on this because i spent to much time myself and knowing what i know would take this whole website to type up. ok so
back to the boot screens.. the site unrevoked is just one click... litteraly start it up with the files all ready and it'll do the rest including rebooting your phone and loading into recovery everything, now you will not loose everything, i did the root and lost nothing but just incase because there is always the chance of errors... get an app called astro... to back up all of your installed apps and an app called MIQ to backup your contacts, calandar, notes, everything basicly on your phone besides apps... on a website create a profile to upload too and then get one more app called SMS backup to backup all of your text messages outbox and inbox and you can restore it all later if for anyreason something is lost.. these are all free apps... now after it roots your phone it will install the clock work rom or w.e. i guess it does flash your phone with a rom but its pretty much the same exact thing and when i did it i lost nothing everything was still installed. if you have the correct files on your computer in the C drive on the root of the C drive... the directory you should have for the files you need to download are "C:\android" and thats it.. anyways again just root the phone then download an app called boot animation changer lite....
with boot animation changer lite all you need to do is have a rooted phone.. scroll through what you like and preview them and if you want it then tap it and choose your screen for me on the evo i chose "480x800" i don't know if thats the wrong one or causes problems but it hasn't failed yet its working good and looks fantastic
I used the exact same way to root my phone, I too used a youtube video and did a lot of research before doing something crazy. I got the app your reffered to me and it worked pretty good (thank you!) But now I want to figure out how to use adb or how to push boot roms from this site onto my phone and 480x800 was the correct size..I think. Your help was very descriptive and I like that. So can anyone help describe the adb method and or the push method so I can learn how to use the boots from this site? Please and thank you in advance.
Sent from HTC EVO 4G via xda app
jacoballen22 said:
So can anyone help describe the adb method and or the push method so I can learn how to use the boots from this site? Please and thank you in advance.
Click to expand...
Click to collapse
First - Do you have the EVO drivers, and the Android SDK installed on your computer? This is needed in order to utilize ADB.
If not:
ANDROID SDK
Some of the bootanimations have been made available in a flashable zip that you can install from recovery.
If you are talking about the ones that were installed during the root process under /android then yes, so how would I go about using that to install the boots?
Sent from HTC EVO 4G via xda app
OK then.
Place the bootanimation.zip, and (optional mp3 file)
Open a command prompt and cd to wherever you have your TOOLS folder in the SDK.
ex) cd c:/AndroidSDK/tools
Then you mount the device, and can push the files to your phone to this directory:
/system/customize/resource/
ex) :
adb push bootanimation.zip /system/customize/resource/
adb push SPC_animation_final.mp3 /system/customize/resource/
Then simply reboot through adb:
adb reboot
NOTE: If the bootanimation you are switching to DOES NOT have sound then you need to remove the SPC_animation_final.mp3 from /system/customize/resource/
DONESIES!
Thanks goes to #TeamWin for Temp Root
This is For Windows only, if you wish to make it work for linux or mac help your self...
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
It's stable & works 100%
I Personally have not lost Root with this new Method
Q. I thought RW was Fixed?
A. Caused by Deleting an apk / file that was already deleted. Journaling shows it still there!
Keep Track of what you delete, as trying to delete something off system that you alread di hangs the /system into RO state.
Before Using!!HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
What's Fixed:
Revamped due to new Method:
~ Superuser Apps now Function
~ If you Lose Root, all you have to do is Open terminal & type SU then type fixit! > No More Rebooting & running the exploit again for R/W on system to get Root back in place
~ Fixed R/O Bug!!
~ R/W is now Forced
~ /system is fully editable now! until reboot that is.
~ Busybox is installed to /vendor/bin
~ hex Edited libext4
~ hex edited libfuse.so
~~ This is the Last Update due to it working & Stable ~~
Download for RW HTC Sensation 4G:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo 3D:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Flyer 16GB/32GB:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo View:
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal & type fixit to get root back!.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot..
Q. Can I push & remove items to system & will it work?
A. Yes, but all changes are reset on a reboot.
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
OLD NEWS:
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
I am Asia Sensation..Can i use it?
thanks loads
will give feedback
seems to work the same as before, cant wait until we can permanently change /system files
Thanks a lot !!!
I think the new thread it's beter, for the noob not confusion
with the old one
Great update. You should seriously consider talking with agrabren since your making temp root so much better. And I'm assuming you still can't permanently delete system apps right? Just permanently delete them for the time being until a reboot right?
does this still remove the bloatware as per the previous release? looking at the .bat doesn't seem to remove the apks in the manner/or at all?
Fantastic. Works great.
biglolz said:
does this still remove the bloatware as per the previous release? looking at the .bat doesn't seem to remove the apks in the manner/or at all?
Click to expand...
Click to collapse
No, the user can do that now from root explore
Sent from my HTC Sensation 4G using XDA App
Any difference between this and Easy Fr3vo from this thread?
Is there an OC module for gae358b5?
eugene373 said:
No, the user can do that now from root explore
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Even though Root Explorer is granted SuperUser, I still can not modify system files. I also can not actually overclock with SetCPU 2.2.4. It will show the max as 1728000 but it will never scale above 1188000
The process is extremely easy and very user friendly though
i have been trying root my sensation it says its a success but my phone is not rooted can anyone help
i did root it before and it worked i restarted my phone and lost root access as expected but now when reattempt it fails
RaDeN305 said:
Any difference between this and Easy Fr3vo from this thread?
Click to expand...
Click to collapse
Read next time.
Sent from my HTC Sensation 4G using XDA App
xanderdad said:
Even though Root Explorer is granted SuperUser, I still can not modify system files. I also can not actually overclock with SetCPU 2.2.4. It will show the max as 1728000 but it will never scale above 1188000
The process is extremely easy and very user friendly though
Click to expand...
Click to collapse
Reboot and start from scratch
Sent from my HTC Sensation 4G using XDA App
Can we just freeze the bloatware with any freeze app?
Sent from my HTC Sensation 4G using XDA App
eugene373 said:
Reboot and start from scratch
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Reboot did allow me to rename system apps, thank you. SetCPU still doesn't work correctly, but reading the other threads, this seems to be the normal behavior at this time. Awesome tool Eugene.
xanderdad said:
Reboot did allow me to rename system apps, thank you. SetCPU still doesn't work correctly, but reading the other threads, this seems to be the normal behavior at this time. Awesome tool Eugene.
Click to expand...
Click to collapse
Open terminal and type fixit, as mine works perfect.
Sent from my HTC Sensation 4G using XDA App
it doesn't get any easier then this thx for this , everything works perfect except SETCPU is not letting me overclock ...
I really hate to add to the chaos, but no matter what I do. I am not able to get this to work properly. I have HTC sync turned off, and debugging and mock locations checked off, but when it gets to waiting for device, it just hangs, and never picks up the device again. I tried to remove the wait for device commands out of the .bat file, and it gets through but when I attempt to use even titanium, it says root not achieved, and will not let me through. Yes superuser is installed.
T-Mobile US Sensation 4G
EDIT: I finally got it to work. The last two downloads of the files must have been bad or whatnot. I redownloaded a third time and it was the charm! Disregard this. Love your work Eugene!
TheAnarchist1 said:
I really hate to add to the chaos, but no matter what I do. I am not able to get this to work properly. I have HTC sync turned off, and debugging and mock locations checked off, but when it gets to waiting for device, it just hangs, and never picks up the device again. I tried to remove the wait for device commands out of the .bat file, and it gets through but when I attempt to use even titanium, it says root not achieved, and will not let me through. Yes superuser is installed.
T-Mobile US Sensation 4G
Click to expand...
Click to collapse
You need USB debugging on
HTC Swyped from my Sensation using XDA Premium
I am posting this in the Developer forum, because it is still a little more than a In-experienced user can handle at the moment, and the potential to get into a bootloop is a little higher if you are not familiar with what you are doing here.
If you are at all new / uncomfortable with Android, UNIX/LINUX, this phone, or adb, then: PLEASE DON'T TRY THIS AT HOME.
If you get into a bootloop I am not responsible for this, nor is this the place to complain if that happens. You can ask for support here though if this process has caused that.
If you do get into a bootloop, then try and help me out, with providing as much info as possible with what happened (any output or screen prints are VERY helpful). I am also posting the original /system/etc/init.goldfish.sh file here AT THE BOTTOM OF THIS POST. That way if it does all go wrong it is here to grab. So don't go asking for it someplace else, or even asking here for it.
You have been warned!
Now with that out of the way, on to the good stuff.
1) Go grab some kind of bloat freeze program, from the market. I have used bloat freezer from the market with great success.
Just download and install it, don't run it just yet, if you already have, and frozen the "Device Health Application", then unfreeze it, and reboot, before doing the next step.
It is VERY important that it is done in EXACTLY this order. The reason is, if the Device Health program is frozen when you let the init script run, it will not work exactly as it should and these services will restart, since part of it is frozen when it first runs, and it all has to be disabled in the proper way, so that it can not be restarted remotely, or we will HAVE to use cron to run checks. Cron is an elaborate hack, I don't want to have to do, unless we HAVE to. If you do it in the exact order noted here, cron will not be needed and this will not restart.
2) Go get the init.goldfish.sh file from http://dl.dropbox.com/u/45576654/init.goldfish.sh.tar
push this tarball to your phone:
Code:
adb push init.goldfish.sh.tar /data/local/
End code
Now is the command line part of this hack.
Code:
adb shell
su
mount -o remount, rw /system
cd /data/local
tar -xvf init.goldfish.sh.tar
cp /system/etc/init.goldfish.sh /sdcard/init.goldfish.sh
cp ./init.goldfish.sh /system/etc/init.goldfish.sh
chown root /system/etc/init.goldfish.sh
chmod 550 /system/etc/init.goldfish.sh
mount -o remount, ro /system
reboot
End code
Now when your phone comes back up:
3) Open your bloat freezer program and freeze the "Device Health Application"
Your phone will freak out, and tell you that Device Health has stopped and it will keep asking you to FC, all you can do is pull the battery.
Put the battery back in the phone an boot it up.
Now CarrierIQ should be 100% disabled on your Atrix 2.
As promissed, here is the Original /system/etc/init.goldfish.sh file in a tarball, just use the same code above to put this back in place.
DON'T USE ROOT EXPLORER TO COPY THESE FILES INTO PLACE!!!
Original /system/etc/init.goldfish.sh file:
http://dl.dropbox.com/u/45576654/init.goldfish.sh-orig.tar
The Jedi Master strikes again!
The force is strong in this one. Seriously Jim you absolutely amaze me. You are the Linux guru.
Sent from my MB865
Train us, he will.
Sent from my MB865 using Tapatalk
LOL....
Hopefully I have not scared everyone from trying this.... I just want to let all the newbies who just got this as thier first android phone yesterday, and rooted it today, and now think that this is a good hack to try, that this is not the best thing for them just yet. It can and will bootloop the phone if you get too excited and don't follow the directions exactly... I got mine in a bootloop testing this all out, and finding the exact steps, but it was not hard to get out of, because it gets into android enough to let you adb in, if you screw up...
quick question: Why would rooting followed by freezing not work for that application? I think I did that when I got the phone. I don't see anything called Device Health in my running or installed applications.
Is carrierIQ still running on my phone? Have you got a string I can look for in the 'ps' output in the Terminal to confirm? There are 100000 processes running on these phones these days, most with cryptic names.... I miss the G1 days....
devsk said:
quick question: Why would rooting followed by freezing not work for that application? I think I did that when I got the phone. I don't see anything called Device Health in my running or installed applications.
Is carrierIQ still running on my phone? Have you got a string I can look for in the 'ps' output in the Terminal to confirm? There are 100000 processes running on these phones these days, most with cryptic names.... I miss the G1 days....
Click to expand...
Click to collapse
No just freezing the device health app just stops the collection process.
The part where you run the commands to stop the services in android are where the data can and will be sent to CIQ or AT&T, there are other things collected that att does not care much about (ATT only wants what is collected with the dev health app), and that goes straight to CIQ, so the services at the OS level are VERY important to stop. There is really not a way to see them running, but I have found that these can and will restart if my instructions are not followed 100%. To find out if CIQ is doing anything take a look on youtube there is a video that explains how to look at the system logs and see what is being collected if anything, and what is being sent out. After a lot of trial and error, I found this is the ONLY way to stop it 100%.
Hey Jim. sorry I've been out of the forums for so long on this. I was going to dig around my atrix2 and see what I could find wrt carrieriq. I got stuck on missing shell tools and you gave me some advice wrt paths and such. I was wondering if you could point me in the right direction for fixing up my env when I shell in? I also don't seem to have grep anywhere... odd.
YOu mentioned doing some of the destructive work in an emulator, and I would like to try the same thing, but I've no idea how to get the atrix2 ROM into an emulator. How did you accomplish this?
I followed the instructions above precisely and verified that my init.goldfish.sh is indeed modified correctly with the carrieriq stuff, and have suffered no ill effects. I have not, however, attempted to determine if carrieriq processes have stopped running. I did notice that after having frozen and unfrozen device.health.monitor a few times, it doesn't ever register as a running app... wonder what's up with that.
thanks for the help.
I was wondering....could this be made into a handy dandy flashable zip?
Then after flashing just freeze the app?
Sent from my MB865 using XDA App
tylercarter said:
I was wondering....could this be made into a handy dandy flashable zip?
Then after flashing just freeze the app?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Yep, working on it, should have it up for download tomorrow.... It will also be in my rom.
Jim
Sent from my MB865 using xda premium
jimbridgman said:
Yep, working on it, should have it up for download tomorrow.... It will also be in my rom.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Sent from my MB865 using xda premium
jimbridgman said:
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
NICE! you really are a jedi master!
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
jimbridgman said:
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
Click to expand...
Click to collapse
It said switch to edify scripting. Installation aborted. Something about gingerbread cwm 3. Not sure. Never see this before. I checked the zip and it has 2 updater scripts. One just has a ~ at the end. I know nothing of code but just trying to help.
Sent from my MB865 using XDA App
jimbridgman said:
Who wants to be the first to try this out? I have created a flashable zip to disable CIQ on every boot, all you have to do is grab the file below:
http://dl.dropbox.com/u/45576654/NoCIQ.zip
Then with CWM, flash it, don't wipe anything, except maybe dalvic cache, but nothing else. This will only flash one file to your phone.
You will still have to freeze the device health app as in the OP.
This is just a test right now, once someone other than me tests this, and reports back, that all is great, then I will update the OP, to this method.
Click to expand...
Click to collapse
Tried this. No go. Here is the error in CWM.
Installing Update...
Amend Scripting (update0script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recover.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation Aborted.
There ya go. Hope this helps.
holeshot77 said:
Tried this. No go. Here is the error in CWM.
Installing Update...
Amend Scripting (update0script) is no longer supported.
Amend Scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recover.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Installation Aborted.
There ya go. Hope this helps.
Click to expand...
Click to collapse
hes working on it. wont be much longer
Why not use the app by TrevE?
Sent from my MB865 using xda premium
1.18.12 said:
Why not use the app by TrevE?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
That does not perform the hack, only detects if it is running. The voodoo ciq detection app works much better though.
Jim
Sent from my MB865 using xda premium
I just rooted my phone, applied the hack and used Titanium Backup to freeze the Device Health App but I didn't see any FC.
Although when I opened Ti Backup, it told me that my su right are wrong. They are 4755 instead of 6755 or something like that and TiBu told me that it will fix it. I fixed it then froze the app and no FC or nothing. Phone is running fine but not sure if it worked.
Is it really necessary for the app to FC in order to show that it worked?
Should I try it all over again?
Thank you.
noobsquared said:
I just rooted my phone, applied the hack and used Titanium Backup to freeze the Device Health App but I didn't see any FC.
Although when I opened Ti Backup, it told me that my su right are wrong. They are 4755 instead of 6755 or something like that and TiBu told me that it will fix it. I fixed it then froze the app and no FC or nothing. Phone is running fine but not sure if it worked.
Is it really necessary for the app to FC in order to show that it worked?
Should I try it all over again?
Thank you.
Click to expand...
Click to collapse
Go download and install this, and it will show you if it (CarrierIQ) is active or not.
https://market.android.com/details?id=org.projectvoodoo.simplecarrieriqdetector&hl=en
I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!
ned4spd8874 said:
I installed a custom boot animation and now my phone won't boot up properly. The animation won't show during boot and basically after the galaxy sIII screen, nothing is shown. The phone seems to be started okay, I hear sounds and vibration when I press buttons, but the screen just is not showing anymore.
I'm trying to boot to recovery and use adp to either delete the bootanimation.zip or push a different version, but I get the device not found error.
PLEASE HELP!!!
Click to expand...
Click to collapse
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app
ajrty33 said:
How'd you install it? Do you have a link to what you flashed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.
I am have execet same issue please help
ned4spd8874 said:
Thanks, but I finally got it figured out. Scarred the crap out of me for a minute there though!
I was able to run "adb push bootanimation.zip /system/media" and it works after reboot. I couldn't get it working in recovery, but was able to with the phone started like "normal".
Not sure what was wrong with the other version of the bootanimation to totally killed the screen though. The only thing I can think of is there was zip compression on. But I would have thought that wouldn't kill the entire screen like that! Dunno.
Click to expand...
Click to collapse
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!
MyMymusicIsSoHard said:
So I am experiencing same issue I can please be little be more detailed how you pushed the bootanimation. except command. please i am panicking i know there is a solution but i just cant seem to make it work. You help would be much appreciated. thank you!
Click to expand...
Click to collapse
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.
Had to flash the fireware
ned4spd8874 said:
Sorry, it's been so long I can barely remember this! I think what I did was pretty much as I described. I booted the phone up, waited for a little bit to make sure it was all the way started since I couldn't see the screen. And then plugged in the cable and performed the push command. It was pretty straight forward as long as you can ignore the fact that the screen wasn't displaying anything.
Click to expand...
Click to collapse
So my Debugging mode was off so I could not use adb push command, I had to do a complete firmware flash, that got my phone to work but lost all my data on the phone. but still a happy camper.
Thank you for prompt response, all your help it's much appreciated.
I had the same problem but with an ASUS memo pad hd7. I downloaded a bootanimation.zip that was the wrong orientation, so I unzipped it, rotated all the pictures rezipped and placed it back in /system/media/. Mistake! After that the device would not boot! At least that's what I thought until a quick google search led me here, thanks for your help! My situation was a little different, i'll explain my journey below in case it helps others with similar situations.
Installed minimal ADB and Fastboot from here http://forum.xda-developers.com/showthread.php?p=42407269 . I already had the device drivers installed on my computer so I skipped that step. Luckily I had USB debugging selected, however, I had never used ADB and had not given it SU permissions on the tablet. I input the following code into adb:
adb shell
cd /system/media/
ls
This verified that the offending bootanimation.zip was in there. I then tried to remove the offending bootanimation.zip with this command
rm bootanimation.zip
It failed because system was mounted as Read Only and I could not change it because I did not have SU permissions so I hit the power button on my tablet to wake it up, blindly swiped to get through the lock screen, and typed this into ADB to request Super User permissions
su
I then blindly tapped near the middle of my screen. After a few tries I successfully hit the right spot at the right time and granted SU to ADB
Once that was done I remounted system as read write and deleted the offending file with this code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
rm bootanimation.zip
ls
After verifying that bootanimation.zip was gone, I rebooted the tablet and was greeted with success in the form of some generic Android boot animation.
Same thing with my Panasonic p11 and I have a password for SuperSU so I am stuck pls help
I would suggest flashing a backup from before the custom boot animation. Then taking more cautious steps the next time you try.
To avoid this kind of unpleasantness, whether for changing the boot animation or anything else, here's a few tips:
always root your phone
It's your phone, you should have access to everything, shouldn't you? That's like buying a new car and the dealer won't give you a key for the trunk.
always use a custom ROM
Stock ROMs are usually bloated with apps you don't need and can't uninstall. Also, stock ROMs often disable features and access either "for your own good" or to keep the interface simpler. Case in point, neither of the stock ROMs that came with my Galaxy S4 or my Atrtix HD allowed me to customize the LED notification light. Whatever defaults they picked, that's what I got. A flashing green light meant I received "something" (text or email). There are a variety of 3rd party ROMs out there ready to flash for a specific device, find one that you like.