Database Users

Some help with my Magic please

Hi Folks,
I've had a TP2 for a while now and modded it loads of time with help on this site and wanted another unit with android so I bought the magic from another user on here called thedalmeny, the deal went through flawlessly may I add.
I am not a noob when it comes to modding but I am when it comes to the magic! I have a Vodafone branded Magic in the UK 32B.
Now the Magic was rooted when I got it and has Qteknology Devs Roms for VodaMagic 32b.
How do i find out which SPL has been used on it?
Also, I'm finding this rom to be a bit slow, which one's could I use instead?
And i'm getting a notification, "SD card is damaged" it's asking me to format it. If I do this via the phone is that ok?
thanks for the help.

I don't wanna be an ahole, but seriously. You just asked a ridiculous question, it's the most simple and most basic question. it's answered EVERYWHERE because you NEED it if you even wanna root your phone, it's the first thing you check. Seeing as how you modified your TP2, you should have some knowledge on how to look up info yourself. Please don't tell me people spoonfed you every step of the way.
DaneFTO said:
How do i find out which SPL has been used on it?
Also, I'm finding this rom to be a bit slow, which one's could I use instead?
Click to expand...
Click to collapse
Have you even tried looking for help? Start here: I click on the dev section and theres a bunch of stickies. People also always ask which roms they could use, take a look at the other 8126189217 threads. But seriously: Do something yourself. Spoonfeeding = more horrible questions. I don't see why your questions should be answered here when they're all already answered elsewhere. Trust me, you'll continue asking more and more. There's a lot you have to know and you could learn all this if you read things and searched.
As for the third question, I guess thats an ok question, not really but sort of. Why is it not ok to format via phone? I don't see how it could damage it more or anything. Just make sure everything on your sd card is backed up incase.
Hopefully from now on, you can do some research yourself and if you get really stuck, we'll definitely help.

Haha, love it. Don't worry, I don't take offence easily!
Come on, I see these types of questions all the time and they always get answered.
Yes, I realise this one has been answered, not exactly the way I would've liked it but still it is much appreciated.
I have already done a whole bunch of reading, I just wanted the learning curve not to be so steep...
Flashing a TP2 rom seems a piece of cake compared to all the messing you have to do with the magic.
My real q was to do with the SD card really, I added the other 2 as a cheeky try to get info easy, don't worry, lesson learned.
The reason why I asked about the SD card because I've read that you need to partition this and that and did not want to format the sd card incase the format would not make all the necessary partitions and it would in some way brick the phone. I know, I know, how could the sd brick the phone. Just wanted to check.
Cheers.

Yeah the learning curve is a bit steep, but if you need help or something you can just send me a pm and hit me up on google talk or something. The SD card only has to be Fat32 and you're set. Theres other things such as swap/ext partitions which are explained in other help topics but to be honest, you don't need them. It's more for the old G1/Dream devices. You can use swap if you want but I find my phone perfect without it. if I'm correct, it may even cause some damage on your sd card (although im not 100% sure). But yeah, if you really do need help (I personally find it easier talking to someone rather than reading a billion instructions as well) then let me know via pm.

Dev seems really slow on Ubuntu/Kbuntu

I would have thought somebody would have edited the files to boot from MAGLDR by now

feel free to do it yourself

brashmadcap said:
feel free to do it yourself
Click to expand...
Click to collapse
haha smartass, how long did it take you to come up with that one?
I wasn't been an arse or complaining, I was starting a discussion as its unusual for develpment to take this long on a popular platform. I was simply commenting on my surprise that a dev hasnt had a go yet or if they have its taken quite a while so maybe its harder then porting a SD build to magldr.
There was no need for the cliché of "do it yourself then" when somebody makes a remark about dev. 99% of people on this site are not devs, It may have started out as a dev majority site but it isnt anymore. If you didn't want to discuss the topic , sod off!

Wow, way to be defensive.
People on this site get touchy when you comment about developers. Here's why:
1. Developers are less likely to release their stuff if people are pushing them for releases, ETAs, etc.
2. Developers do this for free, for the most part. Sure, they can ask for donations, but that's only after development is completed, and I doubt it's much money for the average dev. So since we're basically being gifted these developments, people don't like to see comments against them.
I understand where you're coming from, but a flame war isn't really warranted. Just my $0.02

