Call for Organization/Stickies! - Nook Touch General

Hey all,
Although I'm new here, fantastic forum, thanks for being so great!
However, I'm surprised by the lack of stickies or posted notes regarding the basics of hacking the NST. Mods, admins, can we make this happen? If we're still reading about people bricking their devices because they read something wrong, or the wrong post on something--heck, even then main, backup, article has an error where on Linux: dd if=/dev/sdb of=my_backup.img bs=1M *but* on
OS X: dd if=/dev/disk3 of=my_backup.img bs=1m <-notice the small "m" or it won't work.
There seem to be a few topics we could have posted:
1. Backing Up & Restoring.
Heck, I'll even make a guide like in iClarified so that kids don't brick their devices by trying to restore to their 250mb "backup" that they made because they didn't use Noogie.
2. Rooting - and the various ways to do it/benefits of each method
3. Jailbroken: Now What? guide to the first few things to do after having rooted.
4. How to transfer files to the NST.
5. List of compatible software (and maybe bluetooth hardware?)
If we have these 5 topics I think many would be saved much grief, n00bs would have a good resource, and even old-timers could check in and see what's new without having to have individual threads bookmarked.
Mods, can we make this happen?
Cheers,
-Feliks

I'll help with making some of the guides

Do you want to "sign up" for any of the above? What do you want to write a guide for? Pick something, and then I'll edit my first post with your name beside what you want to do. That way, we don't accidentally have more than one person working on the same piece.
Cheers,
-F...

I'll sign up for writing a guide. Currently I'm trying to introduce the B&N forums to rooting, and the current thread on rooting is for 1.0.1.

A lot of this is actually covered already:
http://forum.xda-developers.com/showthread.php?t=1380400
http://forum.xda-developers.com/showthread.php?t=1346748
http://forum.xda-developers.com/showthread.php?t=1475613
The problem is that the forums lack organization, and therefore unless there's constant chatter on one of these pages they're all pushed deep into the bowels of the forum, some stuff and "projects" have been completely lost and forgotten until someone decides to post and it's brought to the front, like XorZone's Reading Now button mod.
I think it'd be nice to see something similar to this:
http://forum.xda-developers.com/showpost.php?p=22036179&postcount=10
In which a post completely discusses the differences between all the different methods, and an index like: http://forum.xda-developers.com/showthread.php?t=1380400 in which he tried (unsuccessfully) to have people not post in that thread, while posting a list of all the latest tweaks and hacks and work arounds.
The only problem I see with this idea is a problem we're already having regardless of lack of organization, and that's people not completely reading what they're doing before they do it. There are plenty of cases where people have killed their devices because they were unable to read and follow directions, instead writing TouchNooter or CWM or whatever directly to the nook, trashing the /rom in the process.

