yashsingh1/xdaforums huggingface dataset:
[Nook Color General] buckeye09:
Here are the steps I followed to get B&N content on Aldiko. Found it on Aldiko help page.

I was able to use the SD Card feature in Aldiko to import DRM'd Nook books on my Android Device.

At the Home screen in Aldiko, tap SD Card.

Navigate to the Nook folder on your device

Navigate to the Content folder within the Nook folder

Tap on the book you want to import (not on the check box, just tap the title)

You will be prompted to open or import, tap "open"

you will then be prompted for a username and password. The user name is the name on the credit card associated with your Nook purchase. The password is the credit card number itself, no spaces.

Once you have been able to open the book, go back to the home page and follow steps 1 through 4.

This time, when you are prompted to open or import, choose "import". The book will be imported to your Aldiko Library.

The reason I open before importing is that there is no password prompt when importing. I did find that once I had entered my credit card info for one book, I was able to import all of the rest of my Nook purchases without opening first, the app seemed to just need this information once.

Enjoy!
[Nook Color General] JHyena:
Im having the same problem. I completely erased and rebuilt my whole nook - most recent CM7, and the most recent nook app, and still no librar. Tried Aldico and it does not work as there is no content on my card. I downloaded off my pc to the card and it would not read it.
[Nook Color General] galatians51:
This has happened to me before, I posted in the B&N forums how to fix it.

What worked for me after (a lot of headache) is simply this: on your online B&N account on the PC, move every single book to Archive, then move them back to the library. They should then show up in your NC.

It seems to be a server refresh type of issue.
[Nook Color General] darien87:
B&N support had me try moving one book to archive and back and it didn't show up. I guess I can see if moving them all makes a difference.

EDIT: Nope didn't work
[Nook Color General] darien87:
UPDATE:

With the Nook app update on the on the market this morning, suddenly my library is back! Not sure what they updated but it seems to have solved my issue, for now.
[Nook Color General] virii01:
I'm having this same issue. Nook app one my rooted NC was working fun until one day, poof, library is empty.

I've tried uninstalling, rebooting, re-installing, signing out, moving the app to SD card, etc etc. App is version 2.6.2. Anyone else experiencing this? I tried to engage B&N support but it's pointless. :mad:
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
Step by step what I did:

I rooted my tab via this tutorial: http://xdaforums.com/showthread.php?t=812367

