Having problems after switching rom to gummycharged with imo's 3.1.0 kernal and using tegrak overclock. I was previously using another rom with Imo 3.1.0 kernal and used Tegrak overclock without any issues. Yesterday I flashed Gummycharged and flashed Imo 3.1.0 kernal once again after installation I am now having issues loading module in Tegrak Overclock. I know that Tegrak overclock works based on kernal. I can't seem to figure out why with a different rom running the same kernal that Tegrak Overclock now wont load a module. I was hoping someone has had this experience and would be able to help me. Thanks
So what's the error message? Also, do you have a chance to allow it Superuser permissions?
Sent from my Droid Charge running Infinity Beta
The error I get it. Your device is not availiable. Do you want to see available models?
You know its funny when I adjust scaling was the only time that it asked for superuser permissions. I have tried to clear data in the app, uninstall app and reinstall and it never asks me for superuser permissions. I thought the same thing and thats why I tried to uninstall. I also looked in my superuser app to see if I could force the application permissions and couldn't find any options for that.
Open /system/build.prop and change the ro.product.model= line from "GummyCharge..." to "SCH-I510" and reboot the phone.
Awesome! Thanks for the help. I appreciate that and I'll save that for future reference!
Related
Hello, I am still learning but I have downloaded Setcpu and am curious do I just flash this on my phone like its a rom? or can someone tell me how to get this on my phone? THanks
Should just be installed like any other apk. If you don't have a app installer, just download Astro file manager, or something similar and you can install it from there.
Well, I can tell you that if you had used the Android Marketplace to buy SetCPU, it would have automatically installed. If SetCPU was obtained from a different source, then you should contact them.
As a warning, be very careful with overclocking: go too high, and you will see instability of the phone. I would recommend ensuring that "enable at startup" is NOT checked until after you have tested and found a stable setting.
Sent from my PC36100 using Tapatalk
Ayryyn said:
Well, I can tell you that if you had used the Android Marketplace to buy SetCPU, it would have automatically installed. If SetCPU was obtained from a different source, then you should contact them.
As a warning, be very careful with overclocking: go too high, and you will see instability of the phone. I would recommend ensuring that "enable at startup" is NOT checked until after you have tested and found a stable setting.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Setcpu is available here on xda. But one can/should download from market to support the developer.
http://forum.xda-developers.com/showthread.php?t=505419
Op, like kb112 says, use astro to install any apk.
Sent from my PC36100 using Tapatalk
Thank you guys! I have figured it out!!!
I am ready to install SetCPU. Is one better than the other? >
'Storage' (Modify or delete SD card contents)
'System tools' (prevent phone from sleeping)
Thanks
Hi Family
I have update to Dexter's froyo 2.2.1 for Milestone XT720, I now find that I am unable to update Milestone Overclock 1.4.7 or install Busybox 1.18.4. When trying to update Milestone Overclock to 1.4.8, I get Package file was not signed correctly installation error message. And if I updatebusybox 1.15.2 to busybox 1.18.4 phone locks up at bootup, can anyone help me out please?
XT720Dawg said:
Hi Family
I have update to Dexter's froyo 2.2.1 for Milestone XT720, I now find that I am unable to update Milestone Overclock 1.4.7 or install Busybox 1.18.4. When trying to update Milestone Overclock, I get Package file was not signed correctly installation error message. And if I updatebusybox 1.15.2 to busybox 1.18.4 phone locks up at bootup, can anyone help me out please?
Click to expand...
Click to collapse
Search is failing me, but I remember someone had trouble when they updated busybox using the app because they accidentally changed the install location. Dexter's ROM boot scripts require /system/xbin/busybox. If you accidentally move it to /system/bin/busybox or somewhere else you will bootloop.
To upgrade Milestone Overclock, first delete the ROMs copy from /system/app. This will avoid the signature error when you try to install Milestone Overclock from the market.
Thanks, I haven't try to install busybox yet but, the Milestone overclock apk is read only I cannot delete it, do you know how to change file attributes?
Titanium Backup will remove system apps. If you're getting the read only error in Root Explorer there is a button at the top to mount the partition with r/w permissions.
HTH
I also having this issue. My phone is running Dexter's Froyo 1.3 with patch v2. (See my signature). When I tried to uptade Milestone OC 1.4.8, I got signature check issue.
I removed the app with Titanium Backup and install the new version, it failed to load the module. I reboot the phone and to my surprise, the Milestone OC is 1.4.7 again (but able to load the module and OC)
Is something is restoring the system apps on every start-up?
Sent from my XT720 using XDA App
spiderx_mm said:
I also having this issue. My phone is running Dexter's Froyo 1.3 with patch v2. (See my signature). When I tried to uptade Milestone OC 1.4.8, I got signature check issue.
I removed the app with Titanium Backup and install the new version, it failed to load the module. I reboot the phone and to my surprise, the Milestone OC is 1.4.7 again (but able to load the module and OC)
Is something is restoring the system apps on every start-up?
Click to expand...
Click to collapse
The overclock module is automatically loaded by the ROM boot scripts, so when you try to load it again in the app, you get an error. This isn't a problem. I don't know why it came back as the old version, though. I don't know of anything that would cause the old version to be restored. Maybe, the dalvik-cache needs to be wiped...?
milestone overclock reset @startup
hello all
unistall or update milestone overclock failed on my devices setup after a few trys i found another solution
i run my xt-720 with dexter`s milestone2.2.1 xt720 remake v1.3 bugfixv3 and till yet found no more bugs without milestone overclock
if you type milestone overclock in market search there are 6 apps,cpu master (free) is one of them with this i fixed my problem that the cpu is set on 550 mhz at startup!
Just download it!
Open the old milestone overclock set cpu on what you want (i did 1ghz).
After this open cpu master (free) set my cpu min 1ghz max 1ghz,hook in set on boot box and tada after startup it sets cpu to 1ghz
,for more battery life take a lower number a the min value
precaution hook in set on boot in milestone overclock,dont know if its relevant XD
mfg jens
ps:hope this can help some people and sry for my bad english
I am trying to install busy box so I can using it to OC using the Tiamat kernel. Droid Over lock ask if I want to install busy box and I agree...it loads and then does nothing. I have gone into the SU app and chose to "forget" the busy box installer and it says that busybox does not have root, which I have. Any thoughts on how I can fix this? I like Droid Over lock versus SetCPU so I would really like to figure it out. I know that it has worked before (before the update) because I have used Droid Over lock on the Xoom before. Thanks!
No help, anyone?
How do you know it failed?
I'm confused! I have superuser installed and as of yet no app has asked for permissions; they just work. With the exception of ROM Manager which just freezes (needs long hold on back key). On previous ROMs I've flashed, requests for permissions pop up and you allow/deny etc. I've tried using the updater from the marketplace (force closes) and updating the binary (force closes). Am not able to uninstall superuser. I've turned on/off USB Debugging, fixed permissions, almost everything else I've found on the net.
As apps are working it isn't the end of the world but I'm confused about why they are working and also slightly concerned over the security aspect of apps not asking me and just running.
Apps that work without asking include: Titanium Backup, CPU Master, NSTools, File Explorer
I9020
Matr1x 15 Kernel
Orca 1 RC-0.1 (Drew Garen/BamtauMod)
What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Hi,
According to the app it's version 3.0.7 (41).
I should've mentioned that it's an ICS ROM, sorry.
flodb113 said:
What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Click to expand...
Click to collapse
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.
Dynamo Nath said:
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.
Click to expand...
Click to collapse
Glad you're happy with it! When ICS came out, we had to wait a week (I think) for the update to make SU work properly. Great work from the dev, as always.
I have find a new supersu here
http://forum.xda-developers.com/showthread.php?p=23427715
It is working good so far. Is it possible to remove the original super user bundeled with the custom roms. Or it can get some bad effect on custom rom.
Yerp saw this back in march...see it's been updated....:thumbup:
Thx
Probably not that great. Superuser is used universally for a reason.
wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
guess you know this because.....
Actual it is....but you prob installed it and ran it huh?
I have deleted the /system/app/SuperUser.apk through Root Explorer
SuperSu is working fine.
(It should only be done after installing SuperSU from the market, then run it a popup will come up asking to update binary say yes.)
Bought it a while back to support Chainfire.
wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a pain for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.
Entropy512 said:
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a ****ing pain in the ass for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.
Click to expand...
Click to collapse
Would you recommend using SuperSU over superuser in CM9?
stratatak7 said:
Would you recommend using SuperSU over superuser in CM9?
Click to expand...
Click to collapse
Not in CM9
Entropy512 said:
Not in CM9
Click to expand...
Click to collapse
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?
TDuran said:
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?
Click to expand...
Click to collapse
Just for kicks, I installed it and tried it. This probably isn't the "proper" method and you could possibly mess something up but anyway here is what I did: 1. Delete superuser.apk from your app folder in /system. 2. In Play store download superSU and install. It will ask you to update binaries. Do it and you should be golden.
**Delete files at your own risk** I used Root explorer and make sure you mount app folder as r/w before deleting and then put it back to normal when you're done.
failed... on galnet miui.. time to reinstall old SU
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Working great for me on the infuse and the nook. Both cm9. CF is a great dev.
Sent from my NookColor using Tapatalk 2
ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
Yes. Many Rom devs include SU.
Sent from my Emancipated Infuse having Communion.
ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).
I am not getting any source information of SuperSu. It seems closed source.
Entropy512 said:
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).
Click to expand...
Click to collapse
SuperSU is free on the market (there is also a $$ pro version). I'm seeing the same thing ndhanta is with the infusion kernel. There is a script called install_su.sh which does the old ef su install but I haven't been able to track down the parent script that calls it, or figure out where the $source and $dest variables are being set... I'm assuming it may be possible to stop the script from performing the su install by changing the modify date of the file specified in the $dest var.
Any chance a version of the 4.4.12 GB kernel might materialize that supports OC? (Or an update to the infusion kernel that removes the su installer?) This would help eliminate the issue...
I just Re-rooted my SGS2 and I now have SU and SuperSU ??
Im assuming that SuperSU was installed automatically with the root ROM??
I have puirchased the Pro Version of SU .. so is it safe to Remove SuperSU without messing something up ?
Yes no problem
Just update the binaries of SU.