Currently I'm working on making a good tutorial (with pictures) that will cover all parts of the rooting process, like backup, choosing a method, actually rooting, setting it up after rooting, etc.
I'll be posting it on the B&N forum, partly because the people looking for it on there won't know how to do most of what we consider basic stuff, and for now I'll just be editing it in this post. I don't like the B&N forums...
Have some copypaste
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-Introduction-_-_-_-_-
In the other rooting thread, it links to a website that is not updated, so it can confuse many people, and if the tutorial from the other thread is used on a Nook Simple Touch running the 1.1.0 update, it will make your Nook fail to turn on! While it does have a link to a tutorial for people using the 1.1.0 update, it doesn't go very indepth, and also uses a more outdated rooting method, and while it still works, there will be some issues that have been resolved with later roots.
Here is a link to a good Nook Simple Touch rooting community (this line is a link to the site), where you can get the newest rooting methods (there's only 2 major ones, with one old minor one). You'll find the rooting methods in the "Nook Touch Android Development" forum, and if you're somewhat good with computers you should be able to just pick a method and follow the instructions provided by the author of the rooter. For the rest of the people reading this, just keep reading this; you'll find detailed instructions telling you how to backup your Nook and root it, along with pictures. Unfortunately, there isn't a video (yet).
As you read through this, be sure you do NOT skip any part of it, even if you think you know how to do something already. There are a lot of people that have skipped over the instructions and disregarded the warning to make a backup before they began, and have had some problem while rooting and couldn't fix it.
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
-_-_-_-_-_-_Rooting-_-_-_-_-_-
Here, have a brief overview of the rooting process! This is not intended to be used in place of the actual instructions to root your Nook.
Write a disk image to a Micro SD Card.
Put the mSD into your Nook while it is off.
Turn on your Nook, then back up your Nook using the mSD.
Write a different image to your mSD Card.
Put the mSD into your Nook while it is off.
Turn on your Nook, then wait while it is rooted (depending on the rooting method you chose).
Enter some details your Nook needs so you can use the Android Market and several other things work.
Enjoy.
It's not an altogether difficult process, but it does take some time and you need to have a few things first. You need:
A Nook Simple Touch. I will refer to it as the NST.
Your Nook needs to be registered prior to rooting. After you root you will not have the chance to register.
A 128MB or larger Micro SD Card.
You MUST have a way to connect your Micro SD Card to your computer using an adapter. You CANNOT just put the card in your Nook and plug your Nook into the computer and write the image through that. If you do, your Nook will be broken.
A program to write disk images to your Micro SD Card. If you use Windows, use
Your Nook needs to be connected to the same WiFi network as your computer.
Click to expand...
Click to collapse
Oh wow, I just realized how big this is going to be... I haven't even made the tutorial itself yet! Also, feel free to comment and suggest what should be added. For now, I need to take a break...

Googie2149 said:
[...] I'll be posting it on the B&N forum, partly because the people looking for it on there won't know how to do most of what we consider basic stuff, and for now I'll just be editing it in this post. I don't like the B&N forums...
Click to expand...
Click to collapse
I wonder if poking a stick at B&N like this is really a good idea, particularly by those who are not the actual creators of these tools. What comes of all these efforts when B&N's legal department decides that XDA is infringing on their rights, especially in the day of take-downs? How much of various rooting tools might they decide they own? What do we do when guys like Gabrial start getting C&D notices?
I prefer to link to external references from the B&N forums so at least someone has to make an effort to see the material. There are definitely some folks over there who think we're abusing B&N by not buying apps from them to support their "subsidized" pricing. The more we're in their faces, the more likely we are to get a response, and I can't think of a good one.

bobstro said:
I wonder if poking a stick at B&N like this is really a good idea, particularly by those who are not the actual creators of these tools. What comes of all these efforts when B&N's legal department decides that XDA is infringing on their rights, especially in the day of take-downs? How much of various rooting tools might they decide they own? What do we do when guys like Gabrial start getting C&D notices?
I prefer to link to external references from the B&N forums so at least someone has to make an effort to see the material. There are definitely some folks over there who think we're abusing B&N by not buying apps from them to support their "subsidized" pricing. The more we're in their faces, the more likely we are to get a response, and I can't think of a good one.
Click to expand...
Click to collapse
Oh... Didn't think of that. :/

Googie2149 said:
Currently I'm working on making a good tutorial (with pictures) that will cover all parts of the rooting process, like backup, choosing a method, actually rooting, setting it up after rooting, etc.
I'll be posting it on the B&N forum, partly because the people looking for it on there won't know how to do most of what we consider basic stuff, and for now I'll just be editing it in this post. I don't like the B&N forums...
Have some copypaste
Oh wow, I just realized how big this is going to be... I haven't even made the tutorial itself yet! Also, feel free to comment and suggest what should be added. For now, I need to take a break...
Click to expand...
Click to collapse
Just a few pointers, first, some people don't feel a need to backup their devices before rooting, secondly, depending on root method, that backup may be done automatically anyways so adding it in as a required step for rooting may confuse people and frustrate others.
Your line where you explain a second adapter doesn't flow well, and in my case is very confusing, even knowing exactly what's needed.
You must have an external microSDCard reader or this will not work. Using the Nook Simple Touch can result in it becoming unusable.
Click to expand...
Click to collapse
It expresses the same information and flows well enough that it should make sense to even the most technologically inept user.
A program to write disk images to your Micro SD Card. If you use Windows, use
Click to expand...
Click to collapse
This is going to mean very little to someone who has no experience "burning" images to an SDCard, Micro or Otherwise.
Your Nook needs to be connected to the same WiFi network as your computer.
Click to expand...
Click to collapse
If the person has already registered a WiFi connect isn't completely necessary depending on again root method. Also the Nook doesn't need to be connected to the same WiFi network as a computer, someone could put together a MicroSD card and do this sitting in a cafe without a computer after buying a brand new MicroSD card (depending again on root method).
Another thing I want to point out is that the repetitiveness in a guide will frustrate people who just want to get it done and over with and may drive them to skip parts of the tutorial or even miss important steps.
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
bobstro said:
I wonder if poking a stick at B&N like this is really a good idea, particularly by those who are not the actual creators of these tools. What comes of all these efforts when B&N's legal department decides that XDA is infringing on their rights, especially in the day of take-downs? How much of various rooting tools might they decide they own? What do we do when guys like Gabrial start getting C&D notices?
I prefer to link to external references from the B&N forums so at least someone has to make an effort to see the material. There are definitely some folks over there who think we're abusing B&N by not buying apps from them to support their "subsidized" pricing. The more we're in their faces, the more likely we are to get a response, and I can't think of a good one.
Click to expand...
Click to collapse
I agree that it's a bad idea to put this all right in their face on their website especially considering progress people have made on XDA towards bug "fixes" that B&N probably won't even acknowledge. You may end up with them just removing the post completely on the one hand, on the other you may end up in them going after XDA, myself, or anyone else who has worked on root if it got pushed too far.
However people can't get up in arms about "not buying apps from them" because B&N doesn't have an App store for the Nook Simple Touch, they have made no claims to ever putting one on this device, and I believe even if we tried to pressure them into adding an App store the community would be split right down the line about whether or not it was truly needed.
This is the same reason it's so hard to find anyone willing to port say CM7 or CM9 to the nook simple touch, people don't believe there's a reason or purpose to even do it. Developers and plenty of the B&N community see the Nook Simple Touch as nothing more than a device in which to do reading. So to them there is no need for the extra apps.

GabrialDestruir said:
[...] However people can't get up in arms about "not buying apps from them" because B&N doesn't have an App store for the Nook Simple Touch, they have made no claims to ever putting one on this device, and I believe even if we tried to pressure them into adding an App store the community would be split right down the line about whether or not it was truly needed.
Click to expand...
Click to collapse
Good point. I'm on the NC discussions too. For the NST, scratch apps and substitute "ebooks". The same players will be equally upset about evil rooter hackers installing the Kindle app, or anything that links to Project Gutenberg, I'm sure.
This is the same reason it's so hard to find anyone willing to port say CM7 or CM9 to the nook simple touch, people don't believe there's a reason or purpose to even do it. Developers and plenty of the B&N community see the Nook Simple Touch as nothing more than a device in which to do reading. So to them there is no need for the extra apps.
Click to expand...
Click to collapse
To a point, I agree. It would be nice to have CM7 or CM9 as the basis for a customized NST experience, but an alternate shell will probably meet 80% of that target. There's the "hack value", of course. I'm actually quite happy with my rooted NST running just a few more things than B&N thinks I should. I really like their hardware, and battery life is delightful. Anything that compromised battery would be a move backwards, IMO.

Admins, senior members-
regardless of whether or not a certain guide is "good" yet, can we agree that it would be good to have a few "sticky" posts, so that the good ones don't get buried where they would be hard for users to find?
Formally, then, I request:
1. Sponsorship of this project by a moderator--I/whoever else can do the editing, what have you, but we just need to start to get organized.
2. Does anyone *disagree* with the list that I made at the beginning? Being:
a. Backing Up & Restoring
b. Rooting - and the various ways to do it/benefits of each method
c. Jailbroken: Now What? guide to the first few things to do after having rooted.
d. How to transfer files to the NST.
e. List of compatible software (and maybe bluetooth hardware?)
I'll break each part into a section, and will have a main index so that people can skip to where it's relevant.
So, moderators! Do we have a sponsor? Fellow users! What is missing from this list? Or is it good enough?
*cracks his knuckles*
Let's do this.
-F...

bobstro said:
Good point. I'm on the NC discussions too. For the NST, scratch apps and substitute "ebooks". The same players will be equally upset about evil rooter hackers installing the Kindle app, or anything that links to Project Gutenberg, I'm sure. To a point, I agree. It would be nice to have CM7 or CM9 as the basis for a customized NST experience, but an alternate shell will probably meet 80% of that target. There's the "hack value", of course. I'm actually quite happy with my rooted NST running just a few more things than B&N thinks I should. I really like their hardware, and battery life is delightful. Anything that compromised battery would be a move backwards, IMO.
Click to expand...
Click to collapse
I think the only reason I'd want to CM7/9 on this and it's the major reason is to enable Wifi tethering, while this may seem stupid for the average Nook Simple Touch user due to lack of 3G/4G or whatever. I honestly think the ability to toss on infrastructure tethering and PAW server with the piratebox plugin could make the Nook Simple Touch, easily one of the simplest and easiest PirateBox setups. Giving it a long battery life even with wifi running (Did a Wifi On test, and before I turned Wifi off got something like 9 days and still had 25% left). I'm sure others could find other reasons to want CM7/9 on here but I think that'd be my main reason.

GabrialDestruir said:
[...] I honestly think the ability to toss on infrastructure tethering and PAW server with the piratebox plugin could make the Nook Simple Touch, easily one of the simplest and easiest PirateBox setups. Giving it a long battery life even with wifi running (Did a Wifi On test, and before I turned Wifi off got something like 9 days and still had 25% left). I'm sure others could find other reasons to want CM7/9 on here but I think that'd be my main reason.
Click to expand...
Click to collapse
You mean as a PirateBox server? The NST wouldn't be able to sleep then, so battery life would be significantly reduced, wouldn't it? Still not bad compared to some devices.
Unfortunately, my home is in an area that's too sparse for any sort of community mesh network. I always thought that would be a fun project.

Googie2149 said:
I'll help with making some of the guides
Click to expand...
Click to collapse
Same here, that would be fun.

Not letting this thread die. *bump* let's do this, folks!

bobstro said:
You mean as a PirateBox server? The NST wouldn't be able to sleep then, so battery life would be significantly reduced, wouldn't it? Still not bad compared to some devices.
Unfortunately, my home is in an area that's too sparse for any sort of community mesh network. I always thought that would be a fun project.
Click to expand...
Click to collapse
Well with some sort of CM on there you most likely you could allow the device to sleep while leaving Wifi and the server active. Either way even with the device "awake" it wouldn't be really that much of difference I think as long as nothing was messing with the infrared. Even if you were doing some reading I still think you could get more than a dozen hours, though that would depend on how busy the server is too.

Related

Organized info for rooting the G1

I am currently a G1 owner on the fence about rooting my phone, as are many others. One of the first issues I've come across is being overwhelmed by forum threads. Unless I have missed something (and if I did, please point me in the right direction!), everything is posted in forums here, requiring people to pour through tons of posts and pick through the right information.
Is there an official wiki or something where all the latest news, guides, FAQs, etc. are being updated? If not, I'd love to start one, but unfortunately I don't have the knowledge to do so (yet, at least). I'm thinking of a super simple, jargon-free site for users to find answers to their questions, and a simple outlined "official" process for how to begin and where to go from there.
For example, some FAQs..
Can T-Mobile/Google "cut me off" in any way if they determine I have rooted my phone?
If I change my mind later, can I go back to original firmware and leave no trace that I ever rooted the phone in the first place? Future over-the-air updates will install with no issues?
Let's say I mess up during the rooting process. Is there always a way out, or am I screwed?
How safe is storing apps on the SD card? What can happen to my phone, and how do I avoid problems?
What are the JFvX.XX firmware releases? How do they work? Are they required? Are there other alternatives?
What if a future OTA can't be hacked, will we miss out on features?
I've seen various different methods of rooting the G1, which one is the most popular and why?
etc.
This is just an idea, but there's all these questions like this that I know many people have. While these questions can easily be answered in forums, I'm looking for a more convenient solution for the community. As official answers are nailed down, it would be great to have a reference to check with rather than flooding forums with questions.
Anyway, thanks for all the hard work from the developers here. It's really exciting to follow, and I can't wait to see what the future holds for the G1!
they have one:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream
look first
kay11224 said:
they have one:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream
look first
Click to expand...
Click to collapse
Thanks for the link, but unfortunately this doesn't seem user friendly (it's filled with unexplained links and jargon), and seems pretty outdated. I'm thinking about info aimed the average n00b end-user here, not developers or people actively following the forums and progress made.
I'm not sure if you understand fully what you're asking. Keeping your phone updated without "actively following the forums and progress made" is a simple task right now, just wait until Google pushes an update for you. If using the search function is too hard for you, I think root access is biting off more than you can chew. All of your FAQ's can easily be found in the development section of the forums. As far as step by step guides are concerned, read the stickies, use the search function, and then ask. It's not complicated at all.
dudinatrix said:
Can T-Mobile/Google "cut me off" in any way if they determine I have rooted my phone?
If I change my mind later, can I go back to original firmware and leave no trace that I ever rooted the phone in the first place? Future over-the-air updates will install with no issues?
Let's say I mess up during the rooting process. Is there always a way out, or am I screwed?
How safe is storing apps on the SD card? What can happen to my phone, and how do I avoid problems?
What are the JFvX.XX firmware releases? How do they work? Are they required? Are there other alternatives?
What if a future OTA can't be hacked, will we miss out on features?
I've seen various different methods of rooting the G1, which one is the most popular and why?
etc.
Click to expand...
Click to collapse
1) as far as i'm aware no. They can remove apps from peoples phones (allegedly) but i can't see how they would know you have root, or even care. It's good publicity for the phone if anything.
2) Yup, you can easily un-root your phone and the updates should work correctly.
3) Once you have the hardSPL bootloader loaded it's pretty much impossible to brick your phone, see this thread for details.
4) Not sure about this, so i can't comment
5) the JF firmware releases are essentially hacked firmwares, created by JesusFreke, that allow us to get root access (among other things ). they are incredibly easy to install and they are required for certain things such as, multi-touch. as far as i know, there are no alternatives.
6) They will be as everything is open source. I imagine xda will have a firmware hacked within hours of it's release
7) personally, i find this way the best. nice n simple and easy to follow.
have fun
Iceucold said:
I'm not sure if you understand fully what you're asking. Keeping your phone updated without "actively following the forums and progress made" is a simple task right now, just wait until Google pushes an update for you. If using the search function is too hard for you, I think root access is biting off more than you can chew. All of your FAQ's can easily be found in the development section of the forums. As far as step by step guides are concerned, read the stickies, use the search function, and then ask. It's not complicated at all.
Click to expand...
Click to collapse
I am perfectly capable of handling root access. I am a Linux system administrator (among other things) by profession. I admit, this would be my first attempt at "hacking" a device and thus voiding the warranty, hence my hesitation and "noob" questions. Using the search function is not my concern here, but I can appreciate where you're coming from.
What I'm talking about, and what appears to be misinterpreted, is an information source for common end users, not developers or tech-savy users. If I have questions about rooting the G1, certainly those less technically inclined do as well. And unfortunately for them, they don't necessarily even know where to begin looking. I'm talking about people like my brother in law, for example... who probably never used a forum in his life, but wants to have multi-touch on his phone, or change his themes, or find a solution to his constant "low storage" warnings. People like him don't care about hacking into the phone and getting all this flexible access for himself. They just want to take advantage of what's already been achieved, but unfortunately require root to do so.
I agree that it is pretty simple to root the phone, but face it you have to be somewhat comfortable with technology first, even just to obtain the information.
Perhaps now isn't the appropriate time to wrap things up in a bow and give to the general G1 user base in a tidy little easy-to-digest package. As things develop further it may just naturally come about, perhaps via installers or something. I just think it would be helpful to many to have a source written for the common folk with jargon-free information... considering the more people get their hands on it, the more successful the platform can become.
And to Metlus, thanks for being receptive and answering my questions kindly without making me feel judged for asking what I assume many think is a "just search for it" type of post.
Meltus said:
1) as far as i'm aware no. They can remove apps from peoples phones (allegedly) but i can't see how they would know you have root, or even care. It's good publicity for the phone if anything.
2) Yup, you can easily un-root your phone and the updates should work correctly.
3) Once you have the hardSPL bootloader loaded it's pretty much impossible to brick your phone, see this thread for details.
4) Not sure about this, so i can't comment
5) the JF firmware releases are essentially hacked firmwares, created by JesusFreke, that allow us to get root access (among other things ). they are incredibly easy to install and they are required for certain things such as, multi-touch. as far as i know, there are no alternatives.
6) They will be as everything is open source. I imagine xda will have a firmware hacked within hours of it's release
7) personally, i find this way the best. nice n simple and easy to follow.
have fun
Click to expand...
Click to collapse
Great post meltus!
If and when you do decide to root g1 take your time and breathe, really isn't too hard just nerve racking the first time. I did it and im not a pro at all so you will probably breeze through it! The advancements made so far are unreal, auto browser, themes and many more make rooting well worth it in my opinion
I'm not sure if it gets any easier than this, but gizmodo today posted what looks like the easiest "recipe" yet for rooting the G1:
How To: Hack Android For Multitouch Web Browsing on the T-Mobile G1

