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

Root M130 Rooted!

Think I almost caused some issue with mine. Was playing around with init.d & A2SD and everything was still working fine (though I can't get A2SD to work properly the phone wasn't freaking out).

But then I wake up this morning and she is sitting there at the Initializing... section of boot up. Pull the battery, power on, same thing. Remove the SD card, power on, same thing.

Plug it into the PC and start up ADB, adb reboot recovery, restore NAND and its working again.

Had myself quite scared there for a second...

But now I need to figure out exactly what I did and how to avoid doing it...though I seriously want A2SD to operate on here.

It's nice to have that back up.... You never know.
 
I think I managed to remove root access or something during the NAND restore or something else.

First noticed that some things were performing slower than even stock (yet it boots in about half the time).

Then I opened Busybox only for it to tell me there is a problem. Try uninstalling and reinstalling, allowing a new SU permission. Super User never asked, and in the program Busybox was allowed. Ran through these steps a few times to no change.

Root Checker confirms it isnt rooted. strange.

edit: must've been from when I was in Recovery. Went to Development and chose Unguarded SU, everything is honky dory again.

edit2: now the Wifi reports: Error

facepalm.gif


Restored original NAND and it works fine. Stole the .sh from /system/etc and just transferred it to the SD, restored the NAND that is 'broken' and replaced it but it had no effect.

This did the trick though:

change the permission /system/etc/init.qcom.sdio.sh to rwxrwxrwx [chmod 0777] to fix your wifi
 
i recomend using this Link2SD
Quite simple and no need advanced configuration skill.
Just create 2nd partition from sdcard [prefer ext4 - do this from recovery mode] , no need to create swap partition , current C771 kernel have no support for it.
It saves a lot internal storage space and have the feature to freeze app for free.
 
I'm setting up to do this. I downloaded the commando zip file to my SD card and opened so I hope there will no need for a PC or ADB. I'm more of a GUI and not a command line interface type of brain and I'm a little nervous. Is there a way to back up the system as it is now in case things get out of hand?
 
You'll want to install the GNM Recovery ASAP & make a NAND backup.

This will require some ADB but it's only 2-3 lines & very simple.
 
yeah i agree with rasta, chmod the exploit file to 0777 and the wifi works fine. this is with my updated su and busybox. also, as stupid as it sounds, if you wifi breaks, just reboot your phone is an option. it fixes the wifi problem every time. Personally, i havn't had that problem since January, so idk any new info on it.
just putting my two bits in.
Thank you all for the thanks you give me :P
 
I thought I was finally rooted. checking with adb verifies rwsr-sr-x on the "su" row. BUT Root Checker says "Sorry! This device does not have proper root access." what would fool the su into thinking I have access?
 
I thought I was finally rooted. checking with adb verifies rwsr-sr-x on the "su" row. BUT Root Checker says "Sorry! This device does not have proper root access." what would fool the su into thinking I have access?
Did you install superuser and busybox?
 
I have been checking around on these forums since I've owned my C771 every couple months, and was psyched to see this thread, I am now rooted!! I've had it for over two years, I'm not going to use my upgrade now that its rooted! This thing has been through hell, fallen off scaffolds onto concrete, dropped in puddles, been in the pool, slid across the concrete many many times, to list a few. I wasn't looking forward to getting a newer, 'rootable' phone but now I don't need to worry about that, thanks again!!
 
I downloaded SuperSU and Busy box from market. I open supersu and it says the binaries need to be updated and I do the normal installation. Failed.
The su the you can flash the one from zergRush through the recovery or on superuser check the box to stop checking out don't push the new one adb you'll loose the ownership and permissions then your screwed
 
The su the you can flash the one from zergRush through the recovery or on superuser check the box to stop checking out don't push the new one adb you'll loose the ownership and permissions then your screwed

I didn't push su, copied from the sd
 
Do I need to do any back-tracking to a certain point in the procedure or, at the point I am now, push SU with adb? Others had done this totally on the phone, why did it not work in my case?
 
Do I need to do any back-tracking to a certain point in the procedure or, at the point I am now, push SU with adb? Others had done this totally on the phone, why did it not work in my case?
Flash through recovery
I did say don't push the su then you said you copied it from the sdcard I said that was not good.. Did you see the option in superuser to turn off that check binary? I the older one works as well... I'm telling you from experience.. I pushed the new one because of the same message you got I screwed the root. And could not set the permissions back.. Google it a little before it happens to you..
 
I'm not yet rooted. Are you saying I should recover to stock and start over? Don't know how to "flash to recovery"

I wish I had been here when this first got started
 
I'm not yet rooted. Are you saying I should recover to stock and start over? Don't know how to "flash to recovery"

I wish I had been here when this first got started
Your not rooted in so what's the issue what did you doing.. I'm lost now
 
It seemed like everything was working. I made the first 2 text edits a couple of times until I got it right. The su failed to copy until I got it right. Then miss typed the second set of text and the permissions for su was "-rw------3565------root" but finally got it right and permissions read "rwsr-sr-x". So installed superSU and busy box along with root checker. I just don't know what missed. I think I've read this thread 4 times. Any ideas?
 
It seemed like everything was working. I made the first 2 text edits a couple of times until I got it right. The su failed to copy until I got it right. Then miss typed the second set of text and the permissions for su was "-rw------3565------root" but finally got it right and permissions read "rwsr-sr-x". So installed superSU and busy box along with root checker. I just don't know what missed. I think I've read this thread 4 times. Any ideas?

Did you reset system and bin back to 755 using the same file to change them to full permissions after adding the su? then make sure you added the su to system/bin/ with ownership and group is root root. Then removed all added lines with in that file.
If the su is in system/bin/
With correct permissions and owner /group the your rooted.
 
I downloaded SuperSU and Busy box from market. I open supersu and it says the binaries need to be updated and I do the normal installation. Failed.

I had same problem,this is what I did.
Checked all file permissions and they were correct.I had installed supersu wouldn't take update,so I replaced it with superuser.Superuser took update now rooted,yea.
That worked for me.
 
I had same problem,this is what I did.
Checked all file permissions and they were correct.I had installed supersu wouldn't take update,so I replaced it with superuser.Superuser took update now rooted,yea.
That worked for me.

I'll give that a try. Should I remove SuperSU first?
 
Back
Top Bottom