yashsingh1/xdaforums huggingface dataset:
[Nook Touch Themes and Apps] gwpurnell:
Not really an answer to your question because I don't have any Mobi files, but I thought I'd recommend the e-ink friendly version of the Kindle app available on this forum.

http://xdaforums.com/showthread.php?t=2268593&highlight=kindle+app

The interface is much easier to read than the one downloaded from the market.

I will, however, grab a couple of public domain mobi files from my daughter (she has a Kindle keyboard) and report back on whether it works or not. Other readers do work with Mobi but probably not with DRM files. Come to think of it, maybe that's why your GOT book isn't seen by the app.

---------- Post added at 04:04 PM ---------- Previous post was at 03:23 PM ----------

I've just downloaded a .mobi file from Gutenberg using Dropbox and can confirm that the Kindle app doesn't see it. FB Reader can read it very well, but it is a public domain non-DRM file.
[Nook Touch Themes and Apps] lekofraggle:
I am not sure kindles are used to side loading DRM content. Try going into settings and looking at the device name. Then, log into Amazon's website and send the files to the device.

That should work. Also, make sure the app is registered with the same account you used to purchase the books.

~Leko

Go forth and work toward your salvation with diligence.
[General Questions and Answers] Dan Law 001:
Hello, I don't know why when I insert my ext sd card in my Samsung Galaxy Note 2, it says that the SD:silly: CARD is blank or has unsupport filesystem. Therefore I cannot mount it with the phone. I then try to insert it into my ATRIX 4g, it does the same thing. However, when I insert it to my computer it mounts successfully. What is the problem?

Sandisk 32GB SD card.
[General Questions and Answers] abhi7395:
fat32/fat is supported format for smartphones...windows pc can recognize many file system but smartphone can't... :D

change sd card file system to fat/fat32 to use it on your note 2...
[General Questions and Answers] Dan Law 001:
I formatted it on my computer using the long method with fat/fat32 selected. I turned off my device, inserted it and powered it on and it works.
[General Questions and Answers] abhi7395:
CONGO !
[Verizon Samsung Galaxy S 4] h311sdr0id:
Hey all you devs. If your like me, youve been super-pissed about the VRUAME7 build and the fact that it wont work when making ROMs. I, with the help of scrosler (Scott from ScottsRoms.com), andybones (from BoneStock) and gatesjunior (DarkSlide ROMs) have figured out a cheap fix.

ALL credits go to gatesjunior, andybones and scrosler for this method. All I did was some reverse engineering and piecing together.

Because I have not recieved word back from gatesjunior, I will not post the boot.img needed to do this. You will have to download BoneStock or DarkSlide ROM to make this happen.

You Need:

1- a stock rooted VRUAMDK ROM

2- the VRUAME7 firmware unpacked into a WORKING FOLDER in dsixdas kitchen

3- DarkSlide or BoneStock ROM

Directions:

1. Download either BoneStock or DarkSlide, unpack and take out the boot.img.

2. Go into your WORKING FOLDER of VRUAME7 (this tutorial assumes you have download the VRUAME7 source and created a working folder for it in dsixdas kitchen)

3. In your VRUAME7 WORKING FOLDER, go to system/lib/modules

4. Now go into an old VRUAMDK stock rooted ROM, unpack it and go into the same system/lib/modules folder.

5. COPY all the files in the VRUAMDK system/lib/modules and PASTE them into your VRUAME7's working folder (system/lib/modules folder) and let them overwrite the files already in your VRUAME7 system/lib/modules folder (there are approx 23 files in the VRUAME7 system/lib/modules folder and 19 in the VRUAMDK folder, so you wont be overwriting all the files)

6. Pack your ROM and your good to go.

7. I didn't loki the boot.img. When I tried to unpack it in dsixdas kitchen, only a zImage was there.

8. GIVE GATEJUNIOR THE CREDIT HE DESERVES AND CREDIT HIM!!!

ALL CREDITS TO gatesjunior, andybones, and scrosler
[Verizon Samsung Galaxy S 4] Scott:
This is the same method I used on AT&T ;)