[Pet Peeve] ADB? What's that? Oops I bricked my Xoom, HALP!

If you don't have the first clue what ADB is or the intellectual curiosity it takes to learn about it you should not root your Xoom and definately should not try to put custom ROMS on it.
This has been a public service announcement.
Have to learn somehow.
If you dont know what adb is, this helps me out
http://forum.xda-developers.com/showthread.php?t=879701
After you read it and you still havnt a clue what it is stop hacking or read it again and again.
Yes, it seems like there is a new "did I brick?" question each and every day.
Read first, read again, and make sure that you fully undestand the process first. It certainly saves time and frustration later. I am certainly no pro, but I was able to successfully unlock, root, install CWM, upgrade to 3.1, install all of BRD's kernels (now on 1.4.4), and set-up USB tether by reading the excellent information here on XDA.
I bet if more people made one click root methods this wouldn't be a problem...
Sent from my Xoom
bwcorvus said:
I bet if more people made one click root methods this wouldn't be a problem...
Sent from my Xoom
Click to expand...
Click to collapse
It appears that a fair number of people tried real hard to brick their WiFi Xoom using the 3g section of one-click root.
Well, it took me to completely stuff my Xoom, to get how adb works. Yay!
Is there a way to flash official Moto images if my PC won't recognise my Xoom via the usb cable? I can get into CWR, and even reboot via adb, and that's it.
?
To be honest "you have to learn somehow" isn't a good defense, because you can do your research before actually trying and you'll probably avoid a lot of the problems that we see here.
It's not like the only choices are "do it blind"/"don't do it at all".
Some people learn the hard way, I'm a glowing example. Just make sure you read until you get really confused, grab a coffee, and read until it makes sense. If you don't understand what you are trying to do, but you want to give it a go, make sure your your prepared to have the worst happen.
BTW. I finally figured how to restore my system to factory! YAY!!!
Now the fun part of trying it all again....
Learning is great, however blindly trying something that you do not understand can be disastrous. Root, wiping, flashing, etc are all tasks that modify or rework the basic functions of a device. The devs who find these ways to help us do this are simply amazing, but it is NOT for everyone. Too often we see "Help!!!!, or What now???" because people simply see a thread and jump into rooting, and flashing without knowing what they are doing.
I am not an ADB expert, but I do believe that if you take your time and follow the posted instructions to the T, you will be fine. Again, people often report back, myself included that something doesn't work right or it is not doing what it should. After looking back I noticed that I skipped a step or did something out of order because I "thought I knew what I was doing".
I do caution people who are new to the XDA forums and new to Android. I would lurk for a but, gather some knowledge, then try a few things. If you have some issues, PM a member who you see has some good skills or knowledge in the area. This is a forum to help each other and too often it turns into a flame session.
Again, I am no expert I just try to offer some helpful advice.
dubie76 said:
Learning is great, however blindly trying something that you do not understand can be disastrous. Root, wiping, flashing, etc are all tasks that modify or rework the basic functions of a device. The devs who find these ways to help us do this are simply amazing, but it is NOT for everyone. Too often we see "Help!!!!, or What now???" because people simply see a thread and jump into rooting, and flashing without knowing what they are doing.
I am not an ADB expert, but I do believe that if you take your time and follow the posted instructions to the T, you will be fine. Again, people often report back, myself included that something doesn't work right or it is not doing what it should. After looking back I noticed that I skipped a step or did something out of order because I "thought I knew what I was doing".
I do caution people who are new to the XDA forums and new to Android. I would lurk for a but, gather some knowledge, then try a few things. If you have some issues, PM a member who you see has some good skills or knowledge in the area. This is a forum to help each other and too often it turns into a flame session.
Again, I am no expert I just try to offer some helpful advice.
Click to expand...
Click to collapse
Well said, don't forget irc zoom channel.
Sent from my Xoom
Thanks for "getting" the spirit of my post. I wasn't trying to be mean at all just saying... there's so many "help me i screwed up my xoom" posts and what concerns me is that too often the advice given around here is "just go root and and load a custom rom". Well that sounds real attractive until you realize that you have no idea what's going on and your Xoom won't turn on. Then your heart sinks and you don't have many places to turn to, fortunately there is this forum but I just hope that people will take more time in the future to understand what it is that they are getting into or at the very least be absolutely willing to set fire to six to eight hundred bucks
there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.
gnackattack said:
To be honest "you have to learn somehow" isn't a good defense, because you can do your research before actually trying and you'll probably avoid a lot of the problems that we see here.
It's not like the only choices are "do it blind"/"don't do it at all".
Click to expand...
Click to collapse
dubie76 said:
Learning is great, however blindly trying something that you do not understand can be disastrous. Root, wiping, flashing, etc are all tasks that modify or rework the basic functions of a device. The devs who find these ways to help us do this are simply amazing, but it is NOT for everyone. Too often we see "Help!!!!, or What now???" because people simply see a thread and jump into rooting, and flashing without knowing what they are doing.
I am not an ADB expert, but I do believe that if you take your time and follow the posted instructions to the T, you will be fine. Again, people often report back, myself included that something doesn't work right or it is not doing what it should. After looking back I noticed that I skipped a step or did something out of order because I "thought I knew what I was doing".
I do caution people who are new to the XDA forums and new to Android. I would lurk for a but, gather some knowledge, then try a few things. If you have some issues, PM a member who you see has some good skills or knowledge in the area. This is a forum to help each other and too often it turns into a flame session.
Again, I am no expert I just try to offer some helpful advice.
Click to expand...
Click to collapse
It wasn't really a defense just a "it's what happens" type of thing. Yes people can be smart and read up. But the reality is that most people won't (rather it be because of stubborness or lack of time). Something happens, then you have the "ok i gotta fix this, let me look up..." or "oh noes I brokes it. I'm going to join a forum to whine about it to the people so they can help me. I mean it's their job right?".
Thing is that rooting is most misunderstood to be the equivalent to jailbreaking. Just as jailbreaking is most misunderstood as only being useful for free games and apps. Some people just never want to look into what these type of things really are, because they don't care unless it's the means of getting something for free.
bigrushdog said:
there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.
Click to expand...
Click to collapse
Sounds like some money to be made here
bigrushdog said:
there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.
Click to expand...
Click to collapse
I'm sure there's at least one taker out there. Its likely the guy who started the 'Motorola refused to fix xoom' thread. At http://forum.xda-developers.com/showthread.php?t=1107488
bigrushdog said:
there is no such thing as a bricked xoom. Ill prove it. Send me your bricked xoom along with a $100 PayPal unbricking fee. Ill send you back a restored factory state xoom. If Its truly bricked Ill send the xoom back to you and give you back $120 for the trouble. Any takers, contact me.
Click to expand...
Click to collapse
So how would you fix the partitioning of a xoom through cwm? That seems to be the most common "i bricked my xoom" thread.
Sent from my HTC Vision using XDA App
I feel that the best way to go about things is to read all you can about ADB, how the Xoom works and the specific root method or kernel you want to use. Then, if something goes wrong, search, search then search some more to try and find someone who had a similar problem as yours and try to learn what went wrong and how...then solve your own problem. If you are REALLY stuck, PM a user who seems to know what they are doing and appears to be patient, or post a question that includes all the details and ask politely for help. Take the knowledge you are given, add it to your own, then try to help other people in the same pickle.
If you look up the word EDUCATION in Websters, odds are the picture will look something like the paragraph above.
Personally I am not cheesed off too badly by the people who do things without sufficient knowledge. The ones that drive ME nuts are the ones who do that, then come into the forum and demand that someone hold their hand and personally walk them out of hell step by step...or better, blame the hardware/software and then angrily return it to the store, pretending that it just suddenly died.
rschenck said:
Personally I am not cheesed off too badly by the people who do things without sufficient knowledge. The ones that drive ME nuts are the ones who do that, then come into the forum and demand that someone hold their hand and personally walk them out of hell step by step...or better, blame the hardware/software and then angrily return it to the store, pretending that it just suddenly died.
Click to expand...
Click to collapse
Exactly what I was trying to say. And I know what specific thread you're talking about lol

