I just recently moved into this part of the forum, trying to find my way around and I notice that there are no sticky's or wiki pages. I have a few questions that I want to ensure are answered with up-to-date information.
Yes I have searched. It's stupid having to include that qualifier but I know how some people are.
What are the differences between the touchnooter's - 1.1 (2.1.31) & 1.0 (1.6.24)? I can guess that they apply to specific software packages, but I do not like to guess with rooting.
I have software 1.0.0 and I see the update at B&N for 1.1.2 so should I upgrade first or does it matter?
Does the NST require themes that are monochromatic or specifically modified? Or will any launcher or configuration work?
Is there a known way to brick that I should be aware of?
I appreciate any help.
Nuenjin said:
What are the differences between the touchnooter's - 1.1 (2.1.31) & 1.0 (1.6.24)? I can guess that they apply to specific software packages, but I do not like to guess with rooting.
Click to expand...
Click to collapse
1.1 (2.1.31) is for the software versions 1.1 and 1.1.2, 1.0 is for the software versions 1.0 and 1.0.1
I have software 1.0.0 and I see the update at B&N for 1.1.2 so should I upgrade first or does it matter?
Click to expand...
Click to collapse
You should upgrade to 1.1.2 first, making updates breaks root, so do it before you start rooting.
Does the NST require themes that are monochromatic or specifically modified? Or will any launcher or configuration work?
Click to expand...
Click to collapse
Everything that supports Android 2.1 works. There are some apps with unreadeable text in the menus, but most work just fine.
Is there a known way to brick that I should be aware of?
Click to expand...
Click to collapse
Some people bricked their nook by writing the rooting images directly to the nook and not to a sd-card. Just make a backup http://forum.xda-developers.com/showthread.php?t=1142983 and make sure that it's size is ~2GB and you are on the safe side.
The wiki is real
Nuenjin said:
I just recently moved into this part of the forum, trying to find my way around and I notice that there are no sticky's or wiki pages...
Click to expand...
Click to collapse
Welcome to our little corner of the galaxy. Actually, there is a tiny but growing wiki:
Barnes & Noble Nook Simple Touch (NST) wiki
Related
Just got mine today and have a question on how to proceed with Dexter's Mod.
The a7 is currently at v. PBJ8000.2.0124
Should I first update the firmware from eLocity's site (v. 2.0133) and then update with Dexter's v1.3 or should I just go straight to Dexter's?
Thanks,
_mr
middle_road said:
Just got mine today and have a question on how to proceed with Dexter's Mod.
The a7 is currently at v. PBJ8000.2.0124
Should I first update the firmware from eLocity's site (v. 2.0133) and then update with Dexter's v1.3 or should I just go straight to Dexter's?
Thanks,
_mr
Click to expand...
Click to collapse
Already asked, already answered.
Link:
[Q] mabey a stupid question - xda-developers
Thanks Netstat, I saw that one with yours and '5[Strogino]' replies,
however I didn't see where anyone had installed the latest firmware (2.0133)
I've seen references to v2.0121, & v2.0127 but haven't seen and can't figure out
where v2.0124 fits in. Probably mostly confusion on my part with all the reading
I've been doing since unpacking this puppy.
I wasn't certain if I had to have my tablet at v2.0127 before proceeding with
Dexter's mod or not.
_mr
middle_road said:
however I didn't see where anyone had installed the latest firmware (2.0133)
Click to expand...
Click to collapse
I installed 2.0133 already. Nothing extraordinary, except improved bluetooth compatability
middle_road said:
Thanks Netstat, I saw that one with yours and '5[Strogino]' replies,
however I didn't see where anyone had installed the latest firmware (2.0133)
I've seen references to v2.0121, & v2.0127 but haven't seen and can't figure out
where v2.0124 fits in. Probably mostly confusion on my part with all the reading
I've been doing since unpacking this puppy.
I wasn't certain if I had to have my tablet at v2.0127 before proceeding with
Dexter's mod or not.
_mr
Click to expand...
Click to collapse
To me it seemed like your question was "should I update to the latest eLocity update before installing Dexter's Mod"
That being the case, your question was answered. Installing the latest eLocity update before elocitymod 1.3 would be pointless since by installing elocitymod you are wiping the device (getting rid of the update you just ran)
Maybe I linked the wrong thread, I'll have to check on that.
netstat_EVO said:
To me it seemed like your question was "should I update to the latest eLocity update before installing Dexter's Mod"
That being the case, your question was answered. Installing the latest eLocity update before elocitymod 1.3 would be pointless since by installing elocitymod you are wiping the device (getting rid of the update you just ran)
Maybe I linked the wrong thread, I'll have to check on that.
Click to expand...
Click to collapse
middle_road said:
Just got mine today and have a question on how to proceed with Dexter's Mod.
The a7 is currently at v. PBJ8000.2.0124
Should I first update the firmware from eLocity's site (v. 2.0133) and then update with Dexter's v1.3 or should I just go straight to Dexter's?
Thanks,
_mr
Click to expand...
Click to collapse
First off......Welcome to the forums and I hope you enjoy your new Elocity A7.
Second......I apologies for the initial attitude you received. The answer to your questions is that there is no need to update to the official rom. Dexter has not made another update to the rom that includes the new update. I'm sure that he will in time.
Finally........You will still be better off installing the dexter mod over the official. Just having the market makes a big difference. May I also suggest that you install Launcherpro as well. It's a much nicer and more fluid way to go.
tetsuo_shima said:
First off......Welcome to the forums and I hope you enjoy your new Elocity A7.
Second......I apologies for the initial attitude you received. The answer to your questions is that there is no need to update to the official rom. Dexter has not made another update to the rom that includes the new update. I'm sure that he will in time.
Finally........You will still be better off installing the dexter mod over the official. Just having the market makes a big difference. May I also suggest that you install Launcherpro as well. It's a much nicer and more fluid way to go.
Click to expand...
Click to collapse
Sorry, I forgot to say welcome to the forums, so .... welcome to the forums.
As for the rest, how is clean dry facts attitude? People are way to sensitive these days.
tetsuo_shima said:
First off......Welcome to the forums and I hope you enjoy your new Elocity A7.
Second......I apologies for the initial attitude you received. The answer to your questions is that there is no need to update to the official rom. Dexter has not made another update to the rom that includes the new update. I'm sure that he will in time.
Finally........You will still be better off installing the dexter mod over the official. Just having the market makes a big difference. May I also suggest that you install Launcherpro as well. It's a much nicer and more fluid way to go.
Click to expand...
Click to collapse
Thanks Tetsuo! Precisely what I wanted to find out.
Dexter's Mod v1.3 flashed without any hiccups.
A couple of Apps that I had side-loaded under 2.0124 are acting up with the Mod, but I haven't had a chance yet to dig into them.
Having the Market is Great!
And my buddy just dropped off his A7 for flashing. Now we'll see if I can pull this
off twice in one week...!
_mr
Hello Everyone!!
I recieved my DX last Friday and am quickly becoming acustomed to it. I do, however, have a few questions and was hoping that you could point me to the right threads or answers I seek.
First off, Rooting and deodex. If I understand things correctly, I need to do this before I can make any changes/mods. I did read here:
http://forum.xda-developers.com/showthread.php?t=940986
It sounds pretty straight-foward and I'm not shy when it comes to doing this.
Second, start-up/running apps/battery life. I hear some people wishing for better battery life and others saying it's ok. I also read somewhere about disabling apps with a start-up mgr to improve battery life. Like a dummy I didn't bookmark the thread and can't find the info again. I'm curious about how to do this. Which apps can I safely disable without causing problems or making a brick. I really would like to get rid of CityID, amazon MP3, Blockbuster, and maybe a few others. There are many apps listed in the "running" section under manage apps, are all of these necessary?
And, Third, App Killers/Pgm Mgr's. Are they required/helpful? If so, any suggestions for a good one? I read about them in the post mentioned in Q2 and am curious. I'm not positive, but the thread I didn't bookmark may be elsewhere.
Thanks in Advance for any and all help and suggestions.
Mike
Heres a list some quick googling turned up on safe to remove apps in Gingerbread, nothing official, just what someone removed successfully
http://www.droidforums.net/forum/droid-x-hacks/137295-gingerbread-apps-safe-freeze-rename.html
Here is a list I found for Froyo
http://androidforums.com/droid-x-al...vable-non-removable-root-pre-gingerbread.html
There are a few ways to freeze/remove apps, but the method I use is using Root Explorer, rename the .apk file of the app you wish to remove, for instance, in the folder system/app/ you can find "CityID.apk", I would rename it to "bak.CityID.bak", where the first "bak" is to change the alphabetical order to group frozen apps, and the second "bak" is to remove the .apk file extension.
Everyone has their own opinions on Task Killers, but heres two articles that make sense to me
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Ok, this brings me to another, maybe dumb, question. When you say Gingerbread and Froyo, are they names for stock ROM's? If so, how do I know which one I have. I'm still learning about the DX and Android OS. I come from a Win6.x smartphone. The learning curve there was much shorter before I decided to flash a custom ROM to it (ookba's work is excellent, btw). Thanks for the first two posts, I'll read up and enlighten myself.
Android versions
They are android versions. Go to settings>about phoneand look for android version.
3.0.x is honeycomb
2.3.x is gingerbread
2.2.x is froyo
2.1.x is eclair
2.0.x is donut (i think)
Notice a pattern? I also came from windows mobile 6 so thats as far back as I know for versio.n names
SharkBaitDave said:
They are android versions. Go to settings>about phoneand look for android version.
3.0.x is honeycomb
2.3.x is gingerbread
2.2.x is froyo
2.1.x is eclair
2.0.x is donut (i think)
Notice a pattern? I also came from windows mobile 6 so thats as far back as I know for versio.n names
Click to expand...
Click to collapse
Pretty good. Donut actually started at 1.6 and Cupcake was 1.5. That's all I got lol
Fern, if you haven't modified your phone then you have FroYo.
Sent from my DROIDX using Tapatalk
Right- 2.0 was also eclair.
SharkBaitDave said:
They are android versions. Go to settings>about phoneand look for android version.
3.0.x is honeycomb
2.3.x is gingerbread
2.2.x is froyo
2.1.x is eclair
2.0.x is donut (i think)
Notice a pattern? I also came from windows mobile 6 so thats as far back as I know for versio.n names
Click to expand...
Click to collapse
Thanks for the info! I'm 2.2.1 aka Froyo. Now this gets me started. Anyone recommend a rooting and/or deodex pgm?
I am new to the Kindle Fire, and recently rooted with Kindle Fire utility without a hitch. Many thanks to all the Dev's that put that together, great work. I am not new to rooting and customizing ROMs on Droid phones, but new to the "tablet" world.
However, after doing some searching, I am unable to find information on some things.
1) Google Market. Its running fine, but there are a ton of apps missing from the market (ie Facebook). I have seen some threads on how to fix this if I am on CM7, but was wondering if its possible to do this on a "stock" rooted KF?
2) Blocking updates. Is there an easy way to "block" Amazon from being able to push updates to the device? I know this has caused issues like losing root, etc.
3) Freezing Apps. Are there any "standard" apps or processes that can be frozen/removed from the Stock ROM that aren't needed? I haven't been able to find a definitive "list".
Thanks again,
-Sf-
INFO
Hey there.
Let me see. You can use "Titanium backup" to freeze stupid things like maps. I dont have mine anymore so i cant populate a list for you atm. You can try to update the "Market" app to resolve issues with missing apps. My advice: use stock rom,root it. And use a launcher like launcher pro. Then use setcpu.
1 - try the modaco rom - it shows to the market as galaxy tab:
http://forum.xda-developers.com/showthread.php?t=1439916
2 - http://forum.xda-developers.com/showthread.php?t=1451328
this one is also a good starting place to find different things:
http://forum.xda-developers.com/showthread.php?t=1467013
Editing the build.prop file should fix market visibility. I just purchased and rooted mine last night but i'm also having the same issue. Going to try out this after work. Should do the trick. http://forum.xda-developers.com/showthread.php?t=1371021
res1n said:
Editing the build.prop file should fix market visibility. I just purchased and rooted mine last night but i'm also having the same issue. Going to try out this after work. Should do the trick. http://forum.xda-developers.com/showthread.php?t=1371021
Click to expand...
Click to collapse
Sounds good. I saw this post, but I haven't seen a build.prop for the stock rooted Kindle fire. If you get yours to work, please post it. Thanks!
b63 said:
1 - try the modaco rom - it shows to the market as galaxy tab:
http://forum.xda-developers.com/showthread.php?t=1439916
2 - http://forum.xda-developers.com/showthread.php?t=1451328
this one is also a good starting place to find different things:
http://forum.xda-developers.com/showthread.php?t=1467013
Click to expand...
Click to collapse
I would like to stick with the stock rom, since hardware acceleration seems to be an issue with most of the custom roms. Do you know if Modaco supports hardware acceleration?
The only roms that have trouble with hardware acceleration are the ICS roms, all other roms have working HWA.
As far as I know the missing apps from the market can't be fixed if your on stock, even if you edit the build.prop, thats why I moved from stock to cm7.
I don't know if there is a way to completely block amazon updates, but I just froze silentupdate with titanium backup when I was stock and I never got the notification to move from 6.2.1 to 6.2.2.
The only app I know of that can freeze apps is titanium backup pro in the market, and there is no list of apps that can be removed/frozen on the stock rom, just use common sense when removing/freezing the apps, don't delete an app if you don't know exactly what it is or delete the kindle launcher, and then wonder why your homescreen is gone, and make sure to backup any apps you mess with.
scarfoot said:
I would like to stick with the stock rom, since hardware acceleration seems to be an issue with most of the custom roms. Do you know if Modaco supports hardware acceleration?
Click to expand...
Click to collapse
modaco is a optimized 6.2.2 stock rom - you can update with it and loose nothing cause it don't format any partitions - read the op of modaco for more information ...
b63 said:
modaco is a optimized 6.2.2 stock rom - you can update with it and loose nothing cause it don't format any partitions - read the op of modaco for more information ...
Click to expand...
Click to collapse
Thanks I will take a look at that. Thanks for the advice.
Looks like MoDaCo for the Kindle Fire was the way to go. My market is working great now, system is very fast, really impressed overall. Still retains the "stock" feel with a few tweak. Now I have to figure out if it doesn't get updates from Amazon.
look at my first post - the link in point 2
allthrough i think in modaco the file is allready removed it's better to check twice
There is a system app called OTA Silent Update and you can just delete it and your all good.
There is a new B&N v1.2.1 for the Nook Touch/Glow.
The same replacement uRamdisk (for 1.1.5) appears to work fine (tested on the Nook Touch) for providing ADB access.
The only change I have seen is that WiFi channels 1-13 are supported by default. Prior versions required a minimal patch to build.prop.
Whats new in 1.2.1 beside wifi Channels?
Sent from my NOOK using xda app-developers app
v1.2.1 changes
3dwarehouse said:
Whats new in 1.2.1 beside wifi Channels?
Click to expand...
Click to collapse
Who knows? B&N doesn't publish changes, and the above is what I discovered in reconfiguring it after the minimal root (I don't run gapps), before going out to dinner. My GUESS is some internationalization changes, as B&N moves into Europe.
Check the B&N forum, where I and others will be posting any changes. I only posted here to let people know of the update (which some have already received OTA).
DeanGibson said:
Who knows? B&N doesn't publish changes, and the above is what I discovered in reconfiguring it after the minimal root (I don't run gapps), before going out to dinner. My GUESS is some internationalization changes, as B&N moves into Europe.
Check the B&N forum, where I and others will be posting any changes. I only posted here to let people know of the update (which some have already received OTA).
Click to expand...
Click to collapse
At least they're good about their GPL obligations. B&N has the source for the 1.2.1 changes up at:
http://images.barnesandnoble.com/PResources/download/Nook/source-code/nook2_1.2.1-delta.tgz
It looks like the changes have to do with charging over USB and when the system thinks it needs to shut down due to low battery.
Jeff
There is a new shutdown graphic in the 1.2x, /system/assets/shutdown_images/autoshutdown_screen.png
This joins the other images which have been moved from /boot also.
The last I checked, the link on B&N for the manual 1.2.1 update was still pointing at 1.2
Another B&N goof
Renate NST said:
The last I checked, the link on B&N for the manual 1.2.1 update was still pointing at 1.2
Click to expand...
Click to collapse
That's just a file naming issue; the file contains the 1.2.1 update.
I cannot find it in https://forum.xda-developers.com/nook-touch/development
zaoqi said:
I cannot find it in https://forum.xda-developers.com/nook-touch/development
Click to expand...
Click to collapse
There are a few descriptions in that thread. You need to read the whole thread carefully--especially the parts about potential screen burn...
FWIW, I'd stay away from that project if I were you. It was abandoned by the developer in a more-or-less experimental state with a lot of issues unresolved.