Glad it worked for you!
[Verizon Samsung Galaxy S 4] andybones:
Very nice, Sir!:)
[Verizon Samsung Galaxy S 4] pschatz12:
A Scott sighting!!!!!!! Cleanrom for Verizon?!
[Verizon Samsung Galaxy S 4] cj2566:
I wouldn't get my hopes up....
[Verizon Samsung Galaxy S 4] KappaAce2010:
Is this only for dev edition s4's?
[Motorola Atrix HD] aselker:
Since I installed my first custom ROM, my Atrix HD hasn't been able to charge while off: It just sticks at the bootloader-unlocked screen. I have tested this with several ROMs on several occasions, with several chargers. Any ideas?
[Motorola Atrix HD] audit13:
Do you experience the same problem with stock 4.1.2 roms? Does this happen with the phone off and connected to a computer and wall charger?
[Motorola Atrix HD] deeje00:
The ROMs basically won't let the phone stay off. Just kinda got to deal with it.

Sent from my PACMAN MATRIX HD MAXX
[Motorola Atrix HD] aselker:
I haven't tried any stock ROMs yet. It happened with 4.1.2 and 4.2, on both computer and wall power.
[Motorola Atrix HD] audit13:
I'm using Holoblur v.9 and it charges while on or off via my computer and wall charger without issue.
[Nook HD, HD+ Q&A, Help & Troubleshooting] seattlecard:
My Nook HD+ is completely bricked. I think I might be able to revive it, but would need some kind help from someone here on XDA.

Situation summary:

1. I was running the infamous 'LagFix' application on my HD+, and it hung. Manually rebooted, and it appears that the lagfix application deleted all partitions on the device. I cannot boot the device at all, except for using SD CWM. Same situation as this thread: http://xdaforums.com/showthread.php?t=2325101. Unfortunately it seems more and more of us are getting hit by the lagfix app issue in effort to improve speed on this device

2. I can still boot to CWM using an SD card (verygreen instructions). I have an ADB shell session that is successfully connected to the device.

3. Unfortunately, as mentioned all internal memory partitions appear to have been destroyed by the devious lagfix app. Thus - what I *think* I need help with is something similar to this thread (http://xdaforums.com/showthread.php?t=1570022) but with partition files for the HD+

The above is my assumption based on somewhat limited skill. I'm hoping someone can possibly help me out to revive my HD+ back to life, hopefully with the partition files and/or other advice. I don't care to ever run stock image again, but can supply S/N if needed. Thank you (fingers crossed!) for any help!
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
To verify if your partitions are borked, go to my HD/HD+ stock tips thread linked in my signature and read item 16. Since you have ADB working you can try backing up the partitions per my instructions.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Q&A, Help & Troubleshooting] seattlecard:
Thanks for the response, leapinlar.

I can confirm that the partitions are indeed borked:

~ # dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/factory.img

dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/factory.img

dd: can't open '/dev/block/mmcblk0p7': No such file or directory

~ #
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
The only thing I know to suggest is to use gdisk, available in the Nook Tablet forum, and I think used in that post you referenced, to rebuild the partition table. I have given you the layout in my thread. I have never actually done this so really can't help. But I know gdisk will display the GPT table for you. Maybe just fixing the table will get you out of it since the data is still probably there.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Q&A, Help & Troubleshooting] seattlecard:
OK thanks for your assistance and feedback. I will give that a shot later and see if I can get somewhere. If I am unsuccessful, would it be possible to boot a version of CM via the SD card to at least make the device usable?
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
Only if you can get /rom repaired. With it borked, the only thing it can boot to is recovery.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Q&A, Help & Troubleshooting] talha970:
any luck?

---------- Post added at 07:52 AM ---------- Previous post was at 07:07 AM ----------

is there any way we can get the partition images? or can you please show the partition table
[Nook HD, HD+ Q&A, Help & Troubleshooting] jbbandos:
Do you even have access to the EMMC? Mine only shows the uSD partitions, and shows them as mmcblk0p1 to p3. There is no mmcblk1. :(
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
How are you trying to see them? Fdisk does not work on emmc.
[Nook HD, HD+ Q&A, Help & Troubleshooting] jbbandos:
I know, I just checked in dmesg and also if /dev/block was populated with mmcblk entries. I assume that if the recovery kernel can't find the emmc than I won't also be able to find it using any other tool.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] fadentales:
Very very strange I've never seen this before, so I was just doing my typical day walking around at work and all of a sudden I feel my phone got hot, pulled it out of my pocket and it was stuck on boot screen. So I did a battery pull to get it back to the rom and it just stopped at the bootscreen, after that I tried a dirty flash, then a clean flash...all I see is a bootscreen never gets past it. Recently updated to new firmware 2 weeks ago and did notice it was strange when I flashed the GE Rom kept asking me to Install SU. Anyone got any idea how to fix this? Only issue i noticed was during the install of the rom i get a unable to mount /preload but besides that everything completes fine
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ROMANTiC KiD:
Use odin to go back to full stock, upgrade to MF9, do a factory reset, later root the device install recovery, do a full wipe install GE rom fix permissions. Report back on what happens. (Keep in mind this will wipe internal memory MAKE BACKUP!)