[Q] Thread Hell Help

Interested in re-rooting my KF. Did it a week or so after I first got it back in November, and having nothing of real note (for me), let the update unroot it.
Looking at things now, it's virtually impossible to determine (if you haven't kept up on a daily basis), exactly what is going on now. Many utilities claiming to root, make it easy to root, re-flash, recover, etc.
Could someone (or several someones) please put together a sticky or series of stickies that is kept up-to-date (and NOT allow posting to, so it is simply ONE post that is updated, and if there is some reason to have ancient history, the most recent info is at the TOP of that ONE post) that would cover the following:
What utility to use to root the KF
What utility to use for recovery, etc. (I assume TWRP)
What each of these utilities does, has, etc. (some seem to have more bundled in them, and at this stage, I can't tell who's got what bundled that does what and more importantly, WHY I want to use utility A over utility B)
Is there one utility that "has it all" and makes it pretty easy and goof-proof?
Updated status and ETA of CM9 or other Android 4.x ROM for the KF (Yes, I know the devs have said "don't bug me", but it's been quite a while now, and we still don't seem to have HWA for video on CM9/etc. So, a "rough" ETA? I'm a developer too, so I know these things aren't always exact, but are we a week/month/3 months/year/when pigs fly away from potentially having ALL of the HW supported on the KF with CM9? At least I can go away for a while, come back at some time when the ETA is supposed to be reached, and do a check)
While Amazon VOD was important to me at the beginning, I've been exclusively using Netflix, so I'm not sure if having the Amazon video disabled due to rooting is an issue to me anymore. But HWA is an issue for watching videos on Netflix or over my DLNA server at home.
The stickies need to be updated by the authors - NOT a reply to the thread the author of the utility started. This stuff is simply too time-consuming to wander through, and attempt to wonder if "idiot A" bricked his KF due to a bug in the utility, didn't follow instructions, or whatever 27 posts later. I'm looking for a direct "here's the utility, here's the instructions, here's why you want this over this" kind of thing.
Here's my 2 cents, take them for what they are worth.
In my opinion, Kindle Fire Utility is sort of the one stop shop for all things root/recovery/etc. and it has TWRP built in. It is super easy to use in my opinion and you can get burritoroot, firefirefire bootloader and TWRP all at one time.
Credit to vashypooh on a job well done.
http://forum.xda-developers.com/showthread.php?t=1399889
Hashcode and csholmq have been working with serial output, which probably offers the best chance of getting HWA working, etc.
csholmq issued and upate, but no ETA yesterday.
http://forum.xda-developers.com/showthread.php?t=1471813
+1 to Yuma75.
I rooted with BurritoRoot, heavily modded the stock ROM, which was my daily for several weeks. I then used gscript to install CWM and FireFireFire and then installed Kang ICS ROM.
But for someone just starting out, KFU seems to be the way to go. I would have used it to install recovery, etc., but for user error (that is, my own). That's my two cents.
All of the developers come together to share their tricks, techniques and ROMs, often without compensation, and yet you think this "stuff is simply too time-consuming to wander through?"
If you don't have time to look through discussions, why are you on a forum?
There are already stickies and great utility threads, but if they aren't up to snuff, I think you should make one.
UrticantOwl said:
All of the developers come together to share their tricks, techniques and ROMs, often without compensation, and yet you think this "stuff is simply too time-consuming to wander through?"
Click to expand...
Click to collapse
No, I don't. What other site offers tools to root KF? None I'm aware of. If all I want to do is root the device....
Also - a dev posts "hey I've just got X and released it, here's the link", etc. Then I have 40-50 PAGES (not posts) of follow up. Some with problems, some just going "Ata boy!". Are there kernels of wisdom in there? Probably. But to follow through and separate the wheat from the chaff takes a LOT of time.
I've rooted before using KFU. Basically a 5 minute process. Why should I read pages of posts (not all of them even with the original post of the utility, etc.), to find out what I need? Post it in one location. Keep it up to date (things like, "oh, I forgot to upload the correct script, updated now" - updated in the original link in the original post? Updated at the web site shown in the original post? Updated in a following post somewhere?
Many of the "first posts" with links now point to dead download links. One would presume it is because the dev uploaded to something like RapidShare or the erstwhile MegaUpload, and either the link expired, or the dev killed it because there's a newer version. Do I really need to wade through dozens of posts to find the most recent D/L URL?
UrticantOwl said:
If you don't have time to look through discussions, why are you on a forum?
Click to expand...
Click to collapse
In this particular case? To get a utility to root a KF. I have no desire to develop on the platform, I've been developing on a great number of platforms for nearly 40 years, and have gotten more into the "I want it to work and use it", rather than "I love the struggle and fight to make something happen". So, I peruse the forum once every 3-4 weeks to see where things are - and without spending 3-4 hours perusing posts, questions, etc. it is not really possible. Sorry, I used to be one of those guys who would sit up for 2-3 days straight pulling things apart, coding in assembler, making "things dance". These days, I simply don't have the time - but would like to enjoy the fruits of a device that might be more open. Or might not. As I said before, I rooted within a week after getting the KF, using KFU. Played with it, and at the time, simply didn't see a point (other than saying "I did it"). So I let it die out. I'd very much like to try out Android 4.x to see if there's anything more - or I just leave it alone.
UrticantOwl said:
There are already stickies and great utility threads, but if they aren't up to snuff, I think you should make one.
Click to expand...
Click to collapse
Having been on forae for many, many years, and having worked with, made my own notes and posts regarding Linux since 1995 or so - sorry (and a great many other topics/forae). I've found in that time that the dev, or those working most closely with the dev are the only ones qualified with enough knowledge of not only what a utility does, but the thought and design behind it. Someone else attempting to step in, will simply "step in it" most of the time.
If the dev doesn't have documentation skills (and most devs don't), I'd encourage the dev to work with someone to help document and write up what their x does. I would presume that the dev has a desire for some praise and accolade for their efforts (otherwise why would they make their work public). By posting a sticky that is up-to-date and current, with correct (or corrected info), they help many others to partake of their works, even if the dev does not have their own web site (and I presume many don't since many don't point to their own website, but post a link to some file sharing service from within a post here).
I wasn't able to use KFU because I got the unsigned driver error and KFU wouldn't run correctly on my PC. But I have heard that it is a very good tool for someone that isn't good with adb.
Sent from my Kindle Fire using Tapatalk
tundrwd said:
No, I don't. What other site offers tools to root KF? None I'm aware of. If all I want to do is root the device....
Also - a dev posts "hey I've just got X and released it, here's the link", etc. Then I have 40-50 PAGES (not posts) of follow up. Some with problems, some just going "Ata boy!". Are there kernels of wisdom in there? Probably. But to follow through and separate the wheat from the chaff takes a LOT of time.
I've rooted before using KFU. Basically a 5 minute process. Why should I read pages of posts (not all of them even with the original post of the utility, etc.), to find out what I need? Post it in one location. Keep it up to date (things like, "oh, I forgot to upload the correct script, updated now" - updated in the original link in the original post? Updated at the web site shown in the original post? Updated in a following post somewhere?
Many of the "first posts" with links now point to dead download links. One would presume it is because the dev uploaded to something like RapidShare or the erstwhile MegaUpload, and either the link expired, or the dev killed it because there's a newer version. Do I really need to wade through dozens of posts to find the most recent D/L URL?
In this particular case? To get a utility to root a KF. I have no desire to develop on the platform, I've been developing on a great number of platforms for nearly 40 years, and have gotten more into the "I want it to work and use it", rather than "I love the struggle and fight to make something happen". So, I peruse the forum once every 3-4 weeks to see where things are - and without spending 3-4 hours perusing posts, questions, etc. it is not really possible. Sorry, I used to be one of those guys who would sit up for 2-3 days straight pulling things apart, coding in assembler, making "things dance". These days, I simply don't have the time - but would like to enjoy the fruits of a device that might be more open. Or might not. As I said before, I rooted within a week after getting the KF, using KFU. Played with it, and at the time, simply didn't see a point (other than saying "I did it"). So I let it die out. I'd very much like to try out Android 4.x to see if there's anything more - or I just leave it alone.
Having been on forae for many, many years, and having worked with, made my own notes and posts regarding Linux since 1995 or so - sorry (and a great many other topics/forae). I've found in that time that the dev, or those working most closely with the dev are the only ones qualified with enough knowledge of not only what a utility does, but the thought and design behind it. Someone else attempting to step in, will simply "step in it" most of the time.
If the dev doesn't have documentation skills (and most devs don't), I'd encourage the dev to work with someone to help document and write up what their x does. I would presume that the dev has a desire for some praise and accolade for their efforts (otherwise why would they make their work public). By posting a sticky that is up-to-date and current, with correct (or corrected info), they help many others to partake of their works, even if the dev does not have their own web site (and I presume many don't since many don't point to their own website, but post a link to some file sharing service from within a post here).
Click to expand...
Click to collapse
This isn't the place to go looking for a handout this is a place to read, search, read some more, learn to use a tool properly or risk bricking your device, your piss poor "I don't wanna search I just want it given to me" attitude isn't gonna get you far in these forums.Either suck it up and search to find what you want, or don't it's as simple as that. These devs do this for free, in their spare time and are nice enough to share their work with the rest of us. They do have jobs, families and lives outside of this forum and they aren't here to cater to you needing a handout. Plain and simple. If you even bothered to read to forum rules, rule #1 is SEARCH. If you want a handout I'd suggest going to another forum aside from XDA cause this isn't the place for you :-|
________________________________
{We are legion, for we are many}
>Sent from my Anonymous DeathStar in the depths of GalaXy S2<
-Coming soon to an Evo4G near you?: [AoSP]EViL-MoD_FReEvO v0.1[Free your phone]-

