I have a Nook Tablet 8gig that I rooted about 10 months ago with no problems. I have had no complaints so I have not mucked around with it, but now I am wondering about updating a bit. The issue is that I want to be able to use an external keryboard dock with my NT, and I read that it was only possible with CM7 (not sure if that means CM7 and above). I rooted the NT using the great instructions and files recommended in the developers thread, but to be honest I have no idea what my nook is rooted with- it works well so I have not messed with it.
I am essentially looking for instructions on how to re-root my NT after I re-set it to factory, or how to alter my current root to run CM7. My screen is half wonked, and I may take it back since I got the extended warrenty, especially if I have to re-root it for this anyway.
Also...what is CM7? Is that an Android version?
As a side note: Can anyone confirm that you can use an external keyboard with CM7 or above?
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
systems6 said:
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Click to expand...
Click to collapse
Ultimately what I want to do is run an external keyboard, and the information I have is that they will run on CM7. I will probably (assuming my warranty will cover this) be getting this one fixed to replaced soon, so I will need to re-root when I get it back, but for now I don't see the need to re-root if I don't have to.
What does it mean to "flash" cm7?
drworm73 said:
What does it mean to "flash" cm7?
Click to expand...
Click to collapse
If your nook is broken already, why bother doing anything to it? Just get it fixed then address the things you want to address. And while you are waiting for the replacement see the next line.
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z".
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
SlowCobra96 said:
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z"
Click to expand...
Click to collapse
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
Click to expand...
Click to collapse
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
drworm73 said:
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
Click to expand...
Click to collapse
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
SlowCobra96 said:
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
Click to expand...
Click to collapse
Thank, I just took it back to Best Buy and they replaced it with an HD. I thought about an HD+, but I use my nook for reading more than anything (lots of comics, some novels), and the 9" is much less comfortable for that. Now I need to root this bad boy, and I don't have to monkey around with roms other than rooting because the HD already has support for an external keyboard.
This can be closed, as far as I am concerned. Thanks.
Related
I attempted to flash my gtab with Android OS 3.0. I am not a noob to flashing a new FW so I am not sure what happened. But now my gtab sits at the viewsonic screen and that's it. I try to boot into CW but when I press the Vol+ key I get the message at the top:
"Detect a recovery key pressed"
"Booting recovery kernel image"
And that is it. So I can't boot into CWM to mount my storage. Can ANYBODY please help me?!?!?! I'm freakin out that I have ruined my gtab.
Thanks
-Buddah
You tried to jump a cliff and fell down the great chasm. What you need to do is visit my website (just put it up today) and follow the procedure to nvflash. It's written for beginners like yourself so I'm sure you won't have any problem with it.
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
What happened was you tried tried to use the wrong CWM. Just read my website and you'll see what I mean.
Added by edit.
Also, visit my ROM page for the appropriate way to flash a ROM.
Assuming you used Bottle of Smoke, were you on a 1.1 ROM (ie. 3588 stock, VEGAn-TAB or CM7) and then flashed with cwm? If so, that's your root cause (1.1 ROM jumping to a 1.2 ROM with cwm = soft brick).
As mentioned, you need nvflash to fix it. It's most likely a soft-brick, not a hard brick.
dun dun dun....another one bites the dust, da da dun dun dun
Many many thanks! I NVflashed my gtab and I am back up and running.
There's been a wave of people soft-bricking their gtab because they were not aware of the 1.1 - 1.2 issue. Wonder if that has anything to do with the recent woot and tigerdirect sales...
buddah77 said:
Many many thanks! I NVflashed my gtab and I am back up and running.
Click to expand...
Click to collapse
Just curious. Did you use my nvflash instructions or the ones in this forum? I just want to get a feel of if my site is helpful to beginners at all. I've simplified the instructions as much as I could without giving up the technical stuff.
goodintentions said:
There's been a wave of people soft-bricking their gtab because they were not aware of the 1.1 - 1.2 issue. Wonder if that has anything to do with the recent woot and tigerdirect sales...
Click to expand...
Click to collapse
I, for one, want to again thank the power users here for their excellent user support. YOU have the hardest job of all and I appreciate anyone who helps do post-support for my own ROMs. It is very much appreciated.
goodintentions said:
There's been a wave of people soft-bricking their gtab because they were not aware of the 1.1 - 1.2 issue. Wonder if that has anything to do with the recent woot and tigerdirect sales...
Click to expand...
Click to collapse
*raises her hand slowly*
I got a gtab from woot. I soft-bricked it because it came with the 1.2 bootloader and I installed CWM on it (wanted to install CM7) Luckily the instructions on this forum got me back up and running with nvflash.
P.S. Wish I would've know about your website good intentions. The post I followed was very good, but I always like to see more than one set of instructions before doing something I'm not comfortable with. Acutally I wish I would've seen that stuff before I soft-bricked my gtab :-(
I will say this, once you know how to use NVFlash you can do a lot more experimenting...the worst case is you lose a configuration and have to re-load apps.
I think its sad to know so many GTabs are out in the wild running stock, with people going "These Android tabs are Crap!"....
@goodintentions:
I followed your instructions to the letter and that is what did it for me. It was very accurately detailed and left no room for interpretation. I work in IT Support so I have a fair amount of experience reading crappy instructions. Yours was very helpful and again, thank you for saving me so much time and frustration.
HeadRusch1 said:
I will say this, once you know how to use NVFlash you can do a lot more experimenting...the worst case is you lose a configuration and have to re-load apps.
I think its sad to know so many GTabs are out in the wild running stock, with people going "These Android tabs are Crap!"....
Click to expand...
Click to collapse
That's one of the problems with Android vs *gasp* Ipads, the fragmentation and butchering by some vendors leave a bad taste in some peoples mouths, so to speak.
If not for the developers working on the Gtab, I would have probably taken mine back way before now. Some people aren't all that tech savvy and even me, having worked with PC and various gadgets hardware and software wise for many years, and I still scratch my head from time to time.
I've never had stock but keep testing ROMS. Even the more stable ones had bugs. I wish there was a really good stable Honeycomb out I'm considering the Asus tablet but want to wait for Kal-El. Partly because of the better screen/ram. Things that will never get fixed/upgraded with software.
I think part of the problem is that a lot of the times communication is hard between the tech savy and the not-so tech savy.
In the android world, we say "flash" instead of "install". Believe it or not, but this is a source of confusion for a lot of people out there. For kicks, I did a search and couldn't find a single explanation that says something like flash = install. Remember that we're dealing with people who came from the PC world.
The confusion gets progressively worse from there. What's clockworkmod? What's recovery? What's nvflash? Try searching for these terms and you will find explanations that only induce more questions.
I regularly have to instruct totally tech-illiterate people how to use their devices. This has given me an insight into how to communicate with people who are not tech savy.
I remember my first PDA (a DELL AXIM) and had a hard time wrapping my head around how the OS and firmware were integrated. I was used to the the whole hardware / OS separation on PC's and this was hard to ween myself off of. My DAP's were the same way as my PDA, and so when I started messing with Android it at least made some sense to me.
goodintentions said:
In the android world, we say "flash" instead of "install". Believe it or not, but this is a source of confusion for a lot of people out there.
Click to expand...
Click to collapse
This did confuse me at first, but something dawned on me as to why it may be like this. In the android world, we do install apps. So saying that we are installing a rom would possibly lead to more confusion. "where's the APK for me to install Brilliant Corners?" etc.
Seems we use Flash when speaking of operating systems, but install when speaking of applications.
But we don't ever hear people say "I flashed windows 7 last night."
goodintentions said:
But we don't ever hear people say "I flashed windows 7 last night."
Click to expand...
Click to collapse
Updates to hardware devices (BIOS, video firmware, cdroms, etc) usually are refered to as flash... pretty much forever
goodintentions said:
But we don't ever hear people say "I flashed windows 7 last night."
Click to expand...
Click to collapse
fortunately (or unfortunately ependong on your outlook) we don't have 17 different interpretations of one Windows OS version. And most lay users really don't repetatively install different operating systems, either.
TJEvans said:
fortunately (or unfortunately ependong on your outlook) we don't have 17 different interpretations of one Windows OS version. And most lay users really don't repetatively install different operating systems, either.
Click to expand...
Click to collapse
Haha, back in my youthful days (before I turned 103) I tried out every operating system in existant at the time. This included all the windows versions and linux distros. I also tried (sometimes succesful) to flash mac os into pc platform. Fun times.
Hello I'm a newb!
I'm sorry, but this is the unfortunate state I find myself in.
When I first found this site, what I was expecting to find was a ICS for my phone. I could not have guessed what I would learn here. I had no idea I had a counter in my phone to worry about when installing open sourced roms? Next after much more reading I am to learn the source code Google releases is not complete, and uses binary drivers? Now I am to learn about CIQ, and my phone is spying on me? Wow!
Before I say anything else I want to express my thanks to this community. This has been such a resource I had no idea that it would be when I started. Thank you!
Now on to my question that after learning about all of that I don't seem to have a clear answer to. What I wanted when I first considered getting an Android phone, was to build from source, and run my own rom. I still want this, even more so since I learned about CIQ.
1. Due to the counter on my phone
2. I am to understand multiple images that make the phone work (boot, firmware, system)
3. The binary drivers.
Is this at all a reasonable goal?
Are there more flash images that I haven't read about yet?
Would having a direct from Google rom even be desirable?
I own a stock SGH-I777, I have done nothing to it yet.
Lastly about this site:
Is there anything you think I should read about on the forums?
Any language I should know, as in what does hellraiser imply/mean?
Any Android experience you think might benefit a could be developer?
Counter can be reset and avoided all together.
Sorry I don't know much about AOSP building, but your better off starting with compiling CM and learn from there unless you are really experienced in coding.
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source. Ty for reminding me.
NEME5I5 said:
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source.
Click to expand...
Click to collapse
AT&T Galaxy S2 SGH-I777 has never had CIQ.
LiLChris06 said:
AT&T Galaxy S2 SGH-I777 has never had CIQ.
Click to expand...
Click to collapse
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
NEME5I5 said:
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
Click to expand...
Click to collapse
No it was just some phones, I think the skyrocket had it at some point.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Ok, so I rooted my first cell phone. It would seem heimdall latest has a bug that will brick your phone. (I'm on Mac OS Lion) I used the 1.3.1 instead, and it worked fine.
I saw many more sites, and this was quite easy. The way they showed it was very complex. Since I'm new at this should I wait to try out a ICS rom till after Samsung releases their source code, and the devs have had a chance to get it stable? How complete is the open source version of ICS? There was a note on the fsf.org page that linked me over here that some of the parts were still binary. Is it still true?
I think long term I want to get away from the official releases.
Well, you came this far, might as well flash an ICS rom now. If the leaks are any indication of status, the Samsung release will be pretty stable but the included kernel is problematic because it can cause hardbricking. Besides, you want to get away from stock, and all of the big roms released thus far are pretty darn stable; I don't know anything about binary parts or any of the coding, but plenty of people have no problem running CM or AOKP. Even the Samsung-based roms all look AOSP-like nowadays because they use Apex or Nova (not many devs like Touchwiz anymore). So take your pick, they're all good roms and most look like AOSP to some extent, with a few (mainly CM and AOKP) striving for pure AOSP.
Make sure to read and follow this guide carefully for flashing stuff, and have fun!
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Prother, by no mean to offense you, but seriously, if you don't know those fundamental technical terms, I strongly suggest you to hold off what you about to do and spend more time reading.
Let me go off and do a search the post for you, where you can get used to those terms.
Hang tight, prother.
Pirateghost said:
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
So I will. To be honest I don't see the connection between the new jargon, and development I learn in school. There is definately much to learn here. I was expecting this to be like Zaurus development from back when I was active, it's very clear to me that this is a very different beast.
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
votinh said:
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
Click to expand...
Click to collapse
Thank you friend. I may not have my own rom at the end of summer, but I should be on my way to understanding what would be needed for one.
Well the terms I wanted are not present on that list, most of that I was familiar with. To be honest, some of it I have not seen before as well. What is hellraiser, and some of the other xda developed jargon? I do have a tab open to that part of the forums, I just hadn't made it over there yet. I started on the forums for my device, then Android OS, and lastly general. Is there any other place I should pay special attention to that would help me?
Phalanx7621 said:
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok? I'm not sure I understand, is there something you don't like about the aokp rom that doesn't work very well?
I want off of the carrier provided images based on personal conviction. Google's development practices smack of cathedral, as do all of the 3rd party companies. In a sense they are abusing the spirit of free software by using a signed kernel to impede (if not actually prevent) our right to modify hardware we own. Any normal user of the software provided by the community (bazaar) can only help the cause.
I plan to share what I personally learn with close friends who live in my area. The more people we liberate, the better for everyone else. I simply applaud the work done here.
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
karate104 said:
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
Click to expand...
Click to collapse
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
From a relative noob:
Follow the directions in the " [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!! " thread. Then pick a rom you want to try and follow the CWM directions ... after that , find a ROM you like. If you don't want to void your warranty, wait for your carrier to provide the closest thing to what you want ... but, I'm happy with my flashed ICS ROM.
NEME5I5 said:
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
Click to expand...
Click to collapse
Just like everyone else has said. Read read read. Search for answers for your questions before you ask on forums. U will be fine as long as u can read and follow simple directions. Good luck to u. If u haven't flashed a rom yet I would recommend aokp. Awesome rom.
Sent from my SGH-I777 using XDA
I don t know if this question has come up before as I'm a new poster.
I have an Nook tablet 8gb that I rooted via the the NT 8 or 16GB root image I found at Tablet Roms.I also have CWM installed from Indirects recovery flasher apk.
I can run the sd version of CM7 with no problems,but when I install the internal version which is the Team-B CM7-Alpha final version through CWM,do a factory wipe/reset and clean the Devlik cache and partition,when I reboot from CWM,I get the Team-B splash screen and no further.It hangs there and the image jumps around a little with some violet artifacts at the top of the screen.
I have reverted to a stock rooted version1.42 with the Gapps loaded with no issues. I have tried to flash this 3 times with the same outcome.Im using the B&N stock version now right now.
Any help would be appreciated.
artemis65
Can't Flash CM7 Internal on 8GB Nook
you may want to check out these two threads before you try flashing anything to your device. The site is getting a little daunting as far as amount of info out there, but try reading all of the stickies on the different forums.
http://forum.xda-developers.com/showthread.php?t=1644862
http://forum.xda-developers.com/showthread.php?t=1613797
Good Luck
DavDoc said:
you may want to check out these two threads before you try flashing anything to your device. The site is getting a little daunting as far as amount of info out there, but try reading all of the stickies on the different forums.
http://forum.xda-developers.com/showthread.php?t=1644862
http://forum.xda-developers.com/showthread.php?t=1613797
Good Luck
Click to expand...
Click to collapse
It would simplify things if the devs would simply put 8GB or 16GB or 8/16GB so that people knew which worked for which. It would take literally 2 extra seconds and save a whole lot of trouble.
A lot of those threads started before the 8 Gibbs NT. Since it is out you Development do tell what works on the 8 gb NT.
Please read do a little reading before jumping in with both feet.
Thanks,
Bill
So you're saying rather than simply asking the original poster to update a thread (only 3-4 active ROMs right now), its more prudent to have to have the end users read multiple threads which MIGHT have info about whether a build is compatible or to scour threads 100 pages deep?
I don't get it at all.
The HTC HD2 had a similar problem with ROMs for multiple Windows Phone versions plus Android development. After the confusion between Android and WP ROMs started bricking phones, they simply relabeled the threads and required future ROM threads to clearly state in the OP what could use it. Eventually, they make separate boards for WP6.5, WP7 and Android. It was a good move and development has exploded on the device.
Instead of this...
Mirrors:
Internal version - Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed.zip - 103.3 Mb
Tell devs to label it like this....
Mirrors:
Internal version (16GB only) - Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed.zip - 103.3 Mb
It really is THAT easy and being a little more prudent now is going to save a lot of devices in the future as more development occurs for each device.
dornstar said:
Tell devs to label it like this....
Mirrors:
Internal version (16GB only) - Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed.zip - 103.3 Mb
It really is THAT easy and being a little more prudent now is going to save a lot of devices in the future as more development occurs for each device.
Click to expand...
Click to collapse
You don't tell devs to do a goddamn thing. You flash theses roms at your own risk. These devs work for free and I'm willing to bet someone such as yourself hasn't donated a dime to any of them, rather you seem to be of the opinion that you are entitled to a certain level of custom service that you are not getting.
So please, stop posting and leave.
cool it dude!
Cubanluke88 said:
You don't tell devs to do a goddamn thing. You flash theses roms at your own risk. These devs work for free and I'm willing to bet someone such as yourself hasn't donated a dime to any of them, rather you seem to be of the opinion that you are entitled to a certain level of custom service that you are not getting.
So please, stop posting and leave.
Click to expand...
Click to collapse
I see that you offer a lot of good advice on these forums. You are a valued member here. Be careful that you do not destroy your reputation with flames on other valued members.
Although you are correct about the devs working for free, I believe that you are out of place making assumptions about whether someone has (or has not) made donations. I also believe that you are out of line telling someone to stop posting and leave. I don't see "moderator" in your name panel (on the left). BTW, I don't see one or more "stars" there either - check and you will see one under my name. Do you even know what the star means?
Everyone of us is "unlearned" until we ask questions. Questions lead to comments. Comments invite discussion. Discussion expands knowledge and improves processes. That is what the other poster was suggesting - to improve a process.
All of us with 8GB Nooks face the same issues of not being able to differentiate between what works on 16GB and what will also work on our device. It would be a very simple thing for EVERYONE - not just devs - to start listing their device inside each post.
Soooo... cool it. Calm down, take a deep breath & smell the roses! Just like the government, "We are here to help"
I don't need a star under my name to know when someone is showing an entitled attitude that does not belong here and to thus voice my opinion about it.
And there's no need to tell me to calm down. I'm perfectly calm. I just have zero tolerance for people who think xda exists as an arena for people to instruct developers as to what to do. I agree that model specification would be useful now that we have two. But the syntax that was used was "tell the devs to do." Thats simply not welcome here.
Sent from my NookTablet using Tapatalk
raywaldo said:
Do you even know what the star means?
Click to expand...
Click to collapse
Your tone is extremely condescending right here, but you know that already, don't you?
Sent from my NookTablet using Tapatalk
Cubanluke88 said:
Your tone is extremely condescending right here, but you know that already, don't you?
Sent from my NookTablet using Tapatalk
Click to expand...
Click to collapse
That was not my intention. I am sorry that my post came off that way. My post was an attempt to cool the flames - not spread them. Please consider how "condescending" (other terms might also apply) your post must have been to the other poster.
Sent from my NookTablet using XDA
As I said, I have zero tolerance for people that think they are entitled to certain things and that the devs work for them. My tone was intended.
Sent from my MB855 using Tapatalk
I am looking into getting a tablet for a 5 year old and wanted to put android on specifically for just games.
What is the best and most stable rom for this? Thanks
As of 12-13-2012 CM7 is considered (tested) to be the most stable and complete CM that has been made for the nook tablet
Unfortunately this is an opinion thread and the mods hate it. With that said CM7 is (was) the most stable however CM10 has come a LONG way. I'm using the 11-26 and 11-28 SD card CM10 versions provided by Succulent at iamafanof.WordPress. com. Other than battery life not as good as stock I have no issues.
Prior to that I was using his CM7 SD card builds with no problems.
The EMMC versions are preferred by many I happen to like SD for ease of reverting to stock if needed.
Sent from my CM 10 SD nook tablet. Thanks devs.
SlowCobra96 said:
Unfortunately this is an opinion thread and the mods hate it. With that said CM7 is (was) the most stable however CM10 has come a LONG way. I'm using the 11-26 and 11-28 SD card CM10 versions provided by Succulent at iamafanof.WordPress. com. Other than battery life not as good as stock I have no issues.
Prior to that I was using his CM7 SD card builds with no problems.
The EMMC versions are preferred by many I happen to like SD for ease of reverting to stock if needed.
Sent from my CM 10 SD nook tablet. Thanks devs.
Click to expand...
Click to collapse
How bad is the battery life on cm10?
shags72 said:
How bad is the battery life on cm10?
Click to expand...
Click to collapse
I've had fantastic battery life (on standby) on the AOKP release I'm using. When my kids are playing games on it, even, it still lasts all day (8+ hours of Where's My Perry?). I think that's pretty good.
liquidzoo said:
I've had fantastic battery life (on standby) on the AOKP release I'm using. When my kids are playing games on it, even, it still lasts all day (8+ hours of Where's My Perry?). I think that's pretty good.
Click to expand...
Click to collapse
I would say. I am not trying to hijack as I think this might be pertinent to the op's question if he is as much of a noob at this as I am. For a noob is it really advisable to go with these or should a newer Rooter stay with just like the 4.7 root? Because if he is like me I won't know how to maintain if something goes wrong. Thanks
If you run a couple of diffrent ROMS from sd you can get a feel for them. How they work, stability, battery life...
I'm having great battery life from the CM10 version I'm running from sd at the moment. Tomorrow I might change to another one just for fun. Maybe it's better, maybe it's worse. But because it's on sd I can experiment to my heart's content without taking any risks at all!
shags72 said:
I would say. I am not trying to hijack as I think this might be pertinent to the op's question if he is as much of a noob at this as I am. For a noob is it really advisable to go with these or should a newer Rooter stay with just like the 4.7 root? Because if he is like me I won't know how to maintain if something goes wrong. Thanks
Click to expand...
Click to collapse
4.7 root?
I advise anyone to do a LOT of reading before trying to root any Android device for the first time. There is a lot to understand and even more that could go wrong if you're not careful.
liquidzoo said:
4.7 root?
I advise anyone to do a LOT of reading before trying to root any Android device for the first time. There is a lot to understand and even more that could go wrong if you're not careful.
Click to expand...
Click to collapse
I would agree but with the imense size of this forum where do I start? I figured I would start with the moding threads and alot of them sound simple at the beginning and then the replies speak of problems and fixes that when you get done you wonder if the problems got fixed or not. Also is there like an acronym list? Myself and probably alot of other noobs don't know them and what they mean. Let me know OP if you want me to start a different thread on this.
Pm me if you run into acronyms you don't get. Easiest place to start would be the How To Root threads, and those about returning to stock. If there's something you don't understand right away, open another browser window and search for the term(s).
It is definitely recommended to read any beginners guides out there. Preferably those relating to the device you have, as they'll be the most relevant to you, but there are some general guides in the overall Android forum and subforums that will still be useful.
From there, ask yourself what you want to accomplish with your device. Are you content with the appearance as is, or do you want to change that? Are you just looking to install additional programs or do you want to write them? Any questions you can think of, make a list and prioritize that. Then start from the top and search for your answers or direction, asking questions where needed (especially if the info you find seems out of date, though lots of questions you'll find have already been asked and answered). Don't be afraid to say you don't understand something or to ask for additional info. Those who are willing to help will gladly do so if you seem like you've done some research beforehand.
Feel free to PM me any time, or hit me up on gchat. I'm always willing to help out if I can.
Sent via the Skyrocket
Quando Omni Flunkus Moritati
As already stated, 4.7 root? Huh? If I am not mistaken I believe that is something for a Nook COLOR not a Nook TABLET Many people have been on here lately misstating what they have. Verify the actual device you have before doing ANYTHING! Then go to the correct forum. Color and Tablet look the same but are 2 different animals with different methods to get things done.
I have a Google Nexus Galaxy NOOK Color Tablet HD + running the Windows 3.11 version of the Linux iOS. I'm trying to put the CyanogenmodKindleAppleWindowsPlay Store on the Skydrive in my device. My problem is that my laser disc won't fit into the 5 1/4 inch floppy disk drive on my device. This is the right forum for this, right?
EDIT: Sorry, just felt is was necessary for a laugh.
Sent from my NT running CM10
liquidzoo said:
4.7 root?
Click to expand...
Click to collapse
I suspect the poster refers to the 4_7 version of the root zip in the "Albert Wertz method". That is indeed for the Tablet. I have used it myself a couple of times. Whether it is the latest/best/whatever I do not know. But I'm sure a couple of days of reading up can help any new Tablet owners (and I suspect there are MANY after the recent great deals from BN!) make informed decisions on what route to choose.
(And I did laugh at the post above mine! )
Honestly, the SG7 rom is nice, I haven't tried either 4.2 ROMS yet, but they should be reasonably stable for games
Although battery life would be better from SG7
Also, use a file browser to remove the OTA Updater because the updates wipe GApps...
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
ljwobker said:
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
Click to expand...
Click to collapse
Depends on how you used SafeStrap. If you ONLY installed in the stock rom, then an update likely would do it. If you installed safestrap a second time from the working rom-slot as well, then updates won't work, because the BL & Kernel CANNOT be flashed.
The best thing is to remove all wifi connections with "forget network", then go into safe strap & activate stock rom. Then go back to the boot options & delete the rom-slot you created. Boot back into stock partition, uninstall Safestrap & then reconnect to wifi & check for updates.
I would HIGHLY recommend you follow my directions about forgetting nearby, if not all, wifi networks. If you turn wifi off in a slot, but not in stock, or vice versa, it can cause boot issues , as well as wifi issues.
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
EniGmA1987 said:
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
Click to expand...
Click to collapse
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
GSLEON3 said:
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
Click to expand...
Click to collapse
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
EniGmA1987 said:
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
Click to expand...
Click to collapse
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
GSLEON3 said:
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
Click to expand...
Click to collapse
lol. I am glad you know your FACTS. No need to act so butthurt.