Note: more content is coming regularly, so check back regularly! Also, post your input so this thread does not become buried.
As an initiative to kickstart development for the Galaxy Player 4.0, I have decided to put up this guide to try and attract more users to rom development. This, although, does not mean you can willy-nilly post up a rom including one mod, or a quick tweak. Making a rom involves a lot more than that.
The Developer's Code:
1. Your rom MUST be unique from the other roms.
This means you have to have a careful, well thought out rom. It must have several things differing it from other roms, something that makes it stand out. The last thing we need are 200 "me too" roms cluttering up development. Takes Klin's rom and mine, for example. We both have ICS themes, we both have tweaked our roms for performance, but they are both completely unique. Why? Because we didn't copy one another. We saw what the other had, and left it alone. I have an ICS theme, he has an ICS theme, but they are based on completely different themes. The biggest boo-boo in rom devving is copying someone else's rom/features/work. You will get kicked out unbelievably fast if you DO NOT follow this rule. To reiterate, the last thing we need is 200 identical roms. Make sure yours is unique from the others, and has a defining feature.
2. You must be willing to provide regular, consistent updates.
Maintaining a rom can be a full time job. You have bugs to deal with, features to add, and hours of work in which you only accomplish a small amount of work, due to some catastrophic failure. Last night it took me over 3 hours to fix a battery icon issue. Why? because I had almost space left in which to apply my fix, and if I did even one step wrong I had to reflash to correct the issue.
You should NOT release your rom once, and never look at it again. You should be willing to update it at least twice a month, if not sooner. I update mine several times a week, but that's because I have a lot of free time. Your mileage may vary, but try to hit for that mark. Too long wihtout an update and users will get bored/tired of your rom without anything new to spice things up.
3. You must be willing to provide helpful, friendly support.
At times, monitoring your thread can be frustrating. you may have someone complaining about an issue that was fixed several releases back, or someone who wants a new feature and keeps bugging you about it. It can be frustrating at times, but make sure you calmly answer everyone's questions in a fair manner. It can be extremely frustrating for a rom user to post up a question, and have it answered days later because the dev was "too busy" to monitor their thread. This, if anything, is almost more important than rom updates. Users love devs who actually converse and answer them, so be friendly, and keep your thread going!
4. ALWAYS ALWAYS ALWAYS give someone the apppropriate credit for their work.
It is the bane of the dev's existence: spending days/weeks/months of xyz feature/theme/rom, and have someone come along and snatch their work from them without as much as a "thank you". First of all, it will get you banned faster than any other offense out there. Secondly, it is one of the largest insults you can give someone. Our community is one that is supposed to share work, and most people do that freely, but you MUST give credit where credit is due. It is best if you ask someone's permission before you use their work, especially if it is something major (a huge theme for example). But even if you don't (and you should), at the very least list their username and what they did in your rom SOMEWHERE in your description.
5.You do not know everything.
After creating a rom, many people feel that they know much more then the "average" community, and that they are always right when it pertains the their rom. This could not be more wrong. The best way to improve your rom, is to listen to xyz person who knows more about a certain area than you do, and attempt to learn from that person. Everyone is skilled in a different area, so if you listen to your community, and assume they know best, you can learn and accomplish a lot evry quickly.
6. Google is your friend.
Do not assume that dev's know everything, and that they pull these features out of their heads. When in doubt, go to google. Always. There is normally a guide, or someone with your issue to help you out. As usual, make sure you give that person credit if you use their work.
So, to sum it up, Make your rom unique, be dedicated to your work, be ready to handle unexpected situations, ALWAYS give someone appropriate credit, listen to your community, and google a lot!
Not intimidated yet? ready to bring your amazing idea to the limelight? head on down to the section below to get started!
The Easy Way to Dev: Odin flashable packages.
Most people don't want to edit their rom on their computer. As a matter of fact, you can create a killer rom without even touching a computer to mod it. Up until I started theming, I working on my rom 100% on my device. This is the most tried-and-true method out there, and the one most likely to create the least drama. All you have to do is Pull the /system partition from your Player, and create a tarfile out of ti.
Prerequisites:
Samsung Device (system partition location may change with device type. This should be the same for US/INTL players)
PC running Ubuntu/form of linux (ubuntu is recommended for beginners)
ADB installed (actually not needed, but speeds up the process) (look below in resources for a guide)
appx. 300mb free on /sdcard
about 1 GB free on the Linux box
1. Apply whatever mods you want too
2. Open up a terminal emulator
3. type this in: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
4. wait for it to complete (may take up to 10 minutes)
5. You now have a file called factoryfs.rfs on your internal sdcard
6. Hook it up to a computer and activate usb storage
7. copy factoryfs.rfs to whatever directory you want (home is recommended for simplicity)
8. Open up a terminal
9. cd to the directory of your file (if you placed it in home skip this step)
10. Type in "tar -H ustar -c factoryfs.rfs >packagename.tar"
11. Now you have a odin-flashable rom!
ADB users, simply run adb shell and type in the first command, then adb pull the file to the computer.
If you want to save space for a file sharing website (eg. mediafire, which has an upload cap of 200mb), simply Zip the file using 7-zip (set on ultra). You may have to do this on a windows machine.
Now this is even easier! simply flash the stock image in the link below with all the essentials included, and you can apply all the mods you want without having to ever go through dsidxa kitchen! Klin even fixed busybox for you! this way you can easily start from stock and work your way up to more advanced hacks.
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
The Advanced Users Guide: CWM packages.
Maybe you want more flexibility. Maybe you need to deodex your rom to mod some stock files, or zipalign to speed things up. This guide is for you people who need the more advanced options. It is harder, and you have a greater chance of messing things up, but you get to completely control your rom, even easily edit it on the computer! This guide is for advanced users only, or someone who is willing to spend a lot of time on trial and error.
Prerequisites:
ADB installed (Extremely helpful, and may to required)
Samsung device
Ubuntu/linux box
A bit of caution
Patience
1. Install Dsidxa Kitchen
2. Put your factoryfs.rfs in the necessary folder
3. cd to the directory you installed the kitchen
4. Type "sudo su"
5. enter your password
6. Type "chmod +x menu"
7. run "./menu"
8. you are now in the main menu of the kitchen.
9. There are many options, choode the one that you need!
Note: stay away from installing busybox using the kitchen. It installs a bad version of busybox which can make rom development a big headache for you!
10. There is a working folder in the kithcne directory, in there mod all the files you need.
11. When you are done, head into option 99 (create rom)
12. Run the interactive option
13.When you get to the update-script type, type "y" to install the newer type, which is required to flash a cwm zip in the Galaxy Player.
14. If you want to flash your rom using stock recovery, sign it. Else, leave it alone.
15. You can keep the normal name, or change it to what you want. If you are going to be flashing using stock recovery, make sure it is named "update.zip"
That is it! If you want to create a odin package out of it, simply flash the cwm zip, then follow the instructions above!
I will be adding on to this guide as time goes on, so make sure you ask pertinent questions below!
Resources/Additional Guides:
Install ADB:
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Install dsidxa kitchen:
http://forum.xda-developers.com/showthread.php?t=1303311
4.0 base (essentials installed, just apply your hacks and you are good to go! thanks klin):
http://forum.xda-developers.com/showthread.php?p=27973753#post27973753
Easy theming guide:
http://androidforums.com/optimus-m-...guide-theme-guide-noobs-adding-lots-more.html
APK multi-tool (needed to theme):
http://apkmultitool.com/?q=node/5
Recommended hosting sites:
www.mediafire.com
Good Rom practices:
1. If you retheme, include screenshots! people love screenshots.
2. Make a logo if you can, it makes it easy for people to support your rom by adding it into their signature.
3. If you mod, make sure you can easily explain it to someone if need be. Messy hacks are not good in the long run!
4. Focus evenly on all parts of your rom. Some people love speed, others love features. You can focus on one or the other but try and keep it balanced.
5. If you create a custom script/init,d script/documentable file make sure you include comments in your mod so people can try and fix it if need be!
6. Make sure all the bugs are ironed out before release. People love fast releases, but if it is really buggy they may switch to another rom.
7. if you have exhausted all other methods of fixing an issue, or cannot work on it a lot in the opcoming days/weeks, release a beta version stating the bugs clearly. That way while you are gone, more experienced people can help you iron out the bugs.
8.Make sure it is easy for the person to obtain your rom. If they have to download another utlity or click through 30 ads, they may just want to use another rom than go through the hassle. Worse, they may mess it up, forcing you to help them troubleshoot.
9. Make sure you update utilities on your rom as soon as an update becomes availible. That way you get the fewest bugs, and as I said before, users love updates!
10. Even if someone's issue seems isolated, at least spend some time with them figuring out what happened so they can fix it. You never know, it may be the harbinger of a HUGE outbreak of issues.
11. Base your rom on an intl version. There is a fortunate "bug" that klin discovered that allows US users to use any intl rom without their home button breaking. Of course, that has a lot of asterisks, but if you will look below, I have developed a fix for that issue, which allows anyone with a "broken" home button to use it with the problematic rom!
12. Practice good rom devving. If there is a major issue that could be a pain, don't take the easy way/fix out. That always comes back to bite you later, as I have figured out. I once had a corrupt journal on my system partition, and did not want to go through the hassle of recreating my rom on a clean partition. So, I simply added a flag to have /system mount as rw if there are any issues. Sure enough, about 3 days later, I started having some filesystem issues, and had to completely rebase, because I did not have any backups.
13. ALWAYS keep backups. Just do it. Not just one, either. Keep at least three days worth of backups, just in case there is an issue in backup 1 and two, but it not in no. 3. This would have been hugely helpful to me in many cases, but I didn't want to "waste" the space. Guess what I did a few days later: spent a nice evening with linux fully recreating my rom from scratch. Just do it.
Fix home button issues. (useful if you use a rom seperate than a flasher's region) (developed by me)
I have finally, after a bit of luck and some know-how, determined a fix for the home button issue! This will work on ALL roms, not just this one, and will probably work for the 5.0 as well. This also means you can fully wipe data if you want, and simply apply my fix.
1. Navigate to /dbdata/databases/com.android.providers.settings
2.Optionally copy to a computer (easier that way)
3.Open it up in a sqlite editor (if you are doing this on the device, copy it to /sdcard and and then copy it back
4.Navigate to the locale/first section (there should only be one string in there
5.It should look like en_US if you have a US player, or en_GB if you have a UK/intl player
6.Change the string to the language/locale you use (if you are INTL you can merely change it to xx_GB, where xx is your language. If you are US, just perform the same steps, but change the last part to US)
7. commit/save the file and copy it over the old one
8. Reboot, and your home button *should* be fixed!
NOTE: I have not personally tested this. It has a 99% change of working, but I have yet to completely verify it.
NOTE: after you replace the file, android may go a little haywire (wifi disconnects, forgets password, advanced reboot option unavailable, etc.). THIS IS OKAY. Simply reboot, and it will all be back. Do not change any settings after copying until it reboots, as it may possibly break the fix
NOTE: I cannot provide a downloadable file, as that file contains all of your system settings, and if you use mine, my settings will be applied, which could be pretty bad in some cases.
NOTE: this has no chance of bootlooping or bricking your device. At absolute worst, you have to set up a few settings/restore from a /dbdata backup. There is almost no risk involved.
Potential fixes for potential issues:
1.Bluetooth breaks. The main cause of this is if you install supercharger and nullify. Simply unullify and verify it is remove from build.prop, and you are good to go!
2. Home button breaks. (see above )
3. Root/busybox breaks. It's kinda messy, but if you absolutely HAVE to, simply reroot. That should fix it in a pinch. This is a classic case of keeping good backups. I have had to spend an entire afternoon redoing my entire rom because of my lack of recent backups. If you have the space, keep them. I have more than once managed to create a stopgap solution in my rom just to have some weird issue pop up again, and again. Just do it.
I LOVE you, man.!!
Hanthesolo,
Very good achievement, we all have to learn from your good sharing.
Congratulations man
rgds
I am really happy you guys like this! I will continue to add to it as time goes on, so expect even more content!
Sent from my EtherealPlayer.
New content up! also notice the link to the stock rom klin made so that you never need to go through a kitchen to get your rom started!
Has anyone used this yet? successes/failures? make sure you give me feedback so I can make this better!
Yet mre content up! Could this be possibly stickied? I know it's a little rough right now, but noone replies to this thread as there really is nothing to reply TO. I have worked hard on this and would hate to see this information go the way of the dead threads.
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
iAMsalm said:
Thanks for this info man, making roms for my old evo and just stacking up on guides and any kind of reading material that I can utilize for my advantage. So, this will be helpful lol. I'll be checking back every so often on anything new added, but thanks again bro. Thanks given! Feel Encouraged!! lol
Click to expand...
Click to collapse
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
hanthesolo said:
Glad you enjoy it, this forum is the abandoned, dusty wasteland of xda, so I wrote this guide to (hopefully) stimulate development a bit.
Click to expand...
Click to collapse
I know it definitely feels like that from time to time, but that's a byproduct of the nature of our devices. There's ridiculous money in selling someone a shiny new crippled phone with a horrific contract that will never get updated. You won't see a jawdropping ad on TV featuring a Galaxy Player because there's just no money in it. I'd love to have the T-Mobile girl holding my phone while wearing a pink leather riding suit(her, not me). That ain't happening.
I'm pleased and more than a little shocked that some new roms have come out in the past month thanks to this guide. I wanted a Android powered phone without the contract. I wanted an iPod Touch without all the bull**** that comes from being tied to Apple. Thanks to XDA my device fast, sexy as Hell, and does everything I want.
The only thing that makes me sad is that a year from now I probably won't be able to buy a Galaxy Player 4.0 v2 because there's just too much money to be made from contract only devices.
Thanks for this guide. It help me for begin android development.
GalaxySWifi4 said:
Thanks for this guide. It help me for begin android development.
Click to expand...
Click to collapse
I hope you have fun beginning development! It really is a lot of fun once you et past the basics.
Gswifi, I never replied to you, but your speech was so awesome, that I want to put it in the OP .
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
@hanthesolo
do you have some knowledge about kernel compiling, so you could hel me?
hanthesolo said:
If you want me to update the OP with an equivalent for ROM compiling (I know that I had a hard time figuring out just WHERE the folders to go, so we need a good guide...), chime in your support please!
Click to expand...
Click to collapse
please do
I understand early nothing about this advanced stuff of making ROMs, even more about make Kernels XD. But I want to experiment some little things to learn by myself step at step. But... I cannot start... I'm in CM10.1 with Koala's Kernel and I can't make the factoryfs.rfs file doing this: dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096 in Terminal Emulator because /dev/block/stl9 doesn't exists. With ADB I have the same error.
Is this due to this ROM is not stock or something like this? Or only I have to create this folder or change it by other...
---------- Post added at 02:55 AM ---------- Previous post was at 02:37 AM ----------
I'm trying to do this but without if=/dev/block/stl9. I don't know if I'm doing well...
How about some info on modifying or tweaking already compiled roms?
Say you want to remove some of the apps included with CoolDevXYZ's rom or modify some of the settings pre-install (e.g. build.prop tweaks, etc.). How do you tell the kernel these changes are intentional, not the result file corruption, infection or something?
Related
***UPDATE***
I am removing this tutorial from general public view. if you read the warnings/disclaimers and are still interested you will need to read the links below and go about it yourself.
--------------------------------------------------------------------------------------
first off credit for this idea go to all the people/sites linked below. IF credit is missing where due please notify me and i will resolve. This is just a gathering of other posts and steps that worked for me.
This will wipe your device. backup anything and everything before proceeding.
If you are not willing to take it upon yourself to research any problems that arrise and fix them yourself DO NOT ATTEMPT.
If you are unwilling to wipe your stock Firmware DO NOT ATTEMPT.
If you are unwilling to start with a fresh nookie color SDcard NO NOT ATTEMPT.
If you are unable to fix your problems or want to revert to stock you can do so following the link at the bottom of the page
This is for advanced users. Make sure you read and reread everything before attempting anything! I take no responsibility and offer no promise of support if you make yourself a $250 B&N brand paperweight. keep in mind the nc is hard to brick (know from experience) but anything can happen, so be warned and proceed with caution.
if something below is not clear visit the links provided and look for your answers there. they are there and the more you read and learn the more sense this will make. if you are still unable to find help post here and i will try to get you going.
now on to the good stuff. I just wanted to gather the various posts and links that i used to gt a fully working froyo running on my nc from the internal memory (emmc) and present them in a step by step guide for others wanting to run NF from their internal memory and have no need for B&N stock. Flash is working if you install the proper apk. this is not installed out of the box. After installing to your EMMC you will be able to use any sdcard as you normally would in android. I am using a 16gb card with no problems.
***steps removed... see top of post***
helpful links:
http://forum.xda-developers.com/showpost.php?p=10254900&postcount=138
http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
nookdevs steps for creating nookie froyo sdcard:
http://nookdevs.com/Nookie_FroYo:_Burning_a_bootable_SD_card
nookie froyo thread:
http://forum.xda-developers.com/showthread.php?t=883175
nookdevs nookie froyo tips:
http://nookdevs.com/NookColor:_Nookie_Froyo_Tips
wipe nc to stock: (download the images and run the commands from an adb shell.)
http://forum.xda-developers.com/showthread.php?t=919353
Flash back to clean stock ROM (nook devs) http://nookdevs.com/Flash_back_to_clean_stock_ROM
1. first you will want a fresh NF sd card. I tried to use my seasoned nf card and ended with a brick... if you have google apps installed you will not be able to get past the android screen and will have to reimage as stated above. create your fresh nf sdcard following the steps at nookdevs here
Click to expand...
Click to collapse
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
samuelhalff said:
As we say in french, you must call a cat a cat. Your NC wasn't bricked at all. You simply needed to touch each corner of the screen one at a time when on "touch the android" screen, starting with the top left corner, then clockwise.
Would have saved you some time
If I were you (if I may..), I'd put all the links the bottom of the post. Would make reading easier. As for my code to copy sdcard content, go on and post it directly. Opening multiple pages only makes things more complicated. No problem. As for the Volume keys and gapps, it could be ambiguous, those add-ins aren't required at all. Simple leave a link to nookie tips on nook devs for those who want it?
But of course, this is your post..
Sam
Click to expand...
Click to collapse
I tried the touching four corners. no go. several roms required that back when i was using a D1... I couldnt for the life of me figure it out so just scrapped and started from scratch.
thanks for your input. i planned to clean this up a bit, was just in a rush writing the original. Thanks again for your help. couldnt have gotten this far without your steps to start off.
Eager to try this out ... but will it be able to see a non-NF SD card I enter in? Will it recognize it, and let me see it as mass storage when the Nook is plugged into my PC?
Very well written, just copy and paste the code into the console for the most part ... Runs nice and fast, I have a few FC's to clean up but that is due to me not factory resetting the NC prior to doing this as I am an impatient person! I must say it is very nice not to have the B&N notification bar at the bottom of the screen.
So if this is really 2.2, does it have flash?
theyownus said:
I used 0.5.9 and replaced the vold file with the one from 0.5.8 making sure to maintain executable permissions.
Click to expand...
Click to collapse
a) What vold file? Searching for "0.5.8 vold" on this board produces no hits.
b) Executable permissions on what? This "vold" file or something else?
Don't want to be "that guy" but date should read 1/20/2011.
Thanks gonna give this a shot.
What happens to the Media partition?
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
starkruzr said:
Also, slightly random: Why doesn't adb ever seem to work over USB with my Nook Color? 2.1 ROM, Nookie Froyo on SD 0.5.8 or 0.5.9, it never sees a device. By contrast, it works fine on my G2.
Click to expand...
Click to collapse
Re-run ADB configuration. Make sure id is 0x2080.
How do we fix the SD card error. I am unable to do anything with the SD card.
samuelhalff said:
Re-run ADB configuration. Make sure id is 0x2080.
Click to expand...
Click to collapse
Wow. This is INSANELY important and this is the first time I've ever seen mention of it. Every other post simply assumes your ADB "just works." I have been endlessly frustrated by the lack of working ADB on this thing such that every time I do something with my NC I have to find a way to first install ADBWireless.
http://fineoils.blogspot.com/2010/11/pokey9000-has-got-self-booting-image.html
The instructions to get it working are in here, folks. Can these instructions be put in a sticky somewhere? This is about the least-obvious thing I can think of.
Is there any improvement in speed and reliability running this from the emmc as opposed to a class 6 uSD?
"extract them to their respective folders"
Nothin but bootloop
theyownus said:
first off credit for this idea go to samuelhalff
links:
original steps from samuelhalff http://forum.xda-developers.com/showpost.php?p=10747294&postcount=2
Click to expand...
Click to collapse
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
[Replace the files in /system]
It would also be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
fattire said:
What a great idea. If only someone had talked about this weeks ago... Anyway now that it seems people are going to be trashing their nooks trying to do this, it's probably simpler for one to just boot into SD and...
Somewhere in there it would be a good idea to clear out /data and /cache or there will likely be bootloops when froyo boots with the old data stuff still around.
That's off the top of my head and totally untested. Seriously. It probably doesn't work, and is totally unrecommended. Anyone who types "rm -rf *" in their emmc system is saying goodbye to their stock OS and will have to live with their decision. All GPL disclaimers apply.
Note also that IOMonster has a nice bootable clockwork SDcard that does all kinds of things, and automating this type of migration is only a matter of time now.
Update: Actually the steps aren't THAT different. /just sayin'.
Click to expand...
Click to collapse
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most of the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
Please know that my original post recomanded doing dd's of all partition. That way reverting back to stock was easy. My post also mentionned emptying data.....
What do mean steps aren't that different?
Sent from my HTC Desire using XDA App
samuelhalff said:
I had the same reaction reading the post. Not only is it unfair to you, because I have read your post before attempting anything, but it's also unfair to me because it suggest that he did most the practical work..
Anyway does it really matter? People who don't regularly read the forum often don't give a Jack of who's responsible for what. Those who do willl know you were first in line. Anyway, I understand your frustration I should have said something. I was just fed up. Sorry.
What do mean steps aren't that different?
Click to expand...
Click to collapse
Ah, I just mean it's all the same idea-- out with the old, in with the new. Nothing particularly genius about it. In any event, it's not really a matter of credit. We all stand on the shoulders of giants. I was just amused is all... so let's just have fun, eat, drink, be merry, and dance in the rain.
It may turnout that English isn't the OP's native language. Although it isn't mine either..
Nothing really seems genius once you get to understanding it.. but as a newcomer, I still had a bit of trouble getting the sdcard to mount..
Sent from my HTC Desire using XDA App
So I've been doing this android flashing business a long time
And I've got a real mess on my hands. I'll be ****ing with this for the rest of the night! Thanks!
[Guide][Windows][UPDATED 12/31/11] Use SVN to download Synergy & Other ROM Nightlies
Ignore this quoted section if you are reading this guide for the first time. Start at the blue "New SVN Users" line.
List of SVN Checkout Links for ROMs that are developed with SVN:
Do NOT edit the URL in any way. Copy it exactly as it is shown.
Attention All Eternity/Airborne/Synergy SVN Users:
As of 11/29, Eternity and Synergy SVN access is restricted. Virus has stated his reasons here and here. Please do not ask him for a username or password, you will not get one.
To quickly check to see if he has lifted the restriction on SVN, all you have to do is to open the trunk links below in your browser. If it shows you a list of files, Virus has enabled it again. If it asks for a password, it's still locked down. It's much easier to check that way than to SVN Update every so often.
All other SVN Trunks are currently open.
Click to expand...
Click to collapse
Ice Cream Sandwich (AOSP 4.0.1)
Code:
http://android-ics-evo-3d.googlecode.com/svn/trunk/
Prime XL 3D (Sense 3.5)
Code:
http://warm-twopointthree-base-with-sense-three-dot-five.googlecode.com/svn/trunk
Nuggy's Unlimited Evo3D (Sense 3.0)
Code:
https://nuggys-unlimited-evo3d.googlecode.com/svn/trunk/
Synergy Evo 3D (Sense 3.0):
Code:
[Strike]http://synergy-evo3d.googlecode.com/svn/trunk[/Strike]
InfectedROM Eternity (Sense 3.0)
Code:
[Strike]http://infectedrom-eternity-3d.googlecode.com/svn/trunk/[/Strike]
Myn's WarmTwoPointThree (Sense 3.0)
Code:
http://warm-twopointthree-base.googlecode.com/svn/trunk
Airborne 3D:
Code:
http://virusrom-airborne3d.googlecode.com/svn/trunk
Kingdom 3D:
Code:
http://synergy-kingdom-3d.googlecode.com/svn/trunk
XRON 357 Six-Shooter
Code:
http://xron-shooter-357.googlecode.com/svn/trunk/
ROM Developers, if you'd like your ROM to be featured here for easy reference, please PM me your SVN checkout link.
Click to expand...
Click to collapse
New SVN Users, start reading from here!
As promised, I'm posting this graphical guide up for those who wish to use SVN in order to obtain nightly builds of ROMs and all other items that utilize SVN for distribution. As always, my guides are meant for the completely clueless, and come with screenshots for help
First of all. Let's start with the big question.
What is SVN, and why do I care?
SVN is actually not an acronym for anything. "SVN" is the command line phrase that triggers a system called "Subversion", but no one wants to type out Subversion every time they want to refer to svn . Long story short, it allows for simple distribution of computer software/ROMs/etc with methodical updating that can be rolled back at any time. It may sound intimidating, but I'll be making it quite easy for you to understand, and ultimately, you'll find it quite useful. Don't get intimidated or freaked out. A few days ago, I had never used SVN either, but now it's a piece of cake!
Well, uh, that sounds interesting, but seriously, why do I care?
Well, you should. Let's take our Sense-based ROMs, for instance. They're all roughly 300+ MB (maybe less for the Sense-stripped ROMs).
Doesn't it suck to have to download a new 300+MB zip file each time there's a small fix that you really want to get to?
What if I told you, that using SVN, you only have to download the select files that the ROM devs have updated, which tends to be a fraction of the size, rather than download a full massive zip of the ROM each time? That instead of downloading 300 MB, you'd only have to download 30 to get a bunch of fixes and updates? What if I also told you that you can revert changes which broke your previous setup with ease? Sounds good? Great! Let's get started!
Stuff You'll Be Needing
Tortoise SVN (Free and Open Source)
WinRAR (7zip will work just fine as well)
A Windows PC (XP or higher)
An SVN Link Checkout Link*
A few minutes of time, and a relaxed mind
*What is this? An SVN checkout link is the link that your ROM dev or software author will provide you. It tells Tortoise SVN where to get all those yummy files. For the sake of our example, we will be using the Synergy ROM, which is developed using Google Code. Google Code provides automatic SVN links for those who know how to use it. Read on to understand more.
BOLDED Text - These are folder locations.
Red Underlined/Bolded Text - These are hyperlinks.
Blue Bolded Text - These are bonus tidbits that may or may not appeal to you.
Step 1: Install Tortoise SVN
This is pretty straight-forward, simply download the correct installer for your PC (32 or 64).
Step 2: Create the proper folder structure
So then, you don't HAVE to do it this way, but this is how I do it, and will keep your organized.
Start by making a folder called Evo 3D, anywhere on your computer. (I keep mine inside my My Documents Folder).
Inside it, create two more folders. Because the ROM we are downloading for our example is Synergy, we will title it synergy-evo3d and the other one Current. You may change the title of the first folder accordingly based on what ROM you're downloading it. It doesn't matter what you call it, as long as you know what it is. In the screenshots of this post, all screenshots show the folder titled synergy-evo3d, so if you're downloading a different ROM, mentally replace that name with the name of your ROM in each screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3: Start Downloading!
Now that we have our folders set up, let's be clear about which folder is for what. The synergy-evo3d folder is meant as your "cooking pot". You will update your ROM and revert your ROM from there, much in the same way you'd add more and more spices and ingredients to your cooking pot.
Once you have updated or reverted the ROM, you then will export that updated content into your Current folder, which will end up being the zip you flash to your phone. If this doesn't make sense right now, fear not. I'll explain when we get to that step and why we do it this way.
So let's start the downloading process, because this will take some time.
Part 1: Download
Right-click on the synergy-evo3d folder.
Click on SVN Checkout. The following dialog will pop up.
Now, we need the link of the repository. The developer of your ROM/software will provide this for you, you simply need to ask, or look below for a list of SVN Checkout links for SVN-based ROMs.
If you are downloading Synergy ROM, we can find it at their Google Code site here. If you are NOT downloading Synergy ROM, please see the top of this post for the most recently updated list of trunk links.
When you're on that page, select ONLY the shown part of the URL:
We don't want the "svn checkout" part or the "synergy-evo3d-read-only" part. Also, we don't want the last "/" in the URL either.
Remember, if you're not downloading Synergy, look at the top of this post for all recently updated SVN trunk links!
Paste the link of your ROM of choice back into our Tortoise SVN window, and press "OK".
Now begins the downloading process. It will download the proper folder structure. Just sit back, and let it do it's thing. It can take anywhere from 5-10 minutes to an hour and a half, depending on your internet connection. If you have a slower connection, don't worry. Bite the bullet once with this, and then you'll see the beauty of SVN.
Once it finishes, we're left with the completed folder! You'll notice there's now a green checkmark on it, signifying that it's our SVN folder and it has been properly synced:
If we open this folder, we see the following:
Congrats! We synced it properly. Now, here's the thing. Each one of those folders you see contain a hidden .svn folder, which Tortoise SVN uses to keep track of the version numbers whatnot. Therefore, if you zipped up all the files you see right now, you'd have a massive ZIP file full of unneeded files, and it might also malfunction/not flash on your device. This is where we use the "Export" command.
Part 2: Export, Zip, and Flash!
So, to ensure we don't copy any of the .svn folders that are unneeded for our ROM zip, we will use the Export command. This is where we will use the Current folder we created earlier.
Start by right-clicking synergy-evo3d, go to Tortoise SVN, and find "Export".
This dialog will pop up, asking you where to export. Navigate to our EVO 3D folder, and then click on our Current folder.
Click OK. It will begin exporting:
Once it is finished, it will create a synergy-evo3d folder inside the Current folder. If you see green checkmarks on any of these items, you're looking in the wrong location. You need to be looking at EVO 3D/Current/synergy-evo3d
Open it up, and voila! There's our ROM package!
BONUS: From this point on, you can customize the ROM before we zip it up. Stuff in the system/app folder you want to remove? Go on, get rid of it now! Or perhaps you want to add in your own Ringtones now? Do it
Once you've made any personal changes you want (or none, if you want to just flash it as is), highlight all of the files, and click "Add to archive".
This window appears. You've probably seen it before if you've ever zipped anything up.
First and foremost, make sure you select the format to be "zip" and not the default "rar".
Then, pick your level of compression. The idea is simple. if you go as simple as "Store", your file will zip up in seconds, but the finishing zip will be large (in my case, roughly 550MB). If you choose to take the "Best" compression level, it will takea few more minutes (depending on your computer) and can be as small as 330 MB. (That's of course approximate, different people may have different sizes depending on what they remove or don't remove).
Finally, name it what you want, and click OK!
When that's all done? Take the zip, put it on your phone's SD card, and flash that thing. Enjoy!
But wait, Liquid, you said we could update without downloading each time!
Yes, I did. That will be the next post, scroll down!
Part 3: Updating Incrementally
So then, now that we've gone through all that trouble, we've just discovered that Virus, TrevE and Ziggy, being the crazy developers they are, just added 10 or 15 more changes which you saw here. ASDJKHA SLDFKJHS DLKJFHSD KL CURSES!!!!
But this is the fun of SVN Read on.
Go back to your EVO 3D folder. Right click on your synergy-evo3d folder.
Click on it, and it will update ONLY what Virus/TrevE/Ziggy changed. If they removed a file, Tortoise SVN will remove it. If they added a file, Tortoise SVN will add it. And of course, if they edit a file, Tortoise SVN will update that file. When it completes, you'll be told what revision it is at. It may take a few minutes, just be patient
You'll notice it only downloaded about 26 MB, and has placed/overwritten/removed all files accordingly. It also states that I am now properly at Revision # 259.
BONUS: Want to see what was updated and why it was updated? Simply click "Show Log" to get to THIS window:
[*]
[*]You'll be able to see all the revisions made since your last update, and you can go farther back in time if you'd like. If you're the kind of guy who presses "Show Details" when installing applications on Windows, play around with this window, you'll find much that is interesting
Once it finishes, press OK. Go back to EVO 3D/Current/synergy-evo3d. Ensure it's not your SVN folder by making sure you see no green checkmarks on any of the folders or files. Once you have made sure of this, delete the synergy-evo3d folder completely.
If your previous ROM zip is still in there, either delete it too or move it somewhere else. This is to make space/room for the fresh Export we are about to do.
Return to our main EVO 3D folder. Right click, and then export to the Current folder, just like we did the first time. Once it finishes, again, zip it up, just like we did the first time. If you forgot this step, or want to make sure you're doing it right, scroll up to "Part 2: Export, Zip, and Flash!" in post #1.
And that's it! A hell of a lot easier than downloading the ROM over and over, eh? Keep reading, the fun isn't over yet.
Part 4: Reverting To Previous Builds
So then. This is the nature of the beast known as the "nightly" build. A revision has gone in and borked your setup. Maybe it's killed off your battery life, maybe it changed something visual you don't like, maybe it removed an app that you preferred to have in the ROM. Your reasons may vary, but it doesn't matter. You can revert to a working version very easily.
Heads up! This can get a bit hairy depending on what you want to do. There's recommended strategies, and then there's things I wouldn't recommend. Read on to learn more.
Alright then, let's begin.
Remember that "Show Log" button we hit earlier when upgrading? We want to go back there now. Right click on your SVN folder, and click on "Show Log".
Then, this window will pop up. It's a catalog of all the changes made. You can control by many different factors. Let's start by finding the timeframe of the revision you want to go back to. Then, from there, you'll notice there's a search box.
So there's two scenarios here.
One, you already know what build number you want to revert to, in which case, scroll down until you find the right revisions.
Two, you're not entirely sure what revision you want, but you remember the changelog comment. For instance, let's say I'm having issues with the kernel. To see all the changelog comments that contain the word "kernel", I type "kernel" into the search box and press Enter:
Or we could go even more detailed.
Let's say you're a Themer, and you're trying to find a certain framework-res.apk that was modified at some point to ensure your theme still works or to redo your theme.
Simple! We just type "framework-res.apk" into the searchbox, and we press enter.
As you can see, it is showing me every single change that modified the file "framework-res.apk".
For the sake of keeping it simple for this guide, I theoretically want to find all changes related to the "overscroll" effect. So I type it in, pick the revision I want, and then I right click it.
~~~ STOP.~~~
This is where you need to stop and think about what you're doing. As you can see, you have two options in the screenshot above. You can revert to that revision, or you can revert changes from that revision. There is a HUGE difference between the two, and there is a list of things you need to remember before you pick which one to do.
Use Revert To Revision (Recommended)
This will revert ALL changes since the revision you clicked on. If you are on Revision 296 and want to revert to Revision 260, ALL revisions between 261 and 296 will be reversed. If something was added, it will be deleted. Modified files will be restored to what they were in 260. Removed files will be readded to where they were as of build 260.
Use this Option ONLY if:
The latest revision has wrecked a key part of your phone, such as the mobile network, the 4G, the battery, MMS, etc etc, and you need said functions working asap.
You want to revert to a revision that you feel simply worked better, and you will stick with that revision until the changelog reflects that your complaints have been addressed.
It's simply a temporary deal while you wait out the process of more fixes being added.
Use Revert Changes From Revision (Not Recommended)
This will revert a SINGLE revision's changes only. For instance, if you are on revision 290, and there was a change in Revision 260 you liked better than the one in 290, it will only take that single change from 260 and "inject" it into your current 290 build. If this sounds too complicated to you, DO NOT DO IT. Read the NOTE at the end of this section to understand why.
Use this Option ONLY if:
You are an advanced developer, and you're interested in figuring out what changes Team Synergy made to what, and how it affects the items around it.
You are a ROM themer, and you need access to previous files to troubleshoot your theme as you upgrade it.
You are an advanced user and you are trying to troubleshoot how one file that Team Synergy changed is affecting your programs/development/mods etc.
~~~Continue.~~~
Decide which one suits you (most likely the first option), and click Yes when it asks you to confirm. It will finish reverting the changes (it calls this "reverse-merging")
Once it completes, follow the steps to Re-Export, and Flash!
NOTE:
Using SVN Revert is a tricky thing. For now, as far as what I've guided you to know, SVN is only a TEMPORARY solution. And it can also be a problematic one. Why? Because you'll still want to update to a new build, right? No matter which option you chose above, using SVN update will overwrite any revisions Reverts that you have done before. This will get to be a problem if you try to keep reverting back to a version you prefer. The more and more you cherry-pick which changes you want to keep, the more and more unstable you may make the ROM. You might also miss out on new features; say that the ROM's framework-res.apk was updated with some new features as of revision 290, but you're still using the framework-res.apk from build 260. You won't be able to get any of those new features. It gets worse when you get to System files. What if you chose to keep a reverted apk, and in a new build, it gets overwritten? If you keep your old apk, and newer builds have dependencies on that apk, you'll run into errors, because the system will not find the apk it's looking for, it will find your old one.
Essentially, the best place to get ROM fixes is straight from the Devs. Use SVN Revert ONLY as a temporary solution until they fix it!
There's plenty more coming, but I'm tired of this thread again, stay tuned. I'll add some more helpful tips later on
Well guys, that's it for the guide for now. As always, I do my best to make sure you have the easiest and clearest guides to go by, because XDA is about the more knowledgeable spreading their knowledge to the less. Enjoy, and most importantly, spread what you learned here to other people that use SVN. They may not be using SVN for ROMs, but the guide is more or less the same as long as they have their own SVN link.
AWESOME right up brosif thanks
Virus said:
AWESOME right up brosif thanks
Click to expand...
Click to collapse
Part 3 be coming up with instructions on how to update
Forgive my cajun redneck lingo but --- Don't that pretty right there? LOL!!!
Added the "Updating Incrementally" section. Let me know if you guys have questions.
Nice guide, this should stop people from fumbling around with it like I did at first lol
Eh, added in the updater windows just for the hell of it, at least people can see now that I only downloaded 26 MB and am now up to the latest version of the ROM
Updated yet one more time to show the "Log" window.
Dude this needs a Sticky. If this works right it will almost be a slipstream for Roms. WOW!!!!!!
great guide man!! I havent tried these nightlies yet but this SVN seems pretty dam cool.. setting it up now.
Alright, I think I've made my last OCD changes for the night, let me know if there's any questions you have or issues/typos with the guide.
Enjoy guys
fsuwade said:
Dude this needs a Sticky. If this works right it will almost be a slipstream for Roms. WOW!!!!!!
Click to expand...
Click to collapse
Not only that but it allows for more end user input and gets them more involved with the ROM building in general. Kinda fun stuff for sure and should become standard because everything is out in the open as far as changes and the direction the ROM is taking. I likes it...
I genuinely hope more Devs take to Google Code and set up SVN this way. It'll save like hell on bandwidth and time.
thanks for this man, great work it was really needed- just didnt have time to put more than a few sentences together. Hope you guys all enjoy svn as much as we do - one of the big percs of being on an open OS is being open, i personally love letting everyone see what were doing. Its how I learned by tampering and looking at what does what, hopefully everyone gains knowledge and can help give this phone the jets it deserves
TrevE said:
thanks for this man, great work it was really needed- just didnt have time to put more than a few sentences together. Hope you guys all enjoy svn as much as we do - one of the big percs of being on an open OS is being open, i personally love letting everyone see what were doing. Its how I learned by tampering and looking at what does what, hopefully everyone gains knowledge and can help give this phone the jets it deserves
Click to expand...
Click to collapse
Of course! I might not be able to build the ROM like you do, but I sure as hell can help people get it quicker and far more instantly . You should have an increased amount of feedback now, with quicker and more complete bug reports since more users will be able to try it out.
the only part you may want to add is running SVN clean once and awhile on the main folder. that will keep those .svn hidden folder size at bay and fix things if it ever reports a lock or tree conflict (shouldnt really on RO copies of repo)
Thanks
Great guide. One quick question. Do I have to wipe data or just cache and dalvak for synergy rom doing this update methods? THanks
TrevE said:
the only part you may want to add is running SVN clean once and awhile on the main folder. that will keep those .svn hidden folder size at bay and fix things if it ever reports a lock or tree conflict (shouldnt really on RO copies of repo)
Click to expand...
Click to collapse
That's what I was about to say, it shouldn't really need cleaning for read-only. Nonetheless, I'll add it into a FAQ tomorrow, I'm kind of done looking at this thread now, I've been on it for like 2 hours
LiquidSolstice said:
That's what I was about to say, it shouldn't really need cleaning for read-only. Nonetheless, I'll add it into a FAQ tomorrow, I'm kind of done looking at this thread now, I've been on it for like 2 hours
Click to expand...
Click to collapse
haha im sure man. for tomorrrorw theres more infoo here -
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-cleanup.html
if it ever times out updating or something you really should run it, it also speeds things up. i run it all the time
I am new to Android and am attempting to experiment a bit with my brand new sgs2. This is my 3rd Android phone. I have a basic understanding of the modifcations that can be done to the OS to make it more efficient, but don't quite understand all the little details. I have already done research, I just need someone to put it into laymans terms.
Deodexing
I understand that deodexing is an almost necessary part of any custom rom. I have found scripts that will deodex the firmware for me. I see that you can deodex the filesystem and 'framework' of the OS. What else can be deodex'ed? I see that a lot of roms boast FULLY deodex'ed. What does that entail? How would I use these scripts to make my stock rom 'fully' deodex'ed. Also, from the information I have read, deodexing makes the APK actually bigger AND run less efficient. This would actually slow the OS down wouldn't it? I guess my question is, what is the actual benefit of deodexing?
Rooting
From what I understand about this device. All we have to do is flash SU 3.0 and that will root the decvice. And the only way to flash SU 3.0 is with CWM. Is this accurate? I also understand that to get CWM on the phone we need to flash it in download mode, which essentially replaces the stock recovery option. Is all of this accurate? If so, can someone point me to a thread where it will give me the proper CWM and instructions of how to flash it? I have done this on my tab 10.1 so I assume it would be very similar.
Custom power menu
Now something like this is an actual customization of the OS. What I want to know is if the power menu is just simply modified to show the additional features (reboot, recovery...) or if a whole new image has to be created to replace the stock power menu. Also, would there be any way I could take a custom power menu from another rom and insert it into my own or would I have to have one made specifically for the device?
Zipping up a ROM
Last question I promise I have a buddy who knows nothing about electronics. He wants to have the benefits of a modded rom that is slightly faster but is terrified of digging into the device because he thinks he will brick it. I was thinking about helping him but the only thing I can think of is to mod my device and create a nandroid backup of my own device and then restore it on his. Thats all I would be capable of without some guideance. How hard would it be to take my own modded rom and make it into a flashable zip rather than me try to restore a huge nandroid?
I was thinking about posing these questions directly to one of my favorite dev's via PM, but they have a lot on their plates and I didn't want to bug them. I feel like everyone in this forum is more knowledgeable than I am and there would be plenty of people willing to lend some info. Anyways thanks in advance.
Deodexing - This is something I've never done before, so I'm not familiar with the details, but the basics are: Deodexing will cause a small penalty in startup and boot times, but it makes theming and modifications MUCH easier. Theming/modding odexed ROMs is a massive pain in the ass as I understand it.
Rooting - Multiple ways to do this, I suggest reading jivy26's FAQ.
Custom power menu - I think only small parts of the framework need modding here (SystemUI.apk maybe?), and these modded parts could be flashed in CWM. However it's not something I've done before, nor do I know how to do it. Android userland is still black voodoo magic to me. I'll stay in the bowels of the system thank you very much.
Making CWM-flashable zips - also not something I can easily provide advice on. There are tutorials floating around.
Risk of bricking - as long as you don't flash bootloaders it's next to impossible to hardbrick a Samsung android device.
So essentially if Im looking to have the snappiest Rom possible which retains all of the functions and visuals of TouchWiz (no themeing or modding necessary) I would want to actually AVOID deodexing my system?
So what does that leave me with to speed up my stock Rom? OC, ram tweaks, and zip aligning?
Sent from my SAMSUNG-SGH-I777 using XDA App
MOD EDIT : As requested by OP, I'm closing this thread.
Everyone can continue the rooting related discussions on the other thread linked here. Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!].
All,
Here is a "one click" script to root your Nook Tablet AND install gapps (Market) all in one shot. It also includes the latest superuser binary and apk (automatically installed). MAD PROPS to Indirect for being the first to get root on the NT. This script builds off of his (and others) work to make it a bit easier.
I need people to test this. That being said, RUN THIS AT YOUR OWN RISK. It may work perfectly, or it may explode your Nook. You've been warned!
1. Download and extract the zip file located at https://rapidshare.com/files/3156164791/NT-One-Click-Root-by-anlog.zip (PLEASE MIRROR THE FILE FOR ME SO YOU DON'T KILL MY DROPBOX ACCOUNT).
2. Factory reset your Nook Tablet (just do it).
3. Run Windows 7 (32-bit or 64-bit). Sorry Mac and Linux, but that's not my arena.
4. Enable USB debugging and sideloading on your Nook (download an APK and try to install it with package manager. Hit settings and set the options). YOU MUST uncheck "auto mount USB" or debugging won't activate. There are also two checkboxes for debugging and staying awake - make sure both are set. DO NOT REBOOT your Nook once you enable these settings.
5. Plug in your Nook and point Windows to search for the drivers in the usb_drivers directory from the etracted file. The driver has been modified to work with the Nook Tablet and you don't need to mess with any adb.ini stuff. It's ready to go.
6. Once the driver loads, make sure you have a device called "ADB Composite Device" (or something similar) in Device Manager. As long as you don't have an item called "Nook Tablet" with an exclamation point, you're good. Once you are plugged in, check the status bar on your Nook and make sure USB debugging is enabled (there will be a little robot indicator).
7. This step is optional, since it is run at the beginning of the script, but you can open a command prompt AS ADMINISTRATOR and go to the folder where you extracted your files and run "adb devices". It should list your Nook serial number. If it doesn't, start over.
8. Run a command prompt as Administrator and then run the NookTabRoot.bat file to root your tablet and install gapps. Your tablet will automatically restart once the script finishes.
This script is ALPHA and probably won't work, but that's why I need people to test. If anyone finds a way to make it better, please feel free to modify it (as long as you credit me and Indirect).
Good luck!
MIRROR 1 - http://dl.dropbox.com/u/7364988/NT-One-Click-Root-by-anlog.zip
Thanks a lot, this is going to be quite helpful.
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Indirect said:
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Click to expand...
Click to collapse
Your root method is not easy enough for the average user, which is why I've posted this.
I'm not removing anything. It's up to the community to decide if they want to try my script or not. I will host it and setup my own mirrors if I have to.
conundrum768 said:
Thanks a lot, this is going to be quite helpful.
[Mirror removed in light of Indirect's post below]
Click to expand...
Click to collapse
Sorry to see you cave in so easily...
I'm not being disrespectful but my script really isn't too complicated. I was working on rewriting the thread anyway I just haven't gotten the time yet until now. I've been out all day.
This early in the process, it is great having multiple ways to achieve root.
Can't you each add a disclaimer in your package "If you use this method to root, don't use any other method without doing a full factory reset first" or whatever words would be appropriate?
Mostly - don't get ticked at each other.
It's not a multiple way, it's verbatim my script with his added to it.
This is not a glory or recognition thing. This is something that I think will greatly help the community of average users with little to no experience with things like ADB or Unix commands.
Many every day users are discovering XDA and it can be very difficult for them to navigate through the forums and find what they are looking for. My goal is to make it really easy.
The script will not blow up your Nook. The worst thing that can happen is that it just doesn't work.
Not sure what else to say, but this "only one user is allowed to help people root" nonsense doesn't work for me, nor the rest of the community. Sorry Indirect. If it helps, I've credited you at the beginning of my script.
OK - then I would say don't include an early version of a root script except by reference... Let the original author handle the bugs and enhancements.
I dont see a problem with useing each others method as long as the appropriate credit is given when you use someone else's work in your own.
Indirect said:
It's not a multiple way, it's verbatim my script with his added to it.
Click to expand...
Click to collapse
You mean your script with a bunch of STANDARD adb commands in it? Not exactly rocket science. Did you write zergrush? No, but you used it (and credited them accordingly).
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Indirect said:
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Click to expand...
Click to collapse
YOUR SCRIPT IS A BUNCH OF STANDARD ADB COMMANDS. That means that 100% of all other ADB scripts out there use elements from the script you pieced together from other scripts.
Get over it. You obivously only care about recognition. My only goal is to help other people.
anlog, you have clearly not seen any of my other work. I'm not in it for recognition, I need to know if something goes wrong at all and if so, what caused it. That's it.
Indirect said:
I'm not in it for recognition
Click to expand...
Click to collapse
Then stop telling people to remove their work and instead write a better/faster/easier version.
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
okay, so not to get in the middle of anything, I will say I've successfully rooted my nook tablet with the original method. didn't have any luck installing the android market (and getting it running).
as such, I've done a factory restore and have downloaded the script here.
as someone who is fairly computer literate, but is VERY new to rooting (short of 1 click root), I will take the shortest path possible. no loss of credit to indirect. please guys, all your work is recognized.
will report back shortly.
Indirect said:
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
Click to expand...
Click to collapse
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
anlog said:
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
Click to expand...
Click to collapse
Sorry for getting annoyed and worked up but I already had to play "Dueling Batch Scripts" in the evo shift section when mine was CLEARLY superior to the other ones by far because I was still developing it. :| So again, my apologies for losing my head but don't wait too long for my REAL script to be thrown together sometime tonight and blow yours out of the water.
Hey guys.
So in the last couple months I ported the encore u-boot menu/console/configuration stuff over to acclaim (Nook Tablet). The acclaim really needed the menu plus had a ton of "2nd bootloader" issues that needed to be addressed to fix the locked bootloader bug. On nemith's suggestion, the u-boot really isn't just for cm7/9 (it can be used with any OS), so I called the newer bootloader, "CyanoBoot". Kind of a working title until I think of something better.
In the process of the acclaim port, the UI menuing interface was rewritten and some small features were added.
Anyhoo... Last night on a whim I decided to port the improvements back to encore's u-boot. So there's a version now for encore as well so that NC can enjoy the UI benefits.
It's similar to the acclaim version, minus fastboot (which we don't need, since encore doesn't use dedicated boot and recovery partitions) and minus a 'clear bootcount' setting since, well, development is up to speed w/NC that such a feature seems not necessary.
That said, here's the new stuff:
new exciting splash
Indicator in top left. "E" means u-boot is loading from emmc. "S" means it's loading from Sdcard.
Additionally you can now see the system's "boot count" - the number after the indicator described above. If this count goes up, your boot count is not being cleared as it should be.
Instruction to "hold down "n" for menu"
boot menu is way easier to use, clearer, and uncluttered.
all the old stuff is there (Nook Color Tweaks' boot settings), combo keys, etc.
If you feel bold and are willing to risk everything, give it a try and let me know if you run into issues. Think of this as an alpha. If people like it, I'll push it to the repo as the default.
To install: It's just "u-boot.bin", and it goes in the first partition of your SD or EMMC. Make sure you have a good backup in case things screw up.
NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.
Aside from thanks mentioned in the acclaim thread, I want to add thanks to hacdan and racks for testing for me on emmc and sd.
Seriously though, as opposed to the acclaim version that was in development for weeks, this has been tested for like an hour. On the other hand I actually have a device to try it.
Update March 28, 2012
So thanks to some hard work from tonsofquestions, we've got a new version with some very cool improvements!!!
New Stuff
* The UI now dims out any option in the menu that isn't available
* some nice code refactoring that I was too lazy to do
* the "altboot" button combo (up and down volume keys) will now choose regular boot if altboot is set as default (and vice versa)
* You can now enable a previously "hidden" menu option (plus a second configuration menu) by doing the following commands:
adb shell echo "0" > /rom/u-boot.altboot
adb shell echo "0" > /rom/u-boot.device
This unlocks a "built-in" default menu, effectively doing the same thing as the Tablet Tweaks build options, only right from u-boot itself!
Please test from various configurations (emmc/sdcard/normalboot/altboot/etc/etc)... I haven't tested this one as thoroughly.. or really thoroughly at all. And thanks to tonsofquestions for the contribution!
updates:
9/20/12: Two minor fixes...
9/19/12: Moved to a new repository at nookiedevs.
3/28/12: New features from tonsofquestions. See update notice above.
3/16/12: Clear the "Push n for menu" message on screen once boot has been determined.
cyanoboot-12-9-20.tar.gz
(source)
Another post.
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
911jason said:
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
Click to expand...
Click to collapse
It would go in /boot-- or partition 1. On emmc it looks like: /dev/block/mmcblk0p1 on SD it's /dev/block/mmcblk1p1.
There should indeed be one there already. Along with uImage, uRamdisk, etc...
it's not usually mounted by default. One way to access it is to use these commands from your computer:
$ adb shell mkdir /data/mnt
$ adb shell mount -t vfat /dev/block/mmcblk0p1 /data/mnt
$ adb shell cp /data/mnt/u-boot.bin /data/mnt/u-boot.bin.old
$ adb push u-boot.bin /data/mnt/
$ adb reboot
$ is the prompt, of course. Here's what they do:
1. make a "mount point" (a directory) at /data/mnt so that you can
2. mount the vfat boot partition (p1) at that mount point. Then,
3. backup your old u-boot.bin in case this one is deeply flawed
3. push your local copy of u-boot.bin (CyanoBoot) on top of the old one, and
4. reboot and hope it doesn't crash.
Good luck, and my apologies in advance if/when this screws up. Remember, you are assuming all risk here
(you can also do it by loading clockworkmod, mounting boot to /boot and then backing up and/or pushing u-boot.bin to /boot)
911jason said:
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
Click to expand...
Click to collapse
its in the boot partition
Works like a charm! Very nice!
thanks fattire, this in my opinion is much nicer then the other menu we have available to us. hope to see you polish this off
ehh, the possibilities of running 4 OS's with this makes me smile
Dropped it into one of Eyeballer's nightly opengl zips (http://forum.xda-developers.com/showthread.php?t=1526115) and it works great! Thanks fattire!
Excellent work, Thanks
Been following your development on the NT even though I don't have one. I was hoping this would be ported sooner or later.
Can someone please drop this into a normal ZIP file and put it somewhere where it can be downloaded?
Thanks....
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Additionally:
@ fattire... is it ok if I include this in my file for customizing ROM's in this post instead of the cyanogen u-boot.bin?
DizzyDen said:
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Additionally:
@ fattire... is it ok if I include this in my file for customizing ROM's in this post instead of the cyanogen u-boot.bin?
Click to expand...
Click to collapse
Sure and sure. Be sure to include the GPL notice.
CyanoBoot in RAR
Thanks to fattire for all the hard work put in for our devices... and with his ok... here is the CyanoBoot in RAR format for those that have difficulties with gz files.
I will keep this updated and named to coincide with development.
DizzyDen said:
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Click to expand...
Click to collapse
Thx Dizzy....I'll find the win-gz and use that.
---------- Post added at 02:21 PM ---------- Previous post was at 02:09 PM ----------
Works great on an SD card using CM7
Thanks Fattire!
Good to go in my opinion, great work as always fattire.. my nook and tp would be collecting dust if it wasn't for your hard work
Just since we're chiming in here, yeah looks ready to me too. I've been testing several types of software this last week, some of which require flashing and rebooting for what seems to be all day. No joke, I have probably rebooted 60+ times since I downloaded this yesterday. Multiple installations, multiple configurations. No dual-emmc, but everything else has worked great.
It has been kind of bittersweet to lose the little green box though, even to such an obvious upgrade. Despite all the crap I've tried on this thing, once that logo showed up, I knew it was gonna be okay, ya know?
I have had a totally different relationship with technology since the very first time I laid eyes on it.
Good of time as any to thank the commenters on this thread in particular.
Heh. I know what you mean re that green logo (from drakknar, btw). For me it was a HUGE battle to get a multi-colored logo to appear in the first place ...This commit and this one took many, many cycles of booting and rebooting... and trying to figure out how to get the pallette to work, etc. Before it, the u-boot could only do black and white logos (does anyone remember the "Loading..." text?) and it looked pretty awful. But nemith made a good case that for the next revision, the newer u-boot might be rebranded since it's not the start up for only CM... Still, I kept the "cyano" part in the name as a tribute...
Thanks for testing, and I'm glad y'all are having success. Maybe tomorrow I'll push to the repo.
mateorod said:
It has been kind of bittersweet to lose the little green box though, even to such an obvious upgrade. Despite all the crap I've tried on this thing, once that logo showed up, I knew it was gonna be okay, ya know?
I have had a totally different relationship with technology since the very first time I laid eyes on it.
Click to expand...
Click to collapse
Just curious: Tell me about your relationship with technology and how it's changed? I feel like the NC in the last year has really helped me to learn a LOT.
OFF-TOPIC (spoiler alert).
I got a replacement nook for the one my wife got me at Christmas last October. I was absolutely flabbergasted that they has changed the storage so that it couldn't hold the books and music I had sideloaded on the original. I looked to see what I could do, and followed directions to repartition the emmc.Flashing the ROM was an afterthought.
I didn't know before finding the info that the reader had external storage. I didn't know what an sdcard was. I had to sign up for Gmail. My last computer died because of the Love Bug.
Yes.
The only reason I registered here was because I couldn't understand why every time I tried to install the Google Music Manager .exe, it wouldn't work.
Today I decompiled a services file and edited it, so I could share it with others. I spent this evening testing a package distro system. I posted in the forum and some of the words are in color!
My wife bought me an e-reader, you know? These things you've made have had a big impact and it can't only happening to me.
Thanks fattire! Have it on my SD and it works great!
I'm not sure if this is a bug or just a user common sense issue, but if you select an Alternate boot from the menu without actually having an alternate image, the Nook freezes on "Loading AltBoot from"... requiring a hard reset.
Obviously, if you don't have an Alternate boot, you wouldn't be selecting it. But I wasn't sure if there could be a potential improvement, like if Cyanoboot doesn't detect an uAltImg, it wouldn't give it as an option?