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

Root M130 Rooted!

I've asked this in GNM thread but it's a relative ghost town these days.

What does the below sentence mean and how do I do it?
"Download your device specific recovery and check md5sum for a match before flashing."

I've placed the recovery folder on the root of the sd card and the device img in that folder as per the automatic script instructions. I've decided to do the it the manual way which to require placing the recovery img outside of the folder. Why is that?
 
MD5 Checksums are a way to insure you've got the proper & legit file your after. Desktop/laptops need to special software, droid might too.
 
So does anyone do it? Prolly not.

So the aforementioned file would look like this in the AiOR, "old manual way" (bold being my changes):

$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# flash_image recovery /sdcard/recovery-ra-commando-3.06-gnm.img
 
Commando C771M130

I turned off wi-fi and followed the directions in post #125 to the letter. My commando is now rooted flawlessly!

Simple, quick, and easy.

Thanks to all you guys who figured this one out.
 
So, for all of you who want to root, this is a quick 10-step beta guide. Use at your own risk, im not responsible, etc.

1. Install es file explorer.
2. use it to go to /system/etc/init.qcom.sdio.sh
3. long press, open as text, use es note editor.
4. (The follwoing some quoted parts are copied from TommyTopDrive's posts. His work, not mine) Navagate to, "the very bottom (just above "exit 0")" and, add the following:

chmod 0777 /system
chmod 0777 /system/bin

5. Save the file. Then repeat step 3. and add a 1 after the "#!/system/bin/sh" and save. Then repeat step 3 again and remove the 1. The reason you do this is because, "it makes a backup and might try to load the backup."
6. restart your phone.
7. Push (or copy from sd card) the su bianary file to /system/bin
8. do steps 2 and 3, then below the code you put in earlier, put in, "

chown root.root /system/bin/su
chmod 06755 /system/bin/su

9."reboot again and verify by adb from a command prompt that su is owned by root and is rwsr-sr-x by doing the following (press return after each line):

adb shell
cd /system/bin
ls -l

10. "install superuser.apk and install busybox...oh, and that means your rooted." :)

And then your all set! You welcome to all!:)

I did all of this and it seemed to work. I was able to use ES file explorer to uninstall a lot of bloatware, which for now anyway is my reasoning for rooting the phone in the first place. Thank you for all the help. I am however a little baffled. I noticed that when I uninstall an applet ES file explorer saves a backup to "/sdcard/backup" I think this is good because If i remove something I shouldn't I can restore it easily enough. I'm assuming also that "/sdcard/" is a folder on the system where my SD card is mounted. However, when i removed items when i go into "settings->manage applications" applet no free space appears to be acquired. I constantly have the "phone has limited free space" msg in my notifier. Also, a bummer. Is something not reporting the free space right? I have noticed the phone altogether running faster and several apps that couldn't update before due to space constraints are updating error free. I am however leery of running out of space again which is, again, why I did this in the first place. Any insist anyone could give me would be great.

Tim
 
It was suggested by the OP to remove the lines add to the " /system/etc/init.qcom.sdio.sh" file and return the original permissions. Does it automatically do that when you remove the lines or something I do with ES Explorer?
 
It shouldn't do it automatically, especially as the steps in the op require adding & removing the 1,to create a backup file with the same line.

I would make sure to remove it though, I kept losing root as it'd pull the back up with only the first two lines, something would freak & su would end up rwx-rwx-rwx.
 
Has anyone tried using a pc boot into recovery mode and push adb with the chmod exploit left in? If so, we can start looking at custom roms.
 
I did all of this and it seemed to work. I was able to use ES file explorer to uninstall a lot of bloatware, which for now anyway is my reasoning for rooting the phone in the first place. Thank you for all the help. I am however a little baffled. I noticed that when I uninstall an applet ES file explorer saves a backup to "/sdcard/backup" I think this is good because If i remove something I shouldn't I can restore it easily enough. I'm assuming also that "/sdcard/" is a folder on the system where my SD card is mounted. However, when i removed items when i go into "settings->manage applications" applet no free space appears to be acquired. I constantly have the "phone has limited free space" msg in my notifier. Also, a bummer. Is something not reporting the free space right? I have noticed the phone altogether running faster and several apps that couldn't update before due to space constraints are updating error free. I am however leery of running out of space again which is, again, why I did this in the first place. Any insist anyone could give me would be great.

Tim

Using es explorer to delete apps is not wise. Most likely why the space is no freeing up they are not un installed. Back the apps with titanium and uninstall with root app delete. Find it for free @ Google play store. Good luck
 
I would use adb to install su, however, I would install superuser.apk and busybox installer from the play store. I would also after rooted remove the chmods and chown from the file. I would also change the permissions for the /system and /system/bin back to there originals.

I understand how to remove the lines but how do I change the permissions for /system and /system/bin back?
 
I remember adding the 0777 in the init.qcom.sdio.sh file when I started the root process. Once the lines are removed, where does the 0755 go?

Sorry for such a noob question.
 
I remember adding the 0777 in the init.qcom.sdio.sh file when I started the root process. Once the lines are removed, where does the 0755 go?

