It should be noted that this is the current script, however, i am working on a cross platform java program that will do all of this for you
[NARS] is the Nook Automated Rooting System FOR MAC and LINUX
This program has been a WIP for myself for about a month, and I developed it so that people whom wanted to work with the adb development, and “bricking” of devices could quickly restore their devices to root. This program can also be used for a new user to, backup their programs, restore their programs, Root, Unroot, and Full restore.
Initializing ADB:
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 3RD PARTY 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 Debugging modes.
*NOTE: if you disable automount, Debugging will maintain through unplugs
[*]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.
As it stands right now this scrip has 4 functions, and a video will be made for it tomorrow.
USE THIS SCRIPT AT YOUR OWN RISK!!!!!!!!
Using the script:
Download Start up script (Inside NARS):[/I][/B][/CENTER]
Check to see what operating system is running for which adb to used
[*] Inject the product id into the adb_usb.ini file.
[*] Start the adb server and look for devices.
[*] Verify that chosen devices is actually a Nook
[*] Load Menu
Current abilities:
Rooting with zergRush and installation of the su Binary
Installing busybox
Installing Gapps
Unroot
Factory reset
OTA block
Upcomming abilites:
Semi-automated install and config of keyboards
Installing launchers
Installing HomeCatcher
Custom Unbloating
Backup and custom recovery
Download:
[URL]https://github.com/loglud/NARS/zipball/master
Git-Hub
https://github.com/loglud/NARS
Changelog:
1/9/12:
Added ota blockage
New busybox
Bug cleanup
Nice! Will try later on today on my friend's Nook.
Sent from my X500 using XDA App
Windows
Any suggestion for us windows users which are outside of this curve?
verosity said:
Any suggestion for us windows users which are outside of this curve?
Click to expand...
Click to collapse
Use the windows script in this section, it does literally the same thing.
Ubuntu 11.10 not showing my nt
Are there any tricks to getting an Ubuntu 11.10 system to show the nook tablet in the list of attached devices? On my laptop the list is empty. The laptop does see the nook, both the on-board flash and the SD memory. But NARS.sh doesn't find it.
New Nook Tablet, first time plugged into the Ubuntu laptop.
jbs
SandlinJohn said:
Are there any tricks to getting an Ubuntu 11.10 system to show the nook tablet in the list of attached devices? On my laptop the list is empty. The laptop does see the nook, both the on-board flash and the SD memory. But NARS.sh doesn't find it.
New Nook Tablet, first time plugged into the Ubuntu laptop.
jbs
Click to expand...
Click to collapse
do me a favor and go into the NARS directory and type
Code:
./adblinux devices
and tell me what the output is.
also make sure you have adb debuging setup. To do this read the post in http://forum.xda-developers.com/showpost.php?p=19653967&postcount=3 Enableing adb Connection (eab1) part 4 through 8
I lost track of when I'd had the debug settings enabled. Between all my windows boxes, which all loaded a generic driver before I could use the custom drivers, and getting the linux box set for android development, I lost track of the last setting on the nook - I forgot to "measure twice and cut once" - I didn't go back to make sure debug was still enabled.
The reminder about the debug was the key.
Thanks.
Did not work on a mac running Lion. My nook is never detected. Clear, detailed instructions that are self-contained in the first post would be appreciated.
Not sure if any prep work is needed or if your script really should be this easy.
Thanks
UPDATE: YOU MUST COMPLETE THE FOLLOWING STEPS BEFORE BEGINNING NARS.
Cut and pasted from another t-r-i-c-k's thread at http://forum.xda-developers.com/showthread.php?t=1358051.
You must complete the following step before using NARS:
Code:
On the NOOK
Disconnect from USB
Factory restore & initial setup
Browse to this:
[url]http://goo.gl/vTNpJ[/url]
Click on notifications center, wait for the file to finish downloading.
Press on downloaded go_launcher_ex_v2.66.apk file
Select Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Untick Automount
Back/Back
Connect the Nook to the MAC. On the nook you should see "USB debugging connected" in notifications center
Now follow the instructions in post #1 of this thread.
After you have run that script, reboot your nook tablet (you can turn it off all the way by pressing and holding for a few seconds the power button. Then turn the nook tablet back on).
You need to make sure that you install golauncherex, which I forgot to do. Just find the .apk that you downloaded (go_launcher_ex_v2.66.apk in your notifications center on the nook) and then make sure to install it. This will give you a new homescreen with all of your regular apps.
Loglud said:
...
Upcomming abilites:
Autoinstall and config of keyboards
Installing launchers
Installing HomeCatcher
[*]Unbloating
Click to expand...
Click to collapse
Any chance of custom unbloating? Such as, if you want to keep some of the bloat? Like the games?
Hey all. Hopefully you have all gotten a chance to check this out. I would like if you guys could tell me what launchers, browsers, keyboars, etc. you guys use so i can put them into the code.
just some suggestions thanks.
launchers
go launcher
zeam
adw
hcl
ics launcher
keyboards
hacker keyboard
swift tablet and standard
extra app
amazon app store
es file exploxer
mx player
mx player arm 7 codec
swipe pad
I am not sure what is possible these are things I use and feel are solid for the tablet.
Loglud said:
Hey all. Hopefully you have all gotten a chance to check this out. I would like if you guys could tell me what launchers, browsers, keyboars, etc. you guys use so i can put them into the code.
Click to expand...
Click to collapse
Thumb Keyboard 4!!!
Block OTA?
Does NARS block OTA like Indirect's script under Windows?
great script, fails on option7 install additional apk's
would turning this into a full linux distro with say puppylinux for modding/tweaking and development for NC be useful?
Loglud: I've rehosted these files on XDA.
http://devftp.xda-developers.com/files/AdamOutler/NookTablet/Market-8009011.apk
and
http://devftp.xda-developers.com/files/AdamOutler/NookTablet/NARS.tar.gz
I just put in some changes on my domain so;
APK:http://nook1.adamoutler.com
tar.gz:http://nook2.adamoutler.com
This should make it substantially easier for us who are restoring frequently.. now to try this sucker out.
All of the lines like this:
Code:
read -p "Press any key to exit..."
should be
Code:
read -n1 -p "Press any key to exit..."
So that it takes a single key press instead of "Enter"
Also, here's some more stuff to add http://forum.xda-developers.com/showthread.php?t=1424811
Scripts are already written, you just need to modify them for ADB.
Thanks adam the script has been updated
Nice job devs. This nook is open like a brothel on payday!
Related
This is an automated nooter file to streamline the rooting process for the NookColor. This has been tested by myself and others.
Thanks To: pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the hacked framework.jar used to get androidID, mastapsi for testing and coding, lewellyn for coding, [mbm] for ABI Fix, Suteru for the new custom Boot Animation,Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs, Freenode's #nookcolor chat for dealing with my crap and checking my code.
Please Note: If I'm using your app within AutoNooter and you'd like it removed please send me a PM stating so and I will do so for future versions.
DO NOT USE THIS IF YOU ARE 1.0.0
There are a few bugs before I can release 3.x.x that need to be worked out.
This is the only officially supported AutoNooter by those working on AN
Changes:
Added: Gingerbread Keyboard.
Deleted: YouTube.apk from /system/app
Update: Busybox has whoami
Update: Installs Soft Keys 3.0.0
What it does:
Installs su and Superuser.apk
Installs Busybox
Installs Softkeys 3.0.0
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Still Needs:
Custom Kernel to display something while working.
How to Use:
Before you begin:
* To update to 1.0.1 you must do a complete wipe.
* You must update to 1.0.1 to use AutoNooter 2.12.25 Instructions Here.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: auto-nooter-2-12-25.img.zip
2 Linux: Unzip and use dd if=auto-nooter-2-12-25.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory Reset > Wipes /data
You must do both of these to completely wipe clean your NOOKcolor.
Is it safe to try this after already having done Nooter 0.2?
The manual market install hasn't done the trick for me. Every time I have to restage the thing, if I'm not at home, I have to run out and find a wi-fi point to re-register it (argh).
I've had no ill effects from running this over an already nootered system with Market already fully functioning.
Link broken? Not finding it.
Never mind. Got it. You've got an extra j on the end BTW
I already have the market hack working but I don't have calendar and live wallpapers and some other stuff listed.
So just to be extra clear, this is save to just install over what I have already?
EDIT: WOW, this worked really WELL! I didn't mess up my already done hacks
And a little surprise in in store! It has the NEW market installed!
EDIT: Never mind, tired.
I'll be your guinea pig...will try it now.
Thanks for pointing out the extra j. Took it out.
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Wow. I've got an Android setup wizard. Should I run through it? I haven't seen this before on the NC.
"Learn how to use your LogicPD Zoom2"
Ohs you can try, but it should fail at "sign in" you want to skip it so that you can enable location.
johnopsec said:
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Click to expand...
Click to collapse
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
greenmky said:
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
Click to expand...
Click to collapse
When installed, it defaults to the "stock" Infrastructure (AP) only wpa_supplicant that shipped with the NC. This simply gives them the option off switching to ADHOC mode if they need it.
I've been watching the progress on adhoc and it's currently unstable. As soon as there's a more stable adhoc solution it will most definitely be put in a future version.
Same server error as before for the Market.
"! Attention"
A server error has occurred. Retry, or cancel and return to the previous screen.
Anything else I should do?
This is the same thing that occurred with the manual Market enable process.
I'm convinced there's still something wrong with this whole process for some of us. I know there's 3-4 people getting the same server error as me for the market.
Should I try the manual editing of the packages.xml file?
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
There's been some suggestion that the androidID may not have been properly create, this may of happened if you messed with the db that holds it.
GabrialDestruir said:
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
Click to expand...
Click to collapse
Yeah, there's a problem with the process still somehow. This is the same results as the manual process.
This is much easier though and faster to redo. Maybe they'll find the bug in the process for those of us that it doesn't work for.
EDIT: Just a note. The Auto-Nooter didn't change my packages.xml file to remove these lines:
<sigs count="n">
<cert index="n" />
</sigs>
Not sure if it was supposed to...but it's in the manual install instructions.
Well if you can come into the irc chat maybe someone there can help you figure out the issue and we can see about adding the fix the next version.
Thanks to auto-nooter I was able to get farther than I did before with nooter .2 version. However, I've got a new problem.
After rebooting the NookColor, it started the Android tutorial. Then, when I tried to set up my Google account, I couldn't click on the "Enter Account" option since I already have a Google account. When I tried the enter account in the future option, Android seemed to immediately crash on me and the NookColor went to the normal B/N interface.
I power cycled the NookColor. However, now it immediately goes into the B/N interface, and I never see Android.
Any ideas?
Robert
Well you were suppose to skip the entering info so that it'd ask you if you want to enable location. I'm not sure if it's possible or not to get SetupWizard running again. I don't know anyone that's tried either.
Awesome! Market finally works. Thanks a lot for this! It didn't even break my previous mods.
Notice:
Click to expand...
Click to collapse
Sorry guys this no longer works...
Ubuntu removed alot of the files needed to run it on a phone off of their website which is why you are getting the errors on the script to try and install it.
Recapped:
Here's what I mean the website the script is going to to get the files no longer exists...
Heres an example to see for yourself: http://ports.ubuntu.com/ubuntu-ports/pool/universe/t/tightvnc/tightvncserver_1.3.9-4_armel.deb
I will try and find a new link to plug in but for now it DOES NOT WORK!
Thank you for your patience on the thread,
StrumerJohn
==== How to Install Ubuntu Linux on your HTC EVO 3D / Sensation 4G ====
Table of Contents
Post 1
1: Disclaimer
2: Pre Requirements
3: PC Guide to push to phone
4: MAC Guide to push to phone
5: Additional Scripts
6: Credits
Post 2
1: FAQs
2: Recognitions
Post 3
1: News and Updates
2: Additional Notices
Click to expand...
Click to collapse
-Disclaimer-
This has been tested on my phone and runs perfectly fine, I am not responsible for you breaking, bricking, or dropping your phone on the floor and causing the USB cable to fall out and blow up your device.
Pre Requirements:
A rooted HTC EVO 3D or Sensation 4G
A S-off'd HTC EVO 3D or Sensation 4G
netarchy's kernel (Silverneedle Test5)
Android SDK
The USB drivers for your phone. (x32) (x64)
A microSD Card
2.3 GB Free of space on your microSD card
Know how to read to directions
Click to expand...
Click to collapse
The intense Procedure:
1. Download this version of Ubuntu. [Download #1] [Download #2]
2. Unzip the Ubuntu folder to your desktop and if you want, delete the compressed one you downloaded.
3. On your phone go to Settings > Applications > Development and turn on USB debugging.
4. Plug in your USB cable (from your computer to your phone) and mount your (mirco)SD card.
5. Move or copy over the unzipped / normal Ubuntu folder. This will take a long time unless you have a class10 microSD card.
6. After moving / copying that file over, tell your phone to unmount the (micro)SD card / Set the phone to Charge Only mode.
7. Now on your computer, go to where you have Android SDK installed. (Example on my computer: E:\Program Files (X86)\Android\android-sdk )
8. When in the main SDK folder, hold shift and right click a blank area and then click on "open command window here". It should of opened the command line window with the directory of your SDK already put in. If not type cd "C:\Your directory or location of your SDK"
9. Now type "cd platform-tools"
9.5. (Optional) "type adb devices" and check if the computer recognizes your phone. If not you need to reinstall your drivers from the download link above in the requirements.
10. Type "adb shell"
11. Type "su" so we have superuser permissions
12. Type "cd /sdcard" so the directory is changed to the (micro)SD card
13. Type "cd ubuntu" so the directory is changed to the Ubuntu File
14. Type "sh ubuntu.sh" so we can install Ubuntu
15. Type "bootubuntu" to start up Ubuntu. Next time you enter Ubuntu, you just need to type "bootubuntu" from your /sdcard/ubuntu directory, there is no need to run ubuntu.sh again.
16. If you got "[email protected]" in the command line, you have sucessfully installed Ubuntu. If not make sure you installed netarchy's kernel. If it still does not install correctly please try a different ROM, I have only tested this on SteelROM 1.1. *AFTER INSTALLING ANY ROM, YOU NEED TO REINTALL THE KERNEL.*
17. Now type "apt-get update" to update Ubuntu to the latest version. Then "apt-get upgrade" to apply the update.
18. Type "apt-get install tightvncserver" to install the vncserver. (Your telling your phone to read off it self pretty much.)
19. Type "export USER=root" To make yourself a user / the user
20. Type "vncserver -geometry 1024×800" to set the screen resolution you want to display on your phone. Remember you can always zoom in by pinching, so you don't need to make this that much smaller. You should also get prompted to set a password, do so. You will need to remember this password to log in.
21. Download the AndroidVNC Viewer off the Market here.
22. Open the viewer, and put in a nickname, your PASSWORD FROM ABOVE, and for the IP Address put: 127.0.0.1 for the port put 5901. THEN SCROLL DOWN and make the COLOR FORMAT 24-bit colors (4bpp).
And finally, hit Connect to launch Ubuntu on your phone!
For Mac users:
Finder -> Applications -> Utilities (folder) -> Terminal
When you cd to where your adb is located, cd is lowercase as are most all unix commands.
If you're unsure where to go, get to adb in your Finder, right-click, get info, the pop-up will show you the path. Note in unix that the folders (subdirectories) are separated by / and not by \ like in Windows.
Once you're there, the only trick you need to know is to tell unix that adb is located where you are, so you change the adb shell command like this:
./adb shell
That's about it, all other instructions once you're inside the phone shell are the same.
OBTW - after the unzip of the initial file from the OP, just drag and drop the whole ubuntu folder to your NO NAME drive (normal sd card formatting doesn't get a name at the factory, so by now you know that your sd card mounts like that anyways I'd suppose - just put it here in case).
Click to expand...
Click to collapse
Additional Scripts
Danaff37's
danaff37 said:
That's the script catted out.
I posted a different script a few pages back that I think will help you guys. I modified it so we should have no trouble with apps in sd.. I finally got a bigger sdcard so I can test this stuff and this script works great. Please guys try this script. If you download it in phone it will change the name and add a bin on it I think, so rename it accordingly and make sure it gets into /system/bin with the right permissions (755 or rwxr-xr-x), then run it
http://db.tt/gin57Gd
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Credits:
Ubuntu Modded and Guide by: Me
Mac Guide Written by: EarlyMon
danaff37's Script by : danaff37 (of course)
Original dev of Ubuntu: Zedomax
If you have any problems beside the slow downloads because of the blown up servers, let me know below. Also I tried to type this fast, so if there is any typo's or broken links let me know too! Thanks!
Also feel free to hit the Thanks button or Donate for more Guides
FAQS
FAQS
Do I need to have everything in the android-sdk downloaded and installed?
No, you just need to have the base sdk.
When I tell the command prompt to adb devices, my phone does not show up!!
Make sure you have installed the proper drivers for your phone and for your correct operating system
I'm not getting "[email protected]" when I type / copy-&-paste "bootubuntu"
Well, this could be for a various amount of reasons, first make sure you have a rooted HTC EVO 3D/Sensation. And by root, I mean a full root, not just a temp root or S-off. If you still do not get "[email protected]", flash your device (or go though your data folder and delete all the ubuntu files, then delete the ubuntu file off of your sd card and clear your caches.), and retry the above steps. If the problem still persists, then please PM me with your exact problem.
I'm having issues within the VNC, and I get an error message when I hit "connect".
Make sure you typed your password correctly, the passwords are case sensitive. If you still cannot get in, make sure your IP Adress is set to "127.0.0.1" and your Port(s) are "5901".
The colors on my screen look all weird and disorientated, how do I fix this?
Close Ubuntu, and re-open the VNC application, then scroll down to "Color Format" and tap on "24-bit color (4 bpp)".
The on-screen keyboard does not work and I get a different letter or character for whatever character I type!
The on-screen keyboard will work now, if you install LXDE.
I'm not good with reading text! I need a video demonstration!
For a video head here: http://www.youtube.com/watch?v=YbunTRzEQCI
How do I close Ubuntu?
Two options here:
1.Logout of the server and go to your homescreen and push menu, then go to settings, then Applications, then Running Services and close any remaining open part of the server program. The service may re-open later, do not close it though. It won't use up a noticable amount of RAM, just enough to make sure the application opens quick again.
2. Logout of the server and use your favorite task killer to close the server process. The service may re-open later, do not close it though. It won't use up a noticable amount of RAM, just enough to make sure the application opens quick again.
FAQS should be in order chronologically (until the end of them).
I would like to give a huge thanks to EarlyMon, for helping out lost members. This thread would not be as peaceful if it were not for him.
And it seems I have forgotten to list another VERY helpful person here, danaff37. I am really grateful to both of these two for all of the help and work they have done to aid others.
Am I missing a question that you are pretty sure is asked ALOT (lol)? Then PM me please and I'll get it up here ASAP!
Upcoming Change log for final release:
(StrumerJohn's Zedomax Ubuntu Mod)
Made a launchable .exe for easier updating and installing of Ubuntu
Default mode LXDE for fixed keyboard
Pushes Server application to your phone
Fixed a few problems that caused people to have an error in installing
Server application updated
Fixed port issues for log in errors
News update 11/13/11
Bad news and Good News:
Ubuntu was successfully updated
Update brakes keyboard
Update breaks Apps2SD
Update takes up less space (1GB instead of 2GB)
Update ONLY works on MIUI so far
Updated script to add work around for those facing issues
Computer .exe only working on x64 Windows 7 computers ;-;
Thank you for those of you testing! Might make this open Beta...!
Version as of 12/12/11
Alpha Build 1.0
What Doesn't Work so far:
Boots to latest version only to lock up phone (Unless you are running MIUI)
Keyboard borked
Doesn't work on ICS
Audio Broken
Apps Saved on SD
What works:
Everything else
Sweeeeet.
Appreciate my help? Thank me
Wow this is amazing! Never used linux before tho...
Haven't looked at the bootubuntu script yet, but I know a lot of these couldn't work if you had any apps on sdcard at all. Each app moved to sd takes a loop device.
Sent from my PG86100 using XDA App
maazing will try tonight!!!!!!
danaff37 said:
Haven't looked at the bootubuntu script yet, but I know a lot of these couldn't work if you had any apps on sdcard at all. Each app moved to sd takes a loop device.
Click to expand...
Click to collapse
Just moved partially like moving to the SD or Actually having them Downloaded and Installed to the SD?
Interesting. Nice write up
Sent from my PG86100 using XDA Premium App
Cool...
But, why.
Cause you can?
Sent from my 3vo via Tapatalk
Because Ubuntu has some computer applications you can't normally use on your phone. In the browser download Java and check out runescape runs like shizzle but once we get new quad phones out I'm sure it would run fine. lol
This is what I wanted. Million thanks....
Sent from my PG86100 using www.psvitahacks.co app
Added to my 'Complete LIST' thread: http://forum.xda-developers.com/showthread.php?p=16132451
StrumerJohn said:
Just moved partially like moving to the SD or Actually having them Downloaded and Installed to the SD?
Click to expand...
Click to collapse
Using the stock apps to sd like under manage applications (like the same as is available on a non rooted phone). The script for ch rooting can be made to work around it though. But most aren't.
Sent from my PG86100 using XDA App
danaff37 said:
Using the stock apps to sd like under manage applications (like the same as is available on a non rooted phone). The script for ch rooting can be made to work around it though. But most aren't.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If there are any small minor problems like that and it's not working proper, let me know. I'll mess around with some things and release a patch.
Installed successfully and works great except I can't type cause of the keyboard glitch. Anyway around it?
Sent from my PG86100 using XDA Premium App
Working with shooter rewind
akiradavis said:
Installed successfully and works great except I can't type cause of the keyboard glitch. Anyway around it?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
The only way to get around it atm (at the moment) is to use a bluetooth keyboard.
Very sweet! I will test this tomorrow when I get home. It should work on my ROM as well
Nice....can't wait for the keyboard fix.
UPDATED 12/23
---------------------------
1) Added automatic fixing of devicemanager.apk sql databases to prevent OTA root (thanks for the SQL tweak suggestions, Indirect)
2) Added otaban.sh script for those who are already rooted and just want to tweak the sql databases (you will need to put your device back in USB debug mode)
3) Added getroot.sh to just dump the nook back in to rooted/adb mode
INSTRUCTIONS
(Please follow these to the letter; over 500 people have downloaded this script and very few have reported issues)
On the NOOK
Disconnect from USB
Factory restore & initial setup
Browse to this:
http://goo.gl/vTNpJ
Click on notifications center, wait for the file to finish downloading.
Press on downloaded go_launcher_ex_v2.66.apk file
Select Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Untick Automount
Back/Back
Connect the Nook to the MAC. On the nook you should see "USB debugging connected" in notifications center
On the MAC
Download the nooktablet-mac-root-0.6.zip file from http://goo.gl/qyYDB
Open Terminal, and change in to the directory where the zip file was downloaded. Unzip and cd in to the directory created. EG:
Code:
[B]cd ~/Downloads
unzip nooktablet-mac-root-0.6.zip
cd nooktablet-mac-root-0.6[/B]
Start the rooting script:
Code:
[B]./go.sh[/B]
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly. Also don't connect via a USB Hub.
When the script is finished, it should say "Done. Unplug from USB now"
The Nook will reboot.
You are now rooted and the following is auto-installed for you
1) Go Launcher Ex (Rooted App Launch/Desktop)
2) Market Place (The Android "App Store")
3) Button Savior (adds tiny button on right of screen for nagivation home/back etc)
4) Home Catcher (makes 2 clicks of the Nook N bring up the new Launcher)
5) Nook Color App Menu (allows you to install sideloaded apps to the Nook home screen/Library)
6) Dolphin HD Browser (Replacement web browser)
In addition, some tweaks have been made to prevent OTA updates from working, preserving your root state.
trying this now..
thanks a lot! i spent 2 hours last night trying to get the other method working and it gave me the headache of the gods.
edit: that mediafire link is crawling for me (dl is at like .2kb/s) can anyone mirror it for others who may have similar issues?
Worked beautifully! Where can I send a donation to?
beatlesfan01 said:
Worked beautifully! Where can I send a donation to?
Click to expand...
Click to collapse
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
i can confirm this works guys
yes.. someone please start a thread and aggregate donations for some roms on this bad boy.
t-r-i-c-k said:
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
You are a good man. Thanks again for all of your help and great work. You're an invaluable asset to this community.
Sent from my BNTV250 using Tapatalk
Thanks for the tutorial. It works extremely well!
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
jdubr said:
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
Click to expand...
Click to collapse
Ah, I just looked at the script, I realized now I missed out the mkdir -p ~/.android in it, hence your issue. I will likely fix that and update the script/zip file when I get a minute.
I'm currently considering whether to make the script install busybox at the moment. I don't really need it myself, but I see other people might.
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
t-r-i-c-k said:
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
Click to expand...
Click to collapse
I totally get that. I had just gotten done side-loading tons of stuff and getting my launcher screens setup the way I wanted and then I saw your script and thought about it for a day before breaking down and wiping my NT and starting over.
It was worth it! Thanks again!
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Minor problems encountered
I followed the directions and it mostly worked. First, had the problem with the missing:
[ ! -d ~/.android ] && mkdir ~/.android
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail?
Click to expand...
Click to collapse
Sent from my BNTV250 using Tapatalk
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Click to expand...
Click to collapse
Literally type
unzip nooktkablet-mac-root-0.4.zip
cd nooktablet-mac-root-0.4
mkdir -p ~/.android
./go.sh
Sent from my BNTV250 using Tapatalk
kisstek said:
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
Click to expand...
Click to collapse
Launcher: that's what I meant.
Unplug: if you dont before you reboot it probably wants to media sync
Button savior: installs a tiny button on the right of the screen. Gets you back/home
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Sent from my BNTV250 using Tapatalk
Thanks. I found the little tiny button savior icon while trying out an ssh client. It shows up well on a black background.
And that does make it real easy to get back and forth between Android and Nook. Thanks again for making this easy and the button savior recommendation.
I may have to break down and try the Amazon store now.
t-r-i-c-k said:
Connect the Nook to the MAC. On the nook you should see "USB debugging enabled" in notifications center
On the MAC
Download the nooktablet-mac-root-0.4.zip file
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly.
On the NOOK
Click on Notification center again, and press on the Golancher Icon again. Install the Goauncher
Reboot
After reboot, slide to unlock and it should ask "complete action using..". Pick LauncherPRO
Open Marketplace which should be on the launcher screen
Sign in with your google credentials, attach the device to your account
Install button savior from the Marketplace.
Browse to amazon.com/app-email
Click notifications and watch for Amazon appstore apk download
Click and install.
You should now be live with Android Market & Amazon Market.
Click to expand...
Click to collapse
Hey! Noob here. Thanks so much for this! Just have a few questions...is this a permanent fix? I currently have the amazon appstore, but not android, so is this going to be set up the same way (i.e. have to click search and then go launcher to find the apps)?
When I connect to my mac, the usb debugging prompt will come up right away (like the screen for file xfer normally does)?
After unzipping, are those instructions to enter into the mac's terminal command prompt? Sorry, that's where u lost me! Is "cd" short for something? Thanks again for your help. Just want to make sure I do this right the first time. I think swype is the first thing I will install. Hating this keyboard!!!
First, I want to openly thank t-r-i-c-k for this. Even with little to no knowledge of this kind of stuff, after futzing with terminal for a while I got it to work in two tries. Finally, freedom from another lock-in service/device. But I am having a little glitch that I don't understand.
It's intermittent, but now and then I'm getting a crash on the launcher. It happens when trying to adjust settings/preferences. No big deal as it comes right back, and maybe its the app itself. Anyone else facing this?
t-r-i-c-k said:
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Click to expand...
Click to collapse
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
jdubr said:
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
Click to expand...
Click to collapse
ADW seemed slow to me. I just switched to Launcher Ex anf thsts is working nicely. No crashes yes.
Sent from my BNTV250 using Tapatalk
I've searched, but not found, anyone else doing this yet, so I thought I'd post in case it helps. Hopefully this isn't old or well known news tho
I am successfully side-loading on my NT with the 1.4.1 update, using 'adb install ...' - without rooting.
First a little background:
I did have my NT 1.4.0 previously rooted, and Market installed.
I didn't block Over-The-Air updates but didn't get any until just yesterday.
I also had SwipePad installed BEFORE the update and a SwipePad add-on called AppLauncher (all I needed for launching/task switching)
It appears that B&N uninstalled ADW and Go Launchers off my device?!
Wow, that's privacy infringement, I would think!
I'm quite sure they were on my device before the update and aren't to be found now?! Other things in /system/bin went missing also - su, BusyBox, custom scripts etc.
Here's How I managed to side-load:
With SwipePad and AppLauncher add-on (it shows all apps like an app drawer), using AppLaunchers menu for "App Settings" allowed me to go to dev and set USB debug mode and uncheck Auto Mount.
Then simply using "adb install <name here>.apk" with the apk file on my computer, I can install and run apps (including Go Launcher ).
SwipePad + AppLaucher give me all my previously and newly loaded apps.
What's Not Working:
Just gotta figure out how to get su to work again. I've loaded Superuser and gone into terminal but I have no su command anywhere I can find (did B&N remove it too?!).
Epilog:
So I can side-load and run apps, but no super-user (root) access.
Running the Nook&Zergy exploit doesn't work, as it fails on a remounting.
Here's what I'm getting when I try to root...
Code:
NookZergy$ adb push zergrush /data/local/zergy
1557 KB/s (23056 bytes in 0.014s)
NookZergy$ adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
NookZergy$ adb remount
remount failed: Operation not permitted
I did side-load busybox, with a "success" status from adb - but I can't find it on the device after the install - weird?!
DeanGibson actually figured out a way to root 1.4.1 and install Android Market, but you must downgrade to 1.4.0 first.
Also, like you mentioned, adb install works just fine as long as you have an app installed that allows you to access the USB Debugging settings. Indirect actually released a script for sideloading via this way a while back. The Android Central Sideloading Wonder Machine works great as well.
Another thing, brianf21 figured out a way to allow sideloading via browser/email downloads and built the functionality into his Nook Tablet Hidden Settings App. Your 1.4.1 device must be rooted in order for the functionality to work.
darkquota said:
DeanGibson actually figured out a way to root 1.4.1 and install Android Market, but you must downgrade to 1.4.0 first.
Also, like you mentioned, adb install works just fine as long as you have an app installed that allows you to access the USB Debugging settings. Indirect actually released a script for sideloading via this way a while back. The Android Central Sideloading Wonder Machine works great as well.
Another thing, brianf21 figured out a way to allow sideloading via browser/email downloads and built the functionality into his Nook Tablet Hidden Settings App. Your 1.4.1 device must be rooted in order for the functionality to work.
Click to expand...
Click to collapse
Yeah, I did find and read all the posts you referenced. I don't really understand why Dean's method worked any different then what I already had tho, yet my tablet did not stay rooted after the upgrade - is that what he was suggesting happened? We still don't have a rooted 1.4.1, right?
kgingeri said:
Yeah, I did find and read all the posts you referenced. I don't really understand why Dean's method worked any different then what I already had tho, yet my tablet did not stay rooted after the upgrade - is that what he was suggesting happened? We still don't have a rooted 1.4.1, right?
Click to expand...
Click to collapse
Following his method, I ended with 1.4.1 being rooted. He somehow prepares the device to be able to be rooted on 1.4.1 before the 1.4.1 update is applied. I don't know the details, but he'd probably be willing to explain it to you.
back to 1.4.0
@darkquota - used the thanks button on ya
Well, did a funny thing using the hidden settings app... I went into accounts and deleted the "user" account - turns out this re-inits the entire /system folder as I lost everything - custom keyboard the works... Needless to say I'm reverting to 1.4.0.
BTW if anyone stumbles on this thread, there are better resources elsewhere AND it looks like things are getting very close to 'ROM build time' as there are reports of by-passed boot-loader!
...so many Thank-you's to click...
kgingeri said:
Here's How I managed to side-load:
With SwipePad and AppLauncher add-on (it shows all apps like an app drawer), using AppLaunchers menu for "App Settings" allowed me to go to dev and set USB debug mode and uncheck Auto Mount.
Then simply using "adb install <name here>.apk" with the apk file on my computer, I can install and run apps (including Go Launcher ).
Click to expand...
Click to collapse
Just to make sure I'm understanding correctly (I'm a bit technologically challenged), in order to install whatever app you're wanting to install .... Once you've checked and unchecked the boxes, do you have to have your Tablet connected to the PC in order to make the file transfer and install the app or can you send the apk file to yourself via web email account and download/install it from there?
TnTexasNT said:
Just to make sure I'm understanding correctly (I'm a bit technologically challenged), in order to install whatever app you're wanting to install .... Once you've checked and unchecked the boxes, do you have to have your Tablet connected to the PC in order to make the file transfer and install the app or can you send the apk file to yourself via web email account and download/install it from there?
Click to expand...
Click to collapse
Hi Tn, yes you have to load via the 'adb install ....' and the apk file FROM YOUR COMPUTER (tablet connected via USB of course). Email won't work as you get blocked by the security msg
FYI... I've since reverted my NT to 1.4.0 as I messed it up removing the main user account.
Still having debugging issues ...
Hello ...
I do not want to root my NT (1.4.1), I just want sideloading. Running Windows 7 on my laptop. Only USB 2.0 ports.
Yes, I have access to the settings menu, I installed AppMenu (TGPS) before 1.4.1.
I have been able to get USB Debugging ON and AutoMount OFF ... I know debugging is active because I am getting the little Android "bug" in the lower left corner ... and I still have control of the NT screen.
I have checked my installed USB menu with deview, and I do not see any other ADB devices present.
But no matter what I do, I cannot get SWM or the command prompt script to "see" my NT ... all I get is "Device Not Found".
What am I missing? The advice regarding drivers seems confusing if you are not trying to root the NT.
Thanks ...
np
notpaul said:
Hello ...
I do not want to root my NT (1.4.1), I just want sideloading. Running Windows 7 on my laptop. Only USB 2.0 ports.
...snip...
What am I missing? The advice regarding drivers seems confusing if you are not trying to root the NT.
Thanks ...
np
Click to expand...
Click to collapse
Not real sure Np - I am on a Mac, but it does sound like you have driver issues. I've read a lot of posts with Windows users complaining of such.
This from Indirect:
NOTE: Anyone who is having problems with drivers, http://forum.xda-developers.com/show....php?t=1363652 <-- That explains the two most common problems.
Click to expand...
Click to collapse
None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS) 4K
DISCLAIMER: BE WARNED THAT YOU HAVE TO OPEN YOUR FIRE STICK AND IT WILL VOID YOUR WARRANTY, THIS IS NOT FOR THE FAINT OF HEART AND NEITHER THE DEVELOPERS OR MYSELF ARE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR VOID YOUR WARRANTY
Ok, now let's begin:
UPDATE: Per Sus_i, this makes perfect sense:
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."
First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting
In order to unlock the bootloader follow "THIS GUIDE"
I made a quick video on how to open your device and how to Short it using Aluminum Foil:
https://www.youtube.com/watch?v=h4I6ifBLWJ4
Process is pretty self explanitory, make a USB ISO from the image provided on that thread, boot into it and open terminal, make sure you put the file he provides on a RW location, my mistake was that I put it inside a RO folder and it would not load the script, so I mounted the kamakiri-mantis-v1.2.zip unto the /mnt directory of the usb and I was able to run the script successfully, make sure to run the commands quickly as the first time that I it finished the ./bootrom-step.sh script and I left it sitting for 10 minutes to grab a bite, I couldn't run the second script and had to start all over. After the second ./fastboot-step.sh script, your device will be on the TWRP recovery, now on the same terminal page or a new one enter these commands:
Code:
adb devices
adb shell
exit
You should see your device's serial number from the first command with "device" to the right of it and the second command will basically put you inside the device's directory assuming you have established a successful connection. The last command just put you back to your starting point, now open the firefox browser on the FireOS USB and navigate to the URL below
Download the Pre-Rooted Image from "HERE" This image contains Magisk already so you don't have to worry about installing it separately, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you, then run these commands:
Code:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
Code:
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
After running all these commands exit adb and continue with the normal Amazon Setup including adding your amazon account. After you get to the screen where you can see all the apps, open a new web page browser in firefox and download "This Add-On" , this one is less than 200MB so it should fit on the Fire OS USB, so I would download it and copy it to /mnt for ease of access, go back to terminal and type this:
Code:
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Your device will reboot and if everything went smoothly, you should have a rooted amazon fire stick 4k, Congrats :good:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Edit: S̵i̵n̵c̵e̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵ ̵c̵a̵n̵'̵t̵ ̵b̵e̵ ̵p̵a̵t̵c̵h̵e̵d̵,̵ ̵i̵t̵'̵s̵ ̵i̵n̵ ̵m̵y̵ ̵o̵p̵i̵n̵i̵o̵n̵ ̵t̵h̵e̵ ̵b̵e̵s̵t̵ ̵t̵o̵ ̵d̵o̵ ̵t̵h̵e̵ ̵s̵e̵t̵u̵p̵ ̵a̵t̵ ̵t̵h̵e̵ ̵b̵e̵g̵i̵n̵n̵i̵n̵g̵,̵ ̵p̵a̵i̵r̵ ̵t̵h̵e̵ ̵r̵e̵m̵o̵t̵e̵,̵ ̵t̵h̵e̵n̵ ̵u̵p̵d̵a̵t̵e̵ ̵t̵o̵ ̵t̵h̵e̵ ̵l̵a̵t̵e̵s̵t̵ ̵o̵v̵e̵r̵ ̵f̵i̵r̵e̵O̵S̵.̵ ̵T̵h̵a̵t̵ ̵w̵a̵y̵ ̵y̵o̵u̵ ̵a̵v̵o̵i̵d̵ ̵a̵ ̵p̵e̵n̵d̵i̵n̵g̵ ̵u̵p̵d̵a̵t̵e̵ ̵n̵a̵g̵ ̵s̵e̵t̵u̵p̵ ̵s̵c̵r̵e̵e̵n̵ ̵a̵f̵t̵e̵r̵ ̵d̵o̵i̵n̵g̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵.̵ ̵T̵h̵e̵n̵ ̵e̵n̵a̵b̵l̵e̵ ̵A̵D̵B̵ ̵a̵n̵d̵ ̵u̵n̵k̵n̵o̵w̵n̵ ̵s̵o̵u̵r̵c̵e̵s̵.̵ ̵ After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Edit: Update: meanwhile, the fix for the mentioned 'contact manufacturer' error is known...
Take a look here and here.
Edit/Update: Due to efuses (blocking the bootrom access), it isn't recommended to do any update infront of the unlock...
Sus_i said:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Click to expand...
Click to collapse
Ops Typo let me edit it, I meant to put 6.2.6.8 on the command lol, and aaaa I see I didn't know the exploit couldn't be patched great info, so than yes I will revise my instructions thank so much
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
nandroidint said:
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
Click to expand...
Click to collapse
No. If I remember correct, it has something to do with flashing, i.e. the vendor partition wasn't flashed propperly.
Maybe you flashed not the prerooted!? With the Kamakiri TWRP version is flashing full ota update packages (renamed to zip) also possible... and in the prerooted thread is such a full 6.2.6.8 ota linked.
Edit: Could be that this error is prime video related, idk. rbox said he looks into it soon...
Just for clarification: The prerooted rom is a perfect thing since years.
My suggestion 'avoid any rom flashing' from my last post is just an attempt to keep it simple for beginners.
By the way, if the stick gets all updates in front of the unlock, it makes no sense to update it after the unlock again (unless addon.d support is needed).
I hope that has become clear I very much appreciate all the prerooted stuff
thanx for the tut nandroidint this is exactly what I needed, I wasn't sure how to do the shorting so the video helped out a lot now I'm ready to do this. But I'm sorta a noob when it comes to android so I got few questions tho, 1) what are the main benefits in rooting the fIrestick 4K 2) are there different roms to install? 3) are there root only .apks? 4)also one main thing I would like to be able to do is spoofing the Mac address any idea if that's possible?
5)Oh and lastly what OTB cable do you recommend? sorry for all the questions ?
'std::bad_alloc'
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?
i gave root can i remove amazon services
i dont want google launcher jsut remove services
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable ?
Can I please get some support guys ? previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
davinci2798 said:
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
Click to expand...
Click to collapse
Did you deregister before rooting like the tut says? This is why I’ve been hesitant on rooting because of the lack of support on this forum
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
tsynik said:
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
Click to expand...
Click to collapse
Nice! That’s awesome thanx for the info and reply.
davinci2798 said:
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
Click to expand...
Click to collapse
Hey so have you figured out what was the problem yet? If so could u explain how you managed to fix it? I’m going to root sometime this week and would hate to run into this issue.
USB drive for storage
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
Yes, You can use a USB drive for App loading and Movie storage.
See Troypoint.com for good video.
I suggest a single USB OTG Cable and a USB HUB for your drive.
Then you can add a Keyboard and Mouse which make it MUCH easier to type commands.
Good Luck
How might one do this on a Mac?
Thanks
gogorman said:
How might one do this on a Mac?
Thanks
Click to expand...
Click to collapse
Do what? The only thing u can do on the MacOS is to create the bootable iso usb, you can follow these steps to do so https://www.google.com/amp/s/www.le...-on-an-apple-mac-os-x-from-an-iso?hs_amp=true
After your create the bootable usb just reboot and hold down option and select the bootable usb, once in open up Firefox and download the kamakiri-mantis-v1 and open a terminal window and change the directory to where u have the kamakiri folder, in terminal type cd then just drop in the kamakiri and hit enter. From there u can just follow the tut, FYI the bootable usb you create is a Linux OS so that’s how you can do it on a Mac, you just can’t do the rooting on MacOS, just clarifying Incase that was your question.
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Step by step instructions would be great?
chinkster said:
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
RPM99 said:
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
Click to expand...
Click to collapse
The link he provided explains all that https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459 all except for when to connect to the tv, but I assume it’s after running the kamakiri script, btw it’s not software, you just download the kamakiri mantis while in the Linux usb os, open a terminal and change the directory of the terminal to the kamakiri folder in order to run the ./bootrom-step.sh and ./fastboot-step.sh commands
Edit: just follow the main guide from the link above then read this guide after, that’s the best way to understand it.