[Q] Easiest setup for web browsing and book reading?

When I was participating in this forum last year and the year before, I could still follow long threads and extract the relevant information, sometimes even making useful contributions to a discussion. But at this time, if not for what's left of my life, I just can't focus enough to do that for any complicated matters.
My task now is to set up a Nook Color for a friend who is almost clueless about tech matters. His main concerns are accessing the web, including web-based email, and reading books, although he might want to use it occasionally to watch video. I figure the best thing might be to put whatever he needs (or as much of it as I can anticipate) on a microSD card, of which I have a few of various sizes up to 16 GB.
What stable ROMs might be best to use and can somebody point me to a guide to installing such a ROM and other necessary software on an SD card? And by a "guide" I mean something that incorporates corrections in the original post and does not require the reader to follow an entire long thread to find important information.
aarons510 said:
When I was participating in this forum last year and the year before, I could still follow long threads and extract the relevant information, sometimes even making useful contributions to a discussion. But at this time, if not for what's left of my life, I just can't focus enough to do that for any complicated matters.
My task now is to set up a Nook Color for a friend who is almost clueless about tech matters. His main concerns are accessing the web, including web-based email, and reading books, although he might want to use it occasionally to watch video. I figure the best thing might be to put whatever he needs (or as much of it as I can anticipate) on a microSD card, of which I have a few of various sizes up to 16 GB.
What stable ROMs might be best to use and can somebody point me to a guide to installing such a ROM and other necessary software on an SD card? And by a "guide" I mean something that incorporates corrections in the original post and does not require the reader to follow an entire long thread to find important information.
Click to expand...
Click to collapse
To install to an SD follow my NC guide linked in my signature. It is up to date. I would recommend CM10.1.3 stable.
Sent from my BN NookHD+ using XDA Premium HD app

