Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working on X86 Android Tablets #14

Open
switchgott opened this issue Jul 31, 2013 · 16 comments
Open

Not working on X86 Android Tablets #14

switchgott opened this issue Jul 31, 2013 · 16 comments

Comments

@switchgott
Copy link

Hi,
please, could you get it work for the new asus memo pad 10 fhd
with intel soc x86 z2560 and android 4.2.2?

Its an intel x86 soc and if i compile, i only get arm binary!
Big thanks!

@DooMLoRD
Copy link
Member

What is the kernel version?

Are the kernel sources available?
On 31-Jul-2013 6:58 PM, "switchgott" notifications@github.com wrote:

Hi,
please, could you get it work for the new asus memo pad 10 fhd
with intel soc x86 z2560 and android 4.2.2?

Its an intel x86 soc and if i compile, i only get arm binary!
Big thanks!


Reply to this email directly or view it on GitHubhttps://github.com//issues/14
.

@switchgott
Copy link
Author

Hi,
Kernel Version is: 3.4.21

Do you know a nother method, to root the asus tab, if this isnt working?

Kernel Source are only avalible from samsung!No from asus.

http://opensource.samsung.com/

GT-P5210

Your are my and a lot of peopel master if you could help us to get root on asus tab.
Main problem, there is no firmware on hp!Thats why we cant recovery if somethink went wrong :-(

@DooMLoRD
Copy link
Member

There are numerous exploits... Fist check with your kernel sources if these
vulnerabilities exist...
On 31-Jul-2013 7:02 PM, "switchgott" notifications@github.com wrote:

Hi,
Kernel Version is: 3.4.21

Do you know a nother method, to root the asus tab, if this isnt working?


Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-21862585
.

@switchgott
Copy link
Author

Sorry, can you explain me this?
Dont know exactly what you meen :-)

Iam newbee :-)

Where can i find this?
Nex problem is, the code is rather arm or normal pc x86.Not android x86.
How can i get it work?

Do you think you could help me / us?

@hiikezoe
Copy link
Member

Though I've never read the kernel source, libfb_mem_exploit might be useful on x86 machine. Try break_setresuid first.

@switchgott
Copy link
Author

But how can i do it?
If i compile your code, i get arm binary!Not x86 binary.So how can i start?
Can i destroy me device with it?

@fi01
Copy link
Member

fi01 commented Jul 31, 2013

It's not our problem. You have to learn how to build x86 binary with ndk.
Try APP_ABI=x86 or something.
2013/07/31 23:15 "switchgott" notifications@github.com:

But how can i do it?
If i compile your code, i get arm binary!Not x86 binary.So how can i start?
Can i destroy me device with it?


Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-21865536
.

@switchgott
Copy link
Author

THANKS MAN!!
It worked!
Can start inside my ubuntu :-)

Last question: Could i kill my device with this exploit?
Which is the best on for android 4.2.2 and kernel 3.4?

Have very havy thanks

@DooMLoRD
Copy link
Member

no dude...

On Wed, Jul 31, 2013 at 8:06 PM, switchgott notifications@github.comwrote:

THANKS MAN!!
It worked!
Can start inside my ubuntu :-)

Last question: Could i kill my device with this exploit?
Which is the best on for android 4.2.2 and kernel 3.4?

Have very havy thanks


Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-21867257
.

@switchgott
Copy link
Author

130|shell@android:/data/local/tmp $ ./run_root_shell

Device detected: ME302C (JDQ39.WW_epad-V4.5.7-20130724)

Try to find address in memory...
Attempt fb_mem exploit...
This machine can not use fb_mem exploit.
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
ME302C (JDQ39.WW_epad-V4.5.7-20130724) is not supported.
Failed to setup variables.

:-(

@fi01
Copy link
Member

fi01 commented Jul 31, 2013

It is hard to get address without fb_mem exploit on kernel 3.4.
On 3.4 kernel /proc/kallsyms is protected to see.
2013/08/01 0:06 "switchgott" notifications@github.com:

130|shell@android:/data/local/tmp $ ./run_root_shell

Device detected: ME302C (JDQ39.WW_epad-V4.5.7-20130724)

Try to find address in memory...
Attempt fb_mem exploit...
This machine can not use fb_mem exploit.
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
ME302C (JDQ39.WW_epad-V4.5.7-20130724) is not supported.
Failed to setup variables.

:-(


Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-21869153
.

@switchgott
Copy link
Author

Mh any other idea? How to get root?
Its possible with android fakebackup?
No chance to root android 4.2.2 with kernel 3.4?
Othwr exploit? Idea.
Without root, no backup.
And locked bootloader :-((

@hiikezoe
Copy link
Member

I am not sure libperf_event_exploit can work on the device, mole_plough which uses libperf_event_exploit can work without any addresses needed for run_root_shell. It will cause reboot many times, it will finally get root shell if the device has the exploit.

https://github.com/hiikezoe/mole_plough

@switchgott
Copy link
Author

Thanks!Firmware with kernel source still release a hour ago!
so i have recovery now.Thanks i will try it

@switchgott
Copy link
Author

Any news?
Now we have kernel source code and firmware, but if we change some values inside the ota zip file, the flash went wrong :-(
Could someone from you help the community?

@nothize
Copy link

nothize commented Nov 13, 2013

@switchgott What do you mean? You got root now? What do you want to do? A custom recovery? How about the "firmware" file from asus's official site? Is it a good "recovery" image?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants