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

Root Latest twitter feed Loki

This is so unreal... I must be imagining this... uploadfromtaptalk1373514471806.jpg
 
Upvote 0
Let's not get too far ahead.. Honestly I'd sit back and wait for the experts to do this and put together an easy tutorial. We still have to have a custom recovery built... You can then thank them and buy them a beverage of their choice.. But for now be sure to thank Mr. Rosenberg here's a link to his paypal

http://goo.gl/zBGb0
 
  • Like
Reactions: Scorpion7867
Upvote 0
Let's not get too far ahead.. Honestly I'd sit back and wait for the experts to do this and put together an easy tutorial. We still have to have a custom recovery built... You can then thank them and buy them a beverage of their choice.. But for now be sure to thank Mr. Rosenberg here's a link to his paypal

http://goo.gl/zBGb0

True. But im trying to learn as i go lol. I got as far as loki patch. But it no worky. I dont think im doing it right?
 
Upvote 0
I got 1.44 on my card. Damn straight it's going to him!

EDIT: No, but I agree with you on that point. Let the experts do what they do best. You should only do this yourself if you know and accept the risks and wanna get your feet wet.

Knowing me, I'm still gonna try, lol.

Im thinking the files inside the "bin" folder are moved to /system/bin. And then the commands will work.
Trying it now!

Edit: tried it...and i failed. Multiple times. But trying again

What i got by the way...

app_27@android:/ $ loki_patch-linux-arm
Usage: loki_patch-linux-arm [boot|recovery] [aboot.img] [in.img] [out.lok]
x-arm recovery aboot.img cwm.img cwm.lok <
[+] loki_patch v1.4
[-] Failed to open aboot.img for reading.
1|app_27@android:/ $
 
Upvote 0
True. But im trying to learn as i go lol. I got as far as loki patch. But it no worky. I dont think im doing it right?

It was stated to be device specific. Unless I'm missing something? I see no Motion file on the github. I only see the spirit, and op g. From the readme on the git.
"loki_flash" is a sample utility that can be used to flash a .lok image to an
actual device. It will verify that the provided .lok image is safe to flash for
a given target, and then perform the flashing if validation is successful. It
is also possible to simply use "dd" to flash a .lok image directly to the boot
or recovery partition, but using loki_flash is recommended in order to validate
that the .lok matches the target device."
So it looks for the target aka the specific phone.
So unless you have the file for the motion it won't work.

I see where it says its supported now, but does that mean he's got it up? Even if you got something to work we have no custom recovery besides the one we have, or kernel so why even risk anything at this point till we have these made?
 
Upvote 0
Im thinking the files inside the "bin" folder are moved to /system/bin. And then the commands will work.
Trying it now!

Edit: tried it...and i failed. Multiple times. But trying again

What i got by the way...

app_27@android:/ $ loki_patch-linux-arm
Usage: loki_patch-linux-arm [boot|recovery] [aboot.img] [in.img] [out.lok]
x-arm recovery aboot.img cwm.img cwm.lok <
[+] loki_patch v1.4
[-] Failed to open aboot.img for reading.
1|app_27@android:/ $

what firmware are you on?? it looks like it might require version F.


found this
.vendor = "MetroPCS",
.device = "LG Motion",
.build = "MS77010f_01",
 
Upvote 0
It was stated to be device specific. Unless I'm missing something? I see no Motion file on the github. I only see the spirit, and op g. From the readme on the git.
"loki_flash" is a sample utility that can be used to flash a .lok image to an
actual device. It will verify that the provided .lok image is safe to flash for
a given target, and then perform the flashing if validation is successful. It
is also possible to simply use "dd" to flash a .lok image directly to the boot
or recovery partition, but using loki_flash is recommended in order to validate
that the .lok matches the target device."
So it looks for the target aka the specific phone.
So unless you have the file for the motion it won't work.

I see where it says its supported now, but does that mean he's got it up? Even if you got something to work we have no custom recovery besides the one we have, or kernel so why even risk anything at this point till we have these made?

To learn. Never hurts to try.

Plus i have a spare motion so im testing it on that one...
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones