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

Root M150 update

Any chances get M140 or M150 to device out of Verizon network? At other providers InnoPath dosn't work. I can install update only by recovery.

P.S. I'm from Uzbekistan exUSSR Republic. Sorry for my bad English.
 
Yes I can. I will work on it soon. I updated my phones to m140 from the update anyway, so I say with confidence that is is possible.
 
Any chances get M140 or M150 to device out of Verizon network? At other providers InnoPath dosn't work. I can install update only by recovery.

P.S. I'm from Uzbekistan exUSSR Republic. Sorry for my bad English.

In my Casio auto-root plus, I have an option to manually install an inopath update. Please keep in mind that it requires root, and busybox is recommended. Both of those you can install from the kit.

The kit is on my google drive here.

If you are only able to update from the phone and/or dont have a windows pc with adb drivers, let me know and I will help set you up to update from just the phone.
Willster419
 
I have:
1. Custom recovery
2. Root
3. Busybox
4. Windows 7 PC with adb installed and little adb experience
5. My phone is debloated.

Can i install over InnoPath to debloated phone 2 bin files from your google drive?
 
Yes, however:
You must install the stock M130 ROM. When the update works on the phone, it "inserts" its patches on each file from point a to point b. If it cant, like the file is not there, or has been modified, it will quit. After you install the rom, you can update to M140, then M150. Make sure you read all directions in the toolkit, and remember to change out the boot and recovery images in the stockImages folder for each upgrade.
If you need help, just reply. If you want to view the script, you can right click edit the runme.bat file.
 
What is the status on rooting M150? I just got the phone and unknowingly updated to M150, and am hesitant to move forward.

Thanks!
 
So if I have a non-rooted commando with m150 I can use your rootkit 1.5 to root my commando?


So far I have:

1. put the m150 modded boot.img into the bootimage folder as boot.img

2. put the m150 stock boot.img into the stockimage folder as boot.img

3. put the m150 stock recovery.img into the recoveryimage folder as recovery.img


Is there anything else I need to do?

Also, what is he difference between rooting top-down as opposed to rooting bottom-up? And do I need my SD card mounted or unmounted?
 
So if I have a non-rooted commando with m150 I can use your rootkit 1.5 to root my commando?


So far I have:

1. put the m150 modded boot.img into the bootimage folder as boot.img

2. put the m150 stock boot.img into the stockimage folder as boot.img

3. put the m150 stock recovery.img into the recoveryimage folder as recovery.img


Is there anything else I need to do?

Also, what is he difference between rooting top-down as opposed to rooting bottom-up? And do I need my SD card mounted or unmounted?

yes you can root with the kit. However:
you need to put the m150 stock recovery image in with the stock boot image into the stockimage folder. the gnm custom recovery goes into the recoveryimage folder.

rooting top down is more safe (less boot images and recovery images to deal with), but it does NOT protect your phone from bricking, and has a chance to break your wifi, but it is fixable.

rooting bottom up REQUIRES the correct images in the correct folders, but if done right, protects your phone from bricking and does not touch anything about your wifi.

I give you both options in my script.
 
So now I have:

1. put the m150 modded boot.img into the bootimage folder as boot.img

2. put the m150 stock boot.img into the stockimage folder as boot.img and put the m150 stock recovery.img into the stockimage folder as recovery.img

3. replaced the stock recovery.img with the gnm recovery.img in the recoveryimage folder

However, I run the runme.bat, press 2, enter, and at first it said something about daemon not running and starting the port then it said "currently not working..." and it went back to the beginning before i even typed the 2 in. Now all it does is say "not currently working..." then it goes back to the start before i even put the 2 in.

Oh and usb debugging is on, and set to stay awake, and I have it unlocked
 
casio auto-root kit + 1.5

looks like the daemon and port starting message is associated with starting adb.exe. I went to task manager and stopped adb.exe then ran the runme.bat again and the daemon message came up again but the same thing happened...the runme.bat reverted back to the start.
 
ah crap my bad i forget to remove a couple lines. I'm fixing that right now and verifying it works against 2 commands in different states.
 
casio auto-root kit + 1.5

looks like the daemon and port starting message is associated with starting adb.exe. I went to task manager and stopped adb.exe then ran the runme.bat again and the daemon message came up again but the same thing happened...the runme.bat reverted back to the start.

that daemon message is good it just means that its starting the adb listening/sending server for the phone. it has no impact on anything.
 
so the runme.bat got to rooting then went back to the start again. not sure if i'm rooted. checking now. i think my phone tried to call someone from my call log and ended it quickly somewhere in the process too...

root checker says i have root
 
great way to check:
install the root file manager (old version es file explorer) from the script, then settings->rootsettings->enable root explorer.
 
Back
Top Bottom