***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!
Related
TO GET TO THE POINT, AND TO AVOID MY *****ING, SCROLL DOWN​
OK, imma recent migrating bird from the sinking WinMo ship.
Just got this phone from LG, nice phone, but the flashing guides here aren't so easy to understand
I'll quote a 6 line instruction from the Prime/Megatron ROM thread which is
http://forum.xda-developers.com/showthread.php?t=870640
How to flash:
First, reboot into recovery via 3-button-combo, ADB, terminal, w/e.
Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
Wipe data (data,cache,dalvik-cache,ext).
Connect the device to PC, copy Megatron over to the SDcard, disconnect.
Flash it via "flash zip from sdcard"
Reboot
Read important notes below
That's it.
Click to expand...
Click to collapse
SERIOUS? THATS IT???????????
I have no idea what all that means, and so are millions of sad puppies who migrates from WinMo's or dreaded Dumb Phones like the ones they sell in 7-11
SO, the point is (you can stop scrolling now)
PLEASE PLEASE PLLLEEEEAAASE make a easy guide for flashing, possibily a video. Or you could make it easy enough for me to understand, and ill make the guide.
BTW, in the long term, it WILL educate FURTHER n00bs.
Thanks in advance. Sorry for the *****ing. Love u guys
OK, OK, OK, you have got me!! I will prepare some "dictionary" for all noobs. Maybe it will sounds crazy, but when I logged-in I had no idea what android is. OO is my first android phone. I have got everythink from whole this forum, but I was there since thread about P500 started so it wasn't too hard catch and read every post here. So, all informations are there, but sometimes is not possible find them.
So i just have to read everything? Optimus One Android Dev or General?
Great! Thanks a lot
But gonna go to sleep.. I'm sorry lol this is my last week of winter break and its midnight. Bye!
dongimin2 said:
So i just have to read everything? Optimus One Android Dev or General?
Click to expand...
Click to collapse
About 95% of posts it will be useless because there are also some question, helps, and another stuff. There is too much words and useless trash. You also need know basics of unix-like systems to understand what are guys (and you) trying to do in adb shell, what is root and for what it is, what # mean in command line, and so on.
custom ROM is mainly for experienced user. At least, experienced in unix-like system, because android is based on it. Tools like busybox bringing next tools known from unix and some programs needs it for running. And another and another words and name what is normal for advanced user, not for n00bs here.
Because that all stuff it takes some time that I will have some usable noob dictionary.
This is a good and pretty much complete guide.
forum.androidcentral.com/lg-optimus-s-roms-hacks/48543-idiots-guide-rooting-custom-roms-optimus-s-edition.html
Rooting is the same, you just have to change some commands for the custom recovery but once you get there you'll know. And I recommend rooting via Adb, its easier for later.
btw, don't know if its a problem posting the link, if it is, sorry.
One thread is enough!
Do not do this again or you will have an infraction for spam.
Cheers
i currently have the TNT 4.4.0 ROM installed but I was looking to switch to the Vegan Ginger ROM and also to install pershoots kernel. are they compatible? how would i go about this without bricking the device? theres a lot of stuff here about firmware versions and incompatbilities and bricking and stuff and im not really sure about the process.
thanks in advance for your help?
Here is a detail step by step instruction on how to root, install a rom, etc.
http://forum.xda-developers.com/showthread.php?t=865245
I highly recommend Calkulin+Clemsyn combo rom. It's super fast, stable, and is based on the TnT stock rom. Very easy to use for newbies.
PS - with the rom I linked to, market fix and flash have already been applied. All you need to do is flash root and the Calkulin+Clemsyn combo rom and you're set.
what about all of that wiping and stuff. i have to do that also, correct? can any step of this completely brick the device?
thanks again!
None of the steps will brick your device however i would recommend an iPad
joshtb86 said:
what about all of that wiping and stuff. i have to do that also, correct? can any step of this completely brick the device?
thanks again!
Click to expand...
Click to collapse
Ok, here are the instructions, since I feel particularly good today on my day off.
(1) Follow the instruction on that other link for installing ClockworkMod.
(2) Create a folder in your sdcard name "rom" or "ROM" or "hoogabooga" or whatever name you want. Just make sure you remember the folder.
(3) Download the file I have included in this post (down below) called Calkulin's_FORMAT_ALL.zip.
(4) Download your choice of rom. There are now half a dozen to choose from. Calkulin+Clemsyn combo is the fastest and most stable according to my experience.
(5) Put those roms into that "hoogabooga" folder you created in your sdcard. Turn off your gtab.
(6) Startup into clockworkmod by pressing the power button and the volume + button and keep pressing the volume + button until you see something appearing on the upper left hand side of the screen during the birds.
(7) Scroll up and down using the volume control. Go down to where it says "install zip from sdcard" and press the house button.
(8) Choose zip from card.
(9) Go to your hoogabooga folder and choose Calkulin's_FORMAT_ALL.zip.
(10) Press the back button and go to advance.
(11) Choose the 2nd choice where it says wipe dalvik cache.
(12) Go back and pick install zip from sdcard again. This time, choose the rom that you chose.
(13) After it finishes "installing", reboot. Note that the first time the device boots into a new rom it will be very slow. Just let it sit there and do its thing. If you try anything at this point, you will screw up your machine. So, just let the darn thing boot up, please. We got enough users coming in here complaining about why their machine is screwed up because they did something while it's booting up. Good god...
Please be aware that I wrote the instructions thinking you have common sense. In other words, use common sense. Where it says "running" or "installing" or whatever then you're suppose to wait. Don't just follow the instructions blindly.
Invest some time in setting up nvflash. It's much less stressful with a safety net.
http://forum.xda-developers.com/showthread.php?t=861950
Don't even think about an iPad.
My problem with nvflash is that it's newbie unfriendly. I was a newbie not too long ago and I can tell you nvflash looked like a nightmare.
Unless the user does something stupid like interrupting a startup process, the gtab is fairly hard to brick.
And as always, I highly recommend getting rid of the gtab and buy an ipad. Less whiners for us to take care of. Let apple take care of them. Apple already got an army of whiners. I say we let them have a few more.
goodintentions said:
And as always, I highly recommend getting rid of the gtab and buy an ipad. Less whiners for us to take care of. Let apple take care of them. Apple already got an army of whiners. I say we let them have a few more.
Click to expand...
Click to collapse
I know this is sarcasm, crossed with a political statement, spliced with some frustration with newbies. But for me it comes off as a dig at the OP.
The nvflash discussion has been had elsewhere, however as an android modding newbie, following Roebeet's NV flash tutorial (due to his constant encouraging) has made mucking around with my Gtab 10x more enjoyable, knowing that I have a way to easily start from scratch. And it's near impossible to set up nvflash in a hurry after you have soft bricked.
Josh, the tutorial above is excellent, and it will certainly get you to where you want to go. But if you hit one of the gtab landmines (trying out 1.1 to 1.2 for example) nvflash will be your best friend.
brettdwagner said:
I know this is sarcasm, crossed with a political statement, spliced with some frustration with newbies. But for me it comes off as a dig at the OP.
Click to expand...
Click to collapse
On the contrary, I stand behind 100% what I said. Like I said before, I fix computers as a side job to bring in an extra dollar or two to go out and party... I mean to pay my bills. Most people, when it comes to computers and gadgets, like to whine more than they like to enjoy their machines. I'm sure apple's got a whole division specializing in dealing with whiners since they already got an army of whiners.
Whiners have nothing to do with being a newbie or not. It's got to do with the spoon-feed-me attitude. Over the months, I have seen complaints about the gtab by dedicated whiners. Everything from "it's .3 lb heavier than the ipad which makes it too heavy!" to "why you no give me honey!" Frankly, neither VS nor this community is properly equipped to deal with whiners. Why not send them to apple and let it be apple's problem?
I'd like to think I'm a resourceful person. When I see a problem, instead of complaining I try to find a solution. I see the gtab as an investment. So, instead of just watching videos on it I have incorporated it into my daily work. I crinch in pain every time I see people whine before they even tried to find a solution. So, why not send them to apple?
I don't mind it for the true whiners, but since you post this everywhere it looks like your trying to fend off any and all new users who have questions. The subtext of "get an iPad" is 'you can't handle this and we don't really want you here.'
That said, your post above went above and beyond to help out the OP. Your a mystery to me goodintentions
brettdwagner said:
I don't mind it for the true whiners, but since you post this everywhere it looks like your trying to fend off any and all new users who have questions. The subtext of "get an iPad" is 'you can't handle this and we don't really want you here.'
That said, your post above went above and beyond to help out the OP. Your a mystery to me goodintentions
Click to expand...
Click to collapse
It's my day off.
goodintentions said:
Ok, here are the instructions, since I feel particularly good today on my day off.
(1) Follow the instruction on that other link for installing ClockworkMod.
(2) Create a folder in your sdcard name "rom" or "ROM" or "hoogabooga" or whatever name you want. Just make sure you remember the folder.
(3) Download the file I have included in this post (down below) called Calkulin's_FORMAT_ALL.zip.
(4) Download your choice of rom. There are now half a dozen to choose from. Calkulin+Clemsyn combo is the fastest and most stable according to my experience.
(5) Put those roms into that "hoogabooga" folder you created in your sdcard. Turn off your gtab.
(6) Startup into clockworkmod by pressing the power button and the volume + button and keep pressing the volume + button until you see something appearing on the upper left hand side of the screen during the birds.
(7) Scroll up and down using the volume control. Go down to where it says "install zip from sdcard" and press the house button.
(8) Choose zip from card.
(9) Go to your hoogabooga folder and choose Calkulin's_FORMAT_ALL.zip.
(10) Press the back button and go to advance.
(11) Choose the 2nd choice where it says wipe dalvik cache.
(12) Go back and pick install zip from sdcard again. This time, choose the rom that you chose.
(13) After it finishes "installing", reboot. Note that the first time the device boots into a new rom it will be very slow. Just let it sit there and do its thing. If you try anything at this point, you will screw up your machine. So, just let the darn thing boot up, please. We got enough users coming in here complaining about why their machine is screwed up because they did something while it's booting up. Good god...
Please be aware that I wrote the instructions thinking you have common sense. In other words, use common sense. Where it says "running" or "installing" or whatever then you're suppose to wait. Don't just follow the instructions blindly.
Click to expand...
Click to collapse
okay thanks a lot. i read in the clem+calk ROM thread that some people used CWM, the most recent version, not the .8 version which i have been using. is that correct? or should i use the .8 version?
so all the steps say to download this stuff to your sd card, but i cant actually access my microsd card from CWM. i can only access the folder called SDCARD which is actually my internal memory. should i still download it there? is there another way to access my microSD from CWM? is it okay to leave it on the sdcard folder which is my internal drive?
thanks again!
Your sdcard is your internal space. The microsdcard is called sdcard 2. Cwm only access your sdcard which is your internal.
Well here I am again,
Not sure if I should have started a new thread for this or not. And although I feel like there are more threads than needs to be in the Development forum at the time being. I felt like the SD image might have it's own issues unrelated to the EMMC version. So I wanted to keep it seperate. If a Mod feels different, please advise so. I'll be more than happy to remove the thread and have the file posted to Divine_Madcat's original thread.
**Disclaimer: As usual, use at your own risk. Backup! And I'm not responsible for anything period**
I've just prepped an Image for Divine Madcat's latest Honeycomb Hybrid RC1. I've included rookie1's dualboot u-boot.bin and my modded CWM for SD, for the purpose of easier updates in the future for the SDcard rom.
Although there is no option to mount an SDcard in this version. I was able to mount the 4th partition as SDcard. So now you can use a file explorer of choice to browse your SDcard partition. I'm not sure if the EMMC version mounted the internal Media partition or not. Not 100% sure, but with this image you should also be able to browse your /media partition on your nook as well. And remember to thank the devs for all their time and effort into getting this to us. All I did was prep it to work as an SD image.
Directions:
1-Download the update-HC-hybrid-rc1-sd.img.7z
2-Uncompress it
3-The .img file should be able to fit on a 2gb card or larger
3-Follow directions from Nookdevs.com to burn the image
4-Pop the SDcard in your nook
5-Enjoy!
Credits:
Divine_Madcat
deeper_blue
rookie1
nemith
Edit: 5/21 - Well since the world is apparently ending today sometime. Figured I'd at least let you guys try a working .img. So here is an updated .img with the apps installing issue fixed. Everything is the same as the last .img except for the fix and I included a file manager. If it hangs at the "android_" screen on first boot. Just do a hard reboot and it should be fine. Enjoy!
Edit: 5/12 - Seems like there is an issue with installing apps where it will do a soft reboot when attempting to do so. I won't have time to take a real look at it till this weekend though.
-You could push individual apps to /data/app via adb for the time being.
Code:
$ adb push app.apk /data/app
-Or to push multiple apps. Create a folder called data. Within that folder, create a folder called app. Then place all your apks in the app folder. Now you can push the whole directory to /data/app
Code:
$ adb push /your_home_directory/data /data
-If anyone else who might want to jump ahead of me and find a fix, would very much appreciate it!
Downloads:
5/21 : update-HC-hybrid-rc1-sd-v0.2.img.7z
MD5: bba35a262821fbb7e4ef42f8bb4807d6
Click to expand...
Click to collapse
If I've helped out in some way, please say thank you in one way or another!
Thanks,
Racks
Awesome! Does this include anything new from 3.1?
Looks good. I was trying to install nook app from market but it kept rebooting. Thanks for the hard work..
Looking forward to giving this a try...
Whats the size of the image, what is the min/max size sd card required?
@Samir- nothing new. Direct image of hybrid rc1 by madcat
@Flyboy- I really didn't get a chance to test. Thanks for the info. Ill take a look when I can.
@Joenathan- sorry forgot to post img size. Its a 1.8gb image. So any card 2gb or larger should be fine. Ill update OP with size later
The more feedback the better. Can't fix things without feedback.
Thanks everyone,
Racks
Sent from my NookColor using Tapatalk
Are there quite a bit of FCs with this version? I tried the emmc one and had to revert back to CM7 because it was too unstable.
Its a bit too big for my 2GB SD card, my sd card weighs in at 1,921,024KB whereas the image is 1,927,168KB
So 2GB SD cards are out....
Thanks Racks, just what I was looking for.
Well done.
crap! I has 2gb SD card too that I use for this.
Any chance of someone making an SD version of the xboxexpert's HC build?
chisleu said:
crap! I has 2gb SD card too that I use for this.
Any chance of someone making an SD version of the xboxexpert's HC build?
Click to expand...
Click to collapse
Any reason for wanting that build? I ask, because it is out of date, and nothing more than some extra apps added by default. This version uses newer framework, and right now is advisable to use until a 3.1 build comes (especially with the SD card fix also made by Racks).
The ROM is nice, Honeycomb apps are much superior, but for me it runs too slow.
Using a class 4 generic SD. Anyone else having problems?
hirano said:
The ROM is nice, Honeycomb apps are much superior, but for me it runs too slow.
Using a class 4 generic SD. Anyone else having problems?
Click to expand...
Click to collapse
Not that the SDK is as fast as CM7, but i am willing to bet the problem is your SD card. Having used a crappy SD card myself, i know how bad they can be; invest in a cheap class 2 or 4 Sandisk card, and get blown away.
Thanks, this is exactly what I was looking for as my next NC project
Divine_Madcat said:
Not that the SDK is as fast as CM7, but i am willing to bet the problem is your SD card. Having used a crappy SD card myself, i know how bad they can be; invest in a cheap class 2 or 4 Sandisk card, and get blown away.
Click to expand...
Click to collapse
Divine,
For awhile I would see you posting around with random things in various sections and wasnt really sure if you were a troll or not, but lately youve pushed some truly amazing things like the work on dals kernel and now this update hc build and I truly am impressed with all your work. You have my complete respect. Thank you.
RileyGrant said:
Divine,
For awhile I would see you posting around with random things in various sections and wasnt really sure if you were a troll or not, but lately youve pushed some truly amazing things like the work on dals kernel and now this update hc build and I truly am impressed with all your work. You have my complete respect. Thank you.
Click to expand...
Click to collapse
Ill certainly admit, i am not the most agreeable at time; commonly, i let my daily stresses flow out on to forums. I am easily annoyed at what i see as something stupid (which sadly, it feels like has been happening more in this forum).
As it is, I am happy i could have committed something useful to the community.
Apps
Great job! Love not having to flash between CM and HC to play with the 3.0 goodness. My only question, anytime I try to install an app it reboots.....Ideas?
Fodizzle1978 said:
Great job! Love not having to flash between CM and HC to play with the 3.0 goodness. My only question, anytime I try to install an app it reboots.....Ideas?
Click to expand...
Click to collapse
You're the second person to say so. Is everyone having this issue? Is anyone having success installing any apps? From market or from a file explorer. I need more feedback so I can pinpoint the problem.
I'll have to take a look at this when I get a chance. Or if you don't mind posting a logcat? Just save a logcat to a .txt file and upload it here. I'll take a look to see where it's erroring out.
*I could be wrong, but most of the time when this happens, it seems to be a caching issue. But again, i won't know till i see the errors.
Thanks,
Racks
Here ya go
racks11479 said:
You're the second person to say so. Is everyone having this issue? Is anyone having success installing any apps? From market or from a file explorer. I need more feedback so I can pinpoint the problem.
I'll have to take a look at this when I get a chance. Or if you don't mind posting a logcat? Just save a logcat to a .txt file and upload it here. I'll take a look to see where it's erroring out.
*I could be wrong, but most of the time when this happens, it seems to be a caching issue. But again, i won't know till i see the errors.
Thanks,
Racks
Click to expand...
Click to collapse
Fodizzle1978 said:
Here ya go
Click to expand...
Click to collapse
Here's a better one....not sure I captured it the first time
I'm getting the same problem, only tried installing from market.
Sent from my PC36100 using Tapatalk
As of you guys have found out there has been a few threads that have been started that throw around theories about getting CWMR to work and such and I'm here to finally give you guys the progress from the dev that's working on it.
I have been working on getting CWMR working off and on for a few months now to some avail. I have been slowly testing it and sending out alphas to people on the IRC and now I'm here to tell you where I'm at and what has been accomplished.
Part 1: Getting into CWMR
I started working with our current bootstrap recovery as a base for CWMR. It was of course in charge mode, but it was a step that had to be done first. I got a hold on a CWMR binary and after a bunch of shell commands managed to get the mangled version of CWMR that we've seen before. From there I had the idea to inject the ATRIX binary into the recovery and try it from there. It was a big success and I could use some (very few) of the functions that if offered. But I was finally in CWMR on the X2. (I posted the picture on my twitter).
Part 2: Making the Functions Work
From here the first thing I decided to do was to get the "Fix Permissions" script working. By getting this to work I know I could place my own code in there that will log to the file that I could open up and see whatever I wanted as ADB didn't work YET (more on that later). I fiddled with it a bit and got it working.
This also allowed me to access the log and find out why the unmounting and formatting wasn't working either. This was due to an issue with the mke2fs and other complementary binaries not being appropriately compiled for our phone. As I was working on CM7 at the time, i had access to the sources of these and to the recovery binary as well. I decided to build a recovery binary that was tailored to our phone and not the ATRIX and the binaries that handle formatting partitions, etc. These worked on some partitions I could wipe data and cache properly by reformatting, I could easily erase a partition at will except for one: /system.
Part 3: Getting /system Formatted (WIP)
At this point I decided to find out why /system could never be formatted. When a partition needs formatting it must be unmounted first. But I could never unmount /system. By using the logs I found out that the partition was still in use. By using the "Fix Permissions" script, I managed to find that a lot of daemons (aka services) were being ran from the /system sub directories. This meant that in order to format, I had to have them not running. Easy enough as there's a script in CWMR that allows us to kill certain processes before the new recovery starts. I decided to kill all of the services with this script but found that the display would go blank. From there I found that two services are REQUIRED to be running on the phone for drawing (making things show on the screen) to take place: servicemanager and nvrm_daemon.
The servicemanager does exactly what it's title says: it manages the currently running services. This has to be running to keep nvrm_daemon running or else things get kinda freaky.
nvrm_daemon is what is used to manage drawing commands to the screen (the nv stands for nVidia which is who made the Tegra 2). With this service running I was able to (while in charge mode still) draw to the screen and show all of the menus for CWMR.
This created a problem. As these HAD to be running /system could never unmount because they were in there. Unless we used 2nd-init. From here I created my own hijack script that allowed me to copy over the necessary daemons into /sbin (which is just a sub directory of the rootfs). Then by using a new init.rc I could start these daemons from /sbin and see if they worked for CWMR.
After a lot of coding I managed to get the daemons running from /sbin and I thought I was free from there. And while I was at it, I might as well tried to get it out of charge mode.
Part 4: Untethering the Recovery (WIP)
I figured that since I was using 2nd-init anyway that I might as well have been working on trying to get it untethered also. After a bunch of looking into why charge mode was the only way to get it working, I found that before charge mode was started the init.rc started the "pre-zygote" services. These include usbd (the usb daemon), battd (the battery daemon), etc. What was also started was nvrm_daemon (another proof that we needed this running) to draw on the screen (charge mode draws the battery indicator to show charging progress).
I decided to move to mot_boot_mode to do the hijacking. I eventually managed to get things running but it still wouldn't draw to the screen. A look at the logs showed that for whatever reason we still didn't have access to the framebuffer (the memory space aka buffer that is drawn to the screen). I was tired of rebooting over and over again to get results and by now I had SBF'd I don't know how many times, only to not be able to access the logs due to a wipe. So next thing I decided was to get ADB working at boot.
Part 5: Starting ADB at Boot (The Short Version)
I took a look through the init.rc and found that Motorola had disabled the default way to get ADB working at boot. Through a bunch of digging I found that I could re-enable the method but it started usbd also (yet another daemon I'd have to move and thus more time, etc.). But eventually I found another property (aka system variable) that i could set that would start ADB without having usbd started: persist.adb.enable_NV_DISABLED. Setting that to 1 started ADB whenever I wanted it to. This allowed me access to the system (as root actually) without having to reboot and try to get into logs and whatnot. I could see everything that was running, mount/unmount and do everything I normally could and see better why they were failing.
Part 6: Recent Discoveries (as of 1/3/12) On the /system Unmount
I decided that I was going to go back to charge mode for now. After causing too much pain with framebuffer access I decided to look into why /system STILL wouldn't unmount after moving everything out of there. With the help of mastafunk and DrPenguin I was able to get a hold of a program named strace. This allows you to debug what binaries are doing down to pretty much every comparison, file opening, memory mapping, etc. I had found that nvrm_daemon (although started from /sbin) was looking for and loading drivers found in /system/lib. This was a problem and I thought that we may never get /system unmounted. Until I found out one other thing.
The nvrm_daemon doesn't look for the drivers inside of /system/lib first. It looks for them in /vendor/lib first and then if it can't find them, goes to /system/lib. So simple enough. I thought I could just make a /vendor/lib directory, copy the libs over and have them load from there. Well it's not that simple as there is already a file in the rootfs named vendor. But the file is a symlink to /system/vendor so if it looks at /vendor/lib it really looks at /system/vendor/lib. I thought I was stuck again until I took a closer look at the /system directory. There is no ./vendor sub directory in /system. That being said, I was able to delete the symlink in the rootfs and then create a /vendor/lib directory copy over the libs to it and nvrm_daemon successfully loaded the libs from there and not from system.
Conclusion
You are now caught up on when we've basically done to try to get CWMR working on the X2. Being that we're the only Tegra 2 phone from Motorola that is locked, we're kinda stuck trying to get things working. For now I consider this progress. Albeit slow progress, but progress none the less. If you took the time to read this, I hope you now understand the frustrations I've had to deal with this. All the while trying to help masta get 2nd-init fully working for our phones.
Thank you.
Thank you very much for the detailed explanation - well written so that even a novice like myself could understand your progress and frustrations. Thank you to you and your peers also for your hard work and determination to see this through. I think I can speak for all X2 users and say this is most appreciated!
Great writeup. Very informative. Thank you for your dedication.
I thought 2nd init was done and masta was working on aosp? I mean we can log from our new init.rc so it is using it. In the meantime i've been working on my barebones so we can get new blood using 2nd init and because I want a decent daily driver in the event we cant get stuff going.
To echo what others have said, thank you very much for the information. This kind of transparency is always very much appreciated when there's some spare time to put that out there. It not only is really helpful to make it understandable, but it's nice to know that these projects are still active.
Perhaps most importantly though in the context of potential progress: having specific information is a great way for knowledgeable people reading to recognize if they might be able to help out in certain areas. You might get some fresh ideas from people who hadn't considered themselves familiar enough with the situation to be useful. Who knows.
Anyways, thank you very much again. It's very encouraging to hear progress reports in general, not to mention ones like this that involve so many successes.
Wow thanks so much for your hard work and dedication can't wait until you conquer this sounds like you are closer then ever
Sent from my DROID X2 using XDA App
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
skwoodwiva said:
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
Click to expand...
Click to collapse
No need to appologize man... Stuff like this should have been posted or known. To be honest, I thought Masta was finishing 2nd INIT and starting to work on getting AOSP running and CWM was out the window, thats why I jumped in to try and get progress on CWM. Thanks DK and now I know the IRC is more active, I will be on there more to try and help out.
Thank you!
Thanks a ton for all the effort you're putting in. When I got my DX2 I thought that despite the crazily over-bloated Motoblur, I would be OK due to the Tegra 2 power and wonderfully innovative developer community. I didn't count on their being such a small number of us out there for this device or the complexity that Moto would unnecessarily bake in. So, after many months of gut wrenching disappointment, I finally have hope again.
You are a true nerd hero, sir!
Its nice to have an explanation of things and why they work or dont work. A lot of us are just trying to learn so we can be useful.
Sent from my Eclipsed and ICS themed X2.
Dragonz...after reading the info about 1/3/12 I am curious...
Does this mean that you might be able to get it working and unmount system as u need it to?
Or were there still other processes using system that you will need to mess with and change around as you did with the vendor ?
Do you still need to move the servicemanager also?
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
PM me with a copy of your nightly so I can help as well please
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
drapp said:
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
dragonzkiller said:
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
Click to expand...
Click to collapse
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
aceoyame said:
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
Click to expand...
Click to collapse
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
dragonzkiller said:
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
Click to expand...
Click to collapse
Let me rephrase that, add CM stuff and then remove Moto stuff. So get back to that, delete moto apk's and then edit init.rc for the framework. All those FC's we are getting if when were in that state are vital clues as to whats isn't playing nice with CM's apk's and framework. The fact it can even somewhat boot in a state like that means it's fairly close to how it wants. If it didn't wipe /system/ then it sounds like you just need to properly 2nd init that ***** and then in moto's init.rc remove moto jar's and apks's. Remember if it didn't wipe then you replaced the framework with CM and it's blur running ontop of it.
ashclepdia said:
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
Click to expand...
Click to collapse
Thanks ashclepdia.... helpful as always...
Sent from my DROID X2 using xda premium
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?