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...
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.
The world's first ereader with a color Mirasol display is finally on the market, but unfortunately it's running a severely locked-down Android by the Korean bookstore chain Kyobo. The Kyobo ui is entirely in Korean, the browser blocks downloads, and the reader app is crap. In other words, it's basically useless to anyone outside of Korea. A few enterprising Americans have imported them and been extremely disappointed. Will someone please take a look at this device and see if it can be rooted or if something else can be done to make it of use to the rest of us?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Nate over at The Digital Reader has a firmware update that supposedly contains all of the installed apps. He is asking for someone to try and hack it. He has a download link for the firmware at The Digital Reader.
I also posted this as a question here on XDA:
http://forum.xda-developers.com/showthread.php?t=1432283
it is rooted since some time already.
files and instructions are in the following archive, but since instructions are in korean, i'll do a writeup below.
(argh! spambot won't allow this link, so you'll have to piece it together...)
www<dot>4shared<dot>com/zip/aLwRc7ZG/mirasol_rooting.html
edit: needed files are also in an attachment below
the gist is that you need to flash the boot partition via fastboot, setup root and busybox, and then modify secure->install_non_market_apps in settings.db.
you will need to have adb and fastboot from the android sdk working on your computer. There are many posts about this elsewhere, so i won't go into the details.
also, i only print filename without path, just find the corresponding file in the mentioned archive and modify the commands accordingly.
flash the boot partition via fastboot
first get your kyobo into fastboot mode (with usb cable attached) by pressing volume-down at bootup. timing here can be a bit finicky, but easiest seems to be to shut it down completely and then press just after pressing power.
issue a 'fastboot devices' on computer, if successful it should give you the response '???????????? fastboot' or similar. if empty or hangs, try again by rebooting the kyobo by pressing power with volume-up held (you can go into fastboot immediately after reboot by volume-down as expected).
when positive response above, you can flash by
Code:
fastboot flash boot boot.img
and then reboot by
Code:
fastboot reboot
edit: simplified fastboot instructions, thanks to smb_gaiden, whose button-poking-fu is strong.
setup root and busybox
with boot partition flashed you now have adb access, so let's use it. let the device boot as normal, and then issue the following.
Code:
adb push busybox /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/fixsu.sh
adb shell ln -s /data/local/tmp/busybox /system/xbin/busybox
after this, install some apk's from the archive
Code:
adb install superuser.apk
adb install blackmart.apk
fix non-market apps setting
only thing left is to change a setting to allow non-market apps to be installed. if you don't care about your current settings (locale, etc), you can just push the settings.db from the archive like so:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
if you *do* care about your settings, you'll need to pull the settings.db, edit it in some sqlite db editor (set secure->install_non_market_apps to 1) and push the result.
that's it. all rooted. now you just need to install angry birds and yer' set ;-)
Adb doesn't seem to start properly on device
Hello.
I did succeed in flashing the bootloader via fastboot.
However when I boot device - I see adb on usb only for some initial seconds, and then it disappears.
For that matter my device already had December firmware on it.
Any ideas how to activate adb on device?
Thank you,
Leonid
it may be that persist.service.adb.enable is reset, stopping the adbd service. try flashing the attached boot image instead, see if that fixes it. it is the same as above, except that persist.service.adb.enable is ignored.
edit: i took a look at the december update, afaict it should pose no problem (very few changes in there).
Once these steps are done, how do you install google market?
Thanks.
edit: the original instructions were snafu, so i replaced them with something that should actually work.
getting android market running on the kyobo
needed files are in the attached archive.
install like so:
Code:
adb remount
adb push DrmProvider.apk /system/app
adb push MediaProvider.apk /system/app
adb push DownloadProvider.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
adb push init.qcom.post_boot.sh /system/etc
adb push fix-shared-user.sh /data/local/tmp
adb shell chmod 777 /data/local/tmp/fix-shared-user.sh
adb shell /data/local/tmp/fix-shared-user.sh
wait for the reboot, find market in the menu, and off you go (with downloads this time ;-)
if downloads still do not work after this, try re-executing the last line. android periodically writes to the file we are modifying, which might clobber our changes if unlucky.
I am thinking about buying one of these because I have seen it on sale for 50% discount. However, the general reviews aren't too encouraging, so will rooting make any difference to overall performance?
fatboy1976 said:
I have seen it on sale for 50% discount.
Click to expand...
Click to collapse
where is that?
throwaway4096 said:
you'll need GoogleServicesFramework.apk and Market-3.4.4.apk from the following links:
http://androidmarketu.googlecode.com/files/GoogleServicesFramework.apk
http://forum.xda-developers.com/showthread.php?t=1391565
install like so:
Code:
adb remount
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
find Market in the menu and off you go.
Click to expand...
Click to collapse
I'm finding the market force closes when downloading an app.
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
rooting for beginners
Some friends and i ordered the kyobo to solve our eye-problem (nystagm)
We still can´t figure out, how to root it.
Can you please give us some rooting instruktion vor beginners??
It would be so essential for us, as the kyobo is little worth without forgeign apps!
Thank you very much!
Joe
send2toonie said:
I'm finding the market force closes when downloading an app.
Click to expand...
Click to collapse
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
smb_gaiden said:
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
Click to expand...
Click to collapse
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware update on my kyobo, that is found on the web, as instructed from the SD card. Then I installed fastboot and adb on my computer (search for 'how to install fastboot and adb'), as I found instructions for that as well. To enter fastboot I kept Kyobos, volume down button for about 10 sec, when booting the device (kyobo connected to computer with USB) - nothing happens -> however on my computers command window (cmd), 'fastboot devices' command produces an answer with '? ..' as it should. The biggest issue I had was to get adb working. For this purpose I installed and removed a couple of USB drivers - I don't really know how I got it to work finally.
You can tell if you have succeeded installing a useful usb driver, if you enter the 'adb devices' command in the cmd window and it returns a device number. Then you are ready to go with the rest of the commands/instruction as seen in the insturction of this thread.
From the blackmart application I was able to install many useful applications - the Launcher application can replace the Kyobo "home" application, which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Hey Guys!
is there a way to root the kyobo via mikrosd?
thanks a lot
Joe
Hey Joe. I've seen you on this forum as well as The Digital Reader asking for help with the Kyobo rooting. I too am a beginner and I'm trying to build up the nerve to try it. Wish us both luck and I hope someone can share rooting-for-dummies with us.
@fatboy1976: rooting won't improve performance in itself. it makes the device better as you can install apps, but ofc the hardware is still the same.
@send2toonie: yes, sorry about that. it worked for me, but only thanks to other changes. it's hard to keep track :-/. i updated the original post with new instructions which should work properly.
@smb_gaiden: hah, excellent, i never tried that! original post updated.
@Joe84: it should be possible to root via microsd by creating an update.zip. i haven't gotten around to trying that yet, but maybe in future. for now this is as simple as it gets.
Kaarlos said:
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware ...(updated -see above..) .., which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Click to expand...
Click to collapse
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Kaarlos said:
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Click to expand...
Click to collapse
Hi,
Could you post the OS/processor version and driver name that got adb working for you. If you can also remember the keys pressed to put the Kyobo in the correct boot mode for adb, that would be nice too.
I have also managed to load apps on my Kyobo but that is without having su, Superuser, adb and Android Market working. The above info would be helpful in fixing that. Holding the volume down fir 10 seconds after pressing power on puts the Kyobo into fastboot mode. Adb requires a different mode and set of key presses. This is because there is a menu of boot options being displayed which can't be seen on the Mirasol screen. I suspect this is because of display settings within the boot.img but that is only a guess on my behalf.
I have your ICS root ready, how about we call it TPSparkyRoot. I based my research on code written by Dan Rosenberg (similar to what jchase did with NachoRoot in the fact that chown/chmod follows symlinks even when set during startup), here is a link to that research http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
**UPDATE**
Android's source has been patched so that future OEMs can not leave this hole open by accident.
https://android-review.googlesource.com/#/c/36035/
**UPDATE**
This method has been shown to work on the HTC One X see forum
http://forum.xda-developers.com/showthread.php?t=1644167
Theoretically this should work on Honeycomb versions of the Prime as well, since the Honeycomb update is where I found the flaw that is being exploited. I have confirmed this works on my Prime.
**UPDATE**
This exploit does not currently work for the latest ICS update released (v9.4.2.11 on 1/18/2012). You can use OTA Rootkeeper to backup your root prior to updating using OTA, which I have confirmed to work on my device, (this may not work if you push the update manually).
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
For the devs out there, it does not to honor the ro.kernel.qemu=1 setting within the local.prop because it is already set to blank by that point by the build.prop
You must have your Prime set up to use adb and your adb location contained in your path variable (windows) or unzip the files from my zip into that directory before running.
**UPDATED**
If you are have issues getting adb working, make sure asus sync is not running, if it is then kill it.
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
adb shell rm /data/local.prop > nul
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
adb reboot
adb shell id
//IF ID IS 0/root THEN CONTINUE, ELSE START OVER>
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
//UNDO EVERYTHING EXCEPT su
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb reboot
**UPDATE** As jchase stated "If your device "bootloops" don't stress, just follow through with the commands as it "loops" ro.kernel.qemu can do funky stuff." I did notice this in my rooting but just assumed it was normal as this is my first use of adb.
**UPDATE2**
If you get a permissions error on the call
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
then you may try
adb shell rm /data/local.prop
And then try the echo command again. This may be due to having rooted prior without cleaning up properly. Thanks to Franky_402 for this piece of info.
I have updated the batch file to include this step, it should still be fine for those who are not having the issue as well.
I have attached a zip file containing the su and a bat file for a more automated process (just pauses when during reboots, don’t hit go until it’s done rebooting). Or, you can run the commands manually and get the su file from the origin http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
Finally, install Superuser to make it all work https://market.android.com/details?id=com.noshufou.android.su
**UPDATE** UNROOT
There are multiple was to unroot now that you have root access already (all you need to do is remove the su file; so you could potential skip all the steps before the remount and just add the local.prop manually using a file manager and then reboot).
The one most similar way to how you rooted would be to follow all of the steps above, but replace these 3 lines
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
with this line
adb shell rm /system/xbin/su
This will remove the actual root, but it would leave behind any apps that you have given root access to or any files that those apps changed themselves (i.e. RootKeeper backs up the su file and the backup would need to be removed). If you had anything like this you would need to clean up that first before unrooting because it is a dead giveaway that it was rooted.
Viperboy should be releasing his tool shortly that utilizes this method, if you would like a one click process that installs apps along with it (superuser, busybox). I’m guessing it installed them to the root apps directory so these also would need to be removed when unrooting as well (i.e. if you root using his new tool you should unroot using it as well).
**UPDATED** Remove PayPal link in favor of link over there <-
Yes, as it says, I went from the same base exploit that was shown by Dan and was the base for jchase as well.
The commands more than likely are but the exploit must be different or Jcases rot would still be working... Thanks OP!!!
EDIT: He didn't "ask" for donations just gave a link since he doesn't have the donate button <<over there
Not mine at all, props to this guy! Send him some bones.
Yes, thanks, I did not realize that there was a donate button as I am still learning this forum.
This root is confirmed!
If your device "bootloops" don't stress, just follow through with the commands as it "loops" ro.kernel.qemu can do funky stuff.
Good ****.
sparkym3 said:
Yes, thanks, I did not realize that there was a donate button as I am still learning this forum.
Click to expand...
Click to collapse
Yeah it's in the User Control Panel on the top of the forum
"Reported" your thread to a mod, so he can move it to the dev section
And welcome to XDA Don't let the trolls take your love for android
jcase said:
This root is confirmed!
If your device "bootloops" don't stress, just follow through with the commands as it "loops" ro.kernel.qemu can do funky stuff.
Good ****.
Click to expand...
Click to collapse
OP, maybe put that in the OP, so users don't panic
Moved to development.
Holly smoke, it works....
jcase said:
Not mine at all, props to this guy! Send him some bones.
Click to expand...
Click to collapse
As the main man says. Give credit when due. It's not his. and give the guy props and if you wish to donate donate.
This is why this android community is crap. because everyone trolls. If it was jcases he'd release it. not someone else. and im sure as hell he wouldnt be saying these things 'like give the guy some bones'
rhcp0112345 said:
As the main man says. Give credit when due. It's not his. and give the guy props and if you wish to donate donate.
This is why this android community is crap. because everyone trolls. If it was jcases he'd release it. not someone else. and im sure as hell he wouldnt be saying these things 'like give the guy some bones'
Click to expand...
Click to collapse
Biggem isnt really a troll, he's obv just got out of the wrong side of the bed ... i'm sure he'll take that back.
Danny-B- said:
Biggem isnt really a troll, he's obv just got out of the wrong side of the bed ... i'm sure he'll take that back.
Click to expand...
Click to collapse
Also nothing wrong with asking for donations.
YOU ROCK. donations to you and jcase after payday
You would all post this WHILE I'm at work, have my prime with me, but not my charger! lol. I'll DEFINITELY check it out when I get home.
disturb3d1 said:
You would all post this WHILE I'm at work, have my prime with me, but not my charger! lol. I'll DEFINITELY check it out when I get home.
Click to expand...
Click to collapse
Dude mine should be here in 9 hrs
I might do an unboxing vid using my photon
Wait a minute, chainfire is paying attention to the thread, that only means good things. Please tell me your gonna dev some for this device
Sent from my SGH-T959 using XDA App
not going good for me I'm on ubuntu with working adb. copied su to home directory and running all commands from there. when i get to, adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop", i get, /system/bin/sh: cannot create /data/local.prop: Permission denied. So i never get the right id to continue. Anyways please help. thankx
Any chance in the future this can be converted to an apk to install on Prime or a One-click method, per se?
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.
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..