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

Root M130 Rooted!

Unfortunately, I get the same results when bringing up a command window to reboot in recovery. Any clues or suggestions? Much appreciated and thanks in advance!
 
who444444 said:
I fat fingered a backed up file from my titanium app and deleted it by accident.
phone still works fine but I would still like a bu of the file and cant find it on my phone. can anyone help out?
it's called,
com.nec.android.mim

running android 2.3.3
build number for the missing file says
2010911.111646
thanks for reading,
dave
Click to expand...

Did you unlock the bootloader?. I get the same as you guys but the top left I have a menu with options.
I used m130 recovery thread to install the recovery and unlocked the bootloader
 
LimitedRelease said:
mr hippy,

Are you sure you unlocked the bootloader?
when I read that thread I was not convinced anyone had actually done so.
Click to expand...

I'm only going by the thread and what I did. I don't think this phone had a bootloader from what I read like normal androids. But after installing the recovery the Fastboot screen does have boot options unlike before but you can't access it unless you use adb or a quick boot app. Again unlike other droids, by holding the power button and volume key gets you into the typical bootloader.
 
Is there someone that can provided guidance on how to reboot my commando in recovery mode? It was suggested that I download Quick Boot (and I did) from the Google Play Store and that did not work. I also tried to reboot into recovery via a cmd window which produced the same results. Both attempts display a white triangle with an exclamation mark in the center of it, and below the triangle was a green bot. I had to pull the battery to reboot the device each time since the screen did not change. I'd appreciated any support that you can provided.

Regards,

mov
 
mov said:
Is there someone that can provided guidance on how to reboot my commando in recovery mode? It was suggested that I download Quick Boot (and I did) from the Google Play Store and that did not work. I also tried to reboot into recovery via a cmd window which produced the same results. Both attempts display a white triangle with an exclamation mark in the center of it, and below the triangle was a green bot. I had to pull the battery to reboot the device each time since the screen did not change. I'd appreciated any support that you can provided.

Regards,

mov
Click to expand...

Quick boot gets you to that screen with the triangle, but without the recovery installed you don't have the options. Use this thread to install it
http://androidforums.com/showthread.php?t=330813

All In One Recovery Thread

Search for m130.to find everything you need to be root and do what you want
 
Not a programmer here
Viewing both the original instructions at the top as well as Quick Working guide instructions giving a bit more detail down below:

Having issues locating the SU file on the SD card that I'm supposed to push to the System/Bin folder



ADB or root explorer to verify ownership and permissions of su? ..that one doesn't like me either

C771M130 2.3.3
 