Sorry for such a noob question.

There's no need to modify the script again.It has a chance to break your wifi configuration.
Once you have root,you can change permission via ADB or terminal emulator on ur device.
Here's some example :
" su -c chmod 775 /system " and
" su -c chmod 775 /system/bin "
All that without quotation mark.
The best suggestion i can give after root,would be installing GNM Recovery then do Nandroid backup.
 
Has anyone tried using a pc boot into recovery mode and push adb with the chmod exploit left in? If so, we can start looking at custom roms.


Bootloader and Fastboot mode locked by default there's no trick to unlock it yet. The only way to Install a new rom would be from Nandroid restore.and currently there's no one to create Custom ROM.




I did all of this and it seemed to work. I was able to use ES file explorer to uninstall a lot of bloatware, which for now anyway is my reasoning for rooting the phone in the first place. Thank you for all the help. I am however a little baffled. I noticed that when I uninstall an applet ES file explorer saves a backup to "/sdcard/backup" I think this is good because If i remove something I shouldn't I can restore it easily enough. I'm assuming also that "/sdcard/" is a folder on the system where my SD card is mounted. However, when i removed items when i go into "settings->manage applications" applet no free space appears to be acquired. I constantly have the "phone has limited free space" msg in my notifier. Also, a bummer. Is something not reporting the free space right? I have noticed the phone altogether running faster and several apps that couldn't update before due to space constraints are updating error free. I am however leery of running out of space again which is, again, why I did this in the first place. Any insist anyone could give me would be great.

Tim

You can use Link2sd to get more space,it creates links from app folder to sd-ext (sd card 2nd partition),which means you should 1st create 2nd partition from sd-card (you can do it easily from GNM Recovery or using minitool partition wizard with your sd-card inserted to your PC).
This method gave me a lot of free internal space.
I bet your internal has too much app cache need to be clean up.
 
There's no need to modify the script again.It has a chance to break your wifi configuration.
Once you have root,you can change permission via ADB or terminal emulator on ur device.
Here's some example :
" su -c chmod 775 /system " and
" su -c chmod 775 /system/bin "
All that without quotation mark.
The best suggestion i can give after root,would be installing GNM Recovery then do Nandroid backup.

I'm doing the GNM/Nandroid today. I just wanted to clean up first.
 
I typed in the in-device emulator:
$ su
#su -c chmod 775 /system

and got:

permission denied

Apparently I don't have permission to change permissions.
 
hey guys there is a way to flash new roms. you haft to have GNM recovery. a nandroid is a back up of your current rom. i am working on a custom rom right know. that can be flashed with Gnm clockworkmod recovery. i have flashed some of my themes and it works. i also have a stock rom posted already. if any one has question about this just post in my thread and will answer. the best i can. if i have time i will post a how to. on flashing and clockworkmod too.
 
I remember adding the 0777 in the init.qcom.sdio.sh file when I started the root process. Once the lines are removed, where does the 0755 go?

Sorry for such a noob question.

The first two lines to make system and bin 0777 just keep those lines before removing them and change 777 to 755 then reboot then remove the edit simple.
 
I typed in the in-device emulator:
$ su
#su -c chmod 775 /system

and got:

permission denied

Apparently I don't have permission to change permissions.

When you got # it means you have root access.
The command should be this :
# chmod 775 /system
Or :
$ su -c chmod 775 /system ; do this command only if you're still in $ (user mode)
 
hey guys there is a way to flash new roms. you haft to have GNM recovery. a nandroid is a back up of your current rom. i am working on a custom rom right know. that can be flashed with Gnm clockworkmod recovery. i have flashed some of my themes and it works. i also have a stock rom posted already. if any one has question about this just post in my thread and will answer. the best i can. if i have time i will post a how to. on flashing and clockworkmod too.

I think the GNM Recovery based on Amon-Ra recovery for HTC devices.
But that's great work,you have many thanks from C771 Calculator user here and might be the entire world. :D
 
hey your on the money it is based part on htc devices. the casio system is close to the way htc system is but there are a few little differences. But clockworkmod recovery for any device works about the same. I was just saying that a nandroid backup is just that it backs up your current system. it is great if your going to try to flash something. and you have a problem you can restore your phone. I have posted a great guide from team venum. about cwm and how it works. it seems people are scared or have no knowledge about flashing or using cwm. my personal phone is a epic 4g touch. have been themeing and modding for a little bit know. so when I got this phone from work and saw that it had little dev support. I figured I would do what I could to help. A big thanks to tommytopdrive for root and all that helped. I was working on it. But he beat me to the punch lol. people don't be shy it you are wanting to learn or have any questions I am on here a little bit almost every day. and will answer any questions that I can. thanks for the support.
 
I'm doing the GNM recovery using the CP terminal on the phone. I get hung at:

mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

Say's: "failed on: system/etc/install-recovery.sh
no such file or directory"

I checked and "install-recovery.sh.bak" is in system/etc.

permissioned have been returned to 755, I believe.

any thoughts?
 
Back
Top Bottom