I then installed bootstrap (http://xdaforums.com/showthread.php?t=981307), and after going through the steps and restarting I can't get into recovery or anything. It just sits at the logo.

How do I just reset it to factory?
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
If I completly broke this I think I'm going to puke... Can somebody give me a little bit of hope or help?
[Galaxy Tab Q&A, Help & Troubleshooting] k0sh:
1st question .. is your tab unlock ?

2nd if not , means you gonna reflash your stock rom again via odin

3th . maybe you can use P1_add_hidden.pit via odin and press start and maybe its work , but 80% its work if didn't work u have to go for step 2 :)
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
My tab is unlocked. So I'm going to have to reflash my stock rom using odin? Where is the best place to track down the froyo rom for my tab?
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
I just found these links which may help:

http://xdaforums.com/showthread.php?t=889165

http://xdaforums.com/showthread.php?t=888071

Am I correct these should help?
[Galaxy Tab Q&A, Help & Troubleshooting] jalexandre:
Obihannm, I did the same yesterday.

You need the original stock firmware for your galaxy and Odin for flash it again.

Look for sam firmware in the google to grab your stock kernel, tools and guides for recovery.

With luck and patience, it is possible ressurrect your tab, but It will back unrooted and maybe you get a locked bootloader.
[Galaxy Tab Q&A, Help & Troubleshooting] TheATHEiST:
Just go here and follow attached guide guide.
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
Thanks guys, I will be up late trying this for sure. I noticed that this probably should live within the QA area not Genreal, so if a Mod or Admin wants to move it, please do.
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
That would end up with me having gingerbread correct? Should I try to first restore it to factory since right now I can't even enter recovery? Or is it a moot point and I may as well go forward get gingerbread on it?
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
wait by unlocked do you mean rooted? it is rooted but that is it...
[Galaxy Tab Q&A, Help & Troubleshooting] TheATHEiST:
You dont need to enter any recovery at all. Just "download" mode.

Go and read the guide.
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
OK, a few deep breaths and some "reading" (a new concept for me it seems) later I think I have a bit of a better understanding.

So reading through the overcome guide and a few other threads I think my issue is I must have had a protected bootloader, and that bootstrap program would have frigid that up (there probably was a warning if I slowed down). So that means my issue is my bootloader... Am I correct thus far?

If this is true, does this mean my current rom is actually fine, and fixing my bootloader is my #1 goal?

From there I can insteall the overcome rom, the normal gingerbread rom, or go back to stock? As I see it overcome/gingerbread is the best option.
[Galaxy Tab Q&A, Help & Troubleshooting] PBL1:
Just install the stock rom, once back to normal if you have a locked bootloader patch it

All that you need in one handy page

http://xdaforums.com/wiki/index.php?title=File:SamsungGalaxyTab.png
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
I read through the guide you linked to as well as this one (http://xdaforums.com/showthread.php?t=1078622). You suggest I only need to access "download" mode, which I discovered how to do last night. Should Heimdall or other applications be able to see my device via download mode? Or is there a step I am missing.

As well I noticed in the guide you linked me it references patching the bootloader if it is locked, do I need to patch my bootloader or replace it completely as it seems to be broken?

I want to learn this stuff, this I read, and now I am asking. Again all help is appreciated.
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
Heimdall doesn't seem to do anything at all. I followed the guides as I best understood, and when it came time to hit the start button it instantly said completed with no actual results...

Any ideas?
[Galaxy Tab Q&A, Help & Troubleshooting] obihann:
a coworker was nice enough to help me out, using the stock rom with an unlocked bootloader he was able to bring it back for me. I'm now running froyo, rooted, and a unlocked boot loader so I should have no issues putting overcome on it.
[Verizon Droid Charge] imnuts:
I'm sure several people will be wanting this information, so I figured I would post it here for everyone. This will allow you to backup your system and create custom Odin images for restore purposes. For anyone unfamiliar with the Samsung system, they use Odin to flash things to the device, much like HTC has RUU and Moto has SBF. Odin files are either .tar files, or .tar.md5 files.

The .tar.md5 files are .tar files with the md5 checksum added to the end of the file. If you attempt to flash a .tar.md5 file, Odin will automatically check that the contents are what they should be before flashing and proceed with the flash if the md5 is valid, otherwise it will stop.

In Odin, you should use the PDA button for all flashing. The PIT button may be used as well, if we can get a valid .pit file for the device, but for now, PIT won't be used either. Other than PDA, Start/Reset are the only other buttons you need to worry about.

Now, on to creating the backup files. First, you will need your device to be rooted (perm or temp root will work), and you also need to have access to terminal on the phone, either via an emulator or adb shell access. To create the backup files, you won't need a Linux/UNIX system, but you will if you want to create a flashable Odin package. The following will output the files on the root of the SDCard, adjust the "of=" path if you want them somewhere else. It will also create the files for the proper filename for Odin as well. So to create the files, here are the commands you will use from root shell (#):

System:

dd if=/dev/block/stl10 of=/sdcard/factoryfs.rfs bs=4096

Kernel:

dd if=/dev/block/bml8 of=/sdcard/zImage bs=4096

Recovery:

dd if=/dev/block/bml9 of=/sdcard/recovery.bin bs=4096

DO NOT INCLUDE THE FOLLOWING IN ANYTHING BUT A PERSONAL BACKUP

Cache:

dd if=/dev/block/mmcblk0p3 of=/sdcard/cache.rfs bs=4096

DBData:

dd if=/dev/block/stl11 of=/sdcard/dbdata.rfs bs=4096

Data:

dd if=/dev/block/mmcblk0p1 of=/sdcard/movinand.bin bs=4096

The last three files (cache, dbdata, data) may contain personal information, so do not include these 3 files in anything but a personal backup/recovery package.

To create a flashable Odin package, you need to pull all of the files off of the phone/sdcard and onto your computer. From there, you use the following to create the package:

tar -H ustar -c factoryfs.rfs recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5

If you want to include cache/dbdata/data in the above for personal use, just add them after the "-c" and before the ">".

There are other files that may be in Odin packages, but they are protected by Samsung and cannot be dumped properly. The files are the bootloader, secondary bootloader, modems, and .lfs partitions. The files would be boot.bin, Sbl.bin, modem.bin (not sure what it would be for the CDMA/LTE dual modem here), and param.lfs. It however isn't that big of an issue that these can't be dumped as the can't really be altered by normal flashing of the device, and are usually only altered via OTA updates.
[Verizon Droid Charge] jism31:
Thanks for this info imnuts! I unfortunately updated to the new update and would like to go back to rooted but cant until I downgrade.
[Verizon Droid Charge] wynalazca:
Thanks!

Thanks for posting this. I'm going to attempt to make a personal backup and then I can factory reset the phone and make a stock version for people to use. I'm haven't installed the update yet either, so I'm hoping this will let people get back to ED1. I've also been playing around with theming using the fascinate community rom theme and ninjamorph to swap files. It'll take a while, but it's currently the only way I feel safe messing with framework-res.
[Verizon Droid Charge] droidmark:
I'm definitely looking forward to having a downgrade ROM image to get back to ED1!
[Verizon Droid Charge] rami98:
So how do you add the last personal 3 i just got the droid charge and i am not very familiar with samsung files i had a droid x and a thunderbolt very shortly and am familiar with ruu and sbf but how do you add cache dbdata and the other one. I meab like the actual command not the instruction to put it after c
[Verizon Droid Charge] imnuts:
The only thing that would change would be the tar command. If you want to include the other files, it would be:

tar -H ustar -c cache.rfs dbdata.rfs factoryfs.rfs movinand.bin recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5

You just need to pull the files from your phone and have them in the same directory that you're in in terminal, and have them named appropriately. It also doesn't matter what order they are in (that I know of), I just have them in alphabetical order for ease of reading.
[Verizon Droid Charge] MasterRy88:
So im going to try and do the voodoo lagfix for the first time ever but I wanted to make a backup. Im on ED2 and NOT rooted so how would I go about making these backups?
[Verizon Droid Charge] mypantsaretorn:
I tried the above and I keep getting this error message in the command prompt:

'tar' is not recognized as an internal or external command, operable program or batch file.

(I'm trying this on windows 7 professional)

Any help would be appreciated, thanks!
[Verizon Droid Charge] rmanaka:
You wouldn't by any chance be trying the "tar" command at a windows command prompt, would you?

Course you might be running Linux in a vmware or Hyper-V environment....hint?

HTH
[Verizon Droid Charge] mypantsaretorn:
Damn! I didn't pay attention to the second part of that sentence! Lol

Thanks for the "hint"..
[Verizon Droid Charge] imnuts:
The other option would be using Cygwin, but I've never tried it, so it may or may not work.
[Verizon Droid Charge] Deleted member 5132789:
cygwin works!

Edit: Here is how:

1. Search google for cygwin - download

2. Run - you will be prompted to get packages - I assumed "archive" was a good place to start - not sure if you need this or not...

3. When complete you will see a new icon on your desktop - double-click

4. Be patient as it loads

5. Copy the files output'ed from first post to same folder on PC

6. Back in cygwin:

a. cd x: (where x: is the drive letter of the drive that has the folder with the files)

b. tar -H ustar -c cache.rfs dbdata.rfs movinand.bin factoryfs.rfs recovery.bin zImage > package_name.tar

c: md5sum -t package_name.tar >> package_name.tar

d: mv package_name.tar package_name.tar.md5

Complete output of commands:

These files are for the users to personalise their cygwin experience.

They will never be overwritten nor automatically updated.

`./.bashrc' -> `/home/UWINKET//.bashrc'

`./.bash_profile' -> `/home/UWINKET//.bash_profile'

`./.inputrc' -> `/home/UWINKET//.inputrc'

`./.profile' -> `/home/UWINKET//.profile'

Your group is currently "mkgroup". This indicates that neither

your gid nor your pgsid (primary group associated with your SID)

is in /etc/group.

The /etc/group (and possibly /etc/passwd) files should be rebuilt.

See the man pages for mkpasswd and mkgroup then, for example, run

mkpasswd -l [-d] > /etc/passwd

mkgroup -l [-d] > /etc/group

Note that the -d switch is necessary for domain users.

user@computer ~

$ cd h:

System Volume Information

user@computer /cygdrive/h

$ cd downloads

user@computer /cygdrive/h/downloads

$ cd charge

user@computer /cygdrive/h/downloads/charge

$ cd tarbackup/

user@computer /cygdrive/h/downloads/charge/tarbackup

$ tar -H ustar -c cache.rfs dbdata.rfs movinand.bin factoryfs.rfs recovery.bin

zImage > package_name.tar

user@computer /cygdrive/h/downloads/charge/tarbackup

$ md5sum -t package_name.tar >> package_name.tar

user@computer /cygdrive/h/downloads/charge/tarbackup

$ mv package_name.tar package_name.tar.md5

user@computer /cygdrive/h/downloads/charge/tarbackup

$
[Verizon Droid Charge] Deleted member 5132789:
Hmm flash did not work with my personal data in it - got an error. Created a new .tar file with just factoryfs.rfs recovery.bin and zImage and was able to flash that. TG for TiBu!
[Verizon Droid Charge] jadsru1:
How do you start doing this. How do I get to root shell (#)... Thanks

AD
[Verizon Droid Charge] RaptorMD:
I plan to get rooted on ED1 so I can get a stock image backed up, and have a clean base to work from. Still getting my head around the odin stuff first.
[Verizon Droid Charge] DroidXcon:
you dont have to do that its already done

http://xdaforums.com/showthread.php?t=1085190
[Verizon Droid Charge] JKChad:
Well, I successfully followed all the instructions and have created my first ODIN flashable file, I have not tried to flash it yet. I'm just curious, I pull all the different .rfs, .bin, and zImage on this file and noticed it's about 1.8gb file. Is this normal?

Also, before I try to flash this. Should I have dissable voodoo lagfix and converted back to rfs before I dumped the files?

Thanks for all the help!
[Verizon Droid Charge] imnuts:
Yes, that's normal for it to be so large as dd will dump the partition, including empty space. If you were to compress it with zip or lzma, it'd drop down considerably.

Not sure about the voodoo part as I've never dumped files from an ext4 partition. I don't see any reason why it wouldn't work, but I'd flash with caution and have another working image ready just in case.
[Verizon Droid Charge] distortedloop:
Shouldn't be an issue as long as he keeps the voodoo kernel.
[Verizon Droid Charge] MattRussNC:
Anybody try this with voodoo yet ?
[Verizon Droid Charge] kiab115:
doing something wrong

tried the instructions here multiple times using oden and cygwin, every time I get a failure from odin at the recovery.bin trying to flash the image back. I've tried multiple cables and I can flash stock images with no problems. I'm using only the factoryfs.rfs, recovery.bin and zImage to create my package from an ec05 2.2 image which is mainly stock (just trying to reflash additional applications and setups to multiple phones). I'm using odin3 1.61. Any ideas where I'm messing it up:confused::confused:
[Verizon Droid Charge] rami98:
RaptorMD, it didn't work for me. I tried GummyCharged and now that i'm making a ROM i need all my files back and i made a backup before i flashed and now i went back to stock EE4 with the file someone made and everytime i flash any of the 3 i made, it says failed and i have to reflash stock or else it just shows a connect to pc icon when i boot. Here is the log

<ID:0/008> Added!!

<ID:0/008> Odin v.3 engine (ID:8)..

<ID:0/008> File analysis..

<ID:0/008> SetupConnection..

<ID:0/008> Initialzation..

<ID:0/008> Get PIT for mapping..

<ID:0/008> Firmware update start..

<ID:0/008> cache.rfs

<ID:0/008>

<ID:0/008> Complete(Write) operation failed.
[Verizon Droid Charge] rami98:
i still have the original files that i used, so should i just make one without the cache because i dont care about that i just want my data back
[Verizon Droid Charge] c0ns0le:
Just remember your offset, add 1 to the "entry" found in the pit.

There is also a great wealth of info here in the forums which explain pit files. use the advanced search feature.
[Verizon Droid Charge] distortedloop:
Thanks for the offset tip. That matches up. Why are some pulled as stl and others bml and yet others as the mmcblk?

Would pulling stl8 for the kernel produce the same result as the bml8 in the OP examples?

I've already been browsing the pit threads in some of the other forums, need to give it more focus than I have.
[Verizon Droid Charge] addictedhacks:
back up/odin

so after we move these files to the puter do i flash them through odin one at a time? thanks or how exactly thanks for the pointers.
[Verizon Droid Charge] c0ns0le:
Sadly I'm not certain. Give it a try and read the file with a hex editor. Btw sorry for the slow response. Been slightly busy.

CM7.1-06032011| kernel-DuJour-13N3 - SGH-I897 using XDA Premium App
[Verizon Droid Charge] bash_array:
Question...?

In root explorer I noticed under multi select there is a create .Tar function.... Instead of loading all of the outputted files from your phone to the computer to then package them in a .tar... could you just package them in a .tar via root explorer all on your phone?.... eliminating the need to package on your computer?
[Verizon Droid Charge] c0ns0le:
I would stick with pulling them off then tarring them.
[Verizon Droid Charge] bash_array:
ok... so I followed all directions perfectly and was able to successfully make a .tar.md5 recovery file. When flashing in odin It kept failing at cache.rfs... eventually I removed cache.rfs and went with just dbdata and movinand.bin from my personal data and it kept stalling out when attempting to flash over movinand.bin....

Soo finally I gave up on flashing my personal data and just went with flashing factoryfs.rfs recovery.bin zImage and that finally worked... I did notice one thing. When the phone booted up for the first time the voodoo lady said not enough space for the partition and then it hit me that I didn't disable voodoo before I made my factoryfs.rfs file on the phone... could this be the reason why my restore isn't working correctly? because odin is flashing rfs and I have a factoryfs.rfs which is actually ext4? I will let you know what happens.

Right now my phone boots up fine 2 ee4 gummy charge 1.75///
[Verizon Droid Charge] c0ns0le:
Clear cache and dalvick
[Verizon Droid Charge] distortedloop:
With that +1 offset, and the pit information in my post, would the proper commands to pull the EE4 modem/radio be the following:

dd if=/dev/block/bml12 of=/sdcard/lte_modem.bin bs=4096

dd if=/dev/block/bml13 of=/sdcard/cp_modem.bin bs=4096

I ask because in the other thread you're using block numbers that don't have an offset to the pit entry.

I have no faith the results will be flashable and working, but I'm in PM contact with a guy who's got the dreaded unknown modem issue and none of the suggestions, even reflashing the full leaked Odin package with modem in it, have fixed him up. This is kind of a last resort effort.
[Verizon Droid Charge] davpel:
Is there any chance that someone (much smarter than I) can make a script to automate this?
[Verizon Droid Charge] bcrider83:
Create EE4 ODIN Backup

is there any way someone can create a complete EE4 odin back up...I bricked my phone today and am trying to get back to working. I tried one of the two complete ODIN files in the sticky thread but it keeps erroring out, going to try again when I get home but that wont be till later tonight.
[Verizon Droid Charge] bash_array:
Flash my odin bundle.. its ee4
[Verizon Droid Charge] c0ns0le:
Just saw this, the bml devices mapped up in mine, am not certain on the bricked phone, how did he get to this state, haa anyone tried dd'ing a modem and look for boundaries or the output with a hex editor.
[Verizon Droid Charge] mms2020:
when I try to run from adb

dd if=/dev/block/stl10 of=/sdcard/factoryfs.rfs bs=4096

I get the following error:

/sdcard/factoryfs.rfs: cannot open for write: read-only file system

Any ideas what I am doing wrong? Thanks
[Verizon Droid Charge] cronosmachine:
I'm been looking how to create own ODIN rom.

What is the best console emulator to be use to execute those command?

Any apps can do this?
[Verizon Droid Charge] distortedloop:
Easiest way is adb shell. Hook up by USB and open a terminal window.

If you have to do it on the phone, any of the terminal apps should work. I use Better Terminal Pro on the phone.
[Verizon Droid Charge] artvandelay440:
Will this method work for the Fascinate as well? Just want to verify before I create a paperweight.
[Verizon Droid Charge] imnuts:
The method will work, but you need to use the proper device locations to dump from. Most things are just the current device -1. I think that cache is the only thing that really moved.
[Verizon Droid Charge] Boomwaller:
Creating a .tar

So I was able to run terminal on my phone and create the files, my question is how do you get them into .tar files didn't quite understand what you ment by

"To create a flashable Odin package, you need to pull all of the files off of the phone/sdcard and onto your computer. From there, you use the following to create the package:

Code:

tar -H ustar -c factoryfs.rfs recovery.bin zImage > package_name.tar

md5sum -t package_name.tar >> package_name.tar

mv package_name.tar package_name.tar.md5"

also sorry new to odin and Sammy products.