I finally did it...
http://forum.xda-developers.com/showthread.php?p=25157446#post25157446
Now let's wait for ICS and hope that Sony's one will be built on a "good" kernel.
looks very promising, great work Nesquick
maybe in a week (or little more..) we could test it in practice!
keep up the good work
br
condi
Not exactly sure what this does, but it seems important so good job
This should be very interesting. Thanks for continuing to stay with it.
Sent from my Sony Tablet S using xda premium
Nesquick95 said:
I finally did it...
http://forum.xda-developers.com/showthread.php?p=25157446#post25157446
Now let's wait for ICS and hope that Sony's one will be built on a "good" kernel.
Click to expand...
Click to collapse
But it seems we are unable to chmod without root. So this would require one of our rooted ICS friends to give us the offsets?
chmod not needed in recovery, but it doesn't get root:
/sdcard/n95-offsets
n95-offsets by Nesquick95
Gets requiered offsets for mempodroid exploit
./mempodroid 0xd9ec 0xaf47 sh
1|@android:/system/bin $ /sdcard/mempodroid 0xd9ec 0xaf47 sh
/sdcard/mempodroid 0xd9ec 0xaf47 sh
1|@android:/system/bin $
Click to expand...
Click to collapse
Too bad...
Well... That's the copy of a successful session, taken from my Galaxy Nexus (see image attached).
Too bad if the exploit doesn't root our ICS release.
Can you please post your run-as (/system/bin/run-as) binary ? I'll try to get the offsets another way.
Nesquick95 said:
Well... That's the copy of a successful session, taken from my Galaxy Nexus (see image attached).
Too bad if the exploit doesn't root our ICS release.
Can you please post your run-as (/system/bin/run-as) binary ? I'll try to get the offsets another way.
Click to expand...
Click to collapse
I've managed to run your bin, got offsets, but still no root...:
Code:
n95-offsets by Nesquick95
Gets requiered offsets for mempodroid exploit
./mempodroid 0xd9ec 0xaf47 sh
and then:
Code:
[email protected]:/ $ /data/local/tmp/mempodroid 0xd9ec 0xaf47 sh
/data/local/tmp/mempodroid 0xd9ec 0xaf47 sh
1|[email protected]:/ $
Really too bad
Sony's ICS is built on kernel 2.6.39, normally rootable by this exploit... Maybe they have patched it...
Need a copy of /system/bin/run-as binary to try finding offsets another way, as a last chance. My tablet hasn't got the update (unrootable kernel 10 - French region)
Binary attached.
Since we're unable to chmod under normal boot (operation not permitted), the only way is to run under recovery. Is it possible that mempodroid doesn't work under recovery?
The worst thing that could happend
I don't know if running in recovery can make mempodroid fail... It probably doesn't. But as you can see, Condi has run n95-offsets in "regular" /data/local/tmp without success.
I have verified the offsets in the run-as binary posted with IDA disassembler, the offsets returned by n95-offsets are the good ones.
I think Sony's 2.6.39 kernel is patched, the exploit won't work...
(Maybe) we will find an other one (some day)...
A last ray of hope ?
There is something weird in the run-as posted by OCedHrt... His ELF header show an entry point at 0x8000 when the other run-as' that I've seen have their entry point at 0x80C0...
It sounds a little simple but may someone test :
./mempodroid 0xd92c 0xae87 sh
Thx !
Nesquick95 said:
There is something weird in the run-as posted by OCedHrt... His ELF header show an entry point at 0x8000 when the other run-as' that I've seen have their entry point at 0x80C0...
It sounds a little simple but may someone test :
./mempodroid 0xd92c 0xae87 sh
Thx !
Click to expand...
Click to collapse
Tried it, sadly did not work. I also got the latest version of mempodroid off the git, but still didnt work.
EDIT: FOUND a little thing, our offsets (from n95-offsets) are exactly the same as the transformer prime, maybe we can use the exploit they used to root ours?
Nesquick95 said:
I don't know if running in recovery can make mempodroid fail... It probably doesn't. But as you can see, Condi has run n95-offsets in "regular" /data/local/tmp without success.
I have verified the offsets in the run-as binary posted with IDA disassembler, the offsets returned by n95-offsets are the good ones.
I think Sony's 2.6.39 kernel is patched, the exploit won't work...
(Maybe) we will find an other one (some day)...
Click to expand...
Click to collapse
I wonder how he got chmod to work. Well I assume he already had root. Chmod returns operation not permitted for me so I had to try it in recovery.
Sent from my Nexus S using XDA
Maeur1 said:
Tried it, sadly did not work. I also got the latest version of mempodroid off the git, but still didnt work.
EDIT: FOUND a little thing, our offsets (from n95-offsets) are exactly the same as the transformer prime, maybe we can use the exploit they used to root ours?
Click to expand...
Click to collapse
Transformer Prime is probably running the same kernel than our tablet but I guess it has been released earlier than Sony's ICS, when mempodroid was still young and proud (I mean not patched)!
It's hard to figure out, but we must keep on searching, try things like you suggest... I haven't decided yet if I will sell my Sony S or if I will loose some more time on it.
Related
Okay I posted this also in the Themes forum for Nexus but I wanted to see if anyone could assist. Someone in the theme forum asked about the bootanimation.zip that shows us the cool animation during boot, while reading this it reminded me of the behold 2. See below
What are the permissions for bootanimation.zip if they were left open to non root then this may-b a way to get root with unlocking the bootloader. This would be the same approach that was used to root the behold 2 where the "try3" file was renamed to play_logo . play_logo then was used to root and after root was opened it would make play_logo_real play which was the boot animation. I may be wrong but couldnt this be a possibility. Thanks, any help is appreciated. Im wondering if Zinx could chime in...
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
seraph1024 said:
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
Click to expand...
Click to collapse
You can always write if I am not mistaken using the low-level write dd if/of command. We would use the bootanimation.zip to run the root command. An example is in the Samsung Behold 2 it was done as follows:
Example
echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
cat /system/bin/sh > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real" > /system/bin/playlogo
Click to expand...
Click to collapse
This is how it was done. I am wondering if the same can be done on the nexus using bootanimation.zip as it executed at startup. We would basically modify the bootanimation.zip to the above and add a line for it to execute the boot image. By gaining root this way we would still be able to put on a custom recovery and roms without unlocking the bootloader in theroy. The try3 file was created by Zinx and used by Maxisma to bring root to the behold 2. I am pretty sure this may work on the Nexus 1. I hope this helps.
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Okay XDA is back up. Yes I can test. Oh man if this works there will be absolutely no need to unlock the boot loader... Thanks
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Hey Seraph1024 take a look at this. Its too big for XDA so I put it up on pastebin. http://pastebin.com/f62780d32 Its what is contained in the try3 file. Zinx used it in flashrec
No joy.
Code:
$ getprop | grep product.model
[ro.product.model]: [Nexus One]
$ pwd
/data/local
$ ls -al try3
-rwxrwxrwx 1 0 0 74512 Jan 25 13:26 try3
$ id
uid=2000(shell) gid=2000(shell)
$ ./try3 /system/bin/sh
[1] Killed ./try3 /system/bin/sh
$ id
uid=2000(shell) gid=2000(shell)
Exploit does not work.
I was that close to rooting today until i saw this now its made me double think again lol I've been waitin for a custom rom by cyanogen until i rooted, and since its pretty much almost here i was going to root. bah guess i'll wait until CM gets released!
flak0 said:
You can always write if I am not mistaken using the low-level write dd if/of command.
Click to expand...
Click to collapse
You can't on this phone. There are two ARM cores - one running the low-level stuff (bootloader, radio) and the other running Linux.
Without the engineering bootloader (or some exploit) we don't have access to the baseband ARM core, and therefore don't have access to its MMU, which is programmed to deny read/write access to protected areas of the flash - such as the bootloader and splash screens. Even with root, Linux can't access that stuff.
It's going to be really hard to find a kernel exploit for the N1 to get root. Most exploits involve mapping memory to the zero page and then triggering a null pointer de-reference bug in the kernel. But the N1's kernel won't allow such mappings.... I believe the minimum address for mmap on the N1 is around 64k. (It's in the kernel config.)
This is a tough nut to crack.
The behold root was done that way because there's no way to flash the partitons on it.
You still need root in the first place to write to that file. The droid guys have been looking a while for a new root exploit but didnt find one. The problem is that all known exploits have been closed in 2.1.
We need to wait for someone to find a new one that works. Then this would be a real posibility, and there' no need to hijack playlogo.
for what its worth, if you need a lab rat i do not have my phone rooted yet and i am willing to test some things if anyone needs...
i dont plan on rooting it until the ball really gets rolling with everything and until I am 100% satisified with the phones performance
kam187 said:
You still need root in the first place to write to that file.
Click to expand...
Click to collapse
That's what I though. And like it was posted earlier, I don't think there is a exploit since this phone is done differently. I am busy for the next couple of days but if anyone want to "try", I'll make up something but I really doubt any of the old stuff will work on this phone.
I read in the bootloader development thread that it'd reached a level where it could almost boot into a custom system image stored on the SD card. Some questions about that:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Thanks
ddewbofh said:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
Click to expand...
Click to collapse
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
ddewbofh said:
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Click to expand...
Click to collapse
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
zdzihu said:
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
ddewbofh said:
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
Click to expand...
Click to collapse
Bash them for a while as soon as you see SE logo appearing
ddewbofh said:
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
Click to expand...
Click to collapse
Make sure you either name your image rootfs.img (not .ext2) or edit the init in the ramdisk accordingly.
Cheers
Thanks, that should make things much, much easier.
zdzihu said:
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
is there different form flash?
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
ddewbofh said:
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
Click to expand...
Click to collapse
How about busybox --install -s /your_destination_dir ?
zdzihu said:
How about busybox --install -s /your_destination_dir ?
Click to expand...
Click to collapse
Awesome, thanks. My knowledge about busybox is limited at best so when I saw install listed as a busybox function I assumed it was the "normal" install command.
In the quest for finding a way to use custom kernels I'm playing around with the splboot module but I need to find a way to get hold of dmesg or kmsg from failed attempts. Is there a reliable way to get any of these logs?
I've tried adding a line in the mount_iso script which cats kmsg to a file right before executing the splboot but I'm seeing nothing that would indicate that I'm running anything but the stock kernel.
Any ideas?
Hello,
I have found this bug on the TF101 and I do have TF201 as well but its not a production model so i cant really test this 100%
If someone can test my root method. below i will paste.
This is a new root method.
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
http://www.mrcellphoneunlocker.com/V2/tf101_ics_root.tar.gz
Windows version of my exploit can be found at: http://forum.xda-developers.com/showthread.php?t=1515470
Reserved for later
im pretty positive it won't work, seems they made a lil mistake on the rights on your system folder after the backup utility been used bro <- it does work
but still, can't wait for someone to actual test it, would be funny if it however would work.
after all nice catch so far
Hawkysoft said:
im pretty positive it won't work, seems they made a lil mistake on the rights on your system folder bro
Click to expand...
Click to collapse
Did you try it? Im trying to see if it works on only TF101 ICS or does it work on the TF201 ICS too.
I dont have a production model TF201 mine is very diff.
ok since im nice, i will unroot with voodoo and try it >.<
installed all crap again, had a hdd failure this week so yea...
doing this manually on windows7 >.< reading ur files step by step
Hawkysoft said:
ok since im nice, i will unroot with voodoo and try it >.<
Click to expand...
Click to collapse
Thank you.
Want to know if it works on the TF201.
You need to run the backup util on an app installed (This util is found in the app draw)
then once the script runs. it will ask you to do the same backup again and it should reboot and you have root.
it works >.<
ok serious, i lol'ed very hard
commands>
Code:
adb devices
push su /data/local/tmp/
779 KB/s (22364 bytes in 0.028s)
adb push own.sh /data/local/tmp/
25 KB/s (235 bytes in 0.009s)
adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
[email protected]:/ $ cat /data/local/tmp/own.sh > /data/data/com.asus.backupres
tore/files/busybox
/data/data/com.asus.backuprestore/files/busybox <
[email protected]:/ $
adb wait-for-device
adb shell
[email protected]:/ $ su
su
[email protected]:/ #
Forget all these tethered to computer root methods..lmfao we need a simple apk root install method. root from prime itself. This would be easiest to implement and more people could root.
Hawkysoft said:
it works >.<
ok serious, i lol'ed very hard
commands>
Code:
adb devices
push su /data/local/tmp/
779 KB/s (22364 bytes in 0.028s)
adb push own.sh /data/local/tmp/
25 KB/s (235 bytes in 0.009s)
adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $ cat /data/local/tmp/own.sh > /data/data/com.asus.backupres
tore/files/busybox
/data/data/com.asus.backuprestore/files/busybox <
[email protected]:/ $
adb wait-for-device
adb shell
[email protected]:/ $ su
su
[email protected]:/ #
Click to expand...
Click to collapse
Thank you. so its a universal root
rhcp0112345 said:
Thank you. so its a universal root
Click to expand...
Click to collapse
no, only for asus devices when they implemented this bright tool >.<
rhcp0112345 said:
Thank you. so its a universal root
Click to expand...
Click to collapse
Nothing wrong with another method. Viperprime time also roots td101. Can this new method you discovered be made into an apk for installation on prime?
I could. but hmm dono
rhcp0112345 said:
I could. but hmm dono
Click to expand...
Click to collapse
I'm sure there would be great demand for it. You made me laugh. I'm anxious for one. No access to a PC. Lost my root manually updating to. 15 firmware to test for Asus before they rreleased it. Well if you do, ill be up for testing it
Good find though on this universal Asus transformer root.
demandarin said:
Forget all these tethered to computer root methods..lmfao we need a simple apk root install method. root from prime itself. This would be easiest to implement and more people could root.
Click to expand...
Click to collapse
that won't work in this case, since you take the advantage of their app...
you can't make an app control another app without root rights >.<
and if people can't obtain root on the ways that has been given, do they actually need root than?
---
/edit
unless you make an app saying do this than /restart app/ app sees it has been done/ than goes to step 2/ etc.
would be annoying?
Hawkysoft said:
that won't work in this case, since you take the advantage of their app...
you can't make an app control another app without root rights >.<
and if people can't obtain root on the ways that has been given, do they actually need root than?
---
/edit
unless you make an app saying do this than /restart app/ app sees it has been done/ than goes to step 2/ etc.
would be annoying?
Click to expand...
Click to collapse
it can be done
rhcp0112345 said:
it can be done
Click to expand...
Click to collapse
i'll be sitting here and wait to see >.< have fun bro
Hawkysoft said:
that won't work in this case, since you take the advantage of their app...
you can't make an app control another app without root rights >.<
and if people can't obtain root on the ways that has been given, do they actually need root than?
---
/edit
unless you make an app saying do this than /restart app/ app sees it has been done/ than goes to step 2/ etc.
would be annoying?
Click to expand...
Click to collapse
Lol good point. I need root for overclocking, system tuner settings. Ad away etc... I get what you saying though. Just checking to see if anyone coming up with an apk. Install. Someone did before with nachoroot but got shut down since he didn't asknflr permission tl use their exploit. No biggie. I'm sure someone will come up with one again soon enough? Rooting is nothing new to me..just lost root on last update n computer down. Not pressed. Can't hurt to ask though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------
rhcp0112345 said:
it can be done
Click to expand...
Click to collapse
Ill be waiting also if you do decide to make one.
demandarin said:
Lol good point. I need root for overclocking, system tuner settings. Ad away etc... I get what you saying though. Just checking to see if anyone coming up with an apk. Install. Someone did before with nachoroot but got shut down since he didn't asknflr permission tl use their exploit. No biggie. I'm sure someone will come up with one again soon enough? Rooting is nothing new to me..just lost root on last update n computer down. Not pressed. Can't hurt to ask though.
---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------
Ill be waiting also if you do decide to make one.
Click to expand...
Click to collapse
It will go on market or my site for purchase as a small fee.
$1 or something. Been getting a bit ticked lately posting things and no one ever donates anything for work done :/
Fair enough..if it shows on market ill buy
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
If you need a tester, let us know
Indeed, I'll unroot and test if you so please.
I'll certainly buy it if you do release it! I know a lot of people would be that much more comfortable with taking some control over their devices.
I found this in the TF300 thread and thought it might be useful.
http://forum.xda-developers.com/showthread.php?t=1704209
PLEASE NOTE: THIS IS NOT MY WORK AND ALL CREDITS TO THE DEVELOPER.
I am just bringing this to the attention of users of the prime like myself.
Also i have NOT used this method, i used the downgrade method, so i cant comment if it works but comments in the thread seem to show it works.
yeah, there are a few 201 owners that tried and said it works. we may have a more simpler automated tool coming shortly. keep an eye out for it. this is great news for prime owners. i personally don't like all that hassel of downgrading and upgrading and blah blah..lol
Damn and I just unlocked mine to have root. Oh well wooky made a great stock replacement
When i read about the downgrade-methode i thought "wouldnt it be nice to just copy su binary into the writable filesystem" but i didnt know about debugfs...
i just tried it on my t201 - now i am a happy owner of a rooted transformer *woohu!*
onlyolli said:
When i read about the downgrade-methode i thought "wouldnt it be nice to just copy su binary into the writable filesystem" but i didnt know about debugfs...
Click to expand...
Click to collapse
I didn't know about debugfs either, that's why it took me 24h to get the root.
I started to develop my own tool to mess up with partition contents, but didn't find any good reference for ext4.
Then I thought, let's try to just patch an existing tool like fsck.ext4, and I found debugfs in the source tree of e2fsprogs
onlyolli said:
i just tried it on my t201 - now i am a happy owner of a rooted transformer *woohu!*
Click to expand...
Click to collapse
Gald to see people happy
Sent from my ASUS Transformer Pad TF300T using XDA
Rooting went like a breeze Thank you very much for this method. I've got one question about your code though. I'm by no means a linux cmd guru but when I look at these lines of code:
Code:
$ cd /data/local
$ rm /data/local/tmp
$ mv /data/local/tmp.back /data/local/tmp
$ chmod 755 /data/local/debugfs
$ /data/local/debugfs -w /dev/block/mmcblk0p1
It seems to me that the first line is not necessary, as you specify full paths in your code. Wouldn't it be easier to remove that line, or even better: just shorten the paths like this:
Code:
$ cd /data/local
$ rm tmp
$ mv tmp.back tmp
$ chmod 755 debugfs
$ ./debugfs -w /dev/block/mmcblk0p1
Would mean a lower risk of typo's Or is there some issue with adb and or debugfs why you choose to put the commands like this?
Again, just curious
I have created an automated tool using this root method and am looking for confirmation that it works on a Transformer Prime.
http://forum.xda-developers.com/showthread.php?t=1706588
Ovigo said:
Would mean a lower risk of typo's Or is there some issue with adb and or debugfs why you choose to put the commands like this?
Again, just curious
Click to expand...
Click to collapse
Frankly I don't know... I finished to write the "script" after being up for more than 36 hours, that could explain the inconsistencies ^^
Sent from my ASUS Transformer Pad TF300T using XDA
sparkym3 said:
I have created an automated tool using this root method and am looking for confirmation that it works on a Transformer Prime.
http://forum.xda-developers.com/showthread.php?t=1706588
Click to expand...
Click to collapse
I just sucessfully rooted .28 with no previous rooting done. Used the v1.5 posted on the first page of the thread above. I did have to install superuser.apk from the market and busybox. But it is now fully rooted.
I actually tried supersu.apk first, but it failed. But after playing a few minutes, its all working.
I installed the update before I seen this thread on rooting .21 without a downgrade.
automated tool works fine on my .21
installed OTA keeper now and updating to .28 just in case
beady_uk said:
I found this in the TF300 thread and thought it might be useful.
http://forum.xda-developers.com/showthread.php?t=1704209
PLEASE NOTE: THIS IS NOT MY WORK AND ALL CREDITS TO THE DEVELOPER.
Click to expand...
Click to collapse
Thanks dude your post comes really handy.
And confirrmed, it works.
instructions
hi there im a regular noob lol, i want to root my asus tf201 v9.4.2.28 running ics 4.0.3 right i read the instructions of the automated root method the debugfs one by sparkym3, ive downloaded both the drivers folder and the debugfs folder, but im not sure where to go from there, could you please give me step by step instructions on what to do please i searched all over the forum to see if somone already asked my question but had no luck. thank you
baller625 said:
hi there im a regular noob lol, i want to root my asus tf201 v9.4.2.28 running ics 4.0.3 right i read the instructions of the automated root method the debugfs one by sparkym3, ive downloaded both the drivers folder and the debugfs folder, but im not sure where to go from there, could you please give me step by step instructions on what to do please i searched all over the forum to see if somone already asked my question but had no luck. thank you
Click to expand...
Click to collapse
"This tool will root your device based on the debugfs root method developed by miloj.
Just download and unzip everything into a directory; then run RootDebugfs.bat from that directory (if you do not currently have the device drivers for your transformer, they are attached to this post, please install them, please use them to install your device before attempting the process).
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are)."
okay I'm thinking of rooting - but need some advice - I have the latest updates from ASUS (4.0.3) and have never rooted. What are the main benefits of rooting - I'm thinking I'll probably be using Sixaxis (for joystick access in games), the touchscreen fixer app so I can use a stylus better, and titanium backup - any other good apps/tools that need root that I should be looking at?
I was thinking of waiting till ASUS release the ota 4.1 upgrade before rooting - what do you think - better to root now while I know I still can? Still no definite date from ASUS for Jellybean
Finally, I was going to use sparkym3's automated method (http://forum.xda-developers.com/show....php?t=1706588) - is this the best/easiest way to go?
Hello guys, i have a question here, i bought this tablet from Focalprice:
http://www.focalprice.com/CE0427B/Y...PX820_Dualcore_12GHz_Tablet_PC_with_WiFi.html
This tablet have the same specs of the Ippo Y88, BUT Y88 have 1.5ghz and mine have 1.2ghz, they use the SAME dualcore A5 processor, IMAPX820.
Well, i search on google, and use the tool here on XDA to find some information, but its impossible to find anything about this processor, and those tablets... I know they are simple tablets, but someone know if i can ROOT this thing using CWM and put some light ROM, or Cymod?
Thnaks for help, this forum is the best, and i love the Galaxy S3 forum!
This proc is new, or have some other name?
up
up.
too cheap to be rooted? xD
p_morales said:
up.
too cheap to be rooted? xD
Click to expand...
Click to collapse
Hehe, idk maybe this tablet is not so good, so none develop for it. ;x
p_morales said:
up.
too cheap to be rooted? xD
Click to expand...
Click to collapse
How is your answer supposed to help anybody? People buy cheap tablets for a lot of reasons, I bought this to use it for a home automation system and it's perfectly fit for this purpose.
I'm also interested in rooting it, so any information ( ROMs , ideas on how to root it or how to make a ROM dump without root, etc) would be much appreciated.
crwro said:
How is your answer supposed to help anybody? People buy cheap tablets for a lot of reasons, I bought this to use it for a home automation system and it's perfectly fit for this purpose.
I'm also interested in rooting it, so any information ( ROMs , ideas on how to root it or how to make a ROM dump without root, etc) would be much appreciated.
Click to expand...
Click to collapse
My answer helps as yours. I only wanted to say that Aldighieri is not the only person looking for a way to root it.
Maybe nobody will develop a rooting method for this kind of tablets, but there could be an existing method that works ¿isnt it? hope so.
Thanks all of u!
Calm down boys, hehe!
So, none know a way? Is impossible to root this thing? =/
Aldighieri said:
Calm down boys, hehe!
So, none know a way? Is impossible to root this thing? =/
Click to expand...
Click to collapse
If you or somebody else can provide/find the original ROM I might be able to root it. I'm not an expert but I've managed to root an "unrootable" android tv box once. I've asked the guys at focalprice for the ROM but they didn't answer my email and I don't have too much hope given their awful customer service.
Oh thanks! Ill try to find it with someone on ebay, or google, if i find it i tell you! Thanks! )
Same problem for me. Excelent tablet, bu timpossible to root. When I try (with different methods: unlockroot,z4root, superoneclick, root bin4ay, rootx...) a massage say that is rooted, but when I try to install Superuser don't work for me. Please, help!
I asked for sellers on ebay to try to find the rom with the providers, but have no awnser yet, if u can, try it too! ^^
Me too on focal price. If i know something, I will post about it. Is very a rare case...
Thanks.
Aldighieri said:
I asked for sellers on ebay to try to find the rom with the providers, but have no awnser yet, if u can, try it too! ^^
Click to expand...
Click to collapse
elefantino9 said:
Me too on focal price. If i know something, I will post about it. Is very a rare case...
Thanks.
Click to expand...
Click to collapse
Nice! Thanks!
Still no answer from focalprice on my side and I think the best chance to find the ROM is via ebay sellers. I've tried a few methods of rooting the tablet without any luck and I came to the conclusion (with my limited knowledge) that the problem is related to the file system the ROM is packed, which doesn't allow changing file permissions. I can't go further without risking bricking my tablet, but if we find the original ROM I may be able to unpack /repack it, changing the permissions in the process. It may be a long shot but it's worth a try.
Thanks everybody for your efforts!
Fast response from focalprice: a word file with how to use this tablet: on, off, mute, how listen to the music...wow!
IF you find the rom ok, but you can't use it because the recovery is not present on this tablet. If you can do somethins, please, post it.
Thanks :good:
crwro said:
Still no answer from focalprice on my side and I think the best chance to find the ROM is via ebay sellers. I've tried a few methods of rooting the tablet without any luck and I came to the conclusion (with my limited knowledge) that the problem is related to the file system the ROM is packed, which doesn't allow changing file permissions. I can't go further without risking bricking my tablet, but if we find the original ROM I may be able to unpack /repack it, changing the permissions in the process. It may be a long shot but it's worth a try.
Thanks everybody for your efforts!
Click to expand...
Click to collapse
Hello friends!
I'm completly frustated. Google is burned with my researches. I have found this video and I think that is our tablet, but this combination don't work for me. Any idea?
Thank you for the info. I've tried the method in the video and it doesn't work on my tablet either, so probably we have a different model. Even if there is no recovery mode as the guys from focalprice say, I am sure that the ROM can be updated/reinstalled somehow, via usb maybe?
I'll keep trying to make a ROM dump from my tablet and I'll post here if I succeed.
Aldighieri said:
Hello guys, i have a question here, i bought this tablet from Focalprice:
http://www.focalprice.com/CE0427B/Y...PX820_Dualcore_12GHz_Tablet_PC_with_WiFi.html
This tablet have the same specs of the Ippo Y88, BUT Y88 have 1.5ghz and mine have 1.2ghz, they use the SAME dualcore A5 processor, IMAPX820.
Well, i search on google, and use the tool here on XDA to find some information, but its impossible to find anything about this processor, and those tablets... I know they are simple tablets, but someone know if i can ROOT this thing using CWM and put some light ROM, or Cymod?
Thnaks for help, this forum is the best, and i love the Galaxy S3 forum!
Click to expand...
Click to collapse
Okay, I found a way to root it, but its on different device (Infotmic GF20). Firstly you have to enter recovery mode with adb (adb reboot recovery), then disconnect and reconnect usb cable, enter adb shell. If you have # as prompt, you can continue - it will work on your device too - if not, you have to obtain firmware from seller to root it. If you have #, type
Code:
ubiattach -m 1
busybox mount -tubifs /dev/ubi0_0 /system
Then exit adb shell, get su binaries and supersu app, and pull them to the device:
Code:
adb push su /system/xbin/
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell ln /system/xbin/su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 6755 /system/bin/su
adb shell push supersu.apk /system/app/
Reboot device and it should work
OMG! Incredible!
My problem is the seller: they don't have the firmware, but I will try to understand all the process and I will try.
Thanks, thanks and thanks
lolet said:
Okay, I found a way to root it, but its on different device (Infotmic GF20). Firstly you have to enter recovery mode with adb (adb reboot recovery), then disconnect and reconnect usb cable, enter adb shell. If you have # as prompt, you can continue - it will work on your device too - if not, you have to obtain firmware from seller to root it. If you have #, type
Code:
ubiattach -m 1
busybox mount -tubifs /dev/ubi0_0 /system
Then exit adb shell, get su binaries and supersu app, and pull them to the device:
Code:
adb push su /system/xbin/
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell ln /system/xbin/su /system/bin/su
adb shell chown 0.0 /system/bin/su
adb shell chmod 6755 /system/bin/su
adb shell push supersu.apk /system/app/
Reboot device and it should work
Click to expand...
Click to collapse
Don't works for me. I can see the recovery (thanks), but when I unplug and plug the device, windows (xp) don't recognize the tablet. I use the Universal ADB drivers https://github.com/koush/UniversalAdbDriver, but I think that are the correct drivers. Any idea? Thanks! :good:
Here we have the solition, but I don't understand the recovery mode driver installation...