Danation said:
Wow, way to be defensive.
People on this site get touchy when you comment about developers. Here's why:
1. Developers are less likely to release their stuff if people are pushing them for releases, ETAs, etc.
2. Developers do this for free, for the most part. Sure, they can ask for donations, but that's only after development is completed, and I doubt it's much money for the average dev. So since we're basically being gifted these developments, people don't like to see comments against them.
I understand where you're coming from, but a flame war isn't really warranted. Just my $0.02
Click to expand...
Click to collapse
1. I didn't push anybody and didn't ask for an ETA.
2. I didnt make ANY comment against ANY dev, I was simply commenting on my suprise that nobody dev/user etc has managed or tried to edit the files to boot from magldr yet.
I would understand the points given here If I had wrote something like...
"come on devs pull you finger out.." or "What is taking them so long"
etc as that would imply that I had a impression that they owed us it or its their job, I DONT HAVE THAT IMPRESSION" I was simply commenting on my surprise that nobody has managed or tried to do it yet.

So... do you think all the dev work lately is magldr or 0.4 awesomeness based?

straby187 said:
So... do you think all the dev work lately is magldr or 0.4 awesomeness based?
Click to expand...
Click to collapse
latest work as far as i know is a nand based install.
magldr is for cottula to update, it's on his todo list.
plopper

Ubuntu on NAND and android on SD!!!!!!

how they gonna fit 3GB linux on 500MB internal memory!! by the way! i like to edit this files but have no idea to do so! is there any page or somthing that i can begin with?

Ubuntu is setup different than android... it's not an easy fix like it is with sd android builds to get it working with magldr.

I too would really enjoy running it off NAND.
I'm no genius, especially in this aspect..But I would figure we'd at least be able to work in some nifty way to start the boot process in NAND and load up everything else with the SD card.
Cuz' only way I've seen people do it so far is through Windows Mobile, which I do not believe I will ever go back to. XD
If I did have the knowledge to do so, I'd jump at some dev work on making such things possible.
Alas, I do not.
So I shall await word patiently.

there are smaller linux builds that could fit on the NAND, although you wouldn't really have room for swap space unless that gets moved to the sd card.
but basically im just posting to say if i knew how to open up the magldr and write/re-write the files i'd do it. just give me some programs and i'll start messing around and see what i can do
<---- little programming experience, ready to jump in the water with the sharks lol

youngdaddytc said:
there are smaller linux builds that could fit on the NAND, although you wouldn't really have room for swap space unless that gets moved to the sd card.
but basically im just posting to say if i knew how to open up the magldr and write/re-write the files i'd do it. just give me some programs and i'll start messing around and see what i can do
<---- little programming experience, ready to jump in the water with the sharks lol
Click to expand...
Click to collapse
MAGLDR is closed source.

TheATHEiST said:
MAGLDR is closed source.
Click to expand...
Click to collapse
oh, that's too bad. i see why it is of course, so peeps dont play around and brick their phones accidentally. but kind of unfortunate if you want to advance it quickly.

I could be wrong but I think its the kernel that makes it not work woth magldr and clk. I got ubuntu v0.3 to boot with clk but reboots after loading up..... like i said i think its kernel related.... but im not a dev so i may be wrong....and wat was mentioned above about booting from nand is basically what i did with clk bootloader....i just flashed the zimage and initrd from ubuntu 0.3 to the boot partition.... then when turned on it loaded it off sd immediatelt....but just restarts right away like it does with magldr.....
Sent from my HTC HD2 using XDA Premium App

Ubuntu是比Android设置不同... ...它不是一个容易解决，就像是与SD Android的基础得到它的工作与magldr。

Come learn from thanks! ! !

So maybe one day there will be away to dual boot ubuntu and android on the hd2?
Sent from my myTouch_4G_Slide using Tapatalk

[Q] [ROM][Nightly][ICS] Team Eos nightlies. (Motorola Xoom Wifi Only) Query

Greetings folks.
First time posting to these forums so I have to post here. I did see another thread in this forum on the Eos ICS Nightly builds but it has degraded into a discussion of the limitation of posting in the Dev forums, something I'm not fussed about. So far I'm extremely impressed by the work done and am more than happy with my understanding that this is an Alpha Build and not everything works.
This is not a complaint about things not working but rather a query that has come out of reading the entire EOS Nightly thread.
One thing I can not ascertain from the forums: it seems some people are able to use the External SD card in Read/Write mode. Unfortunately, I can not seem to be able to do so. I'm only able to get it in Read Only mode.
I've tried issuing standard Unix chmod commands (g+w) to change the mode without success. I tried checking for a mount table in /etc also without success.
Can someone please advise if a) /mnt/external1 can be made Read/Write under Build 12, and b) if so, how to get it going?
Much Obliged,
M_Cheevy