Notice! You will brick this device...

I know everyone is eager to set up their KF HDX how they want it & many of you are new-ish to XDA, so you have been able to rely on tools to automate everything, making it easier to accomplish what you want, but not so great for learning the basics of Android & the core development & debugging tools that are used in the automated processes like the various toolkits you find throughout the forum threads.
At any rate, I am writing a warning about this device ONCE AGAIN. If you really have no idea what the sdk is or how it is used, the HDX is not something you want to start messing with. You know who you are. If you aren't running Linux, or at the very least a dual boot distro like Unbuntu via wubi & you have never installed or used the Android SDK, PLEASE think twice about whatever you are contemplating.
The Kindle Fire HDX is not like other device you have maybe played with, or owned. It is a low level development device that uses an oddball system for updating & while it is vulnerable to several exploits, the bootloader is 100% locked. Complicating this issue is the fact that the device does not have fastboot access & messing with certain system files or permissions CAN & WILL cause issues ranging from wifi & 4G connectivity to a full on hard brick. There are also checks in place that will prevent adb access if you remove or mess up certain binaries or drivers. Some of these things CAN & WILL lead to loss of ADB access. Without ADB access, anything you break CANNOT be fixed.
This is NOT the device to get your feet wet on when it comes to rooting or modding. In the last two days alone, I have had 8 requests from people with devices that are having issue because of something that was done inadvertently or because something was done in the wrong order. I am willing to help WHEN I CAN, but I am an engineer, not a developer, with a busy schedule & a family, so taking care of my responsibilities comes before anything XDA related, for myself, or anyone else.
If you decide to ignore all of the posts about people bricking their devices & you ignore this warning, the SECOND SUCH WARNING, well, fine. After all it's your device & you can do whatever you want to it. Just don't expect to find an easy fix or someone there 24/7 to hold your hand through the process of trying to recover it. After all, this is a development forum, where you are expected to have a certain degree of knowledge, or be in the process of gaining that knowledge & it's not something you are going to learn by osmosis or be able to cram into a panicked couple of hours because you messed up your device.
So, you have been warned. Again. Unless you want a $300 - $700 project you may never finish, read BEFORE you do. Learn about what you are trying to accomplish & just deal with the Amazon only device until you can understand at the very minimum how to use adb & know how to apply all of the various adb commands. The absolute worst time to try to learn anything is when you are panicked & grasping at straws.
Don't be this guy:
I think that http://towelroot.com/ is a good place to start as the apk can be side loaded and should provide root access. I still have root on my Kindle Fire HDX 7" so I dont have any need for this root method, but according to the CVE-2014-3153 most versions of android are affected including 4.2.2. I would say if your a noob and not comfortable with adb and command line then this is your best bet for gaining root. Once you do have root I would suggest installing a firewall app and block everything except the apps you want to have access to the internet this should stop any updates from hitting your device. Have Fun!!
CDub50
cdub50 said:
I think that http://towelroot.com/ is a good place to start as the apk can be side loaded and should provide root access. I still have root on my Kindle Fire HDX 7" so I dont have any need for this root method, but according to the CVE-2014-3153 most versions of android are affected including 4.2.2. I would say if your a noob and not comfortable with adb and command line then this is your best bet for gaining root. Once you do have root I would suggest installing a firewall app and block everything except the apps you want to have access to the internet this should stop any updates from hitting your device. Have Fun!!
CDub50
Click to expand...
Click to collapse
Not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The ISSUE is what they do AFTER they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely WIPE the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from PM's but frankly I don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, I'll start a brick master thread for you to take care of. :good:
yeap
gsleon3 said:
not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The issue is what they do after they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely wipe the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from pm's but frankly i don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, i'll start a brick master thread for you to take care of. :good:
Click to expand...
Click to collapse
well said and repeated!
GSLEON3 said:
Not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The ISSUE is what they do AFTER they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely WIPE the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from PM's but frankly I don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, I'll start a brick master thread for you to take care of. :good:
Click to expand...
Click to collapse
Come on though, this XDA forums, isn't it? Anyone reading these threads should be well aware of the risks involved. With towelroot app rooting the device is simple, and not going to brick your tab. Being reckless and doing some of the other things you mention, well, sorry, but like Clint Eastwood says in Magnum Force, "A man's got to know his limitations".
sent from hdx+ with tapatalk
Lol. When the vroot method was posted a couple days ago the hdx forum was quite silent...
Then BOOM!
"OMG I BROKED MY TABLET! BRICKED HDX! *BLAH BLAH* BROKE MY TABLET! HELP!!!! HELP!!! BRICKED TAB! "
good warning for noobs.
Sent from my SGH-T999 using Tapatalk
I used the towelroot, then used a ota update blocking script and kindlefree, that's it. I bet people are out there installing safestrap, Roms and whatnot.
GSLEON3 said:
Not helping. Yes, anyone can root there device by installing an apk & clicking a few buttons. The ISSUE is what they do AFTER they root, because now they have access to do things like overwrite graphical drivers with ones that are 4 years old, erase directories from the system partition or just completely WIPE the system partition. These are three examples of things that people have done in the last 24 hours with root. I'd go thru the other 5 from PM's but frankly I don't remember the exact issues, most were some form of the previously mentioned mistakes. But hey, since you are telling people that "aren't comfortable with adb..." they should root, I'll start a brick master thread for you to take care of. :good:
Click to expand...
Click to collapse
To think that everyone who roots their Kindle is going Brick their device is laughable. Most people want to root to install google play store and stop future updates. There are always going to be people that are going to brick their device by pulling a bone head move. People know the risk, but if you can make rooting less risky by just installing an .apk sounds like a no brainer to me.
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
jimyv said:
well said and repeated!
Click to expand...
Click to collapse
Please people root phones all of the time and I would say 99% of people dont run into any issues with having root.
sounds like
cdub50 said:
To think that everyone who roots their Kindle is going Brick their device is laughable. Most people want to root to install google play store and stop future updates. There are always going to be people that are going to brick their device by pulling a bone head move. People know the risk, but if you can make rooting less risky by just installing an .apk sounds like a no brainer to me.
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
Please people root phones all of the time and I would say 99% of people dont run into any issues with having root.
Click to expand...
Click to collapse
You just sighned up for brick duty... Where was your energy and sarcasm Friday when Chinese root hit the forum? But yea thx and for chiming in though.
jimyv said:
You just sighned up for brick duty... Where was your energy and sarcasm Friday when Chinese root hit the forum? But yea thx and for chiming in though.
Click to expand...
Click to collapse
Wow. Suggesting people use a simple apk to root their device earns you "brick duty"? And talk about sarcasm, your last sentence is a good example.
What's the point of XDA if we're afraid to do anything to our devices?
sent from an Elix-R nexus 5
afraid?
move_over said:
Wow. Suggesting people use a simple apk to root their device earns you "brick duty"? And talk about sarcasm, your last sentence is a good example.
What's the point of XDA if we're afraid to do anything to our devices?
sent from an Elix-R nexus 5
Click to expand...
Click to collapse
I don't want anybody to be afraid but I expect them to do their own homework and when they cut their sh*t up not come on here acting like a rotten punk and not willing to do any work to help themselves out.... Which is exactly what a 1-Click Apk breeds.., It tells them yay they were good enough to root device.. And they just dive into making other modifications especially on a device that has no fastboot capabilities and a locked bootloader I just don't think they should make anything that easy for a unit that is this hard to recover.. Because obviously you're not going to be here to help the ones that were ignorant enough to get an application to root device but not educated enough to accomplish any other modifications without bricking their units and then come back here implying that it's anybody else's responsibility but their own.... I'm sorry but most the ones here Bricked right right now can't even run batch application without asking how to double-click thre times ... Much less run ADB commands so stick around and help please... if this device had fastboot or unlocked bootloader. I personally would not give a damn
Well, towelroot was made for a variety of devices and just happens to work with the hdx. So are we supposed to pretend it doesn't work just because some people are not able to know what they can and can't do?
Another movie quote :
Forrest Gump "Stupid is as stupid does".
Don't be stupid with your expensive tablet, if you are it's your own damn fault.
sent from an Elix-R nexus 5
tokenpoke said:
Lol. When the vroot method was posted a couple days ago the hdx forum was quite silent...
Then BOOM!
"OMG I BROKED MY TABLET! BRICKED HDX! *BLAH BLAH* BROKE MY TABLET! HELP!!!! HELP!!! BRICKED TAB! "
good warning for noobs.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I made my toolkit to help people avoid bricking issues by waiting for proven methods that work and that I tested. I made it a menu and not a stooped down click and auto run installer. I wanted to give people the choice what they wanted to install, without risk bricking.
I guess people go outside the box for the "easy fix" to a complex problem. People and jobs are like that, doing some half assed thing to keep the wheels turning. I'm just blabbing now.
Be safe when messin' with the hdx. I play with stuff while on a rom slot to avoid a stock rom brick.
move_over said:
Come on though, this XDA forums, isn't it? Anyone reading these threads should be well aware of the risks involved. With towelroot app rooting the device is simple, and not going to brick your tab. Being reckless and doing some of the other things you mention, well, sorry, but like Clint Eastwood says in Magnum Force, "A man's got to know his limitations".
sent from hdx+ with tapatalk
Click to expand...
Click to collapse
Obviously "anybody reading blah blah blah", isn't the case, as evident by the brick posts & my PM inbox. Sure, this is xda, but it's not the XDA it used to be. Part of that is because of the ease with which one can obtain root. You used to have to do everything manually, so you actually had to read, sometimes info for a completely different device, and then spend time figuring out how to apply it to your particular device. I am not saying nobody should root, frankly I do not care either way. What I am saying is that it is probably a bad idea for some people. Seriously, you think the guy that had no idea what Linux was, or the guy that thought you double click on the adb.exe to make it magically unbrick a device are good candidates for having unrestricted world writable access to a device? No. All you have to do is read some of the posts to know it isn't a good idea for some ill-prepared people & they obviously DIDN'T understand the consequences, otherwise they wouldn't have tried doing things that even the newest well informed member would ever try doing.
At any rate, this is what I think of now whenever I think of XDA, particularly the HDX forums lately. LMAO....
Say what?
Do any of you have anything useful to add besides your nanny pandering bull****? It's funny when you start digging for info on rooting a Kindle Fire HDX and this one of the first things you run across, a bunch of nannies moaning about it being too easy? Don't do it because you might break your toy because you are an idiot? Seriously? Is this a day care or am I missing something?
GSLEON3 said:
Obviously "anybody reading blah blah blah", isn't the case, as evident by the brick posts & my PM inbox. Sure, this is xda, but it's not the XDA it used to be. Part of that is because of the ease with which one can obtain root. You used to have to do everything manually, so you actually had to read, sometimes info for a completely different device, and then spend time figuring out how to apply it to your particular device. I am not saying nobody should root, frankly I do not care either way. What I am saying is that it is probably a bad idea for some people. Seriously, you think the guy that had no idea what Linux was, or the guy that thought you double click on the adb.exe to make it magically unbrick a device are good candidates for having unrestricted world writable access to a device? No. All you have to do is read some of the posts to know it isn't a good idea for some ill-prepared people & they obviously DIDN'T understand the consequences, otherwise they wouldn't have tried doing things that even the newest well informed member would ever try doing.
At any rate, this is what I think of now whenever I think of XDA, particularly the HDX forums lately. LMAO....
Having Root does not cause any issues. People create the issues, but who are you tell tell everyone not to root. Its their device if they want to root by all means root it. EVERY ROM and RECOVERY I have ever flashed or created states that in the terms of use that there is a potential they could brick their device. Who cares about your PM's. If you dont want to help them dont help, but dont create a thread just to complain about people bricking their device.
Click to expand...
Click to collapse
Thanks....but....
I'm not a developer....nor a hacker....nor a ...whatever.....just someone who enjoys reading and learning all that I can about my phone and Kindle Fire HDX....have rooted a variety of phones and Kindles through the years - first "mod" was to be able to download music and my own ringtones to a first edition Razr back in the day. I know there are so many people smarter than me - in some areas...not all - and I gratefully use that info and knowledge I get AT MY OWN RISK....as most people do, I think....the XDA site has over 5 million members - will there be some idiots who don't read or throw common sense and caution to the wind and screw up their devices?...sure....shame on them.
But if others with that knowledge have an elitist attitude about the rest of us - well - shame on them too. If someone knows how to make it easy for someone to be able to get the most of their device - while knowing the risks - BUT WON'T SHARE because they feel we don't 'deserve" that info - please....don't post! Just keep it to yourself and enjoy the fruits of your own labors.
PS...think it's a bit of a coincidence that when the romaster root surfaced - from a Chinese developer - all he** broke loose....it seems others had the knowledge but didn't want to share....oh well.....and please...this is just my humble opinion.
I appreciate all the efforts of the developers and testers who make it easier for people like me to really get the most out of their devices - but I think there is a reason that most of the major companies lock down theirs....to stop the ones who will stupidly brick the device and blame the company....thanks for reading.
I have
revircs said:
I'm not a developer....nor a hacker....nor a ...whatever.....just someone who enjoys reading and learning all that I can about my phone and Kindle Fire HDX....have rooted a variety of phones and Kindles through the years - first "mod" was to be able to download music and my own ringtones to a first edition Razr back in the day. I know there are so many people smarter than me - in some areas...not all - and I gratefully use that info and knowledge I get AT MY OWN RISK....as most people do, I think....the XDA site has over 5 million members - will there be some idiots who don't read or throw common sense and caution to the wind and screw up their devices?...sure....shame on them.
But if others with that knowledge have an elitist attitude about the rest of us - well - shame on them too. If someone knows how to make it easy for someone to be able to get the most of their device - while knowing the risks - BUT WON'T SHARE because they feel we don't 'deserve" that info - please....don't post! Just keep it to yourself and enjoy the fruits of your own labors.
PS...think it's a bit of a coincidence that when the romaster root surfaced - from a Chinese developer - all he** broke loose....it seems others had the knowledge but didn't want to share....oh well.....and please...this is just my humble opinion.
I appreciate all the efforts of the developers and testers who make it easier for people like me to really get the most out of their devices - but I think there is a reason that most of the major companies lock down theirs....to stop the ones who will stupidly brick the device and blame the company....thanks for reading.
Click to expand...
Click to collapse
LOL I have noticed everybody that has chimed in about any complaints going on here have not been here to help recover in any of these devices last few days .. Trying to help people that refuse to help themselves.... I mean really we can only feed them so much info and babysit so much and get told please help please hello please help me . And when you attempt too. they have absolutely no clue of what you are talking about or what you're trying to get them to do it just looks too complicated so they keep asking for help... Expecting somebody here to make an easy one click.. To salvage their mistakes and keep their mommy and daddy from finding out they bricked their tablets.....and btw if this device wasnt soo fn locked down.. We would not be having this discussion because recovery of a brick would be easy with fastboot capabilities and unlock bootloader click click done. So I call BS honestly over the last few years out of all these devices I've been here in xda tinkering with.. The only time see false warranty claims are always on devices that are locked up tight.
If they refuse to help themselves then don't help them. Claiming that something shouldn't be easy and the fear mongering and elitism aren't helping anyone. Instead of trying to be a nanny document the known problems and work arounds if there are any. If you don't want to do that then don't. Save the other BS for your significant other cause no one else worth concerning yourself with wants to hear it. This thread is pointless, people here want to root their devices for any number of reasons; they why's don't matter and if it goes south it's not your problem.
I
jptros said:
If they refuse to help themselves then don't help them. Claiming that something shouldn't be easy and the fear mongering and elitism aren't helping anyone. Instead of trying to be a nanny document the known problems and work arounds if there are any. If you don't want to do that then don't. Save the other BS for your significant other cause no one else worth concerning yourself with wants to hear it. This thread is pointless, people here want to root their devices for any number of reasons; they why's don't matter and if it goes south it's not your problem.
Click to expand...
Click to collapse
I understand your point and this thread was not started as a wine fest it was supposed to be started for a fair warning I can't help it if he had a sarcastic tone to his voice from trying to help ignorant people all weekend and I think it's hilarious how people are chiming in complaining about our complaints but none of them have been here to help all the ignorant folk ... I'm just saying as one that has been here for the last five days repairing brick or trying to help that is ... Is a lot of and uneeded tension here I understand .. And it is turning" quite the Flamer thread ... So instead of chiming here to complain about our complaint and tell us to keep our complaints to ourselves as you are here complaining your self .. Please go to the general section or the troubleshooting section and start helping people... For example help him http://forum.xda-developers.com/showthread.php?t=2783591

Categories

Resources