I Google su android for the su binaries they are freely available from the official site.
Permissions. You can learn what they mean from Googleing Linux permissions. Look for the rwx 's in es you want to set the view to detailed list I believe
 
  • Regarding init.qcom.sdio.sh; this is the mobile data init script that checks for the WLAN (3G Data) card. It's only executed if data is on and WIFI is off. We know that if you boot the phone with WIFI on the script won't execute. My guess is if you then shut WIFI off and wait for your 3G data to connect, the script will then execute, although I haven't had time to try to verify this, yet.
  • Android is a Linux based operating system. Therefore it uses Linux rules. Linux text formatting uses a new line -> "\n" at the end of the line. Windows uses a new line and carriage return -> "\n\r". If you edit init.qcom.sdio.sh on a Windows box and then upload it to your phone, you will have corrupted the file and the init script will not execute. You must use an editor that can be configured for Unix type formatting, such as Eclipse or VI from within Cygwin, or edit the file while it's still on the phone using ES File Explorer or some such editing tool.
  • Regarding the placing of, order of, and spacing of the commands -> "chmod 0777 /system", etc.: each line is a separate shell command. Spacing between words, line order, and blank lines in between each command are irrelevant. You can put them in any order, have additional spaces, etc. And you can place them at the beginning, middle, or end of the file as long as they're after the first line of text, before the last line of text, and in this situation NOT in the middle of the case -> esac block! :mad: As long as you follow these rules, place the command in the correct order (chmod /system 0777 won't work), and have chmod all lower case, if the shell commands are not executing, you have a different problem.
  • As for saving the file multiple times in order to not load the .BAK file, I've never seen Linux try to execute a backup file. I've had trouble with this on Windows, but not Linux. However, going through the extra steps won't hurt anything if you do it properly, so do what makes your heart happy. ;)
  • It took me two days to get my Commando to root. I've owned several Linux servers for years, so I had no trouble changing directory permissions and uploading su. However, no matter what version of su I installed, when from either ADB or Terminal Emulator, when I did the command "su -" or 'su -c "cat init.qcom.sdio.sh"', there would be a long pause, then "Permission denied" or no response at all, including no root access. It wasn't until I installed all the files provided by Willster419 that I was able to get it to work. Apparently, (please correct me if I'm wrong here) unlike Linux where su works independent of any other process, on Android su works directly with and is co-dependent on superuser to request permission for root access. If you have the wrong su installed, or don't have superuser.apk installed, you won't get the GUI requesting your approval for root access. The request will time out and you'll get "Permission denied."
  • Using ES File Explorer to move su from /sdcard/download/ to /system/bin didn't work. ES File Explorer moved it to /system, and renamed su to "binsu". Consequently I opted to use "ADB push" to move it from C:\... to /system/bin.
  • A few have reported problems with WIFI after rooting their phone. The only way I can see that happening because of their attempt to root the phone would be if they accidentally edited init.qcom.wifi.sh after successfully rooting their phone. init.qcom.sdio.sh has nothing to do with WIFI.
  • After successfully rooting your phone, to reset permissions back to normal, change the lines:

    chmod 0777 /system
    chmod 0777 /system/bin

    to

    chmod 0755 /system
    chmod 0755 /system/bin

    and reboot your phone. Or as was pointed out you can enter the above commands one line at a time from within ADB or terminal emulator to accomplish the same thing. If you wish to keep these lines in init.qcom.sdio.sh for future use but you don't want them executed every time you boot the phone, comment them out by putting a "#" at the beginning of the line:

    # chmod 0755 /system
    # chmod 0755 /system/bin

    (The space after # is optional. I use it for easier reading)

    The only line I left uncommented is

    chmod 0777 /system/app

    Once you set permissions/ownership for a file/directory, it will remain that way permanently unless some other script does a check and changes it. I haven't had time to see if Android automatically resets directory permissions for /system/app to 0755. Once I finish the debloating process, I'll be resetting permissions for everything back to original.

My sincere thanks to everyone who did the leg work on this. Love the Commando, hate the bloatware.

This would be a great business phone if Android would have stuck with Linux user permissions instead of giving themselves root access and sticking us with Windows type "You're only allowed to click on the pretty picture" lunacy. Speaking from a business perspective where we have several hundred Android smart phones, Android is an administrative nightmare and a financial black hole. Out of the box security is set up so we have absolutely no control over what our employees do with the phones. Due to Android intentionally blocking us from installing anything that allows us to remotely monitor and control phone usage, we could have a terrorist cell using our phones and we wouldn't know it until the FBI or Homeland Security showed up. Rooting the phones and making the necessary changes will solve that problem. However, it could cost us a fortune if our carrier finds out and fines us on a per phone basis for doing so. As I said, Android is an administrative nightmare and a financial black hole.
 
this is very good information. very nice to see someone compile all the information into one post! good job!
there are only two things I must say about this however:
1. You can *copy* su from sdcard to system/bin. that is how i did my root. When I wrote the guide for this, I wrote it from a using only the phone standpoint.
2. the wifi problem does have to do with the init.qcom.sdio.sh file. I agree with removing the code that one inserts to gain root. In fact, I would just put the origional file back in. One thing that I tested that is correct is that the permissions for the file HAVE to be rwxrwxrwx. (0777) If they are not, the WiFi will not work!
Still, I like the idea of only rooting to remove bloatware. or even renaming them so they don't take up resources. If you want the custom recovery most of us keep talking about, you have to go to this thread:
http://androidforums.com/getitnowmarketing/330813-all-in-one-recovery-thread.html

anything to make the phone more enjoyable...
 
yea. you can download monkeytools ROM and extract the stuff you want, in your case like /system/app/dialer.apk and such
 
yeah that is fine too. just do a titanium backup of all your stuffs so you don't loose it because you have to do a factory reset.
 
I am trying to root my c771 M130. I have been having an issue with the rooting directions. When I go to add the following lines:

chmod 0777 /system
chmod 0777 /system/bin

and try to save it, I get a notice that says "Error occurred when trying to save the file. It will not be saved."

I checked the properties of the init.qcom.sdio.sh file and it says it is readable, writable, and not hidden. Any suggestions? I haven't seen anyone else with this issue yet.

Wifi is off too.
 
OHHH my FAVORITE reason! I noticed this too! this is because ES File Explorer updated to version 3.0 DOH!!!!!!! :(:( It no longer works!
I have two options for you, and others that are now having this problem:
option 1 (working top-down): download this file version. it is the version 2.6 that I used to originally root my phone with TommyTopDrive. DO NOT EVER UPDATE!!!
option 2 (working bottom-up): this option will also avoid the wifi problem and has a video tutorial if you ever become confused. Also it makes your phone recoverable if you ever wipe your system partition! no more bricked phones! Here is the origional text if you are interested:http://androidforums.com/commando-a...-make-your-phone-recoverable-system-wipe.html
the vid will be a little different in steps, but if you follow along, you should be fine:
How to fully root and foolproof your Casio C771 Commando - take three - YouTube
hope this helps
 
Willster419 said:
OHHH my FAVORITE reason! I noticed this too! this is because ES File Explorer updated to version 3.0 DOH!!!!!!! :(:( It no longer works!
I have two options for you, and others that are now having this problem:
option 1 (working top-down): download this file version. it is the version 2.6 that I used to originally root my phone with TommyTopDrive. DO NOT EVER UPDATE!!!
option 2 (working bottom-up): this option will also avoid the wifi problem and has a video tutorial if you ever become confused. Also it makes your phone recoverable if you ever wipe your system partition! no more bricked phones! Here is the origional text if you are interested:http://androidforums.com/commando-a...-make-your-phone-recoverable-system-wipe.html
the vid will be a little different in steps, but if you follow along, you should be fine:
How to fully root and foolproof your Casio C771 Commando - take three - YouTube
hope this helps
Click to expand...

Thanks for the help. I chose option 1. It worked like a charm once I had the correct version of ES File Explorer.

I have a couple follow-up questions though. Once I got it rooted, I installed the busybox and Superuser apps, and also Titanium Backup. I backed up the phone with Titanium Backup, then deleted most of the bloatware I didn't want using Titanium Backup (and also manually made backup copies of each application on my SD card beforehand). That cleared up a bunch of space, but now I have 4.3mb of busybox, and 2.42mb of superuser taking up space on my phone which don't allow movement to the SD card. I want to squeeze out every bit of space I can. Do I really need these apps on the phone?

On a semi-related question, I use the MLB At Bat app to listen to my favorite baseball team's radio feed. The problem is the app installs at 32.4MB!!! It has widgets, so it can't be moved to the SD card. Is there any "rooted phone voodoo" I can do to force the app to the SD card? I don't really care if the widget works or not.
 
glad to hear your rooted. thats great news. as for your questions...
there are three main partitions on the phone. The System partition, the data partition, and the cache partition. And, if you have one, the sd card "partition". By what you are saying, my guess is that you want to move and or un-install the busybox and super applications, from your data partition, where they chill and take up space. Here is what I recommend:
1. The SuperUser app is required. Moving it to the SD card or un-installing it may result in a loss of root:(. Instead, move the apk to the system partition, where you just freed up a bunch of room. ;)

2. As for the busybox app, that has no affiliation with the busybox binaries itself, other than installing it. That can be moved to the SD card.

3. For the MLB app, you have two options. You could move it to the system partition, where the widgets will still work, but only if the system partition has enough room. The other option would be to move it to the SD card, and loose the widgets. Personally, I had lost many widgets when I placed apps on the SD card, but if you fine with just a launcher icon, that will stick on the home screen. Also for reference, ANY app that is on the data partition CAN be moved to the SD card when you are rooted. It's just the question of widgets. So yes, that "voodoo" is possible.

There is even more voodoo called sd-ext, where you can get a second partition on your sdcard, so you can have them there and have widgets (i think). But its a little complicated, and really does not give much vs. just tapping the "move to sdcard" button, so that is up to you as well.

hope this helps...anything to make the phone more enjoyable...
 
I tried doing the "bottom-up" method and when I go to install the drivers it says that they are already installed, but I do not have an "Android Phone" category in my device manager. It just shows up in the "Universal Serial Bus controllers" section. I tried loading the bootloader anyway, but it said "device not found."

I could try the first option, but how do I install an apk from my computer? Totally new at this rooting thing (first smart phone).

EDIT: Never mind. After three hours of sleep, I tried it again and I AM ROOTED!
 
Bottom up. For some reason when I rebooted my phone, it didn't remember that the USB debug was selected. After I selected it again, the phone showed up properly. After that, it was a piece of cake.

So far I've deleted about 20-30 aps and noticed a significant improvement in response time. Got any tips for overclocking? How about installing a newer version of Android (will anything after Gingerbread work on the Commando?)?
 
ok good to know. yeah the usb drivers are a fun one. as for overclocking, there is no current way to make the cpu faster that what it is now, due the kernel being different from everyone else:( however, you can improve the phone using a modifier called the v6 supercharger. it changes some ram settings and makes the commando a little more responsive.

installing a newer os? ha! i personally am happy this thing is even rootable and system-safe, never mind the os's problems! (not to discourage anyone currently working on anything like that...just seems very..."unlikely")

the only thing i can suggest is onandorid, an "online" (meaning powered on, not in recovery mode) android backup script, and pimp my ROM, if you want to fiddle with some custom settings and such.
 
You must log in or register to reply here.
Back
Top Bottom