I think I read in the thread that using root explorer works... I think!
Sent from my Xoom using xda premium

burden010 said:
I think I read in the thread that using root explorer works... I think!
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Burden,
Thanks for the swift reply. I'll give it a try.
I should have mentioned that I've tried using Alpha File Manager to do this. Up until now that is Also, in the past, with the Tiamat kernels, Alpha was able to Read/Write to the external. However, I do understand that not all applications are ICS ready. I'll try Root Explorer and post the results to this thread.
Much Obliged,
M_Cheevy

It only worked for me when I downloaded an External card write app from the market.
As far as my thread went, well you classing it as me complaining mybe explains some of the comments I got I suppose. My point on OTG was not a complaint at EOS but as you have mentioned here it does not work. All I was aiming at and if you read the Motorola forums both external card write and OTG mount were never enabled by Motorola, no one seems to be saying if they will with be enabled by Motorola in ICS ?
Now if this is was an Alpha build by Google I could understand, but if Motorola can only work with this and thats it, it does concern me with how much better off we will be.

Xoom68,
Please don't mistake my characterisation of your query as a complaint. I merely stated that the thread had gone that way. I'd really rather this thread merely addressed the specific issue I had with Read/Write.
Burden010: Thanks. I did cough up the $4 for Root Explorer and it was able to access the External SD in Read/Write mode successfully.
I'll update the thread header with a "Resolved" flag. (Tried, but doesn't seem to be possible)
Much Obliged for all your help,
M_Cheevy

M_Cheevy said:
Burden010: Thanks. I did cough up the $4 for Root Explorer and it was able to access the External SD in Read/Write mode successfully.
Click to expand...
Click to collapse
Glad it solved your issue
Also... and I don't want it to look like I'm trawling for thanks points here (although I blatantly am) if someone helps you out on the forum, it's customary to hit their "Thanks" button.

Etiquette lesson received and acted upon

i have questions to ask. is the problem with games fixed? like dead space not rotating screen or gameloft games not recognizing the xoom...or if there is any problem with apps not working...i dont care is its lags. and i dont care about camara,hdmi...just want apps and games to work. any feedback on games?

jerses said:
i have questions to ask. is the problem with games fixed? like dead space not rotating screen or gameloft games not recognizing the xoom...or if there is any problem with apps not working...i dont care is its lags. and i dont care about camara,hdmi...just want apps and games to work. any feedback on games?
Click to expand...
Click to collapse
I suspect most of these issues will have to be resolved by the game publishers, and there's not much the EOS team can do about it. These are probably compatibility issues with the game itself under ICS. I'm fairly sure they will be gradually resolved by game publishers as more ICS devices get in the wild.

Call for Organization/Stickies!

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.

DO's AND DONT's FOR FLASHING GALAXY NOTE

DO:
1) Hate Gingerbread and pester Samsung about official ICS update to Note
2) Google around for best ways to root your device. Specifically check out rootgalaxynote.com for noob-friendly advice and videos
3) Check out in your phone's about settings and note down the kernel version and the ROM version on your device. Also note the manufacturer's official designation of your device (i717, N7000 or i9220 in this case)
4) Realize that what you do to your device is your own responsibility. Samsung and/or XDA and/or your mom won't be there when you are staring at a fancy black brick as a result of the RISKY procedures here. Well, maybe your mom will be there, so be good to her
5) Check which features are and are NOT working in a given ROM before flashing it
6) Be in it for the long haul and be prepared to tinker, adjust, flash, reflash, backup and restore to mold your device to your liking. There is NO ONE SIZE FITS ALL solution to anything
7) Purchase MyBackup Pro and make complete backups of your apps every now and then
8) Develop sufficient proficiency with ClockWork Mod to be able to Nandroid backup before EVERY flashing
9) Go to your local market and check for fallback options in case you lose your phone. Either shortlist the same device (Note) or get some cheaper options (such as dirt-cheap and excellent Galaxy Nexus) shortlisted. Make sure your bank account has the requisite sum before you even think about hitting download mode on your device
10) Keep in mind that for some strange reason, flashing a Note is more complicated and risky than flashing a GS2 which confirms that earlier assumption regarding both devices being largely the same is not that true
11) Keep in mind that NO TWO GADGETS, NO TWO SETUPS and NO TWO CONNECTIONS are the same, even though they might be the SAME model from the same manufacturer. Some might have different memory, or a different radio, or your PC/Laptop might have a few kilobytes missing from the downloaded drivers, or there might be a power surge. Bottom line: following the same steps as another user might NOT give you the same results.
12) Hit search for 'ICS Repack' in any Note ROM forum. That, and the unstable leaked kernels (LP5/LP6) seem to be causing the most cases of bricking of Note while flashing. Avoid ICS repack if you can - I did with good results.
DON'T
1) Think that the ROM creator, or Samsung, or your mom, is in any way responsible for anything bad that happens to your device
2) Flash without ensuring that your kernel is up for it (see (3) above)
3) Skip steps or downloads in a lengthy procedure in hopes that things will work out in the end
4) Backup or restore system apps via MyBackup or Titanium
5) Conclude on the performance of your battery before going thru several charge/recharge cycles
6) Adopt an accusatory tone in your comments

