Related
I downloaded the mac files from xda and followed the instructions in the readme.txt file but whenever I plug in the command line:
# /data/local/redbend_ua restore /sdcard/zImage /dev/block/bml8
Goes through the blurb but then I get:
failed to read from /sdcard/zImage (Bad file number)
Thought I might have a corrupt file or something but I've downloaded it 3 times with the same result.
Can anyone help please?
Anyone?
Anyone?
xjedi
Nevermind. Got it.
Nevermind.
After wrestling with it for so many days, I got it to work by
cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml7 - Instead of this
# ./redbend_ua restore ./zImage /dev/block/bml7 - I changed it to this
and so the same with the other command for the next reboot for ..../block/bml8 as well
Now I'm happily doing backups and going to flash a new ROM. Woohoo!
I'm in a similar situation, have a mac n im trying to install cwm but I cant figure out from the instructions in the download. Can you please tell me exactly what you did and what you typed in the terminal box?
I followed this same procedure on my mac. I seem to remember running into this, but was able to get it working after trying one or two times.
Here is my suggestion. Learn how to use a linux command line (which is basically what the mac terminal is). I am quite familiar using the command line, so that knowledge along side the mac instructions for clockwork made this much easier. If you learn the basic commands (ls, grep, cd, chmod, etc), you will understand what the instructions are telling you to do much better and have much more success getting this to work. And with time, you'll find these tasks are more easily completed on the mac. No need to screw around with drivers or clunky tools (sorry, I don't like odin).
Sorry I can't be of more help, but I can tell you it does work. If I remember correctly, you can't paste into the terminal. So, if you are typing the commands manually, double check all your spellings before entering them. Good luck
Sent from my SCH-I500 using XDA App
my advice is to boot camp your mac
Sent from my SCH-I500 using XDA App
Boot camp is best, you want Odin around just in case
There's also a pretty good tutorial somewhere in here on how to install ClockworkMod using a Mac. But also not a bad idea to use bootcamp or some virtual machine to install windows on a Mac for Odin purposes... now if I can get my lazy butt to fry's and buy windows 7 for my Mac... lol
Sent from my SCH-I500 using XDA App
alxb577 said:
I'm in a similar situation, have a mac n im trying to install cwm but I cant figure out from the instructions in the download. Can you please tell me exactly what you did and what you typed in the terminal box?
Click to expand...
Click to collapse
@alxb577
These are the instructions I used but with the little changes I did to make it work for me.
Copy zImage to the root folder of your SD Card
Open Terminal
$ cd (path to android sdk)/tools
$ ./adb push (path to redband_ua)/redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
(username)$ ./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore ./zImage /dev/block/bml7
--Phone Reboots--
$ ./adb shell
$ su
# cd /data/local
# ./redbend_ua restore ./zImage /dev/block/bml8
--Phone Reboots--
i keep getting "n o such directory" on the first command. i know i have the directory because i copied sdk to it so i could have a shorter path name.
username$ ./adb push /androidsdk/tools/redbend_ua /data/local
-bash: ./adb: No such file or directory
am i entering this correctly. been up all night working on this because i cant use odin on any of my three different xp machines. i keep getting floating point error r6002 when i try to opin odin on those eventhough i just used odin two days ago to flash my galaxy tab.
can anyone help me with these commands or help me fix my floating point errors o nmy xp machines? do these adb commands work in windows as well?
When in terminal, type "cd .." a couple of times, then "cd and*" and that will change your directory to the android sdk folder. Then "cd tools" to point it to the tools folder. Try your commands after that
Thanks for the help but, I ended up just running those adb commands in windows and it worked!! Good to know though incase I have to whip my hackintosh back out when I get another fascinate.
A side note, can someone point me to info on fixing the floating point error r6002 i got on all three of my xp machines when trying to run odin? This was the whole reason i was trying to install cwmod with my mac.
Sent from my GT-P1000 using Tapatalk
Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might, like mine, just blink on and off for a while trying to flash what it thinks it finds is already flashed but what just gives an error!
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests done in that post on which rom work best for which model.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils im used to in the world of *nix was missing from the 2.2.2 image kindly provided by Huawei ( The Norwegian Telenor image i might add that the camera on a model 101 will not work with!) so i found an easier way! push push push!
Here's what i did, for convenience ill try making it a script, but be prepared to copy these commands manually instead! For windows simply remove the ./ and add .exe .
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adb binary that comes with SOC is a simpler route if your just in for a quick root fix. Simply rename the appropriate adb for your system and use this method.
The simplest thing to do i guess is to copy Exploits/psneuter or gingerbreak to the ADB folder (in SuperOneClick's folder) and go on from there, also copy su-v3 (rename it to su) and Superuser.apk from "Root/" to the folder (ADB), or if you choose to, rewrite this "script" with the appropriate paths. Im unsure if the following script will work in every case, so you might want to do it manually, but most should get the drift, if you are not comfortable with this procedure you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your USB mode to "Developer" mode
AND BE ROOT ON YOUR MACHINE!
Code:
#/bin/bash
echo "The BackAsswardsRootScript!\n\n"
echo "Lets start the adb server.\n\n"
./adb kill-server
./adb start-server
echo "Pushing the exploit psneuter onto the device.\n\n"
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter"
./adb push busybox /data/local/tmp/busybox
./adb shell "chmod 4755 /data/local/tmp/busybox"
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "We should be root now, making sure.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
./adb shell " /data/local/tmp/busybox mount -o rw,remount /system"
echo "Pushing the system files in place\n"
./adb shell "/data/local/tmp/busybox cp /data/local/tmp/busybox /system/bin/busybox"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox"
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only, just for kicks!
echo "Remounting the filesystem as Read-Only\n\n"
./adb shell "busybox mount -o ro,remount -t /system"
echo "You should now be rooted my friend.\n Enjoy!\n"
Please help feed my Linux addiction! Go to http://threader.zapto.org and click Donate!
Rooting S7 using Gingerbreak
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.
Cool, theres a gingerbreak exploit in the superoneclick package also, i tried that after i though psneuter didnt work, just a matter of replacing psneuter with gingerbreak. Did you use this method though or did you find some other way?
I didn't change or replace anything. My terminal skills are not on a level to have the guts anyway.
I simply updated from S7V100R001C43B010 to S7v100R001C98B021.
Then ran the Gingerbreak 1.2 exploit.
Interesting, yeah the gingerbreak exploit will work, when i wrote the fist post i used the gingerbreak exploit instead of the psneuter one thinking psneuter didnt work, turns out it did though and i went back to that one as its designed for 2.2.2, didnt know of this wrapper though, thanks!
Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
threader said:
./adb shell "chmod 0755 /data/local/tmp/psneuter
Click to expand...
Click to collapse
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"
threader said:
Well this was a bit of a mess!
Firstly updating:
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html I followed this nice writeup. Be sure to delete the log file in dload for the second round of the upgrade as your device might like mine just blink on and off for a while trying to flash what it finds is already flashed but what just gives an error. !
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html Links to 2.2.2 Brazil which is the best for the 101 apparently, some tests there on which roms work best for which models also.
Now,
REMOVE YOUR SDCARD IF ANY! AND REBOOT THE DEVICE ! THIS HACK RELIES HEAVILY ON HIGH STRANGENESS AND SPOOKY ACTION AT A DISTANCE!
Originally i though modifying an ol doroot.sh script to using the psneuter exploit from SuperOneClick i would manage to root the device. Not without some fuzz, no. Firstly i discovered "cp" and many basic fileutils was missing from the 2.2.2 image kindly provided by Huawei (Norwegian Telenor image, that i might add, the camera on a model 101 will not work with!) soo i found an easier way! push push push!
Heres what i did, for convenience ill try making it a script, but im making it as i type this post so this is untested as a script(!) Be prepared to copy these commands instead!
Now, to make this work, simply get SuperOneClick from http://shortfuse.org/?page_id=2 and unzip, i used the adb from the google android sdk, but i guess the adblinux binary that comes with SOC will work just as well, simply rename it to adb and use this method. The simplest thing to do i guess is copy Exploits/psneuter to the ADB folder (in SuperOneClick's folder) and go from there, also copy su-v3 (and rename it to su) and Superuser.apk from Root to the folder (ADB), or rewrite this "script"/collection of commands i used" with the appropriate paths. Im unsure if the following script will work as is as i said, so you might want to do it manually, but most should get the drift, if not you probably have no business or reason rooting the device in the first place. Disclaimer; if this bricks your device don't blame me, this is a fact of "it worked for me", your results may differ.
Be sure to set your usb mode to Developer mode
BE ROOT!
#/bin/bash
echo "The backasswardsrootscript!\n\n"
echo "Lets start the adb\n\n"
./adb kill-server
./adb start-server
./adb push psneuter /data/local/tmp/psneuter
./adb shell "chmod 0755 /data/local/tmp/psneuter
echo "Now we run the root exploit.\n\n"
./adb shell "./data/local/tmp/psneuter"
echo "Should say we are already root now.\n\n"
./adb root
echo "Remointing the FS as RW!\n\n"
# This really should be /dev/block/mmcblk0p1, i have no idea why this works.
./adb shell "mount -o rw,remount -t ext3 /dev/block/mmcblk1p1 /system"
# Now instead of copying using cp or moving with mv, considering "cp" was missing
# and mv just didnt work for some reason...! I found just pushing the files straight to the
# system after remounting worked just fine
echo "Pushing the system files in place\n"
./adb push su /system/bin/su
./adb push Superuser.apk /system/app/Superuser.apk
./adb push busybox /system/bin/busybox
echo "Correct permissions might be nice.\n"
./adb shell "chmod 4755 /system/bin/busybox
./adb shell "chmod 4755 /system/bin/su"
./adb shell "chmod 755 /system/app/Superuser.apk"
# Lets go back to read only just for kicks!
echo "Remounting the filesystem as Read-Only\n"
./adb shell "mount -o ro,remount -t ext3 /dev/block/mmcblk1p1 /system"
echo "You should be rooted my friend\n Enjoy!\n BE SURE TO DONATE TO SUPERONECLICK!!!"
# One of the main strangenesses i found was the block device was logically enough placed on
# partioton 1, of block1 which really should have been block 0 part 1, but that doesnt work.
# So it boils down to that this shouldnt work but does for no apparent reason(!).
# even /etc/mtab says that mmcblk0p1 is mounted to a non existent /mnt/dcard
# as an EXT4 partition which isnt supposed to be supported until 2.3.x
Click to expand...
Click to collapse
Dear S7 users,I am using the ideos s7 by Teltra supllier and i did unlock sim by norwegian rom.I read a lot of document but i didnt find out an easy way to run clockwork that i can run cook rom,can u help me how to run it in easy way.Thanks and appreciate that.
http://www.androidtablets.net/forum...wegian-2-2-2-s7v100r001c57b111.html#post82863
PuZZleDucK said:
Just granted su superuser permissions on the Australian s7
Great work. Just noticed a missing final quotation mark:
Probably works because of the end of line but should be:
./adb shell "chmod 0755 /data/local/tmp/psneuter"
Click to expand...
Click to collapse
Great! Thanks! Ops, yeah missed that, fixed now, thank you for pointing that out. I haven't spent much more time on this. the pad has pretty much been untouched since i moved house. I would like to make this easier for less technical inclined here but its just a matter of replacing ./adb with adb.exe if your on windows. Besides, i don't want to be at fault for bricking someone. And maybe i could write some simple application for installing Gnu/Linux as well, ( http://forum.xda-developers.com/showthread.php?t=1109730 ) but that will have to wait until someone bribes me or hits me over the head i guess.
tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..
---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------
Maniacnl said:
Just too inform you. I've just succesfully rooted the Indonesian 2.2.2 running on a
S7-105 using Chainfire's Gingerbreak v1.2.
Click to expand...
Click to collapse
tell me how you did it. i have a s7 - 105 too. please tell me the full tutorial, beginning to the end. cause i'm new to this android stuff. please..
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?
It took some doing, but after following the instructions in this link:
http://forum.xda-developers.com/showthread.php?t=2559915
I was finally able to root my Nook Glowlight. The instructions are kind of sprawled out and extremely unclear so I will sum up.
As always, you will need the ADB. In order to install the ADB, you need the Java Development Kit and the Android Studio (formerly known as the Android SDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://developer.android.com/sdk/installing/studio.html
How to obtain root via ADB: The ONLY way you can root is using Windows. I was successful on Windows 7 32 bit, but it may be possible on other versions.
step 1) install bootloader driver.
You need to grab the drivers from here (bnusbdrivers.zip):
http://forum.xda-developers.com/showpost.php?p=49665945&postcount=279&nocache=1&z=184593200683593
then, open the Device Manager (on Windows). Be ready to right click on the new device 'omap3660' that shows.
With the nook turned completely off, plug in a USB cable. you will have less than 3 seconds to right click the new omap3660 device that shows up in the system profiler.
If you were successful and you right clicked on it in time, manually install the Barnes & Noble USB driver (there are entries added to the generic Google drivers for both the TI Omap 3660 bootloader and the ADB device after you modify the uRamdisk later on)
***NOTE***
If you WEREN'T successful on your first try (took me THREE times to get to it in time), you aren't going to get another chance to install the drivers. At least not easily anyway, because after Windows tries to automatically install the drivers for the bootloader and fails, it will disregard the device any time it shows up after that. So, you are going to need to delete the registry entries that it created, which in my experience was easier said than done. Even admin access was not sufficient to make the necessary changes to the registry.
You will need to launch regedit.exe using another tool called psexec which is available here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
after you download the pstools package, copy those .exe files to C:\Windows\System32\ (in order to add them to $PATH in cmd.exe)
Then, once you've installed the pstools commands to C:\Windows\System32\, run cmd.exe as admin (right click it and select 'run as administrator') and then open regedit.exe with the following command
Code:
psexec -s -i -d regedit.exe
Then, once regedit is open you need to find the keys created by the Nook bootloader and delete them. The Nook bootloader's device ID is 0451:d00e
You are going to be looking in HKEY_LOCAL_MACHINE\Current Control Set\enum\usb\ for the keys with the bootloader's device IDs. There may also be keys generated in control set 001 and 002 as well. Delete all of those keys and then reboot your computer. Then with the nook power off completely, repeat the process from the first step. eventually you will be successful installing the bootloader driver.
Step 2) temporarily boot with uRamdisk-noogie
you need to download omaplink.exe from here:
http://www.temblast.com/android.htm
and you also need to download the four files which allow you to temporarily mount the boot partition; omap3_aboot.bin, u-boot-ng2-exp-v03.bin, uImage-ng2-130-stk and uRamdisk-noogie.
They are available here:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
download usbboot-ng2-images-noogie-v1.zip
The next part is easy.
Extract the .zip file and then fire up cmd.exe. cd into the directory of the newly extracted .zip
in the new working directory, enter the command
Code:
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Then, with the Nook powered all the way off and omaplink running, plug it in and a few seconds later, after the device boots up all the way, you will be looking at the contents of the boot partition instead of the internal storage like normal.
Step 3) Edit uRamdisk
you will need to download bootutil.exe from here
http://www.temblast.com/android.htm
copy bootutil.exe to C:\Windows\System32
with the boot partition mounted, copy uRamdisk to your computer and extract the files init.rc and default.prop, eg;
Code:
bootutil /x /v uRamdisk init.rc default.prop
then using notepad++ (available here: http://notepad-plus-plus.org/) edit the files as follows
default.prop
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
and
init.rc
comment out lines 375 and 392-399
(do this by adding a # to the beginning of the line)
uncomment line 215
(do this by deleting the # at the beginning of the line)
save both files and then repack them into uRamdisk
Code:
bootutil /r /v uRamdisk init.rc default.prop
copy uRamdisk back onto the Nook, eject the disk and power off the device. Reboot and you should be able to connect to ADB via WiFi
eg;
Code:
adb connect 192.168.0.10
replacing '10' with whatever IP your Nook is grabbing from your router.
Step 4) Full Root
at this point, you have root access via ADB only. You will not have root access in any apps like Root Explorer, Terminal, TiBackup, etc.
In order to finish PROPERLY rooting your Nook, you need to install 'su' to /system/bin/ and install the superuser.apk
Code:
adb connect 192.168.0.10
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
reboot your device one more time and then you will be fully rooted.
*** Note ***
this devices firmware seems to be a strange hybrid between donut and eclair, although it purports itself to be Android 2.1. The Superuser.apk and su binary came from an old Cyanogenmod 4.6 build in case anyone was wondering (Android Donut). The ones from Cyanogenmod 5 (Android Eclair) do not work. you will get the 'install failed older sdk' error.
installing busybox
I tired installing busybox by using the stericson busybox pro.apk. It would always freeze at 6.47%.
I figured out that if I grabbed an older version of the busybox binary and pushed it to /system/xbin manually and then chmodded it to the proper permissions, auto updates and proper symlinking work using the busybox app
Code:
adb shell mount -o remount, rw /system
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Then reboot, and run the busybox app to update and create symlinks.
enjoy!
installing nano and bash
Code:
adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/
and then in terminal emulator under 'Preferences' change the initial command to
Code:
export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;
and finally
Code:
adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit
nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
As far as remounting /system as ro, I would HIGHLY recommend just rebooting at this point, otherwise your nook might be stuck in a weird pseudo-rooted state. Probably won't cause any problems, but why risk it?
Thanks for clarifying the line number. I will make the appropriate edits to my instructions. I was working off the top of my head and couldn't remember what exact line the ADB over TCP config was, as I just used ctrl+w '5555' to find it myself.
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
darz said:
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
Click to expand...
Click to collapse
N00b-un-2 said:
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
Click to expand...
Click to collapse
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
darz said:
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
Click to expand...
Click to collapse
Sorry for the really noob question, I have rooted, wifi adb running and installed apps as per your instructions, but I can't seem to access any of it on the nook. How can I get access to the launcher I installed?
You mentioned pre-edited images, do any of those come with the apps I need to get access to a custom launcher?
Cheers,
Dariusz
==============
Updated: All sorted
==============
For some reason had some issues with ADW launcher, Launcher pro worked fine.
ps I think I made a mistake with the su step I suggested, if you run a one line shell command I don't think it keeps su privileges, so I believe you need to run commands within the shell as per below:
adb shell
mount -o remount, rw /system
/system/bin/su
mkdir -p /system/xbin
exit
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Noob
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
The above instructions from N00b-un-2 should work fine running a vm with parallels on your Mac.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
valentin1985 said:
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
Click to expand...
Click to collapse
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
darz said:
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
Click to expand...
Click to collapse
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
thenookieforlife3 said:
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
Click to expand...
Click to collapse
So far so good,but now what?
valentin1985 said:
So far so good,but now what?
Click to expand...
Click to collapse
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
thenookieforlife3 said:
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
Click to expand...
Click to collapse
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
valentin1985 said:
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
Click to expand...
Click to collapse
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
thenookieforlife3 said:
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
Click to expand...
Click to collapse
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
N00b-un-2 said:
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
Click to expand...
Click to collapse
Well, as I ONLY use Windows and Powershell ISE has a nice-enough layout for my purposes, I use it. That's why I gave a tip on it.
Actually on a lot of installs just typing adb in the command console won't work either unless it's got the path variable set up correctly, I find it easiest to just right click and choose run as administrator, no need for the path to be setup.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
FW 1.2.1
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
real-6 said:
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
Click to expand...
Click to collapse
This rooting procedure is for the new Nook GlowLight with firmware 1.3.1. Your device is a Nook Simple Touch with GlowLight, which can be rooted very easily using the rooting package here.