This is really 2 questions. Is there a way to install clockwork on the Captivate if you are running Gingerbread 2.3.3 "stock". The reason I ask, is I want to wipe my battery stats and it seems that clockwork is the only thing that can do it.
Thanks.
Sgs tools has a script for that but i never tried.
Without having to install anything more than an app you can manually delete the batterystats.bin from /data/system using a proper file explorer app (as with SGS Tools mentioned above, you'll need root access).
Related
Hi all,
my problem is this: I've upgraded to Froyo and installed OCLF 2.0. Several months later, my phone is again extremely slow, response times on any task are high and it pretty much drives me nuts!
Wanting to remove OCLF from my device, I've tried the following:
- started OCLF > Undo OneClickLagFix V2+
- Remove EXT2 Tools - this failed with error: Could not remove library libext2_blkid.so: rm: can't remove /system/lib/libext2.ro Read-only file system
Now the "Undo OneClickLagFix V2+" option is unavailable anymore and I can't use Kies to upgrade / restore the firmware as it keeps loosing the connection with the device.
In summary, I'd like to somehow get rid of OCLF. Could you please point me in the right direction here?
Thanks in advance!
anyone? i'm looking to install the oclf 2.0 as well....
It sounds like you didn't let the lagfix finish uninstalling before you tried to remove the Ext2 tools.
Can you select Apply Lagfix 2.0 again? If so I would reapply it, then remove and try removing the Ext2 tools again.
You may also want to consider just flashing cm7 since it will remove any lagfixs during install automatically when it overwrites your file system.
Sent from my GT-I9000 using XDA Premium App
Or flash any full firmware (either stock or non-CWM custom ROM) in Odin using repart and PIT. Since it will completely overwrite your filesystems, it doesn't matter if it was lagfixed (or messed up, for that matter).
help/tips on oclf uninstall for updating android
i have ryan's oclf installed on my 2.1 captivate and would like to update to 2.3 or whatever is most current.
so are the steps for removing ryans oclf as simple as, going into the lagfix itself and selecting:
1. undo oneclicklagfix v2+
then remove ext2 tools should become "available"..so then
2. remove ext2 tools...?
will i also need to unroot to update my captivate using kies mini...?
thanks in advance for any information/help.
hey all,so some days ago i had to restore a nandroid backup because the new superuser app badly messed up my rooted apps etc etc. after the restore all looked good till i go to recalibrate my battery: i use the battery calibration tool which is on market,when i hit calibrate it tells me that batterystats.bin cannot be found
point is that i didn't delete it so i go and see by myself with root explorer and i found this "batterystats.bin.tmp" file. i tried to delete it but it recreates itself after a while. i tried to replace it with a batterystats.bin which i pulled out from previous backup with unyaffs: nothing,system deletes batterystats.bin and replaces it with batterystats.bin.tmp. i even tried to restore another nandroid with a normally working batterystats but immediately,here too,the system replaces it with this .tmp file
anyone has a clue of what it's all about? thx
ps: yes i did multiple full recharge cycles but the normal batterystats still doesn't show up. i'm on rooted stock froyo 2.2 speedmod kernel.
bump,can anyone help please?
ps: dunno if i can bump this whitin 24h,but i really need to figure out this thing,sorry mods
Hi Guys
Ive recently been trying to sort out my wife's SGS its run like a dog since she got it.
Ive updated to the latest firmware kies advises 2.3.5 XXJVT and have now rooted the phone with a view to installing fixes for the phone.
Ive attempted to run the lag fix. Ive used CF-Root-ext4-v1.3 app to do this. It work on all partitions apart from /system where is says "cant restore files - not enough memory ?" then rolls back to an RFS partition. Since doing this the quadrant score comes in at around 2300.
Can anyone advise me on what to do to resolve the issue with the /system partition or advise of any other tricks I can use to make the phone preform better ?
Thanks
Richie
You need to remove some system apps...like Aikedo books and Daily brief, allshare....one you dont use....use an app from the market like absolute sytem to remove these apps...its free on the market. Once removed you will have more space to do a full conversion to ext 4.
Is there any other way around this ?
Is there a list of safe apps to remove ?
a way around it? No, you need more space on your system to convert to ext 4...everyone that has a stock rom needs to make space to convert to ext 4 otherwise they have the same result you did....unless you want to keep aikido books and allshare for what ever reason. Those are the ones that most people remove. Its perfectly safe, you just wont have those apps anymore....those apps arent running your system.
I use Darkys Rom tool to remove apps, it is simple to use and you can always restore them.
Hop you get it sorted man
cheers
i was trying to not go to a rom as I dont want her to loose any data she has now.
I tried removing system apps but when I delete them using a root file manager they just re appear
Can I also ask does sgs phones with out the lag fix typically have crashing issue with system apps like calls ?
think i may have to flash another rom onto this phone but thought id bump this just once more. just incase someone can think of a way to avoid this.
After applying the lagfix on CF Root, can i install Voodoo color and sound??
And is it possible to install CWM Rom Manager and flash some ROMs??
even without applying lagfix you can obtain voodoo sound and color evn the cwm manager.
just use semaphore or any kernel with voodoo sound and color.
Hi,
the problem is next:
I root my phone (xperia x8) with super one click (successful), i follow the instructions
then i installed root explorer. after that I copy the cwm files and with root explorer i tried to remove it to system/bin
the problem starts here. there wasn't enough space, so I remove 3 files of 4.
after that i uninstall some unimportant apps to get some space.
when I tried to enter root explorer the message appear:
"restart app"
"Root explorer has not yet managed to obtain root accsess because of issuses with superuser,this often happensthe first time the app is run but usually fine from the on Click ok and restart the app to try again make sure you respoding superuser promt"
after that i tried everything:
- reinstall root explorer, restart phone, allow/decline in superuser... no result
- install es file es file explorer, and follow the instructions but no results, can see the system/bin folder but can't manage(copy/paste, cut/paste)
the message when i click root explorer in es file explorer said that the phone is not support.
in meanwhile I noticed that i cannot connect to my wireless network....
after that i tried:
- settings reset, nothing
- factory defaults.
after factory default my phone don't recognize my Sim card, and the wireless still not work.
I don't know what to do.
Can someone please help!
Please
did superuser ask you about permision? if not then you need to have superuser to use that alsbo you can install the cwm via rommanager which can be downloaded for free from google play
Thanks for the answer.
The superuser asked me about permission. and I click allow.
what is the procedure with rommanager?
Thanks in advance
after you get it from market you just need to open it and click flash cwm recover after that it will tell you that is completed succesful or not
but...
there is a little problem,
i can't connect to wireless network, and my sim card don't work, so I can't download it from market...
any suggestions?
Thanks in advance
Moved.
Questions belong in Q&A
Sent from my GT-I9300 using xda premium
to solve wifi problem try flash stock rom again
Thanks for your answer misiex2212
Can someone post me a link with good tutorial for updating
Sony ericsson xperia x8 version 2.1.1 to some other version of software, higher
(i need to install apps on sd card because the memory of the phone is to small)
and working software for it.
I manage to back my phone to factory state (without superuser icon)
he is now just like he was when i bought him.
now I'm ready to start again
Please help, I don't want to stuck in the way because of bad instructions or bad software.
Thanks in advance
Root your x8 using flahtool then use x8 toolbox to install recovery or cwm (is better) then try to get to cwm and make backup. Chceck mamufacture date and if you can unlock your bootloader then download and install custom kernel and rom
http://forum.xda-developers.com/showthread.php?t=1254225 gguide for bootloaders and kernels
Sent from my X8 using xda premium
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
Thank you so much. I had this problem for days. Why isn't my unlocked phone writeable in the first place...
sharksfan7 said:
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
Click to expand...
Click to collapse
You just used your stock kernal 0.0
Why isn't mine like that. D=
elfking7 said:
You just used your stock kernal 0.0
Why isn't mine like that. D=
Click to expand...
Click to collapse
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
sharksfan7 said:
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
Click to expand...
Click to collapse
I followed alray's advice. I installed the elementalx kernel which made my system writeable, since my stock kernel wasn't originally. I then retry using the root companion (I installed gsam battery monitor since last week) which finally worked by using the automatic option that the root companion provided. I didn't notice much difference with the app, after giving the battery monitor privileged access to the system=/.