• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root so any luck on custom roms?

paxchristos, if you can get this puppy to overclock i'll love you forever

From what I've learned, so far that's the easiest part... if the bootloader can be unlocked (in fact if the bootloader can be unlocked, gaining root is 1,000,000x easier.)
 
Sick. I used to have a D1 and loved the flexibility, especially lobed liquid's work. Got recovery working on my commando, but no where near smart enough to dev a rom on my own.
 
Yup, I'm starting the development of a Casio Commando ROM; just as soon as I learn the code and what-not. Even then, it might take me a while (mostly because I've got school, that site is the school journalism page :D) So like I said on my article, just be a little patient!
 
Welcome, we are glad you are here. Getitnowmarketing has provided us will a working recovery, Paxchristos helped out with rooting 2.3.3 when nothing else would work, Rafeal and a few others have a list of apps that are safe to remove. Lots of eager testers...

A few are linux/android tech savvy, the rest of us can follow written instructions pretty well.
 
Welcome to the forum! glad someone else likes messing around with their gadgets as much as me haha, i just dont have the time to learn how to write roms, If there is anything you need from froyo, i'm stuck with 2.2.1 for now. Or if you need a tester, just ask!
 
In case anybody's curious, the easiest way to root a phone is to change the ramdisk (I just got the proper tools to unpack the commandos ramdisk) and goto default.prop and change ro.secure=1 to ro.secure=0 ... now all that needs to happen is a little change in init.rc, and I can put an autoroot script in :p

Also, the /kernel source/arch/arm/mach-msm/acpuclock-7x30.c is where you have the ability to overclock your phone (you have to include speed/voltage (another thing i'll be working on))
 
so even with the newest update that is coming out, root will be possible even if they fix the "security issue"?

this next update might have one or two things i might like.
 
Just digging around, I found how to set the max/min CPU frequencies; they're located at /sys/devices/system/cpu0/cpufreq. Just be careful if they work for anything. You also have to set the permissions. They also like reseting at boot; looked into it, looks like /system/etc/init.qcom.post_boot.sh has some to do with it.
 
Just digging around, I found how to set the max/min CPU frequencies; they're located at /sys/devices/system/cpu0/cpufreq. Just be careful if they work for anything. You also have to set the permissions.

That's actually on the device, correct?

If you change the cpufreq tables in the source code for the kernel, you can get your device to overclock (persistantly)

It's going to take a little testing, but I now have a commando that I can play around with (unactivated/not on a plan) so I can start futzing around

What i've learned:
adb reboot fastboot -- skips going to fastboot, and instead goes to normal boot
adb reboot bootloader -- hangs at the bootloader page. I'm going to do a logcat of this (adb - d logcat) and see if there's anything useable there
 
well keep working! *cracking of the whip*

Yes sir, I'll try harder :p

(*Disclaimer! No guarantees, just looking)
Interesting side note, the HTC Evo 4g has the same chipset as the commando, and one of their dev's has overclocked the phone to 1.8GHz (I plan on stealing his cpu table once I figure out how to get the commando into fastboot mode...)
also, (warning this WILL void your warranty) has anybody been ballsy enough to take the sticker off under the battery in back and see if there's a test point hiding there?
(that's my plan for tomorrow... after I fix my computer..)
 
i'm working off the Mugen battery... I get an extra 3 hours out of my phone before it's dead. (before, dead at noon. now dead at 3. I get off work at 5)

and i'm pretty sure everyone in the all things root forum had voided their warranty.
 
Back
Top Bottom