After rooting my phone yesterday I got a little delete happy and deleted a volume warning file with titanium backup. I'm certain it's the file that would drop the volume then display the damage hearing warning. Is there a way to just reinstall that particular file? Where can I get it? Where do I put it? Thanks to anyone who has the explanation. If not I'll just reinstall the OS and re-root.
Phone: Xperia LT30P
OS: 4.1.2
edit: I figured it out. Just restored the file through root explorer. MODS CAN DETETE POST.
Related
Please help. I rooted my Bionic and removed some of the bloatware via Titanium Backup. Not being totally stupid, I did a backup of the apps first. When I tried to load the new OTA, I got an error because it was apparently looking for the IM app (Which I never use). Of course, I had removed it as bloatware. When I tried to reinstall it via Titanium Backup, it just hangs.
I wasn't giving up so easily. So I extracted the apk file from the zip file and tried to reinstall it manually. Unfortunately I get "App not installed".
Any ideas?
I don't have my phone with me at the moment (gasp!) but near the bottom of the main preferences list in TB there is an option for failsafe mode. Make sure this is checked and put it on "indirect" app processing mode. Wording may vary slightly from that but if you set those two options it should work.
88Keys88 said:
Please help. I rooted my Bionic and removed some of the bloatware via Titanium Backup. Not being totally stupid, I did a backup of the apps first. When I tried to load the new OTA, I got an error because it was apparently looking for the IM app (Which I never use). Of course, I had removed it as bloatware. When I tried to reinstall it via Titanium Backup, it just hangs.
I wasn't giving up so easily. So I extracted the apk file from the zip file and tried to reinstall it manually. Unfortunately I get "App not installed".
Any ideas?
Click to expand...
Click to collapse
And for future reference, use the freeze option next time instead f removing them.
MillionManMosh said:
I don't have my phone with me at the moment (gasp!) but near the bottom of the main preferences list in TB there is an option for failsafe mode. Make sure this is checked and put it on "indirect" app processing mode. Wording may vary slightly from that but if you set those two options it should work.
Click to expand...
Click to collapse
I hope you and your phone have been joyously reunited
I triedd your suggestions, but alas no go. Any other ideas?
If you already have everything backed up I'd just go ahead and use RSDLite to set the phone back to stock:
http://forum.xda-developers.com/showthread.php?t=1262540
Just keep in mind you lose root through this, so to be safe you might want to reroot and apply the 'forever root' hack before you update. Although I understand newer root exploits like R3l3as3d work on the newer system as well.
And yes, the battery was joyously reunited with the charger...
It's a little more hard core than I've gone before, but I guess it's my only option. I've flashed ROM's before to my OG, but never had to go this route.
Thanks for your help and wish me luck!
And to johnlgalt - What can I say but I always learn from my mistakes. Monday morning is always the best time to be a quarterback ;-)
The OG DROID had an unlocked everything, so it was easy to do all of this. Because of eFuse and our locked bootloaders, it's most definitely more complicated. Our phones cannot even replace the recovery yet all we can do is use a bootstrap method to bypass the stock recovery and run an alternate recovery - and until we get a disabled eFuse and unlocked bootloader, this ain't gonna change.
Newbie here. I've unlocked the bootloader, but had held off rooting until I could see a point. Now I can; I do not want Moto's incarnation of Jelly Bean, in fact the more I hear about it the more I absolutely hate the prospect. I once found a post on how to disable the ota download, but have now lost it. I gather the simplest is to forever postpone the installation on each hourly reminder, the alternative I seem to remember is to root/download a file explorer from the Android Market (which is easiest?) and modify some code in the firmware.
Sorry, but I can I get some detailed idiot-proof line by line instructions on how to ensure I don't get a Jelly Bean upgrade, ever. I'm one of the lucky ones not to receive a notification yet, so I'd like to get on with it.
UPDATE: I have rooted (seemingly successfully since Titanium Backup works) and also installed root explorer. I can't see an obvious way to freeze the update application in Titanium though. Help Please.
I also found an application Blur.Updater in root explorer, which I have renamed with an additional .bak, but I am not sure if this is right or on its own enough to stop the update? (It was the only result on a search for updater.apk). There are other Blur.Updater applications but root explorer informs me that they cannot be renamed as they are read only system files? I'm getting a bit desperate now.
Is it a fruitless quest?
To summarise: I've an unlocked bootloader, rooted phone; have file explorer, root explorer and Titanium Backup (full edition) all running successfully. With all that lot, is there anything I can do to prevent an automatic update from ICS to JellyBean?
UPDATE: touch wood I used the advice in this thread: T-Mobile, Wind, Mobilicity, Videotron Samsung Galaxy S III > T-Mobile Galaxy S III Q&A, Help & Troubleshooting > [HOW TO] Disable OTA Update Notifications!!!!!!!!!!!!! to modify what seems to be the equivalent files on the Razr i files using root explorer.
Now, unless someone knows better please: to sit back, wait, and see what happens. At least on reboot I still had a working phone!
A few days ago randomly lost root couldn;t figure out wh. Since I'm pre OTA, I used RSD to reset and then reroot with PwnMyMoto.
Since then when my alarm goes off, the original screen that would pop up that would allow me to either snooze or turn it off simply doesn't appear. The only way I can turn it off is to force stop the clock app.
I'm trying to figure out if I should just use RSD again and root or it is time to change to the most recent root method anounced. Are there any disadvantages to the new root method? Has anyone had anything weird like this happen to them?
Icon000 said:
A few days ago randomly lost root couldn;t figure out wh. Since I'm pre OTA, I used RSD to reset and then reroot with PwnMyMoto.
Since then when my alarm goes off, the original screen that would pop up that would allow me to either snooze or turn it off simply doesn't appear. The only way I can turn it off is to force stop the clock app.
I'm trying to figure out if I should just use RSD again and root or it is time to change to the most recent root method anounced. Are there any disadvantages to the new root method? Has anyone had anything weird like this happen to them?
Click to expand...
Click to collapse
this has nothing to do with the root method. it is something going on when you restore to factory stuff. redownload the fxz, make sure its the right one (carrier, version, etc.) and then make sure rsd actually finishes everything it is trying to do.
Is there a way to verify that is has done everything it is trying to do? I have restored with this file before and I had no previous issues.
jayboyyyy said:
this has nothing to do with the root method. it is something going on when you restore to factory stuff. redownload the fxz, make sure its the right one (carrier, version, etc.) and then make sure rsd actually finishes everything it is trying to do.
Click to expand...
Click to collapse
Icon000 said:
Is there a way to verify that is has done everything it is trying to do? I have restored with this file before and I had no previous issues.
Click to expand...
Click to collapse
it would show something failed if something failed. But maybe it just got sent yo your phone improperly or something. The only reason i say this is the case, is because there is no chance it was the root exploit, maybe something you did during that exploit or after but not the exploit itself. No one else is having this issue, so it is most likely something you did and not something that is an actual bug. If the only thing oyu did was restore your phone with rsdlite, then something prob errored during this restore. It is a software issue, so the fact that you have the problem but i haven't seen it reported any where else ever, probably means its something you did to your phone incorrectly.
Galaxy S5 Boot animation like here :
https://www.youtube.com/watch?v=80-Pwv1Q7Qk
How to install:
1.Download Root exploer (or something like lidroid file its has root exploer)
2.Connect to pc and copy the files
3.Copy the all files
4.Put them in system -> media
5.Change the permission to rw-r-r. (thanks vwmaniacx)
6.Click the thanks button <<
7.You are done !
Download here:
https://www.mediafire.com/?p06ja79a3r7nb97 ( By me )
I gave this a shot, and now my phones screen won't turn off, and the phone will not remain off. Ideas?
I don't know I got 4.4.2 you have this version?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Yeah, I updated from 4.3 to 4.4.2. retained root, everything was good. Then tried this, and now I have that problem. Anyone just got the original stuff?
Edit: I unzipped the new 4.4.2 update, none there.
Edit 2: The power button works, but won't turn the screen off. also no widget made for turning the screen off will either. The only way the phone will stay off, is if you remove the battery, and put it back in.
vwmaniacx said:
Yeah, I updated from 4.3 to 4.4.2. retained root, everything was good. Then tried this, and now I have that problem. Anyone just got the original stuff?
Edit: I unzipped the new 4.4.2 update, none there.
Edit 2: The power button works, but won't turn the screen off. also no widget made for turning the screen off will either. The only way the phone will stay off, is if you remove the battery, and put it back in.
Click to expand...
Click to collapse
it's weird its work to me ..
try this :
http://forum.xda-developers.com/showthread.php?p=43397866
Steev43230 said:
CAUTION: Make SURE you really DO copy the new boot animation files back to your phone. Otherwise you run the risk of the power manager service continually checking to find out if the boot animation has finished, and that will result in disabling the power button's ability to turn the screen off and the ability of the phone to sleep in general.
There is very little help on the web for this particular issue, most having to do with broken power buttons and obtaining replacement phones/tablets, but in my case I was lucky and just happened to see the log entries scrolling by in the Android SDK's DDMS tool, which clued me in that the problem was with the missing boot animation files. I was JUST about to do a hard reset of my phone back to AT&T original ROM settings, with all of the pain that would've entailed given that as of this date we still cannot install custom recoveries on our very expensive pocket computers.
Click to expand...
Click to collapse
Helpful. :good
Edit: Found changing the permission fix the whole problem. You should toss in just to make sure they are set up rw-r-r.
@sagi232123
Where to find bootanimation.zip in system of the S5?
JanM RS said:
@sagi232123
Where to find bootanimation.zip in system of the S5?
Click to expand...
Click to collapse
Idk .. i dont have one hh
search in s5 forms maybe you will find
vwmaniacx said:
Helpful. :good
Edit: Found changing the permission fix the whole problem. You should toss in just to make sure they are set up rw-r-r.
Click to expand...
Click to collapse
Found this helpful, had same problem (not because of above posts). Could not turn off screen with power button etc. However this post put me on the right track. I just disabled all boot animations using ROM Toolbox Pro. And fixed said problems. Thanks
Thank you for this, I had already gotten rid of my carrier's boot animation but the Samsung one I had was boring. All the issues brought up in this thread are avoided as long as you set permissions. This worked on my Galaxy S4 Active i537
Worked for me as well on my AT&T i537. Didn't even download through my computer, just downloaded straight to my phone, moved with root explorer and put the appropriate permissions. Worked like a charm.
Custom animation
Hey how can i install a custom animation of my own?
Hello everyone!
So I rooted my Note 3 back when I first got it and I've been loving it. Well, about a month ago I noticed that an application that I wrote (restarts my phone automatically under certain conditions) would not work correctly, as though its Superuser permissions were revoked, but the SU app said everything was fine. Fast forward to a few days later and I try to access the root of my phone using ES File Explorer and discovered that I had lost root. I tried Kingo Root and Towelroot and they both failed, so I'm stumped as to why I lost root and why I cannot seem to get it back. I know I could go about wiping the phone but that would remove everything on my phone except for my applications and those are the least of my worries.
Any ideas? I appreciate any and all help!
Android Version: 4.4.2
Baseband Version: N900AUCUCMLG
Kernel Version: 3.4.0-257432
Build Number: UrDroid KOT49H.N900AUCUCMLG
Not sure if any of this information makes a difference but it's worth posting just in case.
To anyone who may come across this and is having the same issue, I was able to resolve mine, and hopefully the steps that I took (listed below) will be of some kind of assistance to another.
I still had Safestrap installed, so I was able to install a ZIP version through it, and I rebooted after it was done. I let the phone load back up fully before going back into Safestrap to wipe the Dalvik/Cache, attempt to Fix the Permissions (which failed), and then renamed the data/data/eu.chainfire.supersu folder to eu.chainfire.supersuh (as I thought that maybe the old folder was causing conflicts). After booting back into Android I had root again! I cannot delete the eu.chainfire.supersuh hence why I renamed it, but I've got root back on my phone so I'm satisfied.
I will add that all of these steps may not have been necessary but I do not know what step made it work, this is just what I did to solve my problem.