Related
I got a uk glow worm on the 27th (2 days before release ) and one of the first things that I tried to do was to root with glownooter. Bad idea! I thought that I had bricked my device. I had to use a lot of trickery to recover from a loading screen lock-up and once I did the first thing that I did was backup my nook (Which i should have done before).
UPDATE!
Please try my new ROOT install pack HERE:
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
This can be used to root and install the most requested things of this thread in just one zip.
Here is a quick guide to most things you will need to do to get started. I will update this guide as I discover and build new modifications.
To Backup and Restore
Follow this guide. Please do this BEFORE any other tinkering!
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Its important to check your backup before proceeding! Please listen to roustabout and dont skip this step... He knows what he's talking about
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks roustabout
To Root!
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994 (Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593 (Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
To Add Apps
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Setup ADB over USB
OK I have taken the liberty of building a quick driver mod to support your nook through USB. It works for me. First you need to have the android SDK if you don't already (sure you do but just in case ).
http://developer.android.com/sdk/index.html
Make sure you tick to install the android USB driver when the SDK is installed.
Browse to extras\google\usb_driver in your SDK folder (wherever you put it) and replace android_winusb.inf with my file:
http://dl.dropbox.com/u/13673492/android_winusb.inf
Next go to C:\Users\your_user_account\.android and replace adb_usb.ini with my file:
http://dl.dropbox.com/u/13673492/adb_usb.ini
In device manager, point google ADB driver to this and hopefully that should get you set up!
To test type
Code:
adb devices
Its working if you get something like this:
Code:
* daemon not running. starting it now on port ____ *
* daemon started successfully *
List of devices attached
[YOUR NOOK] device
And then try
Code:
adb install app_of_your_choice.apk
UPDATE
Install Multitouch Kernel With Overclocking
Install the CWM zip using your clockworkmod SD card
http://forum.xda-developers.com/showthread.php?t=1906507
:good: Thanks to johnjtaylor for discovering that this kernel works works.
Hopefully this more comprehensive guide will get others with this software to start playing around.
If this helps, be polite and say thankyou
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
David0226 said:
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
Click to expand...
Click to collapse
Thanks for replying. I'm actually working setting up ADB now. As for books I only just got my nook so all of my titles are epub format on an sd card so i wouldn't think it would be that. As soon as I get ADB set up I will post back my results incase it helps anyone else with this new software version.
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
I set up ADB.
Plenty of space in all partitions including /data for the apps that I want. Managed to install through "adb install some_app_i_want.apk" so problem resides with the amazon app store. Not really an issue for me because I have a specific set of apps that I want and don't need to browse the app store.
I will try to work out what's wrong for others.
staylo said:
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
Click to expand...
Click to collapse
Thanks. I'm looking for it now
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
loney01843 said:
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
Click to expand...
Click to collapse
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
staylo said:
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
Click to expand...
Click to collapse
You're obviously not that lazy. Thanks for looking and gathering all of the extra info I need. I'll send B&N an e-mail and see what they say. I wouldn't be surprised if they didn't want to hand it out considering you can use it for an easy root setup and install the amazon and kobo stores which could financially damage their advance into new territories! What are we to do! Can't even subscribe to a newspaper or magazine through the nook store yet!
I'll let you know when / if I get a response
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
roustabout said:
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
Click to expand...
Click to collapse
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
UK tinynoot attempt failing
loney01843 said:
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
Click to expand...
Click to collapse
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
smerrett said:
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
Click to expand...
Click to collapse
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
loney01843 said:
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
Click to expand...
Click to collapse
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
smerrett said:
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
Click to expand...
Click to collapse
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
loney01843 said:
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
Click to expand...
Click to collapse
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
smerrett said:
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/13673492/n2T-Recovery_0.2.img
This is the file needed to force factory reset. However a quality backup like you have is far more important.
For anyone who wants to give this a go, here is a quick guide for root access and app installs using windows tools until I can make something more complete:
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994
(Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593
(Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
loney01843 said:
If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
Click to expand...
Click to collapse
Great - thanks to your more detailed instructions, I have persevered and the second attempt at installing the tinynoot zips worked. Your post gave me the confidence to try installing apks for the first time and for anyone else who is unfamiliar with the processes used, I found these two pages useful for:
navigating within a command prompt (how naive): pcstats.com/articleview.cfm?articleid=1723&page=3
Pasting text into a command prompt (ditto): megaleecher.net/Copy_Paste_Text_Dos_Window
Sorry, as a newb I'm not trusted to post outside links yet. It took a couple of attempts of pasting and pressing enter to work out how to install using the adb code but it's not as hard as I expected.
I have tried installing the 1 Mobile Market which works but it is unable to install apps itself (not enough space).
Also, I have just installed NoRefreshToggle and can't seem to get it to work. Any thoughts - is 1.2 to blame? Really want this to work as Business Calendar Free is just a series of blinks at the moment!
Great! I'm glad you pushed onward and have root.
I am going through possibilities of other ways to install apps and mods.
No refresh is something that I would like as well but I think that the framework may need editing for 1.2.0. For fast mode a new kernel will need to be made or existing one modified.
Be aware that installing kernels not designed for this firmware can give you some serious problems.
Once I can setup app markets, I will work on these other modifications.
Stay tuned :good:
Take a look at the overclock kernel - it's got a lot of the norefresh features baked in, and gives you a nice ability to control both clock and kernel tuning (via the governor control.)
You're right, you can flash the two zips back to back with no ill effect, I was mistaken about what the second zip was doing.
I mistyped when I typed "nook touch tools," I meant nook color tools.
I'm very interested that the amazon store is not working in 1.2. I will see if the software's available for my device, so I can try to see what's happened.
As of now, the us bn site does not mention an os 1.2 for the glowlight.
Sup everyone,
I finally got around to updating my TMO DVP. It's been stuck on 7720 this whole time and want to bring it up to Tango.
My question is: what exactly are the steps to upgrading???
Here are the threads I'm trying to follow in order:
http://forum.xda-developers.com/showthread.php?t=1103011
http://forum.xda-developers.com/showthread.php?t=1497142&nocache=1
http://forum.xda-developers.com/showthread.php?t=1736993
From what I understand it:
Install Windows Phone Support Tool
Install WP7 Backup 1.6
Install WP7 Update Cab Sender
Then???
I don't get it. I've installed WP Support tools which doesn't make sense. I have Win7-64bit. The downloads available are x86 or amd64. My computer is intel based, so which do I use? x86 doesn't install, makes sense. I installed amd64.
My next problem is, are there different versions of WP Support Tools? My Zune is up-to-date 4.8.2345.
After installing WP Support Tools:
WPSupportTools.exe is version 0.0.0.0, date modified 4/1/11
UpdateWP.exe is version 6.1.7600.16385 date modified 4/1/11
Microsoft.WindowsMobile.DeviceUpdate.dll is version 4.7.1404.3 date modified 4/1/11
When I run WP Support Tool, I get:
UpdateWP version 4.7.1404
Error: The installed version of the tool (4.7.1404) needs to be updated to match the Zune version (4.8.2345). Please install the tool version 4.8.2345.
Click to expand...
Click to collapse
What do I do?
UpdateWP.exe Information: 0 : 12/25/2012 12:48:25 AM: Device Manager Initializing
UpdateWP.exe Information: 0 : 12/25/2012 12:48:26 AM: Device Manager Initialized
UpdateWP.exe Information: 0 : zune-tuner://windowsphone/5e7a3cc3%20-%20ebd23705%20-%202fd2d1be%20-%20b9b323c8
UpdateWP.exe Error: 0 : 12/25/2012 12:48:26 AM: Update Exception: System.Runtime.InteropServices.COMException (0x801812C0): Exception from HRESULT: 0x801812C0
at Interop.ZuneWmduLib.WmduFirmwareUpdaterClass.StartFirmwareUpdate(IFirmwareUpdateCollection pUpdates, IFirmwareUpdateCallback pCallback)
at Microsoft.WindowsMobile.DeviceUpdate.Device.Microsoft.WindowsMobile.DeviceUpdate.IDevice.Update(String[] URIs, UpdateType UpdateType, Action`1 progressMadeCallback, Object context)
Click to expand...
Click to collapse
Log from when I got somewhere and nothing happened.
I've uninstalled and deleted everything. If anyone can help me out from square one it'd be much appreciated.
KnightmareCS said:
Log from when I got somewhere and nothing happened.
I've uninstalled and deleted everything. If anyone can help me out from square one it'd be much appreciated.
Click to expand...
Click to collapse
It's been a while since I did this. But you did right, AMD64 is correct. And try the file I attached as that's the newest version to match your Zune software. Let us know if you run into anything :good:
(and no, I didn't create the file. I just have it archived from a working cab sender upgrade so credits go to the original poster)
Ok,.
So I installed WP Support Tools.
Copied the files you gave into the Zune directory.
Copied WP7 Backup 1.6 into the Zune directory.
Tried running a backup.
Attached is the error message I got.
I tried the cmd method and that gave the same error.
GoodDayToDie said:
I ran into this issue too.
First question: Is your Zune install in the default location? The support tool installer seems kind of... stupid. It always installs in \Program Files\Zune even if Zune isn't actually installed there. You can copy the files from that location to wherever Zune is installed, if not. Be careful of overwrites.
Next question (really the important one, but the question above can be the reason for the problem): Is there a file called wm7updatelib.dll, or similar, in the folder with your UpdateWP.exe? If so, is it the same version (exactly, down to the build number)? If not, you may need to re-install the support tool (I suggest uninstalling it first, using appwiz.cpl).
Click to expand...
Click to collapse
Looking at this post.
I have wm7update.dll (not wm7updatelib.dll). It is file version 1.0.0.1 /product version 7.0.0.0.
Can you post the right library file?
Thanks
-
Attached are a list of my files and versions in Zune folder. (Ignore the dual Microsoft and UpdateWP, I just added garbage text to the originals)
Backing up now.
Copied the files attached.
wm7update.dll
Interop.wm7updatelib.dll
Interop.ZuneWmdulib.dll
BEASSSSSSSSST running 8773!
KnightmareCS said:
BEASSSSSSSSST running 8773!
Click to expand...
Click to collapse
Good work Glad to see you figured it out. Might want to share your experience if you ran into specific problems in case others have it?
Thanks.
All it was, was making sure I had the right file versions for the right files. Those of which I posted above.
aleunge said:
Good work Glad to see you figured it out. Might want to share your experience if you ran into specific problems in case others have it?
Click to expand...
Click to collapse
I've just update to 8773 myself as well. However, I want to ask you a question: whether we could re-write the firmware version also? My OS version is 7.10.8773.98, but firmware is 2250.1800.7720.219.
No idea. I noticed that too, but haven't seen anything about it just yet.
KnightmareCS said:
No idea. I noticed that too, but haven't seen anything about it just yet.
Click to expand...
Click to collapse
Yeah, maybe it's not necessary enough for us to consider that. However, I just noticed that while updating via Zune, this firmware version string is changed, but not with CAB sender. So, I just guess there might be a way to do it by ourselves too!
please note that the firmware package contains the bootloader drivers etc.etc.
Dell will probably not update those any more. The latest o.s. updates are provided by microsoft and they don't include any drivers whatsoever.
As long as the OS version is the most recent, you're good.
READ THE ENTIRE POST BEFORE DOING ANYTHING
Disclaimer
I'm not responsible for any problems caused by the use of the installer or by user error and not reading the entire post.
What is it?
First of all, the Easy Installer is not in any way related to Gradular's or xcd's installer. Though these tools are great they don't completely install Android for you. The Easy Installer will completely install Novacom and Java (if needed), get the necessary Android files, and run the command to install them. This does everything for you so you don't have to (whether you are just lazy or new to installing Android).
How to Use (Installer)
There is a single zip file to download which contains installers for both CM9 and CM10. When you download it, extract it. You must then move the easyinstaller folder to "C:\easyinstaller". You must do that or it won't work. Then Run as Admin the correct easyinstaller_cmx.bat (where x is the version you want installed) and it will start the program. Follow the necessary instructions it gives and it will complete your Android install. It's that easy!
How to Use (Uninstaller)
The program is included in the same file as the installer. It is universal for both CM9 and CM10. Follow instructions above for setup but instead Run as Admin easyuninstaller_cmx.bat and it will start the program. Follow the necessary instructions it gives and it will complete your Android uninstall. It's that easy!
How Easy is It?
You only have to do a few things to completely install Android. Plug your Touchpad into your computer in USB mode (in webOS or TWRP Android is not supported but might work). Then, when it says to boot to recovery mode, do it and it will then install Android. Pretty easy stuff huh?
Downloads
Here is the only download you need. Notice that its possible that the roms will be outdated. I will always try to update the Easy Installer with the latest versions of Android. The download is large because it gets you ALL the files needed to install Android.
Download Zip File Here (Mega) v 1.0.3
Download Zip File Here (Google Drive) v 1.0.3
Bugs/Issues
If you find any bugs are have any issues with the program I encourage you to post them here as I am entirely open to making Easy Installer the best experience.
Changelog
v 1.0.0 - Initial Release
v 1.0.1 - Renamed gapps files so they install thanks RolandDeschain79
v 1.0.2 - Renamed CM9 for compatibility, added Uninstaller, fixed fatal coding error
v 1.0.3 - Fixed coding errors thanks hperry and basshead73 added Google Drive link
Next Release Improvements/Fixes
I need testers!
If you have ever tried this out all feedback is appreciated.
Remolten said:
I need testers!
If you have ever tried this out all feedback is appreciated.
Click to expand...
Click to collapse
I'm actually gunna try it when i web doctor my TP
I Will give ya some feedback
Updated with latest Nightly 2/24.
I just tried it. It seemed to install correctly, but CM9 is stuck at the boot screen
Jive Turkey said:
I just tried it. It seemed to install correctly, but CM9 is stuck at the boot screen
Click to expand...
Click to collapse
Probably an issue with CM9 not the installer.
Uninstalling it works at least :/
Attempting to install again. I have a lot of Android files from an old install. I'm removing them in case that's the cause of my problem.
... cancelling Java causes the script to fail. I made sure to Cancel, not close.
... continuing the install. Android is installing...
IT WORKED!!!
It must have been one of the old remnant Android files giving me grief.
---------- Post added at 06:59 PM ---------- Previous post was at 06:02 PM ----------
Thank you. This was much simpler than the previous methods I have used to install Android on my TouchPad. I have a few suggestions, that I hope may make your installer even better:
I don't see anything in your code that requires the installer be in "C:\easyinstall". I think you could omit that instruction.
Line 9 should mention USB Drive mode. I misunderstood it and I think others might too.
Tell people to install Java and novacom themselves separately. This will eliminate extra steps for those who already have them installed. This will also prevent problems with those that close the Java installer without installing it. This will also mean you don't have to worry about keeping the version you supply up do date (it's already outdated as I write this). I think something like this would be better:
Code:
echo Now you need to download and install the latest version of Java.
echo Press a key to open the Java download website.
pause >NUL
start https://www.java.com/en/download/index.jsp
echo.
echo When you have downloaded and installed Java, press a key.
pause >NUL
echo.
echo Now you need to download and install Novacom.
echo Press a key to open the Novacom download website.
pause >NUL
start https://code.google.com/p/universal-novacom-installer/
echo.
echo When you have downloaded and installed Novacom, press a key.
pause >NUL
I hope that's helpful. Thanks again
It worked but didn't work. The java updated, novacom came up, and it went into double penguin mold, but I still have the same date android.
Which Andoid build did you have?
I thank it was 2-17. That was a couple of weeks ago.
cdmcfud said:
I thank it was 2-17. That was a couple of weeks ago.
Click to expand...
Click to collapse
Will update soon.
Links not working
The links above on the main post aren't working folks!
silentarts said:
The links above on the main post aren't working folks!
Click to expand...
Click to collapse
Abandoned.
Remolten said:
Abandoned.
Click to expand...
Click to collapse
does anyone have a mirror?
bearsfan85 said:
does anyone have a mirror?
Click to expand...
Click to collapse
If I get enough interest maybe I can rewrite as I deleted it.
I'm selling my TP in a day or two but maybe I could get something up before it's gone.
Remolten said:
If I get enough interest maybe I can rewrite as I deleted it.
I'm selling my TP in a day or two but maybe I could get something up before it's gone.
Click to expand...
Click to collapse
The main thing I needed were the proper drivers as the 64bit sdk from palm is not available on their website, or at least it wasn't last night. After doing some more searching I was able to find what I needed. Thanks for willing to help out others though even though it doesn't benefit you.
Does Jolla / SailfishOS allow installation of applications to SD card?
Meaning?
uhh good question mate
I have done some thinking after posting this. As far I know Linux does not give you a choice of where to install an application using regular package managers.
So the answer may be no.
sling-shot said:
I have done some thinking after posting this. As far I know Linux does not give you a choice of where to install an application using regular package managers.
So the answer may be no.
Click to expand...
Click to collapse
Technically speaking, unless application has hardcoded paths there should be no problem installing it whereever you want it on Linux, you'll just need to either add path to it's executable to PATH variable or explicitly specify full path when starting it.
I was speaking out of ignorance.
So it is technically possible. Does the default setup of Jolla give an option of installing to SD card?
sling-shot said:
So it is technically possible. Does the default setup of Jolla give an option of installing to SD card?
Click to expand...
Click to collapse
That I don't know as I don't own the Jolla phone yet (I'm oustide of EU), I'm not aware of any freely available existing ports to other devices, and I don't have enough time/skills to attempt to port it myself.
Is there any further information on this topic? Any Jolla owners around?
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
WORKS ON 5.1.1 ALSO!
(Link in next reply)
Fully automated and noob friendly. :3
Done:
Root
BusyBox
Disable OTA
Change Launcher
Install full Google Play Functionality
Autoinstall flash player
build.prop optimizations
A few more features...
This may be compatible with other fires, but I have only tested it on the Fire 7" 5th generation.
This is a script I wrote in my spare time.
This script will optimize, root, install google play, and debloat your device.
Enjoy :3 Don't forget to hit thanks.
STEPS
1. In device options, tap on serial number until the developer options appear. If required (which it is likely not, but for some it is. DON'T DO THIS IF IT'S ALREADY WORKING.) install the ADB driver by going into the device manager of windows and rightclick update driver on your device under unkown devices, then point it to the driver folder included in this zip, or, you know, try the driver installer .exe included. Make sure driver signature enforcement is disabled in Windows!
2. Go into the developer options of android and enable Debugging
3. Go to the homescreen on the tablet, EXTRACT the zip on your computer, and run the script 1_ROOT_FIRE.bat in the zip on your computer.
This should only take around five minutes too complete.
YOUR DEVICE WILL REBOOT SEVERAL TIMES.
Easy enough, right? :3
Troubleshooting:
Unless you are running Fire OS 5 or higher, using this script probably won't get you playstore access, but it may root it. This was made primarily for the Amazon Fire 5th Generation 7" Tablet. (The "50 dollar tablet")
Don't run as root or admin.
If your device gets stuck in fastboot:
When the device reboots and goes into fastboot mode the drivers didn't recognise it. Leave the script running and go into Device Manager. Your Kindle will be listed as "Fire" with a yellow icon. Follow same steps to install drivers but instead of directing it to the "usb driver" folder contained in the zip file - select "let me pick from a list of drivers". Then pick adb interface then scroll to the bottom and select the last option.
The script hangs on adb daemon started:
If it hangs there, android debugging on your device isn't communicating with your computer. The fix can range from reconnecting your device, making sure android debugging is enabled in the Device> Developer options, making sure adb drivers are installed, or restarting the script.
Keep in mind, if you give this tablet to a non tech savvy user, open SuperSU, go to options, and click full unroot.
XDA:DevDB Information
AutoRootScript, Tool/Utility for the Amazon Fire
Contributors
glitch3yf0x, JaboJG, KennBr, k4y0z
Version Information
Status: Stable
Current Stable Version: 4.14
Created 2015-12-30
Last Updated 2016-04-08
Secondary Download Mirror
(Recommend) REGULAR VERSION:
https://www.androidfilehost.com/?fid=24352994023705981
NO DEBLOAT version:
https://www.androidfilehost.com/?fid=24391638059059079
Read the post below to choose the version right for you.
Version diffrences
Regular version: Choose this if you want the full android experience to your tablet with the added features of the script. This will remove all the unwanted Amazon bloatware that fills up the internal storage and will make your tablet feel more like an android tablet.
No debloat version: Choose this if you want to keep the Amazon experience with the added features of the script. This will leave Amazon's features and will make your tablet feel more like an Amazon tablet.
Notice: this script will not wipe or touch any of your files on the internal storage or sd card
Fully stable!
Great news! All bugs have been fixed! As of version 4.14 uploaded 1/5/16, all OS versions have been tested and are confirmed working properly. Enjoy!
If anything goes wrong, such as a USB cable being unplugged or the battery dying, pretty much anything can be fixed by booting into recovery and adb sideloading the latest firmware.bin from amazon.
Thanks for Donating:
Lorenzo
@BarbaraaK
So was the Mac OS X issues fixed?
pride0929 said:
So was the Mac OS X issues fixed?
Click to expand...
Click to collapse
I believe so [Old post. Issue fixed with 4.14, if there was one.]
I ran the script using OS X, everything seemed to go well. But the Fire is stuck booting at the "fire" logo.
Mac OS X
jmallow said:
I ran the script using OS X, everything seemed to go well. But the Fire is stuck booting at the "fire" logo.
Click to expand...
Click to collapse
Updated issue. [Issue fixed with 4.14, if there was one.]
glitch3yf0x said:
Give it 10 minutes before force rebooting. It may be rewriting cache. This is very odd. Any error messages on the computer?
Don't worry about your tablet. We can adb sideload if anything wen't wrong.
What OS is your tablet running? Is your tablet the Fire 7? It may be an issue with build.prop. I'm retesting it now using the Mac OS X source files. In the mean time, tell me if your Fire boots.
Click to expand...
Click to collapse
It's a 5th gen Fire 7 (the one that was released in Sept 2015). I side loaded to get back to factory, but mistakenly used the fire hd .bin file...and now it won't turn on at all. Lol. Might be a dead battery though I think, so its plugged in now. Will try again after a bit.
jmallow said:
It's a 5th gen Fire 7 (the one that was released in Sept 2015). I side loaded to get back to factory, but mistakenly used the fire hd .bin file...and now it won't turn on at all. Lol. Might be a dead battery though I think, so its plugged in now. Will try again after a bit.
Click to expand...
Click to collapse
Alright. Best of luck. I tested it on my fire again and there were no problems. If you have problems the second time tell me.
Any results?
glitch3yf0x said:
Any results?
Click to expand...
Click to collapse
I bricked it by installing the wrong version by mistake.
Hopefully Amazon warranty will replace it without question.
I've just run the script for my daughters fire 6 5th gen running 5.1.1 and all went smoothly. Has the look and feel of a great wee device now!
Thanks for your efforts ☺
Thread moved from http://forum.xda-developers.com/amazon-fire/general/root-fire-5th-gen-autoroot-script-noob-t3276923
Just installed this without a hitch. So far so good!! Thank you!!
Worked really well on 5.1.1 Thank you so much!
Now the only issue I have is that I want to use Google Now Launcher in place of Nova. Is there a way to do it?
EDIT: Never mind, it asked me which home to set after a reboot.
thehrushi said:
Worked really well on 5.1.1 Thank you so much!
Now the only issue I have is that I want to use Google Now Launcher in place of Nova. Is there a way to do it?
EDIT: Never mind, it asked me which home to set after a reboot.
Click to expand...
Click to collapse
I should post a poll. Google Now or Nova.
glitch3yf0x said:
I should post a poll. Google Now or Nova.
Click to expand...
Click to collapse
Just add a selector in the script and have it push the appropriate apk
BaT420 said:
Just add a selector in the script and have it push the appropriate apk
Click to expand...
Click to collapse
I was gonna suggest the same. Nova after rooting makes sense, since the widgets work. But I like Google Now on left swipe.
Yeahhh
Very good. Fire 7 2015 5.1.1.
Now I've an Android table not a garbage :good:
thanks a lot.