Related
So I got sick of typing
$su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#chmod 777 /system
So I wrote a script and I just click on it in gscript.
Does this officially make me a white belt, lowest rank possible dev? Aahaha
Pm me and I can send you the script if you want haha.
(Yes, you are all supposed to laugh and make fun of me now)
Sent from my HTC Vision using XDA App
Ill give you a pat on the back. That's one small step to being a scripter
Also note you can do things in dos for adb
Sent from my T-Mobile G2 using XDA App
might as well post it publicly, i'd be interested in that script, i'll send pm as well
jontornblom said:
So I got sick of typing
$su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#chmod 777 /system
So I wrote a script and I just click on it in gscript.
Does this officially make me a white belt, lowest rank possible dev? Aahaha
Pm me and I can send you the script if you want haha.
(Yes, you are all supposed to laugh and make fun of me now)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Atleast u know how to do a script, I dnt even know how to use ADB.. root guided by youtube, I dnt mod my phone w/o watching video carefully n step by step method..
Cheers.. future DEV
Sent from my HTC Vision using XDA App
Congrats on the script! It's get's easier now that you have the concept - then it gets hard again lol.
While we're on the subject of scripting - any reason you choose that system rw mount script? There's 3 ways I've seen it done and they are all completely different... maybe the have different functions?
Again, good job and I like your idea. I saves a lot of typing especially with those commands since we type them a lot.
I think just by writing a successful script.. you are already above MANY xda users.
Kudos.
jontornblom said:
$su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#chmod 777 /system
Click to expand...
Click to collapse
So this is the part where you tell me what it does, right?
omarsalmin said:
So this is the part where you tell me what it does, right?
Click to expand...
Click to collapse
His script mounts the system as rw.
Sent from my T-Mobile G2 using XDA App
Nice script
What I do is a little different. I have it saved as my initial command for terminal, so it starts whenever I use terminal.
The code I use is this:
export PATH=/data/local/bin:$PATH
su
mount -o rw,remount /system
I am obvlious though as to why you put yaffs2 and mtdblock3 and all that, I never thought it was necessary since it works just fine without it. I'm not too keen on linux syntax though so its probably obvious but I'm curious anyway.
Sent from my HTC Vision using XDA App
mejorguille said:
Nice script
What I do is a little different. I have it saved as my initial command for terminal, so it starts whenever I use terminal.
The code I use is this:
export PATH=/data/local/bin:$PATH
su
mount -o rw,remount /system
I am obvlious though as to why you put yaffs2 and mtdblock3 and all that, I never thought it was necessary since it works just fine without it. I'm not too keen on linux syntax though so its probably obvious but I'm curious anyway.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
That's what my question was too lol. It's a great script especially for his first but now he should make it less bulky. If it's being ran in terminal as a script then all he would really need is this:
Code:
#!/system/bin/sh
mount -o remount,rw /system
I don't believe you need to use su before running it but I always do just in case.
Of course you'll want to make a /system ro script (unmount) too so you're not always in mounted in rw access.
funkadesi said:
I think just by writing a successful script.. you are already above MANY xda users.
Kudos.
Click to expand...
Click to collapse
Haha, thanks!
I found that leaving out the yaffs2 etc didn't work. I read somewhere that you need this line with certain kernels. I wish I could give you a more learned answer though.
I'm thinking it's a good idea to put the system back in ro too, actually. Now I'll have made two scripts haha
Sent from my HTC Vision using XDA App
Not positive on all of this, so someone can correct me if I'm wrong, but
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
is used to mount system by accessing the NAND (hence the yaffs2 filesystem and mtdblock device). Many of the older Android guides use this command (since the older phones all used raw flash).
The Vision (and many of the newer phones) use an eMMC though, which has an FTL to present the NAND as a block device to the OS (just like a hard drive). This is why in many of the guides written nowadays, you'll see something more like this:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
This accesses the eMMC as a native block device (hence the ext3 filesystem). This is probably the "more correct" way of mounting the partition as it utilizes the actual FTL controller on the NAND as opposed to the more inefficient linux virtual block driver (what mtdblock does), so it's a little cleaner from a software development standpoint. Both commands accomplish the same thing though, so you could really use either.
The shortened form of the remount is what others have been listing:
Code:
mount -o rw,remount /system
Basically, since the system partition had already been mounted by the OS on boot, it should already know the proper way to remount it (i.e., you don't have to retell it the device or filesystem used). I don't believe this command will work on every ROM out of the box though (requiring either Busybox to have been installed or ro.secure=0 to be set in your default properties, maybe both).
Excellent and informative post! So is the reason why the
Mount -o rw,remount /system
Command doesn't't work for me is because busybox isn't installed? I'll test this out right now...
Also, I was thinking chmod 777 might be redundant because the system is already rw. Is this true? My understanding is the chmod 777 simply sets whatever path after it as modifyable. Is there a difference between rw and being able to modify files in linux?
Sent from my HTC Vision using XDA App
Hmm. When I try the stripped down command, I get the usage message...
Sent from my HTC Vision using XDA App
jontornblom said:
Excellent and informative post! So is the reason why the
Mount -o rw,remount /system
Command doesn't't work for me is because busybox isn't installed? I'll test this out right now...
Also, I was thinking chmod 777 might be redundant because the system is already rw. Is this true? My understanding is the chmod 777 simply sets whatever path after it as modifyable. Is there a difference between rw and being able to modify files in linux?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Well if you want to know if you have busybox just do this:
Code:
su
cd /system/bin
busybox
That should start busybox. It will say 'not found' if you don't have it - so if you need it the easy way is to use titanium backup to install it.
Btw, ianmcquinn that was very informative and well written. Thanks for explaining it so well.
Definitely have busybox. Definitely still just gives me the usage information...weird.
How do I set secure=0?
Sent from my HTC Vision using XDA App
ro.secure=0 is standard on most roms, so I asume you are just using a rooted stock build? You will need to unpack your kernel, change the ro.secure from a 0 to a 1, and repack the kernel. If you don't know how to do that, use this.
jontornblom said:
Definitely have busybox. Definitely still just gives me the usage information...weird.
How do I set secure=0?
Click to expand...
Click to collapse
What ROM you are using now? VillainROMZ?
Sent from my HTC Desire Z, using magic XDA app
AllWin said:
What ROM you are using now? VillainROMZ?
Sent from my HTC Desire Z, using magic XDA app
Click to expand...
Click to collapse
Virtuous 0.9.0
Sent from my HTC Vision using XDA App
I don't use Virtuous, but I would be shocked if it didn't already have ro.secure=0 set already. You can check by typing this in terminal:
Code:
getprop ro.secure
It should return a 0. This property is set in the ramdisk within your boot.img. To set it yourself, you would have to unpack the image, modify the setting in the default.prop file, repack the image, and then flash it back to your phone. As was said earlier though, pretty much all of the custom roms set this for you already.
Not sure what is going on in your case then. Maybe try running the mount command explicitly through busybox to see if that is the problem.
Code:
busybox mount -o rw,remount /system
If this works, sounds like you may want to reinstall busybox since the symlinks were not properly set up. Another thing maybe worth trying is to swap the order of remount and rw in the options. I've seen reports of this making a difference for some people, but have no clue why it should (maybe different versions of the mount command/busybox). Kind of a long shot. So try either of these commands:
Code:
mount -o remount,rw /system
busybox mount -o remount,rw /system
EDIT: In case you were curious, here's a link I had bookmarked about how to edit the boot.img. I'm sure there are others out there as well.
Does anybody know how to install the new YouTube (the one u find in cm7) and the new Android market in the official 2.1 rom
And also where I can find these apk
Btw I have already tried installing the new android market apk but a error appears
Sent from my GT540 using XDA App
For the Market is an update OTA normally expect and it will come by itself
Or if you have this script
For youtube, do the update on the android market
The new market needs android 2.2 minimum.
For new youtube search google for youtube apk.
Sent from my GT540 using Tapatalk
Here is the YouTube apk. http://www.mediafire.com/?ql6v72qia20wkh7
To install it, do this in a command prompt:
Code:
cd <directory where signed_YouTube.apk is>
adb push signed_YouTube.apk /data/local/tmp/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
rm /system/app/YouTube.apk
pm uninstall com.google.android.youtube
pm install /data/local/tmp/signed_YouTube.apk
exit
Man_u said:
For youtube, do the update on the android market
Click to expand...
Click to collapse
The new YouTube from the Market doesn't work on 2.1, thats why it doesn't show up in the Market. You need the signed_YouTube.apk because that is the ported one
effortless. said:
Here is the YouTube apk. http://www.mediafire.com/?ql6v72qia20wkh7
To install it, do this in a command prompt:
Code:
cd <directory where signed_YouTube.apk is>
adb push signed_YouTube.apk /data/local/tmp/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
rm /system/app/YouTube.apk
pm uninstall com.google.android.youtube
pm install /data/local/tmp/signed_YouTube.apk
exit
The new YouTube from the Market doesn't work on 2.1, thats why it doesn't show up in the Market. You need the signed_YouTube.apk because that is the ported one
Click to expand...
Click to collapse
Can I do this because I'm using 2.1 official
Sent from my GT540 using XDA App
Man_u said:
For the Market is an update OTA normally expect and it will come by itself
Or if you have this script
For youtube, do the update on the android market
Click to expand...
Click to collapse
Would I be able to do this with 2.1 official
Sent from my GT540 using XDA App
mohnim said:
Can I do this because I'm using 2.1 official
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
If your rooted, then you CAN do this. The app is the 2.2/2.3 one but ported to 2.1, it works perfect.
I have a Verizon tab that was rooted. I updated to gingerbread which removed root. Is there a way to root now that I have gingerbread?
Thanks!
you may try SuperOneClick 2.2 with ZergRush...
Thanks. I'll give it a shot.
Soundchasr said:
Thanks. I'll give it a shot.
Click to expand...
Click to collapse
Did it work?
Haven't had a chance yet.
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
receptr said:
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Telling me, I have gingerbread on mine and it does nothing but forceclose crap all over the place
Lakilaulea said:
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Click to expand...
Click to collapse
I was able to get mine rooted by using the kernel from Galaxy Cubed 3 ROM. Downloaded the whole ROM and flashed only the kernel in heimdall. Then I used adb to push the correct files to the system and fixed permissions and rebooted. Worked great.
UPDATE:
If people want to know the adb commands I used, here they are:
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell "cd /data/local/tmp/; rm *"
You can copy and paste these commands to a bat file and run it in a command prompt window. These were taken from a script used to root devices.
Here are links for the files you need. They are:
su
superuser.apk
busybox
They need to be placed in the same directory that you run the adb commands from.
SECOND UPDATE:
Rather than go through all this, go here:
http://forum.xda-developers.com/showthread.php?p=19678785
This is dsb9938's plain stock EI04 VZW ROM that is pre-rooted. Just flash in Heimdall and you are good to go. As long as you only wipe cache and dalvik, all your apps should stay intact.
Gingerbreak.apk should do the trick. Worked on my P1010
chris_toshiba said:
Gingerbreak.apk should do the trick. Worked on my P1010
Click to expand...
Click to collapse
It did not work on my VZW Tab. Someone said it is because it only works on 2.3.3 and older gingerbread and we have 2.3.5.
BTW, look at my earlier post (second update) to get a really easy way to have rooted stock 2.3.5 VZW Tab.
It costed me more than a day but finally it is done and my TF300T is unlocked and rooted. The biggest problem was finding and placing the steps in the right order. It turned out that the Asus tool for unlocking the bootloader on .29 does not work. So, these are the steps (and most easy), to unlock and root a TF300T on WW .29
1 Downgrade to .17 with the DE blob found here and the instructions. Follow step 2.
2 Download the Asus unlock tool from the Asus website (support.asus.com)
3 Download also the .29 file
4 Install the unlock apk and unlock your device
5 After rebooting you will see the message that your device is unlocked. Now the fastboot protocol is available. You need it to perform step 7
6 After unlocking install .29 the same way as you downgraded your device
7 Install CWM by following the instructions found here
8 On the bottom of the same treat there is explained how to root the device (just run a simple apk)
9 It could be the you have to install busybox from the market, but I'm not sure.
The main advantage of this method is that you have CWM installed also.
Suc6!
THIS was posted on May 23rd, and hidden in the CWM Recovery + Root thread with NO thanks given to it:
http://forum.xda-developers.com/showthread.php?p=26478502#post26478502
And THIS was my comment to it just a few minutes ago:
http://forum.xda-developers.com/showpost.php?p=26929082&postcount=176
The unlocked worked on my US .29
Sent from my VS910 4G using xda premium
If it's really true that the ASUS unlock does not work with .29 then ASUS is a bonehead.
"Use this to unlock .. and oh jeah, you have no warranty"
[unlocking]
"Uhh, what do you mean it does not work? Well good luck then at XDA since you messed up the warranty. No it's not our fault, you want to unlock..."
Tnx for pointing this out. Also tnx for providing a step to step overview.
Unlocked my .29 with no problem
keynith said:
The unlocked worked on my US .29
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Same here. I had the modded build.prop so.....
I set the original build.prop back in place and then did a factory reset. Once I did that, the unlock tool worked fine.
Ok so quick question...
My bootloader is unlocked and im on .17
I have the update .zip for .29, but every time I try to flash in recovery (teamwin) nothing happens. Just says "installing update" for well over 15 min. Any suggestions? Btw: tried flashing both zips... the 2nd inside the first and still nothing :/
Sent from my ASUS Transformer Pad TF300T using xda premium
Redownload the update and try again. Could be bad update. Or get CWM and flash a ROM
Sent from my Transformer Prime TF300T using XDA Premium HD app
keynith said:
Redownload the update and try again. Could be bad update. Or get CWM and flash a ROM
Sent from my Transformer Prime TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Didn't work :/
Plus I don't think I can get CWM flashed over teamwin. I think I read, that will brick it and have been too busy lately to check info on that. You see how long it took me to reply to this. Ugh! Sucks being busy all day. I'll keep looking around when I can. Thanks though. For sure
Sent from my ASUS Transformer Pad TF300T using xda premium
Rooting *without* downgrading (from .29)
Hello,
Since this is my first post on this forum I couldn't post it in the dev thread, so I post it here.
I just managed to root my TF300T without downgrading the firmware.
First, I decline all responsibility if you brick your device. Use the method and the binaries with extreme caution, although all should be ok if you follow step by step the following instructions.
Before starting, you should download the two binaries (debugfs and su) that are linked at the end of this post. And please read the instructions till the end before going into.
Here it is:
Rooting the Asus Transformer TF300T
===================================
: first, use known method to get write access to the /system partition
adb push debugfs /data/local/
adb push su /data/local/
adb shell
$ cd /data/local/
$ mv tmp tmp.back
$ ln -s /dev/block/mmcblk0p1 tmp
$ exit
adb reboot
adb shell
: some cleanup first
$ cd /data/local
$ rm /data/local/tmp
$ mv /data/local/tmp.back /data/local/tmp
: and now, let's do the dirty work
$ chmod 755 /data/local/debugfs
$ /data/local/debugfs -w /dev/block/mmcblk0p1
cd xbin
write /data/local/su su
set_inode_field su mode 0104755
set_inode_field su uid 0
set_inode_field su gid 0
quit
: done, let's reboot and get root !
adb reboot
adb shell
$ /system/xbin/su
# id
id=0(root) gid=0(root) ....
# exit
: cleanup remaining files
$ rm /data/local/su
$ rm /data/local/debugfs
Now here is the link to my dropbox containing the binaries and the source file for su. debugfs is part of e2fsprogs, and I didn't touch anything (I just struggled 24h to get it compiled for android, that's why I give it away ^^).
(link removed) (Well I have a link, but this forum won't let me post it...)
Regards,
milo
[edit] added the chmod 755 on debugfs
miloj said:
Hello,
Since this is my first post on this forum I couldn't post it in the dev thread, so I post it here.
I just managed to root my TF300T without downgrading the firmware.
First, I decline all responsibility if you brick your device. Use the method and the binaries with extreme caution, although all should be ok if you follow step by step the following instructions.
Before starting, you should download the two binaries (debugfs and su) that are linked at the end of this post. And please read the instructions till the end before going into.
Here it is:
Rooting the Asus Transformer TF300T
===================================
: first, use known method to get write access to the /system partition
adb push debugfs /data/local/
adb push su /data/local/
adb shell
$ cd /data/local/
$ mv tmp tmp.back
$ ln -s /dev/block/mmcblk0p1 tmp
$ exit
adb reboot
adb shell
: some cleanup first
$ cd /data/local
$ rm /data/local/tmp
$ mv /data/local/tmp.back /data/local/tmp
: and now, let's do the dirty work
$ /data/local/debugfs -w /dev/block/mmcblk0p1
cd xbin
write /data/local/su su
set_inode_field su mode 0104755
set_inode_field su uid 0
set_inode_field su gid 0
quit
: done, let's reboot and get root !
adb reboot
adb shell
$ /system/xbin/su
# id
id=0(root) gid=0(root) ....
# exit
: cleanup remaining files
$ rm /data/local/su
$ rm /data/local/debugfs
Now here is the link to my dropbox containing the binaries and the source file for su. debugfs is part of e2fsprogs, and I didn't touch anything (I just struggled 24h to get it compiled for android, that's why I give it away ^^).
(link removed) (Well I have a link, but this forum won't let me post it...)
Regards,
milo
Click to expand...
Click to collapse
Milo,
I want to give it a try, so can you pm me the dropbox link?
Thanks
Marco
Sent from my GT-I9000 using Tapatalk 2
First, thanks for your work. Why not just "edit" the URL if you can't post one yet. PEx w w w xyz. com. That would work Cheers
...via Tapatalk
Because I'm usually not a cheater ahah!
Here it is:
http : // db. tt/FBUNeVmo
Sent from my Desire HD using XDA
Hi!
$ /data/local/debugfs -w /dev/block/mmcblk0p1 -> cannot execute - Permission denied
cd xbin -> cd /system/xbin?
write /data/local/su su -> write: not found
What to do?
Sorry, I may have missed a chmod 755 debugfs.
A line preceded with $ is meant to be executed inside debugfs shell.
Tell me how it goes, I'll update the doc.
milo
Sent from my Desire HD using XDA
miloj said:
A line preceded with $ is meant to be executed inside debugfs shell.
Click to expand...
Click to collapse
Actually it is the other way round, sorry.
Everything following a $ is executed from the Android shell, and all non-prefixed line is executed in debugfs.
milo
Sent from my Desire HD using XDA
Here is Miloj's link for the necessary files: http://db.tt/FBUNeVmo
Miloj: Excellent work! Will you edit the OP with the correct code sequence, let's save us some bricks.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
/data/local/debugfs -w /dev/block/mmcblk0p1 -> Segmentation fault
cdma77 said:
/data/local/debugfs -w /dev/block/mmcblk0p1 -> Segmentation fault
Click to expand...
Click to collapse
OK it happened to me as well, and while trying to debug it, it then started to work without any change from me but some printf()...
I'll try to see if I can catch the exception and repost the binary.
Sent from my ASUS Transformer Pad TF300T using XDA
Frenchies are good, in'it ?
Miloj, anytime you want to help noobs like me to get root easier than what you explain, I'm interested. Maybe something compiled for linux challenged people...
Anyway, congrats to you !
miloj said:
OK it happened to me as well, and while trying to debug it, it then started to work without any change from me but some printf()...
I'll try to see if I can catch the exception and repost the binary.
Sent from my ASUS Transformer Pad TF300T using XDA
Click to expand...
Click to collapse
Major thanks to Sparkym3 for coming up with this exploit, and to Justin Case & Hashcode for helping do this on my tablet today.
Here are the files that you need:
http://www.reverendkyle.com/download/Superuser-3.1.3-arm-signed.zip
http://www.reverendkyle.com/download/Kindle_Fire_HD_ADB_Drivers.zip
Be sure to install ADB on your computer first!
http://www.reverendkyle.com/index.php/articles/130-how-to-install-adb-for-android-in-windows
The commands:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
The original instructions can be found here:
http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
lol, a whole 3 days, what took everyone so long?
Sent from my One X
I want to say don't release it until the 9 inch version comes out and we can root that too. Don't give amazon the details to patch it.
I think an alternate launcher would satisy lots of people without having to root.
supernoman said:
I want to say don't release it until the 9 inch version comes out and we can root that too. Don't give amazon the details to patch it.
Click to expand...
Click to collapse
I'm not sure when it will be released. I just wanted to tell all of the nay sayers to DEAL WITH IT.
reverendkjr said:
I'm not sure when it will be released. I just wanted to tell all of the nay sayers to DEAL WITH IT.
Click to expand...
Click to collapse
just tried adb shell and it says error finding device. any suggestions? how do i go into "developers" mode with the kindle fire hd?
http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
Sent from my SPH-L710 using xda premium
How complicated and how long of a process is this?
I'm not tech savvy but if not too difficult, I'll give it to a friend to attempt after I buy the Fire HD tomorrow!
Just tried and finally got to the adb shell portion but when I try to rm /data/local/tmp it gives me the following:
rm /data/local/tmp
rm failed for /data/local/tmp, Is a directory
so afterwards I tried just doing a ln -s /data/ /data/local/tmp and it says "link failed File exists" ... What am I doing wrong?
Just about to report that thee was a working root. Good guide
Sent from my Nexus 7 using Tapatalk 2
tenchichrono said:
just tried adb shell and it says error finding device. any suggestions? how do i go into "developers" mode with the kindle fire hd?
Click to expand...
Click to collapse
I have the same trouble... any ideas would be greatly appreciated!
---------- Post added at 08:35 PM ---------- Previous post was at 07:48 PM ----------
tenchichrono said:
Just tried and finally got to the adb shell portion but when I try to rm /data/local/tmp it gives me the following:
rm /data/local/tmp
rm failed for /data/local/tmp, Is a directory
so afterwards I tried just doing a ln -s /data/ /data/local/tmp and it says "link failed File exists" ... What am I doing wrong?
Click to expand...
Click to collapse
I got the drivers installed to fix my previous problem but now I have this problem above
tenchichrono said:
Just tried and finally got to the adb shell portion but when I try to rm /data/local/tmp it gives me the following:
rm /data/local/tmp
rm failed for /data/local/tmp, Is a directory
so afterwards I tried just doing a ln -s /data/ /data/local/tmp and it says "link failed File exists" ... What am I doing wrong?
Click to expand...
Click to collapse
The command should be "rm -r /data/local/tmp"
It removes the directory and its contents.
reverendkjr said:
I'm not sure when it will be released. I just wanted to tell all of the nay sayers to DEAL WITH IT.
Click to expand...
Click to collapse
I'm pretty sure rooting is not the problem everyone is concerned about. Flashing a different ROM will be the tricky part without a working custom recovery.
soupmagnet said:
I'm pretty sure rooting is not the problem everyone is concerned about. Flashing a different ROM will be the tricky part without a working custom recovery.
Click to expand...
Click to collapse
It's being worked on.
reverendkjr said:
It's being worked on.
Click to expand...
Click to collapse
Hey reverend, a little off topic, but could you post a video of root? I'll subscribe
Sent from my Nexus 7 using Tapatalk 2
ncvikingx97 said:
Hey reverend, a little off topic, but could you post a video of root? I'll subscribe
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It's funny that you should ask for that. I'm working on a video of it right now. :angel:
Cool. Sub
Sent from my Nexus 7 using Tapatalk 2
Success!! Thanks for posting these instructions
Also, for verification purposes, I was able to successfully install ROM TOOLBOX pro and after several reboots the 'rebooter' shortcut works...
Now this is exciting! This should really get the ball rolling on the whole development for this device
So how about the Play store? Any ideas how to get it on?