Sent from my SPH-L720
[Shield Original Android Development] agrabren:
ClockworkMod Recovery for NVIDIA SHIELD

* Full support for DPAD, as well as A/B buttons

http://goo.im/devs/agrabren/shield/cwm/recovery.img
[Shield Original Android Development] agrabren:
Changelog:

1.1:

* Fixed details to support official OTAs

1.0:

* Initial Revision
[Shield Original Android Development] :
Thanks once again for all of your work on Shield!
[Shield Original Android Development] Gnurou:
Just tested, seems to be working fine. Great job using the joypad and A/B buttons for control. Strangely the home button also moves selection up.

Rooting and backup have just become easier! :victory:
[Shield Original Android Development] agrabren:
That's because HOME always had a default action. I didn't replace those, but I may in the future.
[Shield Original Android Development] chaind:
Awesome... This works like charm!...
[Shield Original Android Development] glitchhawk:
awesome work buddy!! can't wait to flash this on monday when i get mine. any possibility of TWRP maybe in the future?
[Shield Original Android Development] wwjoshdew:
How to video will eventually come... Once I unlock my Shield. I eventually will...
[Shield Original Android Development] agrabren:
You mean my work has finally earned a wwjoshdew video? :)
[Shield Original Android Development] wwjoshdew:
HA! We just don't cross paths very often. And with the Evo 3D... You never got to release CM10! lol
[Shield Original Android Development] philwinkel:
Will this play nice with OTA system updates?
[Shield Original Android Development] agrabren:
It should, but I intend to verify this soon. I *may* modify it a bit so that any "automatic" updates require you to accept them instead of just silently updating, for those who root their devices and such, and don't want an OTA to blast it without being near a computer.
[Shield Original Android Development] wwjoshdew:
We NEED OTA RootKeeper to update to support 4.3... Then that wouldn't be a problem! haha. That restored root on my Prime MANY TIMES.
[Shield Original Android Development] agrabren:
Actually, it'd be trivial to modify CWM to maintain itself during an OTA (by preventing the flashing of the recovery partition) as well as to re-inject root on the device after the OTA.
[Shield Original Android Development] 1wayjonny:
Hello will you be releasing a stock recovery as well? Just in case we want to go back =)

I see you factory images only have boot & system at the moment.

Thanks
[Shield Original Android Development] agrabren:
Oh duh. Sorry, yes.
[Shield Original Android Development] 1wayjonny:
NP, looking forward to the upload. =)

Will the original recovery be posted here or where the system dumps are?
[Shield Original Android Development] agrabren:
With the system dumps. I'm going to do them tomorrow from work to ensure I get the exact right image. :)
[Shield Original Android Development] Unjustified Dev:
Any device trees ? I want to see about this device so I can dev I would love to save the money to order it. Should have this in about a month or two .
[Shield Original Android Development] agrabren:
I don't have functional dev trees up yet, but once I do, they'll be in github.
[Shield Original Android Development] Unjustified Dev:
Going to try to build twrp or cm-10.2 Idc if I dont have this device I love to develop. Could you explain the roth and thor stuff its a bit confusing?
[Shield Original Android Development] agrabren:
Roth = thor = roth = thor = roth = shield = thor = roth = thor

Yes, I want to stab my brain out with a pencil.

I've built TWRP, but because SHIELD uses NVIDIA DirectTouch, touch doesn't work. Hence the build of CWM I made (which also features a beautiful rotation feature, since the panel is native portrait, not landscape)
[Shield Original Android Development] aDigitalPhantom:
backing up to external sd seems to work.

update

