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
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.
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Sounds to me like a permissions issue. I had that after I fiddled with the contacts database to unrestrict pictures from third party apps. I would double check any files you modified and make sure they got chmod'ed back to what they should be.
You will have to somehow access the Settings to re-enable adb. When you did a factory reset, you disabled USB Development (aka adb).
For now the only known way to recover is through adb. No fastboot or signed update.zip for now.
navalynt said:
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Click to expand...
Click to collapse
When I lost ADB access because of a hard reset (I think), this is what I did to fix my issue: http://forum.xda-developers.com/showthread.php?t=974824
I never lost root after a hard reset so I went to the market and bought root explorer and sqlite editor and copied the adbd to the /sbin folder to fix adb. I then bought sqlite editor and followed this: http://forum.xda-developers.com/showthread.php?t=972760 to re-enable side loading of apps. To install apps that I had the apk's for.
I still lose adb after a reset, but I can copy the adbd file to the /sbin folder and adb works again until I reset the phone.
I made a post about losing adb access on the motorola support forums: https://supportforums.motorola.com/message/332307#332307 to see if there were any solutions, but Mark said he would get back to me after trying to reproduce my problem.
I hope this helps.
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
No problem. That sucks, I'm not sure what you can do. Hopefully motorola or someone here will get a sbf soon so we can mess with our phones and have a way to fully recover. I hope you get it working again. Good luck!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
shadowscreation said:
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Requires USB Debugging to be enabled, but I have no access to enabled it due to Settings force closing and no ADB access in pre-boot.
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
adlx.xda said:
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
Click to expand...
Click to collapse
It won't let me install a downloaded APK because of the security restriction.
If you have an SD card, try booting into recovery with an update.zip on the file.
I can get into the recovery, but the update.zip file needs to be signed. I created one that will push the original copies of the framework files I was working with but it won't install because it's signed with test keys. The stock recovery 3e needs update.zip files signed with the manufacturer release-keys which only Motorola has.
https://supportforums.motorola.com/thread/46051?tstart=30
I started a thread on the official Motorola Owner's Forum in hopes I can find a full factory restore method for the OS. It's unfortunate that unlike HTC and other manufacturers who release full wipe RUU files Motorola has chosen to keep their restore files internally.
http://www.4shared.com/file/7YXo_gmO/update.html
That's the link to the update.zip file I was trying to use that fails because it's only signed with test-keys.
Retracteddd
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!
Indirect is proud to present you with ADB Hijacker
Note: This modification will remove any custom clrbootcount.sh scripts
Alright, what this application does, is hijacks adb using a root version instead which means from now on, you can do "adb remount" and things like that. This comes with all the needed files within the app and it also extracts them so no worries!
After you run the app once and click that magical button then you can reboot and you will have adb autostart as root so you can even uninstall the app afterwards. As of now, we do not have automount killed. However: I learned that adb stays on even while in usb mode.
Download Link:
Here
Screenshots: Uploading
Benefits and change log:
Benefits:
Code:
You can now rerun the rooting script to apply whatever modifications you missed out on
You can now apply any mod using adb instead of file explorer
You can remount your system by just using "adb remount" instead of using a file explorer
Changelog:
Code:
2.0: Included needed files for extract / included busybox installer
1.0: Initial Release
Credits:
Code:
brianf21 for showing me how to extract files from an apk so now you can install directly from the app and nothing else is needed except root.
Nemith for the adb daemon
Myself for the app, hijack method, and testing
puellanivis from IRC for being terrible at communication and also help with a few of the commands
This one is mine as well.
damn you, I am taking this one for video! click comment for video
Firstly,
Thanks Indirect, you make my Nook a joy to use. Many thanks also to Albertwertz - your Youtube videos are helping a noob like me get up to speed with this Android experience.
Can't post this in the Developer thread (still under 10 posts) but there seems to be a problem running the nookandzergy.bat file whilst running the ADB Hijacker. I'm getting a dos error:
"Your device was found to be rooted. Which is bothersome. However: I will see if you happen to have the proper modification installed to continue to use this script:"
followed by
"goto was not expected at this time".
Having a quick look at the bat file I can't see where %adbr% is being set to "yes".
Update: After making sure adb hijack was running, I tweaked the batch file, forcing adbr=yes. The script then worked and allowed me to replace the SystemUI.apk to remove the B&N Home button. Not sure how Indirect intends to set the variable properly, but by adding:
set adbr=yes
above the line:
if %adbr%==yes goto N1
Allowed by to re-run the rest of the root process
Another thing I did notice when testing the script was that by selecting "N" to the "Do you want to replace the systemUI to have a perm back / menu button on status bar and have the N button goto home on first click?" question the script errors with a -N7 not found.
I am having the same problem. I followed the video that albert posted and even opened up the cmd line to double check my adb remout. Everything worked fine till i get:
"Your device was found to be rooted. Which is bothersome. However: I will see if you happen to have the proper modification installed to continue to use this script:"
followed by
"goto was not expected at this time".
I don't know if Nook&Zergy is setup to support the adbd hijack yet. But that is the most likely answer. Or in particular, you might not have the newest N&Z as well.
I also wanted to momentarily divert the thread, and mention that snowball-mod already includes this adb-hijack, so it is unnecessary to run it on snowball-mod. (However, Indirect worked with me to ensure that it wouldn't hose anything if you did.)
Before I ran nz, i downloaded the latest from Indirect's original root thread. If the updated one isn't using that link, then where do I find it?
Indirect and I were up kinda late last night working on this and he made several modification on my nook zergy extraction that he may have forgotten to make when he remade his and uploaded it for everyone. Here is a link to the mod he made of the latest nook zerg on my pc. This may have something that the new one doesnt that he forgot to do. I am sure he will fix the code soon, but until then, download and try this: http://dl.dropbox.com/u/24100179/Nookie/NookandZergy.bat
this is the nook zergy bat file he modified. copy it and replace the bat file in your new nook zergy extraction and see if it runs right with this app
This is only temporary, dont use this after he fixes it
That did the trick! Thanks Albert!
I just got my nook & I don't understand the programming that you are talking about. But if you both were up late working on the root script (assuming). Just an FYI once I finished w/ the driver loads & started loading the root script, my device wouldn't show up, did a factory reset 3 times, as well as removing any usb traces etc... finally got it to take & all the red stopped & never loaded in the gapps, launchers etc... I reloaded it again & it says that I am rooted, but having a heck of a time w/ Titanium doesn't want to accept any of the
devicemanager .apk stuff. Sorry for no tech terms, Indirect & Albert Thank you so much for making this easy. Loved the video, really helped a ton. Just wanted to say thanks & let you know of the glitch.
I got it loaded now it is not recognizing the sd card 4 Titanium. I have done several of your factory reset, as well as the b&n reset still nada even put in 4 different cards. Happy New Year & Thanks for any help
TRI
did this today, easy, took 5 minutes. Grateful for all this
I'm a little bit confused, my nook updated to 1.41, i've tried downloading adb hijacker to my nook, but it won't open, what am I doing wrong?
Edit: What exactly do I need to do to block the updates and allow my nook to use the android market again?
I'm a pathetic no0b, and I tried downloading the ADB hijacker to my nook, but it won't open. What do I need to do to fix this?
Thank you.
ETA the Nook updated the other day.
Indirect said:
Indirect is proud to present you with ADB Hijacker
Note: This modification will remove any custom clrbootcount.sh scripts
Alright, what this application does, is hijacks adb using a root version instead which means from now on, you can do "adb remount" and things like that. This comes with all the needed files within the app and it also extracts them so no worries!
After you run the app once and click that magical button then you can reboot and you will have adb autostart as root so you can even uninstall the app afterwards. As of now, we do not have automount killed. However: I learned that adb stays on even while in usb mode.
Download Link:
Here
Screenshots: Uploading
Click to expand...
Click to collapse
absolutely awesome!
Guys, this doesn't stop updates or is usable on the 1.4.1 update..it's a 1.4.0 modification that hijacks the adb daemon on the device.
Ok, but what do we do if we didn't get to it in time and the stupid thing updated to 1.4.1? Do we have to return the thing to factory settings and lose all our content?
I'm sorry for asking dumb no0b questions, but if there is a guide for what to do in this situation, I can't seem to find it here.
Thanks for all you do, all the experts here!
ETA I found what I was looking for, in the "Nook general" forum. sorry to waste space on this thread.
My mistake, I thought I would be able to apply the update that stops the ota's through this. Which thread has the method to allow me access to market again? (effectivly null n' voiding the 1.41)
nearlyno0b said:
Ok, but what do we do if we didn't get to it in time and the stupid thing updated to 1.4.1? Do we have to return the thing to factory settings and lose all our content?
I'm sorry for asking dumb no0b questions, but if there is a guide for what to do in this situation, I can't seem to find it here.
Thanks for all you do, all the experts here!
ETA I found what I was looking for, in the "Nook general" forum. sorry to waste space on this thread.
Click to expand...
Click to collapse
^^^^^ Quoted for the sake of others ^^^^^
arkraven000 said:
My mistake, I thought I would be able to apply the update that stops the ota's through this. Which thread has the method to allow me access to market again? (effectivly null n' voiding the 1.41)
Click to expand...
Click to collapse
Below is a link to the information as to how to remove B&N 1.4.1 update and restore 1.4.0:
[Stock Firmware]Restore Barnes & Nobel Nook 1.4.0 from SDCard
ENJOY!
Have a strange one I don't know how to fix. Purchased a Pyle PTBL102BCD tablet for the Mrs. to use basically as an ebook reader (according to About, running 4.2.2). When it came in I started sideloading apps to prepare it for her (I do not have a Google account), and searched on the Net about rooting the device. Found a one-click that worked with a different Pyle tablet, so I gave it a shot.
Now I have root access _only_ through the adb shell. None of the apps (including Superuser.apk itself as tested by updating /system/bin/su) can get root access, yet I have no problem running root through an adb shell - remounted file systems, even performed an su which is the only instance Superuser.apk's log shows. Root access in the shell remains between reboots, so it's not a temporary root.
If the adb shell has root, I _should_ be able to use it to grant access to everything else, and I've followed a few different "manual" root instructions (having different permission settings for su and busybox), with no joy. So long as I connect with a USB cable and type on the Windows machine, I'm god. On the tablet itself...not so much.
I hope that someone with a more intimate knowledge of Android internals can point me in the right direction for achieving root completely. Currently have Titanium Backup and ConnectBot (long java errors when I attempt to su there) installed to test root, Superuser v3.1.3 and su v3.1.1. Permissions on su are -rwsr-sr-x. And the human is confused.
Did you get anywhere with this? I have the same problem. What one-click did you use?
mfurlend said:
Did you get anywhere with this? I have the same problem. What one-click did you use?
Click to expand...
Click to collapse
Side note; REALLY hate the new forum software. With all the untrusted Google and Amazon javascript (which my company firewalls), it's a pain for me to even log in let alone post replies. (And I wonder if I'm the only person in the world sick to death of all the unnecessary ajax garbage...)
Anywho, used Kingo, rooted and unrooted a few times, until I finally acquired complete root on the thing. Once I did, I could run Samba, and once that worked, I could more easily transfer files and apks to the tablet.
Still don't understand why it was left in such a...weird...state - having root by default in adb is just a scary thing!
thanks for the information. I tried doing that but I encountered various problems. Eventually, after trying to do it manually, I totally screwed up the device. Now it won't boot.. I still have access to adb. I need to flash this thing. Do you know what the stock ROM is?
mfurlend said:
Do you know what the stock ROM is?
Click to expand...
Click to collapse
No...I can give you the Kernel version info (3.0.36+ [email protected] #48) and build number (rk3168_k11_4.2.2_v20131230), but other than that no clue.