Related
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
Hi guys,
I've been reading this forum for almost a month now (since I got my Epic), and I still haven't seen any description for a lot of the software you're using. I'm not an idiot here, I made a joeykrim exploit uninstaller of my own shortly after noobnl posted the one click exploit. Still, I'm not a mind reader. How do you guys even keep up with this?
ClockworkMod - The website describes it as, "An open source recovery image used by many phones". Not very helpful. There's a post on their forums asking what it does, with no response.
Andromeda - Apparently a ROM Manager with built in root. Not very helpful. Starting from the top, why would I need a ROM manager? Does this run on the phone? Why would I want a ROM manager on my phone? Doesn't this serve the same function as ClockworkMod?
AOSP Magic and Tha Boss ROM - Neither of these have any instructions. Tha Boss ROM actually includes a download link, while AOSP Magic eschews the link in favor of a video review. The video review is nice, as it contains the first instructions I've seen so far, brief as they may be.
A few lines of description on your releases would really help the new people. Really, you'd have to be a fool to download these programs and flash/fry your phone without description or instruction! You're pushing away the more cautious people who might otherwise join in.
Netop said:
Hi guys,
I've been reading this forum for almost a month now (since I got my Epic), and I still haven't seen any description for a lot of the software you're using. I'm not an idiot here, I made a joeykrim exploit uninstaller of my own shortly after noobnl posted the one click exploit. Still, I'm not a mind reader. How do you guys even keep up with this?
ClockworkMod - The website describes it as, "An open source recovery image used by many phones". Not very helpful. There's a post on their forums asking what it does, with no response.
Andromeda - Apparently a ROM Manager with built in root. Not very helpful. Starting from the top, why would I need a ROM manager? Does this run on the phone? Why would I want a ROM manager on my phone? Doesn't this serve the same function as ClockworkMod?
AOSP Magic and Tha Boss ROM - Neither of these have any instructions. Tha Boss ROM actually includes a download link, while AOSP Magic eschews the link in favor of a video review. The video review is nice, as it contains the first instructions I've seen so far, brief as they may be.
A few lines of description on your releases would really help the new people. Really, you'd have to be a fool to download these programs and flash/fry your phone without description or instruction! You're pushing away the more cautious people who might otherwise join in.
Click to expand...
Click to collapse
clockwork rom manager is an app on your phone that requires root access, allows you to flash roms under the android OS and is nice and GUI (graphic user interface)
clockwork recovery is at the boot level, before the android OS loads, it's used as a minimal menu to do lower level functions such as flashing roms to your phone, clockwork rom manager uses this as it's backend for flashing roms.
androidmedia, boss rom and aosp magic are all roms (entire custom android OS packages) flashable though clockwork recovery
everything listed as a kernel is only a chunk of the OS that controls the hardware and such... they can overclock the device and improve battery etc. applications and favorites and other user data stuff is uneffected.
the weird names are just what the developers are naming their software. What you should be paying attention to are key terms like
ROM, KERNEL, RECOVERY those are the different parts that are being modified...
That being said.... for someone that researched for over a month, you don't seem to be quite getting it, also this doesn't need to be in developer forum, and all this is in the hundreds of WIKI's posted on other android devices.. also a quick google search would answer most of your questions you're having
Netop said:
ClockworkMod -
Andromeda -
AOSP Magic and Tha Boss ROM
Click to expand...
Click to collapse
ClockworkMod - makes a custom recovery, along with many other programs and apps, that makes flashing custom rom's and kernels much easier. Add Clockwork Recovery to your phone and you can load any custom rom or kernel you want by simply booting into recovery. Instructions to install it on your phone are in the OP (original post) of the clockwork recovery thread.
Andromeda - It is a group of custom programs noobnl has made. He made a custom kernel (this overclocks (makes faster) your cpu and undervolts (adds battery life)). His kernel also installs rom manager and super user to make make rooting more functional. Noobnl also has an andromeda rom that modifies touchwiz to be a little different with some different features. In both cases read the OP of the two threads and you will find easy installation instructions (using clockworkmod recovery) and a description of what they both do.
Aosp Magic and Tha Boss - These are both custom roms that in some way change how your phone looks and functions. Custom roms are all just ways to personalize your phone. For the most part they all install easily with clockwork recovery. Read the OP of any rom and it tells what they have done, what they do with each update, and how to install it.
Not trying to be mean or anything, but reading the OP pretty much always explains everything. I have only been doing this since they epic came out and have just learned by trying things out. It is very difficult to fully brick your phone. Most the time if you can't get your phone to work you can use Odin (see the thread for more info) to flash back to stock and start over.
Just my two cents but people who are pushed away isn't a bad thing. If they don't know what they are doing they don't need to be doing this. There are several terminology threads on this site...pushing them away means a lot less clutter in the dev threads and else where. Not that I'm saying they shouldn't be here at all, but read read read read....read....and then read some more. And if all else fails bash it with a hammer and turn it in on insurance.
Sent from my SPH-D700 using XDA App
See, its hard to really complain on this because some people are doing some cool stuff on their own effort and time, but I will agree with the OP on this. I agree that only a few lines of descriptions would not only help new users but cut a LOT of threads and posts from people interested but unsure of what do or what something is. And in fairness, it sounds pretty bad when u say that if people aren't that familiar with stuff they shouldn't try it. We don't all know everything and sometimes a little info goes a long way. But that's just my opinion.
Sent from my SPH-D700 using XDA App
Unfortunately if you can't search, read, and understand all the info that is posted you'll have only one option to customize your phone...Sprint ID(which will cost you $$). I've found that none of the processes, such as rooting or flashing kernels, are difficult to perform. In fact sometimes the amount of information already provided becomes confusing to some. I understand the issue devs have with the clutter in this section of the forum. Maybe mods can help by moving topics to the general section and maybe preserving the cleanliness of this section. On the other hand, why all the rage against people asking questions? If I'm not mistaken everyone isn't magically born with all the knowledge required to customize their phone. That's why there are forums like these to provide a community where people seeking knowledge can find it. Personally I find the forums for any piece of hardware from my Directv box to my Epic to be absolutely the most valuable "manual" I can have. Its nice to rely on actual intelligent users for information and not a low paid csr with a script on the other end of the phone.
zetterwing said:
Unfortunately if you can't search, read, and understand all the info that is posted you'll have only one option to customize your phone...Sprint ID(which will cost you $$). I've found that none of the processes, such as rooting or flashing kernels, are difficult to perform. In fact sometimes the amount of information already provided becomes confusing to some. I understand the issue devs have with the clutter in this section of the forum. Maybe mods can help by moving topics to the general section and maybe preserving the cleanliness of this section. On the other hand, why all the rage against people asking questions? If I'm not mistaken everyone isn't magically born with all the knowledge required to customize their phone. That's why there are forums like these to provide a community where people seeking knowledge can find it. Personally I find the forums for any piece of hardware from my Directv box to my Epic to be absolutely the most valuable "manual" I can have. Its nice to rely on actual intelligent users for information and not a low paid csr with a script on the other end of the phone.
Click to expand...
Click to collapse
no problem with the questions, it's just where it's being asked is the problem. People don't think their question will be answered if asked in the general section, or the thread that relates to their problem and decides... I'll just post in the dev section.. there's smart people in that forum!
I've seen it more than once, people don't want to search, or research... or read.. they want to ask a question and have someone answer it directly without having to dig back through posts that don't relate to the question they're asking. Like I said I seen it more than once and the mentality is easy to pick up on.
Don't worry I'm on your side. I've just seen some pretty rough treatment of someone asking a question...in this forum actually(not this thread). They were posting in the wrong place but there's a better way to direct someone to the right place than to berate them. That being said go to the Search and type in "root my phone" without quotes and THIS thread shows up higher in the list than one-click-root. Tends to throw people off the search function. I know it's a faulty way of searching but it's the way people do things. Many forums have problems with their search though. A google search for root Epic 4g has similar problems...the top results link to outdated information and the one click is halfway down the page.
People don't always read the rules of a forum either...it's just human nature. At least the people that make it here are finding the smartest people to answer their questions
Thread moved to General. Please stop flaming the OP.
Link To Tutorial Blog
Hear me out on this one--I think it's a swell idea.
I'm a huge advocate of having very well tagged, chronicled, and accessible information for technical items. Being a novice myself with hacking, theming, flashing, and all the like, I always appreciate it greatly when there are really solid quality tutorials covering exactly what I want to do myself. What is it that the general population of Droid 2 users want? How to root, theme, and flash. Even for tasks as simple as running a one-touch root, some users may be frightened to try it because they're not tech-savvy and think they may load a file to an improper location, press the wrong button with their single touch, etc... Well written tutorials with screenshots make the tech world less daunting for newcomers, and that's something I definitely want to help with!
Being biased to Tumblr since I freaking love the site, I'd like to suggest that a blog be started there. I'll be making a mock-up tonight of the design, or maybe even flat out creating the blog, but the Tumblr theme creation really makes it easy to make your blog look like a fully functioning website. What's perfect about it is that you can make any blog you create into a Group Blog, which is what I propose for this "project." Multiple users are allowed to post and edit posts on the blog, so we wouldn't even have to have a shared account on the site.
I'd like to open this up to serious tutorial writers only! Each tutorial should have a minimum of two screenshots or pictures of your Droid 2 going through important steps for each subject we cover.
I understand wholeheartedly if no one would like to volunteer until they see a tutorial from me first. Once I have the blog up-to-snuff with my own web design standards, I'll dive in to how to root your phone. I might even post a few tutorials for rooting, depending on how many methods I run into.
If you're interested, you can either shoot me an email to allyouhavetolose(at)gmail(dot)com or chat me up on Skype (username: misterivanovich). Don't worry, I totally won't get [fully] naked if we video chat.
Make your way to Droid 2 Development where there are:
Directories on everything Droid 2 related, tutorials, and video tutorials...
And better yet, they are already stickied.
I did find a few nicely done tutorials, but that's just not quite the feel that I'm going for. While those tutorials are informative, they are very technical. If you take a look at Skull One's Overclocking 101 thread on droidforums.net, that's more along the lines of what I want to do (his is WAY more in depth than I care to get with my tutorials though!).
I have the beginnings of the Tumblr page done (which I will link to after I've posted 8+ times here haha), but I haven't finished editing my first tutorial just yet. Really, I'm going to be doing this half as a chronicle of my own learning, because I'm really not well versed with Android customization in any way--I've also been having quite a bit of difficulty getting familiarized with it because of the way that I learn and the way the tutorials are written. For that reason, I'll be writing my own tutorials knowing very well that there has to be at least ONE other person out there that will benefit from it haha. And if I can help one person, then that's kosher with me.
I have updated the first post with a link to the tutorial blog. Although it is incomplete in design and I haven't finished or edited the tutorial I have posted, you can get the general idea for what it is I'm going for. At least I think you can...
Again, anyone who feels like contributing, feel free to shoot me an email or get in touch with me on Skype or via PM here on the board. You are also welcome to give me suggestions for future tutorials, correct me if I've written something incorrectly, etc... All of which will be credited wherever applicable.
Though I appreciate your good intentions, your blog/tutorial thing is... well... time not being put to good use. First of all, there are already tutorials on how to SBF your phone. I would know. I wrote one almost 6 months ago. And there are others out as well.
http://forum.xda-developers.com/showthread.php?t=770224
and/or here:
http://www.kimete.com/sbfrsd.html
I don't see why you are rewriting everything unless there is a need to. Now, if you feel like my tutorial is lacking in quality or quantity, I certainly encourage you to rewrite a guide, write an updated one, or whatever. But what you are doing is recreating stuff that ALREADY exists. Additionally, you didn't even write correct directions to SBF'ing the phone. Not only incorrect, but you have incomplete directions and procedures. In my opinion, your tutorial is incredibly misleading and very inaccurate and will throw a lot of people off.
Well, even if it's not time put to good use for anyone else, I will be benefitting from my own blog. I think it will help me to understand things a bit more if I'm writing it all--sort of like how when you lead a study session, you end up being super refreshed on the topic yourself.
I'm not opposed to, with proper permission and ample credit given where due, just following other tutorials that have already been written and showing screen shots of the process that I follow as outlined by someone else. Some tutorials have no real need to be rewritten, but do lack a visual element in my opinion. I almost want to be able to know what I have to do without even reading the post and looking at the pictures (almost... I realize that's a stupid goal to take literally).
I'll check out your guide for flashing an SBF and figure out what is so terrible and misleading about mine, then I'll fix it haha. I'm not looking to replace any of the tutorials that anyone else has already done--I simply want a super compiled and organized list of them, if only for my own use. But I'm pretty sure that at least one more person out there in the world, somewhere, may eventually one day sort of be happy that I did it. :]
The reason why your tutorial is so misleading is because
1. You have no real knowledge of the topic at hand.
and 2. Because of number 1, your work is incomplete, and not
I have no problem with you taking my tutorial here on XDA and making edits and additions. Add pictures, or make additional notes, or what not. Of course, give credit where due.
But whatever you do, 1. Don't rewrite things that already exist, and 2. know what you are writing about before you write about it. My tutorial has gone through countless revisions. Additions, subtractions, rewording, simplifying the process for the end-user, troubleshooting of errors. EVERYTHING!
In all honesty, if you want to contribute, take my work, run through it on your own phone, and make additions and edits to that.
Well, I wouldn't say I don't know anything about the topic. I DID already flash a SBF to my phone before I wrote the guide, I just didn't read up more than I had to on the topic--I found out how to use RSD Lite, found the .sbf file, knew I would want to make backups first, then dove right into it. I can't say that I agree with you that my guide is really missing much as a general outline for flashing an SBF, but like I said in one of my posts already, I haven't even finished that tutorial yet! I just posted a link to it so that if anyone were interested in helping me compile it all on to the tumblr, they could see what the blog looked like and a very, very general idea of what a post would look like.
I'll certainly be going back to edit that tutorial plenty. That is, after I finish it in the first place.
allyouhave said:
Well, I wouldn't say I don't know anything about the topic. I DID already flash a SBF to my phone before I wrote the guide, I just didn't read up more than I had to on the topic--I found out how to use RSD Lite, found the .sbf file, knew I would want to make backups first, then dove right into it. I can't say that I agree with you that my guide is really missing much as a general outline for flashing an SBF, but like I said in one of my posts already, I haven't even finished that tutorial yet! I just posted a link to it so that if anyone were interested in helping me compile it all on to the tumblr, they could see what the blog looked like and a very, very general idea of what a post would look like.
I'll certainly be going back to edit that tutorial plenty. That is, after I finish it in the first place.
Click to expand...
Click to collapse
I believe what the point here is rather than redo tutorials that have already been done, why not look into something new.
You know how if you read someone's phone number to yourself, then try to dial it the next day, you forget it entirely--but if you had written down the phone number, your chances of remembering it are significantly better?
It's kinda like that. Like I said, this is for my own benefit, I was just opening it up to the community to put all of the Droid 2 tutorials in one common space.
allyouhave said:
You know how if you read someone's phone number to yourself, then try to dial it the next day, you forget it entirely--but if you had written down the phone number, your chances of remembering it are significantly better?
It's kinda like that. Like I said, this is for my own benefit, I was just opening it up to the community to put all of the Droid 2 tutorials in one common space.
Click to expand...
Click to collapse
Do as you desire, however I was shedding light on DarkOnion's mindset as I see it.
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.
Hello, I m using htc leo:hd2, and its now converted to android, but the problem is about phone is showing my phone is htc bravo android v.2.2.1. Please guide me to find a suitable ROM for my phone... and how can i get it?
There is a Android HD2 NAND development section you know.
try LOOKING there
its not hard you know, looking
try this link
http://forum.xda-developers.com/showthread.php?p=25781675#post25781675
I think by now, we are tired of seeing the exact same thread pop up over and over again.. A simple google search of "best android rom" would result in a plethora of hits that would have solved your problem faster than making a new, but redundant thread.. One size does not fit all, and you will have to try out various roms before you find one that you like..
Thanks a lot
adil1508 said:
There is a Android HD2 NAND development section you know.
try LOOKING there
its not hard you know, looking
Click to expand...
Click to collapse
Thanks a lot for ur support
trazzaque said:
Thanks a lot for ur support
Click to expand...
Click to collapse
Your very welcome
Sent from my HTC HD2 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1795608
This one has been really good for me.
look for one of the miui roms
Welcome to forums. I'll give you a few brief tips on what I've learned over the last six months about android, hd2, and android.
With a typical nand install, the bootable system is installed on your internal nand, irrespective of your sd-card being present. Some may relate to the following comparison to a microsoft windows based system: your nand is like your internal hard drive "master" that contains your "C:" drive.
Your system folder on your nand has files specific to your device as required for it to boot and run properly. To access the market (google play) as well as have various hardware functionality, there is a file "build.prop" that is a small file with a text list of various descriptors. Being that the hd2 was not shipped with android, some of these descriptors name other devices as opposed to the actual device. In this case the "leo" or hd2 is using a ported version of android from a "bravo" or desire HD. So your system isn't malfunctioning describing another device name, rather, it could be looked at as "masquerading" as another device. I'm certain that is a severe dumbing-down of the technical details, but it's been helpful for some to look at it that way.
As for xda, I hope you spend an enormous time reading and not posting, as I have done all year. I have not posted at all and have literally read damn near every single post in the hd2 section and many more useful posts in other sections. After over six months and countless hours experimenting/flashing/customizing/etc on my own I am beginning to post now, attempting to contribute a bit in the forums that aren't still restricted for me because I feel comfortable enough to begin working towards contributing my input in the developer forums.
Most forums online have a similar attitude towards the plethora of posts like this, which bluntly request a quick answer for what is best determined through spending time reading and researching.
Hopefully you read the above and didn't skip to the end here where I wholeheartedly recommend the xylograph paranoid android ics rom. Cheers, and best of luck getting this amazing phone to fight well.
Amen to that. Nonetheless for starters go soft on your first rom get the CM7 of tyween. It's light and works well. But it's your choice. Indeed, look at me, just joined yesterday spent also almost six months reading the posts and relevant dev threads. Why am I posting, need it now to be able to complete my ten......
I can say for myself only. By my opinion, AOKP has best combination of settings and tweaks which really make life easier. Battery life and speed of this rom are very very good. But unfortunately this rom was not very stable for me, I experienced hot reboots regularly.
So I switched back to NexusHD2. It has comparable battery life and speed, but less tweaking possibilities. Stability of this rom has always been out of question for me. It is solid rock.
TyphooN CyanogenMod ROM was my first rom on HD2 and I have only positive impressions of it. Switched to ICS just because this phone let me do that. Prefer newer versions when possible.