I suggest using a standard name for flashing purposes, and it looks to me like most are using roth.
[Shield Original Android Development] PR0XIDIAN:
Thanks! Working great on my shield.
[Shield Original Android Development] glitchhawk:
i love this post lol! dont do it agrabren we need your brain intact :P
[Shield Original Android Development] aDigitalPhantom:
How about we just call it.......it.
[Shield Original Android Development] Sess:
flashed recovery to my shield. The root option doesn't work though, i went ahead and manually copied the superuser and su binaries. Everything is looking quite good now, thanks the build!
[Shield Original Android Development] agrabren:
The root worked fine for me, but it only installs the SU binary, not the SuperUser apk. You still need to install that from the Play Store.
[Shield Original Android Development] eman2001:
Can someone pls tell me how to flash CWM recovery on shield I have unlocked my bootloader but dont know how to flash recovery :(
[Shield Original Android Development] agrabren:
fastboot flash recovery recovery.img
[Shield Original Android Development] eman2001:
hey i would like to say that i flashed the system factory boot image then flashed CWM recovery again and it finally worked :laugh:, thanks so much for your help:good::D coudnt have done it without you, now i can finally root my device :)
[Shield Original Android Development] agrabren:
Yes, if you flashed before the OTA applied, the OTA would wipe out the recovery on you. :)
[Shield Original Android Development] joshspringer05:
everytime i go to flash a boot.img or recovery.img it tells me it fails and won't let me. any ideas?

Edit: Nevermind the usb cable nvidia sent with me would not work but my galaxy note 2 cable worked fine
[Shield Original Android Development] agrabren:
You should contact NVIDIA. The cable *should* work correct, as it's actually documented on their own Open Source site on how to do it. Sounds like you may have a bad cable.
[Shield Original Android Development] aDigitalPhantom:
With todays ota not flashing due the this recovery naming the shield thor, and the ota needing roth, I once again suggest to name shield in this recovery roth.

For now here it is with the modifed ramdisk to change the name to roth.

Modded version is here

The ota zip is here

agraben on request I will remove the links.
[Shield Original Android Development] johnnobts:
thanks, so I should reflash this custom recovery, then boot to cwm and update using the ota zip you've provided? just checking:)
[Shield Original Android Development] aDigitalPhantom:
Yes flash recovery first, if you have root and want to keep it without re-flashing a root.zip

The recovery img I posted works for me so far.

The ota zip is the same (unmoddified) zip the shield downloads for update 51. I uploaded it in case if the update failed using the unmodded CWM and was lost it could be re-downloaded easily.
[Shield Original Android Development] agrabren:
Yes, I've already fixed that in my local builds on CM-10.2, but unfortunately haven't had the time to upload it.
[Shield Original Android Development] aDigitalPhantom:
That's fine. I was just trying to make sure you knew, and maybe help someone.
[Shield Original Android Development] :
Kind of useless until we get some custom roms, but great for tweaks, thanks man!
[Shield Original Android Development] aDigitalPhantom:
Actually with the tweaks it will let you flash updates for the stock rom, and also backup/restore.
[Shield Original Android Development] wrc1010:
Success root my shield...
[Shield Original Android Development] themichael:
flashed and running great
[Shield Original Android Development] MakiManPR:
How to install this? How this works & what it do?

I'm new on this Android stuff
[Shield Original Android Development] dark42:
Get adb and fastboot installed and boot into bootloader, unlock bootloader with "fastboot oem unlock", then "fastboot flash recovery recovery.img" to install CWM.
[Shield Original Android Development] Polymira:
I'd love a root method without having to unlock the bootloader.
[Shield Original Android Development] dark42:
That does not exist, you have to unlock the bootloader in order to get root, with any method. That's how it is on the Nexuses and also here on the Shield. I'm just glad Google / Nvidia don't make it a pain for us to unlock.
[Shield Original Android Development] Evo_Shift:
Yeah, with how easy it is to unlock I doubt the hackers who are typically responsible for finding vulnerabilities in the ROMs would want to waste one on such an easy device. They probably like to save those for phones on Verizon.
[Shield Original Android Development] agrabren:
I've updated the recovery image on goo with a new build, which should fix the naming issues when applying an OTA.
[Shield Original Android Development] themichael:
for some reason I cant get this to flash right in fastboot, goes to a black blinking screen whenever I try to reboot into recovery.

OUDHS works fine though, could you make this a flashable zip so i can try and flash through that?
[Shield Original Android Development] aDigitalPhantom:
I don't think the zip will change anything I can't get the new version to work on my shield.

