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
Related
i have rooted my xoom properly and i have my xoom on brd 1.6 ghz riptide kernel..but i have problems using titanium backup...whenever i install it, it says root priveleges not acquired....but other apps like screenshot er, setcpu work perfectly...what to do?????
Install a newer busybox, like 1.8 with stericsons busybox installer from the market
I had to install an app called busybox installer. I also had to go into SU and remove busybox, then it asked for root priv's again, Say yes then everything should work.
Have anyone tryed to update busybox to 1.18?
I founded it with such paths: /system/busybox /system/xbin/busybox.
But when i updated that files with 1.18 i get motologo loop.
Restored succefuly with OR.
Maybe someone knew why that happened?
fjfalcon said:
Have anyone tryed to update busybox to 1.18?
I founded it with such paths: /system/busybox /system/xbin/busybox.
But when i updated that files with 1.18 i get motologo loop.
Restored succefuly with OR.
Maybe someone knew why that happened?
Click to expand...
Click to collapse
I have expirianced this problem for some days, but I toth it's me doing something wrong or Khal ROM doesn't supports it. And I'm pretty sure it's form Busybox indeed.
Same here......even I got stuck in a bootloop when I tried that......had to use rsd lite to flash the stock rom.....couldn't use OR
Sent from my XT720 using XDA App
So.... anybody tryed older Busybox version? Problem still appear? I just optimized my ROM and I don't wanna go true all "tweaking" again.
Here is a link for 3.4.1 (1.18.4 I think) for anyone who is brave enogh http://www.mobileboxs.info/android-apps/busybox-v3-4-1/
And here is even older 1.17.1 http://www.speedyshare.com/files/23737359/Busybox_1.17.1.apk
I had tried 1.17.1 earlier....didn't work..got stuck at bootloop!
Sent from my XT720 using XDA App
vari9 said:
I had tried 1.17.1 earlier....didn't work..got stuck at bootloop!
Sent from my XT720 using XDA App
Click to expand...
Click to collapse
Suffering succotash. Then it's most likely from Khal's ROM.
I know it's of little help, but I just downloaded and used the latest version of that app to update /system/xbin/busybox on an unreleased ROM based on Dexter's 1.3 and I had no trouble.
I do know it is extremely important for the boot scripts we've been using on XT720 to have /system/xbin/busybox. If you move busybox to /system/bin/busybox you will bootloop. You should be able to get into openrecovery (volume up while powering on) and use adb or apply the update here http://forum.xda-developers.com/showpost.php?p=11695842&postcount=1314 to recover. Possibly you'll still have to go fix the symbolic links using adb. I think it's pretty stupid that the app deletes the other ones without replacing them with symbolic links. That app also didn't update all busybox applet symbolic links, either. Frankly, I'm not too impressed by that app.
Mioze7Ae said:
I do know it is extremely important for the boot scripts we've been using on XT720 to have /system/xbin/busybox.
Click to expand...
Click to collapse
I did installed it in xbin, but still bootlooping. I'm not sure what the whole point of this app is, beside it allows CacheMate to do it's job. If anyone can explain?
eSu.Matix said:
I did installed it in xbin, but still bootlooping. I'm not sure what the whole point of this app is, beside it allows CacheMate to do it's job. If anyone can explain?
Click to expand...
Click to collapse
Most (if not all) custom ROMs have busybox already. The app is probably quite helpful on rooted, stock ROMs that wouldn't have busybox otherwise. If you're on a custom ROM all it does is update the existing busybox. When cachemate says it requires busybox, it's refering to the executable, not the updater app from the market.
Mioze7Ae said:
Most (if not all) custom ROMs have busybox already. The app is probably quite helpful on rooted, stock ROMs that wouldn't have busybox otherwise. If you're on a custom ROM all it does is update the existing busybox. When cachemate says it requires busybox, it's refering to the executable, not the updater app from the market.
Click to expand...
Click to collapse
So you mean I have Busybox on my Khal's ROM and I don't need to update it. Thanks alot.
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!
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.
Hello,
I used "OTA RootKeeper" too "save" my root, and then updated my phone.
I had to re root manually, and since this moment when I try to install busybox or to update su binary my phone reboots.
I tried to manually remove the root (by removing the Superuser.apk and su files), to wipe /data, dalvik_cache, cache etc...
Nothing seems to solve the problem
Does anyone have an idea?
Thanks for your answers!
(Sorry for my English I'm French )
Yep, the jb update has a kernel that write protects /system, at least for the One x and Droid DNA
Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....
RootJunkie said:
Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....
Click to expand...
Click to collapse
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot
absolutelygrim said:
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot
Click to expand...
Click to collapse
What to do?
Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....
mihaiolimpiu said:
Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....
Click to expand...
Click to collapse
System is write protected.. due to the kernel, you need s-off or a different kernel, and seeing as there is no kernel source, ICS or aosp are your options. Try making a folder in /system, it should be gone after a reboot
But the files I create from TWRP recovery aren't removed after a reboot. The Superuser.apk is still here after a reboot.
So it seems that I can write to /system from recovery.
Do you know if there's a flashable zip for busybox?
I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
Su + Busybox
WAY LATER EDIT:
System Partition RW on JB stock roms via kernel module
mihaiolimpiu said:
I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
http://forum.xda-developers.com/showpost.php?p=35907661&postcount=1928
Click to expand...
Click to collapse
I just tested it and everything I used before on my phone is working again and no more unwanted reboot
Thanks a lot !
I sent a PM to TeHashX, he was asking for review on his work, and also thanked him... His work could benefit others... so make his post more visible!
Remember, that because of the kernel, AdBlock still doesn't work, basically every program that modifies /system works but only apparently. I could use Titanium very well, only Integrate in Rom option doesn't work so take care using "ROOT" on HOS JB.