My Kindle fire hdx 8.9 worked normally since I bought it. Yesterday I remove the signature to install google service, and the wrong was it can't restart and I reset it to the factory from recovery. Now it still rest on the colored "kindle fire". But it seems some processes have been loaded because the MTP devices can be found in PC and the adb mode seems work normally. I think some steps losed in the boot. Can I recover it by adb mode or other methods? Thank you.
I reset it to the factory from recovery.
Click to expand...
Click to collapse
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
ONYXis said:
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
Click to expand...
Click to collapse
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
tianlie said:
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
Click to expand...
Click to collapse
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
ONYXis said:
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
Click to expand...
Click to collapse
"adb push services.odex /data/local/tmp" This command give an error: device not found.
Does it need the file "services.odex"? Where?
Thanks a lot.
The complete response:
D:\win32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount /system
mount -o remount /system
[email protected]:/ # rm /system/framework/services.odex
rm /system/framework/services.odex
[email protected]:/ # adb push services.odex /system/framework/
adb push services.odex /system/framework/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # chmod 755 /system/framework/services.odex
chmod 755 /system/framework/services.odex
Unable to chmod /system/framework/services.odex: No such file or directory
10|[email protected]:/ # reboot
reboot
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
ONYXis said:
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
Click to expand...
Click to collapse
It should be 14.3.2.5. OK. I wait you.:good:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
ONYXis said:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
Click to expand...
Click to collapse
That's great! Kindle is upgrading... Select language, register, the desktop come back.
Thank you, ONYXis, you are my god!:good:
To others, don't think the factory set is best.
Thank you again.
Related
This guide is for people who want root but want to keep their stock rom, not breaking the warranty, unlocking bootloader etc.
A proud ubuntu user, I am writing this in a new thread purely because the manual rageagainstthecage method and SuperOneClick method did not not work for me, see link to my conclusion below if you care
http://forum.xda-developers.com/showpost.php?p=11305312&postcount=2526
What did work however was via adb shell using psneuter and its fairly simple if you follow the following commands.
This guide assumes you know how to get access to the shell via adb, if you dont then search elsewhere.
OK lets get to business!
1. Download the attached nexus_one_softroot.tar from the bottom of this post and extract contents to the same folder as adb
2. Open up your terminal, cd to the same folder as adb and the extracted files
3. Enter the following commands:
Code:
sudo ./adb push psneuter /data/local/tmp/psneuter
sudo ./adb push busybox /data/local/tmp/busybox
sudo ./adb push su /data/local/tmp/su
sudo ./adb shell chmod 755 /data/local/tmp/psneuter
sudo ./adb shell chmod 755 /data/local/tmp/busybox
sudo ./adb shell chmod 755 /data/local/tmp/su
sudo ./adb shell
After this you should see only a $ which tells us that we at the android command line with user privileges only, lets continue
Code:
$ cd /data/local/tmp
$ ls
busybox
su
psneuter
$ ./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
You will now be kicked out of android shell, lets go back in
Code:
sudo ./adb shell
After this you should see only a # which tells us that we root baby! If you want to double check issue this command
Code:
# id
uid=0(root) gid=0(root)
Lets continue on. From this point we will install busybox and su which will make root permanent
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /data/local/tmp
# ./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
# busybox cp su /system/bin
# chmod 4755 /system/bin/su
# exit
For some reason I sometimes have to enter exit twice to leave the android shell. Again, re-access the android shell
Code:
sudo ./adb shell
Now in the android shell we can finish up
Code:
# su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
# exit
Lastly we must install Superuser, and I did this from the android market so I knew its the latest version, its simple to get, less command input etc.
Now you have root! I hope this was simple enough to follow, I have not really written a guide before but from lots of searching I just could not find a solution for my Nexus One 2.2.1 FRG83D, especially any guide that uses psneuter.
Anyway, glad to contribute
EDIT - also, being new to starting threads, this may not quite be in the right section of the forum, sorry if thats the case mods
How to manually root. Download and unzip the SuperOneClick zip file and...
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
shawnbuck said:
What OS and software are you running? I had the same problem on Ubuntu 10.10 x64, but was able finish the process by completing it by hand. If your brave enough to use the command line to do the process, I can provide the steps.
Click to expand...
Click to collapse
Could you? I have this same problem trying to root on my mac.
Sent from my MB860 using XDA App
I basically have this:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v1 /sdcard/
./adbmac push su-v2 /sdcard/
./adbmac push busybox /sdcard/
./adbmac push Superuser.apk /sdcard/
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
./adbmac remount
./adbmac shell
(the following 3 steps may fail which is OK)
# mv /system/bin/su /system/bin/su.bak
# mv /system/xbin/su /system/xbin/su.bak
# mv /system/xbin/busybox /system/xbin/busybox.bak
# busybox cp /sdcard/su-v* /system/xbin
# cd /system/xbin
(try to execute both su-v*, whichever works keep and renamed to su. For this example we'll assume su-v2 is the correct su)
# rm /system/xbin/su-v1
# mv /system/xbin/su-v2 /system/xbin/su
# busybox cp /sdcard/Superuser.apk /system/app
# busybox cp /sdcard/busybox /system/xbin
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# busybox ln -s /system/xbin/su /system/bin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
In this steps you put up previously, you missed remount the /system partition rw.
Also, what OS & software are you guys using? I'm curious to find out what is causing this problem, so we can correct it in SuperOneClick.
Ubuntu 10.10 x64
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# mount -o remount,rw -t yaffs2 /system
Click to expand...
Click to collapse
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
shawnbuck said:
In this steps you put up previously, you missed remount the /system partition rw.
# busybox mv /data/local/tmp/su /system/xbin
Click to expand...
Click to collapse
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
gdanko said:
Please do, I have most of it down.
su, busybox, Superuser are installed and permissions set, but I still get permission denied when I type "su". What am I missing?
Click to expand...
Click to collapse
gdanko said:
# mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p12 /system
Click to expand...
Click to collapse
Whoops, that slipped by. In any case, you can check what /system is mounted on by checking /etc/mtab.
Still getting permission denied when I type su
How are you using su directly?
Also, have you installed superuser and root checker from the market?
Add these steps to the end:
# chmod 06755 /system/xbin/su
# chmod 0755 /system/xbin/busybox
# reboot
When the phone is up, adb shell back in
Unlock the phone
Type su in the console
Accept the Superuser prompt
I am now rooted
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
I've noticed that the phone doesn't like when you call reboot from the terminal on it.
Also, put the instructions in the first post for anyone in the future.
gdanko said:
This should work:
./adbmac push psneuter /data/local/tmp
./adbmac push su-v2 /data/local/tmp
./adbmac push busybox /data/local/tmp
./adbmac shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
# exit
$ exit
./adbmac remount
./adbmac shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 06755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
$ exit
./adbmac install Superuser.apk
./adbmac reboot
Click to expand...
Click to collapse
Perfect, thanks!
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
agentdr8 said:
Might want to update chmod command for /system/xbin/su from 06755 to 6755. I found that after copy 'n pasting these, /system/xbin/su wasn't suid and sgid so it would still give the permission denied error when trying to run su from adb shell.
Click to expand...
Click to collapse
I can confirm this, typing `chmod 06755` doesn't work for me.
Is there a reason we need to set the sgid bit as well?
Probably doesn't need setgid but I left it since it was part of the original instructions.
try with acer liquid mini failed
adb push psneuter /data/local/tmp
adb push su-v2 /data/local/tmp
adb push busybox /data/local/tmp
adb shell
$ busybox chmod +x /data/local/tmp/psneuter
busybox 'permission denied'
what should i do? i am using ubuntu 10.10..thanks for your help...
This thread is designed for representation of the current progress on the Nook Tablet rooting and exploits, the second post will contain how to guides so you can learn to work on it for you self. REMEMBER I DO THIS FOR FUN, please respect the thread as well as others opinions
OLD UPDATES AT THE END OF THIS POST.
First off if you haven’t read the wiki yet to know what is currently in the device you should look here.
Also you should look at the http://www.nooktabletdev.orgfor information on the Nook Tablet Development process. - Thanks to dj_segfault
Rooting ScriptsWindows: Root, OTA block, De-bloat, Gapps Thanks to Indirect
Mac/Linux: Rooting script Thanks to t-r-i-c-k
Mac/Linux: Root,OTA Block, Gapps
CURRENT PROGRESS
adb connection: COMPLETE
adb root: COMPLETE
busybox:COMPLETE
permanent root: COMPLETE BY INDIRECT
GApps and Market: COMPLETE BY INDIRECT & Anlog
recovery mode: COMPLETE BY nemith
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THANKS TO NEMITH
bootloader: Locked and Signed Irrelevant
uboot: CRACKED BY BAUWKS
THANKS TO BAUWKS
Loglud said:
bauwks method uses the flashing_boot.img to his advantage, and since it is not checked by security, effectively he has made an insecure uboot. While this is not an unlocked bootloader, it is a way to get around the security, and enable custom recovery and higher level processes to be run.
I have been looking at this line of code for a long time, and as im sure hkvc and bauwks saw it is a large (but 100% necessary) flaw:
distro/u-boot/board/omap4430sdp/mmc.c: 559 : setenv ("bootcmd", "setenv setbootargs setenv bootargs ${sdbootargs}; run setbootargs; mmcinit 0; fatload mmc 0:1 0x81000000 flashing_boot.img; booti 0x81000000");
Without this line of code, it would be impossible for any one but the factory whom could JTAG flash (but since it is secured, most likely they also have to make a flashing_boot.img).
Click to expand...
Click to collapse
12/9/11:
UBUNTU is here, thanks to ADAMOUTLER
http://www.youtube.com/watch?v=PwUg17pVWBs&hd=1
Keep in mind this is only an overlay verson but it is prof that one day we might be able to push roms and kernels over existing ones, then hijack then (next work) and then use them.
Please PM me or post if you know anything else, and or want to add anything.
Usefull threads
Usefull threads:
ROOTING:
Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!] Thanks to indirect
Noot Tablet - Easy root & Market on MAC (1 download, 1 script to run) Thanks to t-r-i-c-k
[Windows/Linux] Unroot and uninstall gApps for the nook tablet [Scripts] Thanks to indirect
MODS to Default Rom:
[Full Mod + Root + OTA block] Snowball-mod: Full Modification Root [1/6/2012] Thanks to cfoesch
[DEV][WIP] Enable init.d scripts and build.prop mods for Nook Tablet! Thanks to [DEV][WIP] Enable init.d scripts and build.prop mods for Nook Tablet! 1 Attachment(s) (Multi-page thread 1 2 3 ... Last Page)
Originally Posted By: diamond_lover
Kernels:Coming Soon
ROMS:Coming Soon
APPS:
[Tutorial][WIP] Installing alternative Keyboards on the NT. Thanks to robertely
[DEV] - HomeCatcher Redirect n Button to any Launcher Thanks to gojimi
Hidden Settings App Updated 12/30/11 Thanks to brianf21
Replacement SystemUI.apk v2: Permanent back and menu buttons, n as Home button Thanks to revcompgeek
DEVELOPMENT:
[Dev]Files of interest in the system Thanks to indirect
[REF] Nook Tablet Source Code Thanks to diamond_lover
BHT Installer (Basic Hacking Tools) Thanks to AdamOutler
[Stock Firmware]Restore Barnes & Nobel Nook 1.4.0 from SDCard Thanks to AdamOutler
Guides
Table of Contents
Enableing adb Connection (eab1)
Rooting using zergRush (rug2)
Installing busyboxy (ibb3)
Permanent root (pr4) THANKS TO INDIRECT
Installing GApps (aga5) THANKS TO ANLOG
Full system restore/wipe (fsr6) THANKS TO INDIRECT
Enableing adb Connection (eab1)
Install the andriod SDK that is required for your Operating system.
NOTE: This will requries the SDK, and JDK both of which can be downloaded by clicking the links, downloading and installing it.
Run the andriod SDK Manager and Install "Andriod SDK Platform-tools"
[*]Modify your adb_usb.ini file to read such as the following:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080
This will be in your /home/{username}/.andriod/ folder for mac and linux
This will be in your C:/Users/{username}/.andriod folder for Windows.
ADB is now enabled for your device, however it is not ON your device. YOU MUST DO THIS EVERY TIME YOU WISH TO ADB INTO YOUR DEVICE.
[*]To do this you will need to download any app, and attempt to install it.
You can use this app if you need.
[*]Click on the Package Installer, and then a prompt will pop up asking if you want change the settings to allow 3rd party apps.
*DO NOT ENABLE IF YOU WISH TO ACCESS ADB*
I am working on a way to have it enabled by default.
[*]In the settings page you should see *2* USB Debuggin modes.
[*]Press them both and accept the prompt.
[*]PLUG IN YOUR DEVICE.
Note* You should see the Android Development icon on the bottom of the screen.
ADB will now be able to see your device. How ever you will need to restart the server before it sees it.
Rooting using zergRush (rug2)
This is for the poeople whom have access to adb. You will also need this file. Unzip the file.
Type in the following command (while in the folder with the zergRush Binary):
Code:
adb push ./zergRush /data/local
[*]Once thats installed run this:
Code:
adb shell chmod 777 /data/local/tmp
[*]And lastly:
Code:
adb shell /data/local/zergRush
[*]You are now rooted (only for this reboot)
Installing busyboxy (ibb3)
You will need root and the following busybox file.
Type in the following command while in the location where busy box was downloaded to:
Code:
adb push ./busybox /data/local
[*]Busybox works by calling binaries from a file outside of /system/bin/. We must make this file by issuing the following command:
Code:
adb shell mkdir /data/busybox
[*]Lets make sure we can install busybox without permission probles:
Code:
adb shell chmod 777 /data/local/busybox
[*]Next install busybox in the folder:
Code:
adb shell /data/local/busybox --install
[*]We now need to take the /system/folder, and mount it as a writeable folder:
Code:
adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
[*]Link it into bin:
Code:
adb shell ln -s /data/local/busybox /system/bin/busybox
You now have busybox installed
Permanent root (pr4)
THANKS TO INDIRECT for Files and Scripts
We will need SU and Superuser.apk
First we need to install the Superuser.apk:
Code:
adb wait-for-device install Superuser.apk
adb remount
[*]Next lets go ahead and push the su application up to the /data/local/ folder
Code:
adb push su /data/local/
[*]Next we will need to change the permissions and cp su from the /data/local/ folder to the /system/bin/
Code:
adb shell chmod 4755 /data/local/su;mount -o remount,rw /dev/block/platform/mmci-omap-hs.1/by-name/system /system;busybox cp /data/local/su /system/bin
Installing GApps (eab1)
THANKS TO ANALOG and INDIRECT for Scripts
First things first we need to download the GAPPS. The most reacent one is this one or get the most recent one here.
[*] Unzip and navigate to the most root folder of that package in your shell.
[*]We need to verify that adb is booting into root. To do this we can issue the command:
Code:
adb shell id
If id doesn't return root then you will need to re-zergRush your device
[*]Now it is time for us to export the apps to the directories.
Code:
adb shell mount -o remount,rw /dev/block/platform/mmci-omap-hs.1/by-name/system /system
adb push system/app/CarHomeGoogle.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system/app/FOTAKill.apk /system/app/
adb shell chmod 644 /system/app/FOTAKill.apk
adb push system/app/GenieWidget.apk /system/app/
adb shell chmod 644 /system/app/GenieWidget.apk
adb push system/app/GoogleBackupTransport.apk /system/app/
adb shell chmod 644 /system/app/GoogleBackupTransport.apk
adb push system/app/GoogleCalendarSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleCalendarSyncAdapter.apk
adb push system/app/GoogleContactsSyncAdapter.apk /system/app/
adb shell chmod 644 /system/app/GoogleContactsSyncAdapter.apk
adb push system/app/GoogleFeedback.apk /system/app/
adb shell chmod 644 /system/app/GoogleFeedback.apk
adb push system/app/GooglePartnerSetup.apk /system/app/
adb shell chmod 644 /system/app/GooglePartnerSetup.apk
adb push system/app/GoogleQuickSearchBox.apk /system/app/
adb shell chmod 644 /system/app/GoogleQuickSearchBox.apk
adb push system/app/GoogleServicesFramework.apk /system/app/
adb shell chmod 644 /system/app/GoogleServicesFramework.apk
adb push system/app/LatinImeTutorial.apk /system/app/
adb shell chmod 644 /system/app/LatinImeTutorial.apk
adb push system/app/MarketUpdater.apk /system/app/
adb shell chmod 644 /system/app/MarketUpdater.apk
adb push system/app/MediaUploader.apk /system/app/
adb shell chmod 644 /system/app/MediaUploader.apk
adb push system/app/NetworkLocation.apk /system/app/
adb shell chmod 644 /system/app/NetworkLocation.apk
adb push system/app/OneTimeInitializer.apk /system/app/
adb shell chmod 644 /system/app/OneTimeInitializer.apk
adb push system/app/Talk.apk /system/app/
adb shell chmod 644 /system/app/Talk.apk
adb push system/app/Vending.apk /system/app/
adb shell chmod 644 /system/app/CarHomeGoogle.apk
adb push system/etc/permissions/com.google.android.maps.xml /system/etc/permissions/
adb push system/etc/permissions/features.xml /system/etc/permissions/
adb push system/framework/com.google.android.maps.jar /system/framework/
adb push system/lib/libvoicesearch.so /system/lib/
Now you have GApps installed from Anlog's. All Credits go to him and Indirect
Full system restore/wipe (fsr6)
THANKS TO INDIRECT
WARNING THIS WILL WIPE YOUR ENTIRE FILESYSTEM!!!
Go into adb shell or terminal emulator.
Issue command:
Code:
echo -n '0000' > /bootloader/BootCnt
Next reboot your device by conventional methods or issue:
Code:
reboot
Your nook will now restart and tell you it is resetting.
You now have a clean slate!
Got some links for howto's on the adb connection/root.
Yeah - if someone has details on how to adb connect and root, it'd be helpful to include links. I've yet to see specifics for either.
Reserved
Sent from Tapatalk, NOOK Color CM7 Nightly's!
I aplogize im still typing them up
Damn loglud, I ended up beating you to the root lol. Sorry about that! D:
The Droid 2 and Droid X had locked bootloaders with the 'e-fuse' and Koush got around them and installed CWM with this...
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
What do you guys think? I don't have a NT yet to try anything (probably won't get one until sometime around x-mas).
l
Indirect said:
Damn loglud, I ended up beating you to the root lol. Sorry about that! D:
Click to expand...
Click to collapse
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Loglud said:
l
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Click to expand...
Click to collapse
Superoneclick...love!
Sent from my Nook Tablet using Tapatalk
Loglud said:
l
Its no problem at all. Hints why i posted these guides. I was hoping someone wouod figure it out. I found it last night too. It sucked cause im now back at my childhood home trying to get my macbook pro to boot fedora and windows. Im gonna repackage the root with Superoneclick. Thanks so much for your effort. Would you mind if i added that to the guides?
Click to expand...
Click to collapse
Not at all so long as you give proper credits.
Loglud said:
This thread is designed for representation of the current progress on the Nook Tablet rooting and exploits, the second post will contain how to guides so you can learn to work on it for you self.
First off if you haven’t read the wiki yet to know what is currently in the device you should look here.
CURRENT PROGRESS
adb connection: COMPLETE
adb root: COMPLETE
busybox: COMPLETE
permanent root: IN PROGRESS
bootloader: Locked and Signed
By the bootloader being locked and signed it is very difficult to design anything that will boot besides nook roms. In order to solve this some of the Devs have suggested the following:
kexec: RESEARCHING
2nd init: RESEARCHING
CWM: NOT STARTED
Please PM me or post if you know anything else, and or want to add anything.
Click to expand...
Click to collapse
hopefully it is cracked soon cause i dont want to buy this if i can't have a full custom rom, all of the verizon motorola phones run roms off of 2nd init and it just isnt the same to be honest. you can never run a full custom rom with second init(well you can but you have to build the rom to fit the kernel) and honestly i want my device to be mine
you should tweet cvpcs or someone who makes and maintains 2nd init roms to get more info on it though
Can't get busybox installed
I'm stuck... I get errors for #3 for busybox... errors like...
Code:
$ adb shell /data/local/busybox --install
busybox: /data/busybox/[: No such file or directory
busybox: /data/busybox/[[: No such file or directory
busybox: /data/busybox/addgroup: No such file or directory
.....
busybox: /data/busybox/yes: No such file or directory
busybox: /data/busybox/zcat: No such file or directory
busybox: /data/busybox/zcip: No such file or directory
So I logged into root via adb shell, set busybox permissions to execute and tried that but same messages?!
Also, adb won't let me 'remount' - (I thought i'd try to copy it direct to /system/bin)?
(I'm running from OSX, if that matters)
EDIT: and of course I'm getting...
Code:
$ adb shell ln -s /data/local/busybox /system/bin/busybox
link failed Read-only file system
$ adb remount
remount failed: Operation not permitted
kgingeri said:
I'm stuck... I get errors for #3 for busybox... errors like...
Code:
$ adb shell /data/local/busybox --install
busybox: /data/busybox/[: No such file or directory
busybox: /data/busybox/[[: No such file or directory
busybox: /data/busybox/addgroup: No such file or directory
.....
busybox: /data/busybox/yes: No such file or directory
busybox: /data/busybox/zcat: No such file or directory
busybox: /data/busybox/zcip: No such file or directory
So I logged into root via adb shell, set busybox permissions to execute and tried that but same messages?!
Also, adb won't let me 'remount' - (I thought i'd try to copy it direct to /system/bin)?
(I'm running from OSX, if that matters)
EDIT: and of course I'm getting...
Code:
$ adb shell ln -s /data/local/busybox /system/bin/busybox
link failed Read-only file system
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Sorry it took me so long to get back to you. I have updatd my guide to help you out. First of you will need to make the busybox directory, then change the permissions of the binary file, then run the install. You will then have to mount -rw
Still some glitches installing busybox...
Loglud said:
Sorry it took me so long to get back to you. I have updatd my guide to help you out. First of you will need to make the busybox directory, then change the permissions of the binary file, then run the install. You will then have to mount -rw
Click to expand...
Click to collapse
Thanks Loglud, but I still had trouble using adb. It's like I don't have root from adb? I get permission errors on mkdir and remounting etc?
Weird that the 'adb shell mkdir /data/busybox' gave me permission errors?! It did work fine with the interactive adb shell - weird!?
After the initial 'push' command, I could install via:
Code:
mac-osx$ adb shell
$ su root
# cd /data/local
# chmod 755 busybox
# ls -l
-rwxr-xr-x shell shell 1745016 2011-11-21 00:21 busybox
# mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# mkdir ../busybox
# ./busybox --install
Also, is the line:
Code:
# ln -s /data/local/busybox /system/bin/busybox
not supposed to be
Code:
# ln -s /data/busybox /system/bin/busybox
Things went weird on me in the final step, but I did manage to get all the hard linked busybox files to show up in /system/bin eventually, so I'm a happy camper.
EDIT: PS my mount on data is as follows..
Code:
# mount|grep /data
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,data=ordered 0 0
EDIT2:
Hmmm... seems like maybe my /data folder has weird permissions - if so not sure why?...
Code:
# cd /
# ls -l | grep '\<data\>'
drwxrwx--x system system 2011-11-21 18:25 data
# chmod 777 data
kgingeri said:
Thanks Loglud, but I still had trouble using adb. It's like I don't have root from adb? I get permission errors on mkdir and remounting etc?
Weird that the 'adb shell mkdir /data/busybox' gave me permission errors?! It did work fine with the interactive adb shell - weird!?
After the initial 'push' command, I could install via:
Code:
mac-osx$ adb shell
$ su root
# cd /data/local
# chmod 755 busybox
# ls -l
-rwxr-xr-x shell shell 1745016 2011-11-21 00:21 busybox
# mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# mkdir ../busybox
# ./busybox --install
Also, is the line:
Code:
# ln -s /data/local/busybox /system/bin/busybox
not supposed to be
Code:
# ln -s /data/busybox /system/bin/busybox
Things went weird on me in the final step, but I did manage to get all the hard linked busybox files to show up in /system/bin eventually, so I'm a happy camper.
EDIT: PS my mount on data is as follows..
Code:
# mount|grep /data
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,data=ordered 0 0
EDIT2:
Hmmm... seems like maybe my /data folder has weird permissions - if so not sure why?...
Code:
# cd /
# ls -l | grep '\<data\>'
drwxrwx--x system system 2011-11-21 18:25 data
# chmod 777 data
Click to expand...
Click to collapse
ok so whats happening? i modified the guides and i was hopping that would help you. The command is
Code:
# ln -s /data/local/busybox /system/bin/busybox
and as for your permissions it seems as though your root since your in the # shell but, you have to change the permissions on your /system folder not the /data folder the permsisions on the data file should be fine since i think shell is a member of system, so you can put all your data in there.
Loglud said:
ok so whats happening? i modified the guides and i was hopping that would help you. The command is
Code:
# ln -s /data/local/busybox /system/bin/busybox
and as for your permissions it seems as though your root since your in the # shell but, you have to change the permissions on your /system folder not the /data folder the permsisions on the data file should be fine since i think shell is a member of system, so you can put all your data in there.
Click to expand...
Click to collapse
Yeah, I'm root in the 'adb shell' because I 'su root' but adb commands fail from the Mac shell. I'll reboot my NT and give you the script. My /data permissions get reset when I reboot...
Here you are as it happens
MBAir$ ls busybox
busybox
MBAir$ adb push ./busybox /data/local
2881 KB/s (1745016 bytes in 0.591s)
MBAir$ adb shell mkdir /data/busybox
mkdir failed for /data/busybox, Permission denied
Of course there is no point continuing until I do the following...
MBAir$ adb shell
$ su root
# chmod 777 /data
# exit
$ exit
MBAir$ adb shell mkdir /data/busybox
MBAir$ adb shell chmod 777 /data/local/busybox
MBAir$ adb shell /data/local/busybox --install
MBAir$ adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
To get around the last error, I had to do another 'adb shell', 'su root' and do 'ln' commands manually.
(I actually ran a shell 'for loop' on the tablet, using all files found in /data/busybox as a list and issued ln commands for each against a copy of busybox in /system/bin)
kgingeri said:
Yeah, I'm root in the 'adb shell' because I 'su root' but adb commands fail from the Mac shell. I'll reboot my NT and give you the script. My /data permissions get reset when I reboot...
Here you are as it happens
MBAir$ ls busybox
busybox
MBAir$ adb push ./busybox /data/local
2881 KB/s (1745016 bytes in 0.591s)
MBAir$ adb shell mkdir /data/busybox
mkdir failed for /data/busybox, Permission denied
Of course there is no point continuing until I do the following...
MBAir$ adb shell
$ su root
# chmod 777 /data
# exit
$ exit
MBAir$ adb shell mkdir /data/busybox
MBAir$ adb shell chmod 777 /data/local/busybox
MBAir$ adb shell /data/local/busybox --install
MBAir$ adb shell mount -rw -o remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
To get around the last error, I had to do another 'adb shell', 'su root' and do 'ln' commands manually.
(I actually ran a shell 'for loop' on the tablet, using all files found in /data/busybox as a list and issued ln commands for each against a copy of busybox in /system/bin)
Click to expand...
Click to collapse
re run zergRush exploit. your adb shell is defaulting to the shell username. by rerunning the zergy you will allow for yourself to use the adb shell as root. make sure you dont run it as the root user though. you are also more then welcome to hop in irc and ask questions.
Any one having difficulty rooting or see anything that needs to be updated?
any way to shell root any android device to get root access "#" , may be this might have been discussed many times .. I tried lot of ways but none works ..
stiphen said:
any way to shell root any android device to get root access "#" , may be this might have been discussed many times .. I tried lot of ways but none works ..
Click to expand...
Click to collapse
Rooting Android Wear?
jellycoder said:
Rooting Android Wear?
Click to expand...
Click to collapse
i just want to get # instead of $
stiphen said:
i just want to get # instead of $
Click to expand...
Click to collapse
I don't understand what you are trying to say. Kindly define your problem.
stiphen said:
any way to shell root any android device to get root access "#" , may be this might have been discussed many times .. I tried lot of ways but none works ..
Click to expand...
Click to collapse
Sure it's called root, To get full time shell root you unpack your boot.img change the default.prop to insecure repack and flash.
Just like below.
Code:
[email protected]:~/Desktop$ adb shell
[email protected]:/ #
jellycoder said:
I don't understand what you are trying to say. Kindly define your problem.
Click to expand...
Click to collapse
i tried below commands , superuser.apk gets installed and even devices reboots but i still not get root access "#"
Code:
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
adb shell
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
stiphen said:
i tried below commands , superuser.apk gets installed and even devices reboots but i still not get root access "#"
Code:
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
adb shell
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
Click to expand...
Click to collapse
Try
adb shell
su
vampirefo said:
Try
adb shell
su
Click to expand...
Click to collapse
/system/bin/sh: su: not found
stiphen said:
/system/bin/sh: su: not found
Click to expand...
Click to collapse
you have to have su for # to work.
vampirefo said:
you have to have su for # to work.
Click to expand...
Click to collapse
ok thanks i rooted my device with Impactor
stiphen said:
ok thanks i rooted my device with Impactor
Click to expand...
Click to collapse
Adbd insecure app also works. In your shell, just type SU and accept the SuperSU/SuperUser prompt
I've tried KingRoot but it tells me the device isn't supported. Are there any ways to install a custom recovery like TWRP or CWM?
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
mann1 said:
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
Click to expand...
Click to collapse
I saw your post on another thread here so I got the tools to extract it, but my knowledge is limited at ro.secure=0 and bash. If you wouldn't mind sharing I'd love to know how it's done.
I've attached the file.
Well, first you need to download the following files:
1-Your rooted_boot img from here
2-Compressed folder mann1.zip from here
===
Now lets start,
1- Unzip the rooted img then flash it, (be careful it's not tested)
2- 2- Unzip the file "mann1.zip" to get folder "mann1" then copy it directly into your device internal storage NOT the SD card. Put the the whole folder not the files inside
3-If the rooted boot worked fine, restart your device in the normal mode (NOT the recovery nor bootloader), and type the following commands one by one:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
complete the commands in the adb shell:
mount -o remount,rw /system
mount -o remount,rw /etc
mkdir /system/bin/.ext
mkdir /etc/init.d
cat /sdcard/mann1/busybox > /system/bin/busybox
cat /sdcard/mann1/su > /system/xbin/su
cat /sdcard/mann1/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/mann1/su > /system/xbin/daemonsu
cat /sdcard/mann1/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
cat /sdcard/mann1/supolicy > /system/xbin/supolicy
cat /sdcard/mann1/otasurvival.sh > /system/xbin/otasurvival.sh
cat /sdcard/mann1/libsupol.so > /system/lib/libsupol.so
cat /sdcard/mann1/su > /system/bin/.ext/.su
cat /sdcard/mann1/su > /etc/.installed_su_daemon
cat /sdcard/mann1/install-recovery.sh > /etc/install-recovery.sh
cat /sdcard/mann1/99SuperSUDaemon > /etc/init.d/99SuperSUDaemon
chown 0.0 /system/bin/busybox
chmod 0755 /system/bin/busybox
chown 0.0 /system/app/Superuser.apk
chmod 0755 /system/app/Superuser.apk
chown 0.0 /system/xbin/su
chmod 0755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
chown 0.0 /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
chown 0.0 /system/xbin/otasurvival.sh
chmod 0755 /system/xbin/otasurvival.sh
chown 0.0 /system/lib/libsupol.so
chmod 0755 /system/lib/libsupol.so
chown 0.0 /system/bin/.ext/.su
chmod 0755 /system/bin/.ext/.su
chown 0.0 /etc/.installed_su_daemon
chmod 0755 /etc/.installed_su_daemon
chown 0.0 /etc/install-recovery.sh
chmod 0755 /etc/install-recovery.sh
chown 0.0 /etc/init.d/99SuperSUDaemon
chmod 0755 /etc/init.d/99SuperSUDaemon
daemonsu -d
reboot
I assumed you already know the adb and fastboot commands to flash the boot
If everything run smoothly,after restarting your device you will find SuperSU installed, and the device is rooted w/o custom recovery.
mann1 said:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
Click to expand...
Click to collapse
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
Code:
[email protected]:~/Music/root$ adb root
restarting adbd as root
[email protected]:~/Music/root$ adb shell
[email protected]:/ $ exit
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
adamhighdefinition said:
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
Click to expand...
Click to collapse
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
mann1 said:
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
Click to expand...
Click to collapse
Just tested it, it caused a bootloop though, I cleared the cache and it still looped. I'll flash the first one and test it on windows then I'll report back.
The first one does allow me to see the Logcat output for all of the system services in Android Studio though, so it is giving elevated permissions.
Yeah, same on windows. Drops me into a normal shell.
Well, try this one
mann1 said:
Well, try this one
Click to expand...
Click to collapse
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
adamhighdefinition said:
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
Click to expand...
Click to collapse
Yvw, then this last one worked fine with you.
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play.
mann1 said:
Yvw, then this last one worked fine with you.
Click to expand...
Click to collapse
Yeah, last one worked for the Mediapad T1 8.0 Pro T1-921L.
mann1 said:
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play..
Click to expand...
Click to collapse
Must just be supersu being weird then, thanks again.
This tutorial explains how to root the kernel of any device under Linux. Here
Good luck