It does the same blinking black screen thing.
[Shield Original Android Development] agrabren:
Sounds like I f*ed it up. :( I'll take a look.
[Shield Original Android Development] wwjoshdew:
It's good to know I'm not the only one that had that problem.
[Shield Original Android Development] agrabren:
I've got it working again on my device, but need to put it through it's paces before I upload, since it's based on the new 4.3 tree.
[Shield Original Android Development] agrabren:
A new build has been uploaded! Should be fixed.
[Shield Original Android Development] themichael:
Works great. Much appreciated.
[Shield Original Android Development] Nikojiro:
Works for me too, thanks ;)
[Shield Original Android Development] Entropy512:
What's the md5sum of your 1.1 image?

The link in your post is giving me a recovery that results in assert errors when trying to flash update 59.

md5sum: 0cbcd13de85036c12d9370ee3afd9640
[Shield Original Android Development] agrabren:
I didn't add support for flashing blobs, which is what the official updates require.
[Shield Original Android Development] Eozik:
Question

Hi agrabren! Could someone provide me with info how to remove cwm from system, it's not allowed me to install latest update :(
[Shield Original Android Development] Entropy512:
Ah. I guess I misunderstood the changelog item for 1.1...

I'm curious now how nv_copy_blob_file works. :)

Eozik - http://xdaforums.com/showthread.php?t=2388870
[Shield Original Android Development] aDigitalPhantom:
does flashing blobs do more that just copy the blob to the USP partition?
[Shield Original Android Development] agrabren:
I honestly haven't looked.
[Shield Original Android Development] Entropy512:
It's interesting since the /staging partition is mounted as type "emmc" - which pretty much means "used for raw images".

I need to look at how updater-binaries and recovery interact here - it may be a simple matter of adding /staging to the fstab but I'm not sure.

I'm also curious if nv_copy_blob_file is implemented in the source tree NVidia pushed - haven't looked yet. If source code for nv_copy_blob_file exists, it makes things much easier. :)
[Shield Original Android Development] aDigitalPhantom:
the partition that /staging mounts is /dev/block/platform/sdhci-tegra.3/by-name/USP

as can be seen in the factory recovery's recovery.fstab

# mount point	fstype	device

/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/metadata emmc /dev/block/platform/sdhci-tegra.3/by-name/MDA
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA
/sdcard vfat /dev/block/platform/sdhci-tegra.0/by-num/p1

I would like to know if the line

nv_copy_blob_file("blob", "/staging");

can be replaced with this line

package_extract_file("blob", "/dev/block/platform/sdhci-tegra.3/by-name/USP");
[Shield Original Android Development] djGrrr:
This should work, you can always use fastboot though to manually flash it with:

fastboot flash staging blob

I actually did the update without updating the staging partition and it still worked fine, then later manually flashed the blob file with fastboot
[Shield Original Android Development] aDigitalPhantom:
http://goo.im/devs/agrabren seems to be gone.

This was a simple ramdisk edit.

I don't know for 100% sure if this recovery is 1.1, but if I am correct 1.0 was based on 4.2.2 and 1.1 on 4.3

From that I am guessing that this is 1.1, as to my knowledge there have been two recovery images so far.

Also I have been wrong about 1.1 solving the naming error.

I have edited the ramdisk for 1.1 now and it should work.

Link

device name from update 63

assert(getprop("ro.product.device") == "roth" ||
getprop("ro.build.product") == "roth");

name from 1.1

ro.product.device=thor
ro.cm.device=thor

name for edited recovery

ro.product.device=roth
ro.cm.device=roth

I also want to point out that I could be wrong here.

Link removed it seems to be broken
[Shield Original Android Development] desertflame:
Upload link is gone. Can someone upload their's for me?
[Shield Original Android Development] shinratdr:
I hope you were able to find it. If not, I located the copy I left on my computer. Enjoy! Hopefully OP doesn't mind me re-uploading it, its a pretty key part of a re-rooting.

http://cl.ly/2o3n3f0C0G2S
[Shield Original Android Development] :
Please anyone share information about how to remove CWM recovery in my nvidia shield? i want to remove it because its a old recovery and doesnt have support anymore
[Shield Original Android Development] UrbanRunnerX:
What version do you have

---------- Post added at 03:00 AM ---------- Previous post was at 02:46 AM ----------

Want to restore have you used the kit http://xdaforums.com/showthread.php?t=2444525