Thanks captain obvious.

someone actually thanked the OP for this list?

panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
That's a bad thing why? If the majority of new Note users would actually read lists like these we'd have a lot less 'oh noes' and 'why doesn't this work' threads and posts.
Taking the time to make a list like this shouldnt be rewarded with ****ty remarks like yours or irish-sid's. At least he's trying to contribute something to this community.

DO:
11) Flame OP
Sent from my GT-N7000 using XDA

irish-sid said:
Thanks captain obvious.
Click to expand...
Click to collapse
panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
Beretta93 said:
DO:
11) Flame OP
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
you guys are what's wrong with this community and the world in general. zero tolerance for anything. The OP is just trying to be helpful, no need for snide comments, and useless posts unless its helping answer someone's question or making an informative post/thread. If something is misleading, then yes make a post that's letting someone know its misleading, THAT's informative. This may all be obvious, but its all the right information given, and it may help someone that's new here, and even to regular members.

It's a joke come on...
Sent from my GT-N7000 using XDA

fail0verflow - Long-ass dos and don'ts list with not a mention of ICS repack kernel issues, which is THE most important issue for this device right now.

Entropy512 FTW!
Sent from my GT-N7000

Nice list. Problem is: People who really need such info usually don't read or google They prefer to ask the same questions over and over again.
Sent from my rooted Galaxy Note using XDA Premium App

Thanks op.
Why would anyone need to search rootgalaxynote.com to know the best method when everything is here at xda (most of the time those guides are copied from XDA). Don't take me wrong I appreciate your efforts.
It should mention ICS kernel repack issues.
My friend bricked his phone while flashing with Odin.
He had custom power saving plan on his laptop that put it to sleep mode in the middle of flashing process.
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.

Boy124 said:
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.
Click to expand...
Click to collapse
*nods sagely*
Sound advice!

panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
Listen, if you go even in a cursory manner around the Galaxy Note ROM forums (esp Stunner) you will plainly see that this guide is badly needed.
And thanks for taking out the time and the effort for that constructive comment.

Boy124 said:
Thanks op.
Why would anyone need to search rootgalaxynote.com to know the best method when everything is here at xda (most of the time those guides are copied from XDA). Don't take me wrong I appreciate your efforts.
It should mention ICS kernel repack issues.
My friend bricked his phone while flashing with Odin.
He had custom power saving plan on his laptop that put it to sleep mode in the middle of flashing process.
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.
Click to expand...
Click to collapse
Many thanks for your support. I intended it to be a general guide leading up to the relevant information in the forums, rather than reproducing the information here. That's why I stressed on people reading all the posts on an entire forum. Reading this would easily lead people to ICS repack related issues, but still I am editing the OP to include a mention.
I plugged rootgalaxynote.com simply because it contains some helpful videos, otherwise I agree that XDA has everything needed.

Oh boy.. look's like I've managed to transgress with several of the items listed.

Is there any advisable way to restore apps + app data (not system data) after a fresh flash? I'm really not crazy about starting from scratch every time. Seems very un-Androidy.

Xephrey said:
Is there any advisable way to restore apps + app data (not system data) after a fresh flash? I'm really not crazy about starting from scratch every time. Seems very un-Androidy.
Click to expand...
Click to collapse
Titanium backup. I advise you to buy the pro version. It's really worth it. You cant have a rooted phone and not have this (that's if you are even rooted).
Sent from my GT-N7000 using xda premium

Oh! He said not to backup or restore -system- apps. I'm retarded. Dunno why I missed that.