Database Develop

Possible to put stock image on sd card

I am on rooted 1.1 v2 and everything works great. The only thing missing is the in store reading free books for an hour a day. I was wondering if I could boot stock BN image on sd card when I am in the BN store, so I could get the in store feature?
I have been reading a lot and many people with 1.1 v2 cannot get access to the free one hour reading. I am a newbie, so alot of android dev forum is a little over my head.
If anyone knows of another way to get in store reading, I would appreciate the help.

Not a bad question. In theory i bet its possible. Id love to have an sd for stock use....
Sent from my Nook Color (zoom2) using Tapatalk

I just want it for in store reading.

Why no one has thought of this before I have no idea, but its a Great Idea, Count me in if they can come up with this, maybe some high and mighty dev will come by and hear our pleas.
It would be great to have the Free Reading and to get books on free book Friday, Also i think they have in-store coupons.

therealguppy said:
Why no one has thought of this before I have no idea, but its a Great Idea, Count me in if they can come up with this, maybe some high and mighty dev will come by and hear our pleas.
It would be great to have the Free Reading and to get books on free book Friday, Also i think they have in-store coupons.
Click to expand...
Click to collapse
I believe it was tried previously, but there's things in the stock ROM that have hard coded reference points to parts of the system (if memory serves). The person trying to do this early on gave up for that reason. I could be wrong, but I think this was in mid December.

I was getting ready to ask this question when I found your thread. I really hope something like this does pop up in the Dev section - I'll use my nook daily with a custom froyo rom, but it would be nice to be able to use the stock image off a SD when I stop into a B&N.

Well, in theory it's quite easy to do. Read the entire post before attempting the trick.
As usual, I'm not responsible if your NC starts speaking Flemish. Be careful with your Internal partitions!
Requirements: stock on internal, gparted, maybe my UMS utility (DEV), an SDCard (8GB at least, to be safe), a few minutes.
Partition an SDcard following stock layout.
You can partition the SD by using gparted. Create a new partition table, then create the partitions. Then apply. Don't forget to use "round to cylinder" and always leave a 1mb space at the beginning of each partition (except boot). Or else, you'll end up with corrupt partitions, writing over one another. Partition size can be changed, just make sure they're big enough..
Make sure the first partition has the bootable/boot flag.
To print the layout, use ADB command "fdisk /dev/block/mmcblk0 -l".
Or search for the layout in dev forum.
Layout looks like this (by heart, so check):
(Primary: )
p1: boot = FAT32 ~70 MB
p2: rom = FAT32 ~70 MB
p3: factory = ext2 ~??MB (this can left at 1mb, its a recovery partition, no use here)
p4: extended (not a partition strictly speaking, it's an extension)
(Logical: )
p5: system = ext2 ~470MB
p6: data = ext3 ~900MB (this can be bigger, app data storage)
p7: cache = ext3 ~350MB
p8: media = media FAT32 ~5GB (this can use all the remaining space, as big as you can/wish: media storage, books, films)
Then, you'll need to copy partition contents onto the SDCard's newly created partitions.
The easyiest way of doing it is by making .tar files of internal partition contents and extracting the files onto the SD partitions.
To create the tar files:
- either use <tar XXX.tar *> adb command on each partition, make sure you compress the actual content, not the container folder (i.e tar system content and not system, the * in the command stands for all content). Then pull the tar file. Delete it afterwards from internal!
- OR, probably more user friendly, use my USB mass storage utility found in DEV, mount each partition and create tar files with your usual UI (Ubuntu, Windows, OSX).
Copy every tar file onto your PC.
Tar files of internal partitions aren't all mandatory, all depends on if you want to make a complete backup of running stock rom, or if you just want the general stock rom on an SD. For instance, cache and media can be ignored, if you just want a general version. If you want to backup your media, tar media as well.
Then, extract each file onto the corresponding partition of you partitioned SD. Delete .tars afterwards from SD partitions.
THEN: download attached file, erase uRamdisk from you SD's boot partition and replace it with the one in the attached zip file (rename SD-STOCK-uRamdisk to uRamdisk). Without this step, your SD will boot from system and data internal partitions.
This uRamdisk has adb activated, so you should be able to push files to the SD once booted. Some internal commands won't work though (i.e, mount). You'll have to install busybox and root (su) the system, well if that's your goal that is.
Then insert the SD and boot.
In theory, this should boot up to stock from SD.
I could be missing something, it's late here, and I haven't tried any of this.
Beware: recovery, even from SD, will affect the internal partitions! Maybe it's best you delete uRecRam and uRecImg from your SD's boot (NOT INTERNAL!).
NB: you need to edit vold.conf. See second page of this thread.
Note: you could also use 'dd' command instead of making tars, but you'd end up with huge .img files.
PS: If you have no way of accessing your SD partitions once they're created, use the following command from ADB while booted from working internal system, with SD inserted in NC:
echo /dev/block/mmcblk1 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
This last command should open every SD partition in you PC's explorer.
Sam

I don't see the point in asking a question if you're not interested in the answer...
Sent from my HTC Desire using XDA App

samuelhalff said:
I don't see the point in asking a question if you're not interested in the answer...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I for one appreciate it, but missed that reply. I'm going to need to stockpile some microSD cards for all these various things to try .

I tried these instructions and it boots to the initial setup screen. I can see broadcasting AP's, but unfortunately I can't get it to connect any WiFi hotspot.
It appears to associate, sits at obtaining IP, but eventually gives up.
ADB connects and I was able to look at dmesg, but nothing stands out.
I went back to the eMMC and registered, exported /data, imported it to the SD card, and was able to bypass registration. However, it still doesn't connect to WiFi.
Only point that is probably worth noting is that I used a 2GB SDCard and here's what my mount output looks like:
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk1p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk1p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk1p6 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block//vold/179:17 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
Any ideas?

Success
I could follow the instruction and made a 8gb stock bootable micro sd card. Only problem I can see is it mounts the boot partition of sd card as "/sdcard" and creates few folders like "B&N Downloads", "My Files". Is there any way to disable the sd card mount.
If anyone is interested in getting a copy of the sd card I can upload.

pbcal said:
I could follow the instruction and made a 8gb stock bootable micro sd card. Only problem I can see is it mounts the boot partition of sd card as "/sdcard" and creates few folders like "B&N Downloads", "My Files". Is there any way to disable the sd card mount.
If anyone is interested in getting a copy of the sd card I can upload.
Click to expand...
Click to collapse
I'm interested in it, or at least a "dummies guide" to doing this via a Windows PC..
I mean, as I read samuelhalff's post, it looks like it should be relatively easy to follow, but I have a few questions...
I see things like creating the partitions on the SD using gparted (which appears to be a linux command) so I don't know if I can maybe use EASEUS in Windows do do it? And am I reading it correctly, that TAR is a command I can run from inside an ADB SHELL? (i.e. type ADB Shell, then TAR)

I'll upload it tonight and post the link.

pbcal said:
I'll upload it tonight and post the link.
Click to expand...
Click to collapse
only reason that might not be a good idea is copyrights... not sure what if any might make it against the rules here, or something B&N would frown upon... then again, I guess its no worse than the .ZIP image in the recovery threads?
In any case, Thank you!!! I do appreciate it!

pbcal said:
I could follow the instruction and made a 8gb stock bootable micro sd card. Only problem I can see is it mounts the boot partition of sd card as "/sdcard" and creates few folders like "B&N Downloads", "My Files". Is there any way to disable the sd card mount.
If anyone is interested in getting a copy of the sd card I can upload.
Click to expand...
Click to collapse
I eagerly await this...and thank you for the work. I would use this as a dual-boot SD card with my daily-use ROM installed to internal memory. There are fairly easy-to-follow directions here on xda that will allow us to dual boot your SD card and internal memory. If you choose to boot from internal memory, then the SD card just becomes your external storage. No SD card swapping needed to go between your daily OS and the B&N stock. Very cool.
Thanks again.

You're welcome..
Sent from my Desire HD using XDA App

I'd love to get this as well. I had a 1.1 rooted stock which didn't give me the free hour in the store laast weekend. Sort of bummed as I heard it worked for some people.
Dan
Sent from my NookColor using Tapatalk

As I mentioned above, this would be great for dual-booting from eemc and sd card. I messed around with this a bit this evening and got it working nicely with one of the old Honeycomb images. The instructions for setting up dual boot are here:
http://forum.xda-developers.com/showthread.php?t=947698&highlight=dual+boot
I did have to mess around with the SD card a bit as once you boot from the internal memory, it is the first partition of the SD card that is used as your SD storage. Most SD card images have this as a very small boot partition with the fourth partition the larger SD card partition. I used a free program called Parted Magic to move the second, third, and fourth partitions over and expand the first partition into the unused space, creating a 5GB boot partition. I then put the multi-boot files from the thread above into the large boot partition. Worked like a charm - when booting from the SD card, Honeycomb used the fourth partition as the SD card storage space. When booting from internal memory, CM7 (the ROM I have installed to internal memory) used the 5GB boot partition as the SD card storage space.
Eageraly awaiting someone to build this and post an image file. I will admit that I am not smart enough to carry out the lengthly and excellence directions posted by samuelhalff.

Here is the link for the image. You will need a 8 GB or higher SD card.
Sorry for the large file. It has all partitions with stock data except data, cache and media.
Post your results / issues.
[COLOR="Red"][B]Removed[/B][/COLOR]
Click to expand...
Click to collapse

To avoid having /sdcard mounted on boot, you need to edit /system/vold.conf :
Code:
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 8
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}
volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
Add "partition 8" in the sdcard section.
Explanation: see, media is set to partition 8 of internal. That's right. But here, sdcard will mount automatically the first sdcard partition (boot), as partition isn't set. You need to manually set it mount partition 8 (sdcard)..
Sam

Need help rebuilding emmc

Ok fellas, my nook color has been out of commission for over 2 months. I can boot from sd but not from internal emmc.
Sam has been helpin me but it has been difficult due to him being in a different part of the world. From what i've been told my emmc is corrupt and my partitions need to be rebuilt or formatted.
I have tried the different fixes here and still i am stuck on the N screen.
I am trying to return my NC to stock form.
I will let Sam chime in also. I know there are a lot of talents on this forum and pretty sure this can be fixed.
Thanks everyone..
Sent from my SGH-T959 using XDA App

Hi,
As Wendell said, I've tried helping him with his corrupt emmc.
The problem is:
The emmc semms to be corrupt, or at least some sectors of it. Wendell cannot return it, because it boots to CWR. That's the strange part, though the disk seems totally corrupt, it still seems to be able to boot. I guess some sectors and still working. But I don't know of any way to find out which..
This is what I know so far:
The internal emmc generally returns I/O error when trying to use fdisk or parted.
But, somehow, depending on the bs and count, I can dd /dev/zero to it.
Even after having dd zeros to it, it still seems to boot to internal CWR. So, the dd isn't working. Still don't know why, or how to remedy to it.
If someone could give us a clue or two here, it would be very much appreciated. I must admit I'm really no HDD expert..
Thanks!!
Sam

http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?

Any idea how the partition became corrupt? Did you dual-boot?

Partition became corrupt after flashing a couple of the very first OC kernels. Not sure if thats what caused it but wouldn't boot past N screen. Since then i have been trying to fix it by doing the several fixes to no avail and possibly damaging the emmc even more.
Sent from my SGH-T959 using XDA App

fprice02 said:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?
Click to expand...
Click to collapse
Please correct if I'm wrong but i think i need the stock recovery for this method. Unfortunately, the stock was replaced with CWR and now i cannot even get rid of CWR off the internal. If I could do it again, I would not place CWR on internal but rather run it off sd. I installed CWR via rom manager because the sd method was not yet available.

Try option number 3 in the thread I made in the general forum. the clockworkmod recover + stuck at " " screen. Flashing cwm via rom manager can cause corrupted /boot partition
Sent from my Vortex using Tapatalk

Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.

Excuse my ignorance, but will linux run off the sd card on the nook?
What about using something like GParted? Perhaps the USB bootable image on the sd card might work?

I know you are all trying to help. But please keep in mind that there aren't any obvious answers here. The emmc is corrupt. You can't flash anything to it.. and as I already stated, parted won't work either, it returns I/o error.
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
We need someone with hdd repairing experience. None of the answers found on existant threads will help Wendell..
Thank you.
Sam
Sent from my Desire HD using XDA App

samuelhalff said:
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
Click to expand...
Click to collapse
The boot may be from real hardware/non-eemc rom.
I know you said it's a emmc error - but have you tried to flash back to stock using CWM off of the SD with thecubed's MonsterRoot pack?

Yes
Sent from my SGH-T959 using XDA App

I'm sure you have tried this... but just in case...
Can you fdisk the partitions... then dd image img files to it?
I don't know if you will have any way of saving mmcblk0p2 and 3 to save your device specific information.

I believe sam has already tried
Sent from my SGH-T959 using XDA App

Here is what i would try.
First thing, get a cwm sd card setup that is bootable and has a decent amount of space so you can backup your emmc. The cwm sd card will allow us to adb in, but not worry about having any emmc partitions mounted (booting to a full android image would want at least the mmcblk0p2 partition mounted).
Make sure you have adb setup and working, so you can adb in once you've booted into cwm from the sd card. Make sure you know how to use adb pull and adb push to get files onto and off of the device easily.
Boot from the card, adb shell into the device. make sure when you are doing dd commands you are pulling from and writing to image files in a directory on the sd card, not on the emmc. you probably shouldn't even have any emmc partitions mounted at all.
Note: dd and bzip2 are both on the cwm 3.0.10 ramdisk, dunno about the earlier versions
I'd make a backup image of your emmc just in case things go from bad to worse:
Code:
dd if=/dev/mmcblk0 | bzip2 -9 > backup.img.bz2
This will take a while.
Now you'll need a MBR from someone with a stock partition table (i'm dual booting so mine probably won't work, otherwise i'd make one for you). Any volunteers?
Code:
dd if=/dev/mmcblk0 of=mbr.img bs=512 count=1
Once you have this file, just dump the image onto your emmc.
Code:
dd if=mbr.img of=/dev/mmcblk0
once you have a working partition table, you should be on your way to using the standard recovery techniques peppered throughout the forums.
btw, this won't fix any corruption in the extended partition table, that would take a little more effort (i'd have to read up on where/how that info is saved). Also obviously if it's a hardware problem rather than just corrupted data you have more problems than this will fix.
p.s. cwm loading witch a corrupt partiton table isn't that weird imho. the bootloader has barely over 400 bytes to load up the boot file and hand things off, it's probably not taking a close look at the partition map when it does this.

I know am probably being a stupid noob...have you tried the 8 failed boots?
Sent from my NookColor using Tapatalk

wendellc said:
Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.
Click to expand...
Click to collapse
Again..probably being a noob...are the file permissions set as ro? Mayhaps you need to change permissions?
Sent from my NookColor using Tapatalk

Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App

samuelhalff said:
Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Did you read my post? It is exactly telling you how to replace the first sector of the emmc. you can source it from /dev/zero with a bs=512 and a count=1 if you really wanna wipe the bootloader, but better would be just getting it working yeah? all our nooks have the same partition map (unless we are dual booting) and that map is stored on the first sector. My instruction tell how to pull the first sector with dd, and how to push it back on. notice i'm accessing the mmc directly? not the partitions? so unless his hardware is bad (or the extended partition is corrupt too) then my instructions will work. He just needs a copy of the first sector of a working nook. I'd put mine up but i'm not sure it would work, i have two extra partitions from stock. It probably wouldn't matter, but i'm not 100% sure on that, so i'd rather it be someone else that makes the image from a nook with a stock partition map (the contents of the partitions can be whatever, as long as they are all in the same place as stock).

Hi,
Thanks. Yes, I read your post. dd, for some reason, only works if I set bs to at least 1M. I don't have the NC, but maybe Wendell could confirm that.
Wendell: go to "adb shell" and type [dd if=/dev/zero of="/dev/block/mmcblk0" bs=512 count=1] without the [].
Please confirm that this returns an I/O error.
But for some reason, using 1M or greater as bs works, but the bootloader still isn't erased.. it still boots to CWR..
I'm pretty sure all the I/O error i've had mean that there's a hardware failure.. But that's my opinion, nothing more..
Thanks.

[Q] 8 interruptions doesn't work - install failed___UPDATE I am back to 1.1.0

My nook color is back to 1.1.0 now. I want to say thank you to all of you guys for helping me out. It was such a great experience here and I really appreciate it.
What happened is that Joja15 helped me to create the missing partitions, and then something miraculously happened during charging: it just booted all up to 1.1.0, which I had on emmc before it got stuck. I could never have done this on my own without the help. Thank you so much Joja !
Liz
This is how it was done after you have adb working:see the original thread here:
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(1) Connect Nook to PC
(2) Boot Nook into CWM off of uSD card.
(3) Verify ADB is connecting to nook by issuing the command:
adb devices
(4) If you see a serial number you are connected. Next go into adb shell by typing:
adb shell
(5) Before going any further we will want to back up your partitions 1-3 as they contain important unique information for your nook like the serial number. Make sure you 450mb of free space on your SD card.
(6) Issue the following command to backup your mmcblk0p1 boot partition to your SD card.
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1-boot.img
(7) Issue the following command to backup your mmcblk0p2 rom partition to your SD card.
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2-rom.img
(8) Issue the following command to backup your mmcblk0p3 factory partition to your SD card.
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3-factory.img
(9) Once your first three partitions are backed up in adb shell go into fdisk by typing:
fdisk /dev/block/mmcblk0
(10) Upon issuing the fdisk command you should see the following:
Command (m for help):
(11) Type m to get the help menu:
m
(12) You should see the following:
Command Action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
(13) We will use the above commands to recreate our partition table. First lets see what our current one looks like. Issue the print command by typing:
p
(14) You should see the following but probably will not because your partition table is screwed up what is listed below is what you will want to see once you have recreated your partitions:
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
/dev/block/mmcblk0p8 282 935 5253223+ c Win95 FAT32
A)
(15) We will need to first delete the partition #4 using the d command. Enter d and it should ask you which partition to delete. You will want to select or enter the mmcblk0p4 one or the #4 partition. I entered "4".
(16) Now that it is deleted we will want to create the #4 partition fresh. Issue the following command to create a partition:
n
When you enter the n command it will ask you questions like the start, the end, and the type of partition. Use the information in the print out above to enter the correct information. After you create a partition use the print command "p" to look at the partition layout and make sure that it matches the above for the new partition you created. If it does not delete the partition and create it again with different settings until it does. I tried this step several times before it was done in the correct way
(17) Use the n command to create partitions 5,6,7, and 8. Same as partition 4, it took me several times to get this done.
After that step I got a very similar layout as in step 14, but not exactly the same.
So I took the SD card out and planned to charge the NC. And that is when my nook color booted all up to rooted 1.1.0.
Hi, I am new here. Please talented people hear me out.
What happened to my NC is that I have it rooted by auto no, and CM7-ed, and it's been amazing. (Thanks to all of you guys!)
But one day, 2 days after RC4 I messed up somehow. Now my nook color won't boot right, it stuck at the n screen forever, if I don't hold the power button to power it off. I tried a lot of things here on this forum. Most of the time I get this error msg: can't mount /cache, can't format /system, install aborted......
So I removed CWR, then try to use the 8 interruptions plus the N+POWER key. It always give me the install failed msg after it started to install. I've tried to power it up after this and nothing changed. I have tried this for more than 10 times, crying now, any advice will be appreciated!

Launch cwr from SD, and use adb:
fdisk /dev/block/mmcblk0 -l
And print the output here.
Sent from my Desire HD using XDA App

ktan said:
So I removed CWR, then try to use the 8 interruptions plus the N+POWER key. It always give me the install failed msg after it started to install. I've tried to power it up after this and nothing changed. I have tried this for more than 10 times, crying now, any advice will be appreciated!
Click to expand...
Click to collapse
Do as Sam pointed out... however... the 8 failed reporting install failed is not a real uncommon item.
Even though you get the install failed message... power off by holding power button... holding "n" button... power on... keep holding "n" it should boot to factory clear... do the clear... then it will (probably) boot normally.
After that... there are things we can do to fix the 8 failed boots...

Thanks for the reply.
I will try this after work today then update here.
samuelhalff said:
Launch cwr from SD, and use adb:
fdisk /dev/block/mmcblk0 -l
And print the output here.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse

I did this power + "n", and did the factory clear. When it's done the NC automatically reboot, then it stuck at N as always
What is next then?
DizzyDen said:
Do as Sam pointed out... however... the 8 failed reporting install failed is not a real uncommon item.
Even though you get the install failed message... power off by holding power button... holding "n" button... power on... keep holding "n" it should boot to factory clear... do the clear... then it will (probably) boot normally.
After that... there are things we can do to fix the 8 failed boots...
Click to expand...
Click to collapse

I get this:
C:\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # fdisk /dev/block/mmcblk0 -l
fdisk /dev/block/mmcblk0 -l
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
~ #
samuelhalff said:
Launch cwr from SD, and use adb:
fdisk /dev/block/mmcblk0 -l
And print the output here.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse

If you have the cwr working from sd, just download the latest cm7 and place it on the sd card. Boot from the sd to cwr and choose install zip from sd card, install the cm7 zip you just downloaded.
Sent from my DROID2 using XDA App

If thats all you have on your emmc, then 4 partitions are missing.
Could someone help him rebuild the partitions using fdisk or parted, based on the stock layout? I don't have time right now.
Rebuilding of system, data, cache and media is needed.
What have you done to mess with partitions? Dual-boot?
See this thread for what you're supposed to print with fdisk: http://forum.xda-developers.com/showthread.php?t=942324
Sam
Sent from my Desire HD using XDA App

I've tried stuff here and there, after got stuck at n screen. Not dual-boot I think. Now I know what I have messed up
Thank you for the reply. I am going to study that thread.
And please, any help from you guys will be great.
samuelhalff said:
If thats all you have on your emmc, then 4 partitions are missing.
Could someone help him rebuild the partitions using fdisk or parted, based on the stock layout? I don't have time right now.
Rebuilding of system, data, cache and media is needed.
What have you done to mess with partitions? Dual-boot?
See this thread for what you're supposed to print with fdisk: http://forum.xda-developers.com/showthread.php?t=942324
Sam
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse

I've tried to install from zip file (stock). It just say install aborted. As you said, maybe i should try CM7 instead.
juvetch said:
If you have the cwr working from sd, just download the latest cm7 and place it on the sd card. Boot from the sd to cwr and choose install zip from sd card, install the cm7 zip you just downloaded.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse

How can you flash anything..? You don't have the appropriate partion layout..
You need to add the 4 missing partitions..
You should use parted (adb command). But if you have no clue and wish to use a GUI.. read the following, but I wont be held responsible for any damage..
If you choose to try, it's your responsibility all the way.. read the thread entirely before you attempt anything.
If you want repartition using a GUI on Linux, you can use a live cd:
For the following I would use gparted (linux disk utility). You can find a lot of info on Google if your not sure. Easiest is to use an Ubuntu.live CD and launch gparted.
- First with ADB:
- Boot with a bootable CWR. Once booted:
- then: echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
- The last command will mount your entire internal 8gb partition to your PC
Open Gparted:
- Select the 8GB drive (top right)
- you should see the4 existing partitions, with the extend at the end, on which you'll create the four missing partitions (system, data, cache and media, in that order)
- Unmount all partitions.
- Add the missing partitions starting with system, right after the extended partiton, find stock layout as an example and for partiton size references (from memory around 500 MB, then 900MB, then 350 and then 5GB, but find the exact size!)
- WARNING: every time you create a partition, make sure you choose round to cylinder and not MB, PLUS make sure you always leave a 1MB as preceding space, except for first partition (boot). If you don't follow this last recommendation, you'll end up with partitions writing over one another = corrupting partitions... Always leave a 1MB free space preceding.
- Finish by applying settings (nothing will be written to the disk before you apply). Then unmount the drive and reboot to cwr SD.
After that you can flash any rom to your nook to get it to boot again..
If you want to use command line partitioning, use fidsk/parted. Google it.
Again, if you attempt any of this, keep in mind you're playing around with the internal memory. IF anything goes wrong, you'll be left with sdcard booting only. But you'd really have to make a big mistake to get screwed.
And take time to check each step.. Instead of having to go through the process twice..
Sent from my NookColor using Tapatalk

Sam,
Thanks for all these input...
You are right. I am too stupid to see the truth I don't even have the right patition at this moment. I might go ahead start from parted. Need some serious reading before I screw up further more.

See this post in same thread Sam pointed earlier... it has a 7z copy of the partition 4 (mmcblk0p4) that will correct the other partition structures... then the 8 failed should work... it did on the one I was helping in that thread.
http://forum.xda-developers.com/showpost.php?p=12674635&postcount=18

I found my problem very similar to JoJa15.
When I check my recovery by this:
in adb mount mmcblk0p3 to /emmc and list its contents:
adb shell
mount /dev/block/mmcblk0p3 /emmc
ls /emmc
I found I have only two files:
ls /emmc
factory.zip lost+found rombackup.zip
~ #
This is different from what JoJa15 has. I did read on, but really hesitant to follow the posts after that before further guidance......I am afraid I will mess up with something again. So please tell me what to do next? I am so happy now, this seems to be going somewhere. Many many thanks!
DizzyDen said:
See this post in same thread Sam pointed earlier... it has a 7z copy of the partition 4 (mmcblk0p4) that will correct the other partition structures... then the 8 failed should work... it did on the one I was helping in that thread.
http://forum.xda-developers.com/showpost.php?p=12674635&postcount=18
Click to expand...
Click to collapse

ktan said:
I found my problem very similar to JoJa15.
When I check my recovery by this:
in adb mount mmcblk0p3 to /emmc and list its contents:
adb shell
mount /dev/block/mmcblk0p3 /emmc
ls /emmc
I found I have only two files:
ls /emmc
factory.zip lost+found rombackup.zip
~ #
This is different from what JoJa15 has. I did read on, but really hesitant to follow the posts after that before further guidance......I am afraid I will mess up with something again. So please tell me what to do next? I am so happy now, this seems to be going somewhere. Many many thanks!
Click to expand...
Click to collapse
Those are the only 2 files you should have on mmcblk0p3.
If you dd mmcblk0p4 file I provided in that thread... it will fix mmcblk0p5-8 and the 8 failed shoule work.... since the partitions will exist and be properly formatted.

Just be careful of you where you DD to. And make a DD image of 02 (rom) before you try anything..
Sent from my Desire HD using XDA App

samuelhalff said:
Just be careful of you where you DD to. And make a DD image of 02 (rom) before you try anything..
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'd also make DD image of 03.

Factory.zip is general and rom backup would be done with /rom..
But yeah, your never too careful..
Sent from my Desire HD using XDA App

I tried this
Code:
~ # dd if=/sdcard/mmcblk0p4-logical.img of=/dev/block/mmcblk0p4
dd if=/sdcard/mmcblk0p4-logical.img of=/dev/block/mmcblk0p4
dd: can't open '/sdcard/mmcblk0p4-logical.img': No such file or directory
~ #
I am definitely not doing this right.......
DizzyDen said:
Those are the only 2 files you should have on mmcblk0p3.
If you dd mmcblk0p4 file I provided in that thread... it will fix mmcblk0p5-8 and the 8 failed shoule work.... since the partitions will exist and be properly formatted.
Click to expand...
Click to collapse

Please bear with me coz I am really not familiar with adb.......
Could you please walk me through the steps right after this? Thanks a lot, I really appreciate it.
DizzyDen said:
Those are the only 2 files you should have on mmcblk0p3.
If you dd mmcblk0p4 file I provided in that thread... it will fix mmcblk0p5-8 and the 8 failed shoule work.... since the partitions will exist and be properly formatted.
Click to expand...
Click to collapse

[Q] mmcblk0p2 corrupt?

Hi everyone and thank you for being so active on this forum.
I want to apologize in advance as this post may be (yet) another "bricked" Nook kind of post. Although my situation seems interesting for whomever is looking for this type of intellectual challenge.
I think I read as much as I could but wasn't able to find anything yet that would be similar to what I'm experiencing.
First a bit of history: bought a Nook color (refurb), like new, running 1.2 stock. I was able to start it, set it up and register to B&N, no problem.
Created a CM7 (7.0 to start with) on SD, work great.
Created a 7.1 on SD. I could get pretty much anything running except CWM and WIFI. Now, trying to fix wifi, and I guess also CWM, I obviously messed up and the Nook would not boot anymore on SD.
Tried to boot on emmc … not working anymore. So, I messed up even more than I thought.
Tried to restore to stock 1.2 on emmc (using a formatted SD 1g w/ CWM 3.2.1) and at reboot, it fails with a "ipod-like" icon "Failed to install" message.
Tried to restore to 1.0.1 stock. The Nook will boot but when I go through the setup/register process, it fails after the wifi connection settings with an error telling me to call B&N support. When I look at Device Info at this point, it says "Serial number / Model / MAC" are missing … hmmm.
Now, I tried to recreate a CM7 on SD but the process fails at the end with a message:
init: Mount returned errno=19
FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev mmcblk0p2.
init: Mount returned errno=22
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
and reboot over and over.
Where I stand right now. I was able to install nookie froyo on emmc. Works (kinda). And I'm trying all I can to fix my issue which I suspect to be with /dev/block/mmcblk0p2 as I get the message in dmesg and the stock 1.0.1 would tell me that serial / mac are missing.
I have adb running. With nookie froyo running, I can get into the Nook and mess around. I'd like to try some e2fsck but can't find the tool for froyo.
Before that and before I try again with CM7, I'd like to have (smart) people ideas about this problem.
Any suggestion is welcome!
Thanks for reading.

Sorry to bother. Any idea anyone? It really looks like a problem with /dev/block/mmcblk0p2. The 8 failed restore process won't work as it's obviously not able to mount mmcblk0p2 on to /rom.
I tried manually doing a bunch of repairs but nothing will work. The mount gives me a:
mount -o dev /dev/block/mmcblk0p2 /rom
mount: mounting /dev/block/mmcblk0p2 on /rom failed: Invalid argument
I know that this partition contains device specifics but would anyone have something to share so I could dd into it to see if this is my problem?
Thanks anyway.

solution
All right,
I got it! For the community if anybody runs into the same problem, here is the story.
So, /dev/block/mmcblk0p2 was definitely corrupt. I had to use parted to fix it.
Using parted, this particular partition would not show as "fat32" as it should. I created a FS on this partition (using the mkfs sub-command). It erases everything in this partition but at least it fixes the corruption. After that, I was able to mount it over /rom. It as empty of course.
Restoring a 1.0.1 stock then trigerred the factory reset that I wasn't able to trigger before (the Failed install message) and now I'm able to reboot and go through the setup/registration process again. wow, not fun for a first pb.
Next step, update to latest stock and then will redo my CM7 testing on sd.
Thanks everyone for listening ;-)

mmcblk0p2 error
Thanks, you saved me a lot of time.

[Q] dead mmc -- ideas?

I've been having a grand old time tinkering with my new TF701t. I unlocked the bootloader, tried a few ROMs, went back to stock, and I've been busily playing with it. Earlier this evening, it spontaneously shut down. I booted it back up and it shut down again after 5 minutes. I went into recovery and flashed the xposed disabler zip just in case xposed was to blame, but it shut down from recovery. Now it won't boot at all.
I can connect via ADB in recovery, and when I run dmesg, I see all sorts of nasty mmc0-related timeouts and errors. I can't even mount /system anymore. It's pretty clearly either an issue with the internal memory card or with the bus.
Does anyone have any idea how I can fix this or get it fixed? Of course, with an unlocked bootloader, I'm sure ASUS is going to give me all manner of grief and probably refuse to repair/replace what is clearly a hardware failure. Does anyone know if there's any way at all of replacing this kind of mmc card, or is it just part of the SoC? How screwed am I?
EDIT: Not screwed at all! See my post on page 2 for a fairly simple procedure to boot and run the tf701t (and quite probably many other devices) completely off of the SD card.

lexelby said:
I've been having a grand old time tinkering with my new TF701t. I unlocked the bootloader, tried a few ROMs, went back to stock, and I've been busily playing with it. Earlier this evening, it spontaneously shut down. I booted it back up and it shut down again after 5 minutes. I went into recovery and flashed the xposed disabler zip just in case xposed was to blame, but it shut down from recovery. Now it won't boot at all.
I can connect via ADB in recovery, and when I run dmesg, I see all sorts of nasty mmc0-related timeouts and errors. I can't even mount /system anymore. It's pretty clearly either an issue with the internal memory card or with the bus.
Does anyone have any idea how I can fix this or get it fixed? Of course, with an unlocked bootloader, I'm sure ASUS is going to give me all manner of grief and probably refuse to repair/replace what is clearly a hardware failure. Does anyone know if there's any way at all of replacing this kind of mmc card, or is it just part of the SoC? How screwed am I?
Click to expand...
Click to collapse
See if you can mount /cache or /data. If you cannot then you have royally messed up your tablet. If you have replaced the recovery to something other than the original asus recovery then your best bet is to buy a logic board from ebay and replace it manually yourself.
I took mine to asus repair center and they said they will charge 200$ and 3 days to replace the logic board. I managed to buy the part for 70$ and do it myself. Just a side note, I bought and item that was AS-IS, so I am glad mine worked.

devbro said:
See if you can mount /cache or /data. If you cannot then you have royally messed up your tablet. If you have replaced the recovery to something other than the original asus recovery then your best bet is to buy a logic board from ebay and replace it manually yourself.
I took mine to asus repair center and they said they will charge 200$ and 3 days to replace the logic board. I managed to buy the part for 70$ and do it myself. Just a side note, I bought and item that was AS-IS, so I am glad mine worked.
Click to expand...
Click to collapse
Thanks for the tips!
It's quite weird. I booted it into recovery, and via adb I was able to mount /data fine and poke around. I unmounted, then mounted /system, and that worked fine too. Unmounted, rebooted, no dice; shutdown during reboot. Now I've booted back into recovery, and it locked up even trying to get into recovery, and I can't mount /data or /system (all result in long pauses and kernel errors).
You say I messed up my tablet... what do you think caused this? And yes, I've got CWM on here, although I could just fastboot the original recovery on if that would help...
Is there any way to boot this thing off of the external SD?
What was wrong with yours that required replacing the logic board?

lexelby said:
Thanks for the tips!
It's quite weird. I booted it into recovery, and via adb I was able to mount /data fine and poke around. I unmounted, then mounted /system, and that worked fine too. Unmounted, rebooted, no dice; shutdown during reboot. Now I've booted back into recovery, and it locked up even trying to get into recovery, and I can't mount /data or /system (all result in long pauses and kernel errors).
You say I messed up my tablet... what do you think caused this? And yes, I've got CWM on here, although I could just fastboot the original recovery on if that would help...
Is there any way to boot this thing off of the external SD?
What was wrong with yours that required replacing the logic board?
Click to expand...
Click to collapse
It sounds like your boot is corrupted. There may be a way for ASUS to recover it without replacing the board.
My problem was that I messed up my boot and I could no longer flash anything or even modify files on the filesystems.

devbro said:
It sounds like your boot is corrupted. There may be a way for ASUS to recover it without replacing the board.
My problem was that I messed up my boot and I could no longer flash anything or even modify files on the filesystems.
Click to expand...
Click to collapse
Powering off completely seems to restore the device's ability to mount /system. I think touching a certain place on the emmc puts the controller in a bad state. I'm going to see if I can narrow down the bad blocks and partition around them or similar.
Barring that, where did you find a logic board for so cheap?

lexelby said:
Powering off completely seems to restore the device's ability to mount /system. I think touching a certain place on the emmc puts the controller in a bad state. I'm going to see if I can narrow down the bad blocks and partition around them or similar.
Barring that, where did you find a logic board for so cheap?
Click to expand...
Click to collapse
If you can access it in adb, the first thing I would do is adb pull my data off the tablet.
Then you could run fsck on your partitions in an adb shell.
Maybe just a simple format of/system and /data would clear corruption already....
I don't know the correct fsck command for this tablet top of my head, but you have to unmount the partition you want to run it on and then something similar to this (this is for the /data partition of the TF700):
Code:
e2fsck -fvyD /dev/block/mmcblk0p8
You seem to know your way around, I'm sure you can find it.
Good luck!

berndblb said:
If you can access it in adb, the first thing I would is adb pull my data off the tablet.
Then you could run fsck on your partitions in an adb shell.
Maybe just a simple format of/system and /data would clear corruption already....
I don't know the correct fsck command for this tablet top of my head, but you have to unmount the partition you want to run it on and then
Code:
fsck /dev/target_partition_name
You seem to know your way around, I'm sure you can find it.
Good luck!
Click to expand...
Click to collapse
Nah, it's not simple fs corruption -- first thing I checked, but thanks for the suggestion Been poking at it for a few hours, and it seems like the actual mmc bus/chip is screwed, not just a bad block. I think replacing the logic board is the way to go. Anyone want to let a tf701t with a dead screen go for cheap?
And yeah, I know my way around a bit, but really only enough to sound like I know what I'm doing I recognized the problem because I lost my sgh-i777 to a very similar issue, a failing internal sd. Seems like the Achilles' heel of android devices.

lexelby said:
Seems like the Achilles' heel of android devices.
Click to expand...
Click to collapse
I've owned close to a dozen Android devices. The SD still has to fail on me...
Maybe it's not the hardware, maybe it's - you [emoji33][emoji12]
Anyway, good luck with this. Oh, and devbro found the logic board on ebay..

berndblb said:
If you can access it in adb, the first thing I would do is adb pull my data off the tablet.
Then you could run fsck on your partitions in an adb shell.
Maybe just a simple format of/system and /data would clear corruption already....
I don't know the correct fsck command for this tablet top of my head, but you have to unmount the partition you want to run it on and then something similar to this (this is for the /data partition of the TF700):
Code:
e2fsck -fvyD /dev/block/mmcblk0p8
You seem to know your way around, I'm sure you can find it.
Good luck!
Click to expand...
Click to collapse
lexelby said:
Nah, it's not simple fs corruption -- first thing I checked, but thanks for the suggestion Been poking at it for a few hours, and it seems like the actual mmc bus/chip is screwed, not just a bad block. I think replacing the logic board is the way to go. Anyone want to let a tf701t with a dead screen go for cheap?
And yeah, I know my way around a bit, but really only enough to sound like I know what I'm doing I recognized the problem because I lost my sgh-i777 to a very similar issue, a failing internal sd. Seems like the Achilles' heel of android devices.
Click to expand...
Click to collapse
berndblb said:
I've owned close to a dozen Android devices. The SD still has to fail on me...
Maybe it's not the hardware, maybe it's - you [emoji33][emoji12]
Anyway, good luck with this. Oh, and devbro found the logic board on ebay..
Click to expand...
Click to collapse
Be careful mmcblk0p8 is /data on the TF700, on the TF701 it is mmcblk0p14
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)

sbdags said:
Be careful mmcblk0p8 is /data on the TF700, on the TF701 it is mmcblk0p14
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
Click to expand...
Click to collapse
Thanks sdbags, nice catch. Btw, having developed ROMs for this tablet, do you think it's possible at all to boot android off of the external sd? It'd be helpful to know if I shouldn't even bother trying to figure out how.

lexelby said:
Thanks sdbags, nice catch. Btw, having developed ROMs for this tablet, do you think it's possible at all to boot android off of the external sd? It'd be helpful to know if I shouldn't even bother trying to figure out how.
Click to expand...
Click to collapse
Yes I have it working But haven't released it maybe after CROMi-X 7 is finished I will release the flash files that allow you to run one ROM internally and one rom off the card as ROM2SD
It's just an awful lot of work to maintain that doing it for the 300, 201 and 700 transformer crowd has kind of put me off doing for the 701. Also the internal mmc is faster than most fast sdcards so we won't see the benefits that especially the 700 users get.

sbdags said:
Yes I have it working But haven't released it maybe after CROMi-X 7 is finished I will release the flash files that allow you to run one ROM internally and one rom off the card as ROM2SD
It's just an awful lot of work to maintain that doing it for the 300, 201 and 700 transformer crowd has kind of put me off doing for the 701. Also the internal mmc is faster than most fast sdcards so we won't see the benefits that especially the 700 users get.
Click to expand...
Click to collapse
Dude, that totally just made my day, knowing that this is possible Any way you'd be willing to share your development version with me? I'd be your best beta tester every -- hell, I'd be maintainer for the rom2sd part for tf701t if you'd let me. I'm rather motivated at this point, and I have years of professional Linux experience... probably about time I took up android ROM development

lexelby said:
Dude, that totally just made my day, knowing that this is possible Any way you'd be willing to share your development version with me? I'd be your best beta tester every -- hell, I'd be maintainer for the rom2sd part for tf701t if you'd let me. I'm rather motivated at this point, and I have years of professional Linux experience... probably about time I took up android ROM development
Click to expand...
Click to collapse
Hmmm Ok let me sort out the main CROMi-X release and I might take you up on that. I warn you that it is rather a lot to get ROM2SD working though! But if you are up for it ....

sbdags said:
Hmmm Ok let me sort out the main CROMi-X release and I might take you up on that. I warn you that it is rather a lot to get ROM2SD working though! But if you are up for it ....
Click to expand...
Click to collapse
I am totally up for it -- it's that or shelve my tablet until I can afford a logic board I'll be trying to port a ROM to sd from scratch anyway, so having your ROM to start from would be a huge leg up.

lexelby said:
I am totally up for it -- it's that or shelve my tablet until I can afford a logic board I'll be trying to port a ROM to sd from scratch anyway, so having your ROM to start from would be a huge leg up.
Click to expand...
Click to collapse
If your internal sd is completely dead then rom2sd won't work I'm afraid - it relies on the kernel being able to at least read some files from internal to allow it to switch to external....

sbdags said:
If your internal sd is completely dead then rom2sd won't work I'm afraid - it relies on the kernel being able to at least read some files from internal to allow it to switch to external....
Click to expand...
Click to collapse
That's the thing, it works enough to get it into recovery. My plan was to try to kexec from recovery into a modified ROM.

Victory!
I took sdbags's stock zip (4.3) and extracted it on my computer. I used unmkbootimg to extract the initramfs.gz and kernel.gz from the boot.img in the ROM. I unzipped the initramfs and un-cpio'd it, then modified macallan.fstab to refer to /dev/block/mmcblk1p1 for /data, p2 for /system, and p3 for /cache. I also modified init.macallan.rc to avoid having it try to make filesystems on the EMMC -- I want it not to try touching the EMMC at all.
Next I rebuilt the initramfs.gz. I bought a good quality class 10 microsd and partitioned it on my computer with 3 primary partitions, one for /data, one for /system, and one for /cache (about 2GB and 1GB for /system and /cache). I made ext4 filesystems on all 3 partitions, mounted p2, and copied the rom over and installed it by hand using the updater-script as a guide. Then I unmounted and popped the SD card into my TF701t.
To boot it, I put my tablet into fastboot mode. I booted the kernel and ramdisk using 'fastboot boot' -- no need for kexec from recovery. I can do this without any reliance whatsoever on the internal EMMC. It took awhile to boot up, but it booted first try. The app drawer was a bit slow to come up, but I'm pretty happy I get to use my tablet at all! This whole process turned out to be MUCH easier than I expected it would be, and I'm quite confident I could do this to boot any ROM I wanted. I only use stock because of driver issues with my bluetooth keyboard.
Still willing to try my hand at maintaining cromi's ROM2SD branch though
Thanks everyone for all of your help!

Now that it's finished booting, it's really not sluggish at all. Hooray for class 10 sd cards.
Just to make this whole thing even a bit easier, I grabbed an arm-compiled version of the fastboot tool (search for fastbootarm) and put the kernel and ramdisk on my phone, so I can jump-start the tablet using my phone (via USB OTG cable) even when I'm not near my computer.

Will this be usable only from OTG pendrive?(Moto G no sdcard slot)

I had a similar issue with my Nexus 5 and 7 (2013) where I could no longer mount or read the /data or /system partitions but I could still boot into recovery and thought I scored two brand new drink coasters, but then came across this thread where it repaired corrupted partitions and I could now read and mount all partitions normally.
Being a Transformer tablet and not a Nexus device i'm assuming one or two of the adb commands might be a bit different for the disk partitions like someone mentioned in a previous post though..?
Might not be useful to you but thought I'd post it here anyway incase it might help somehow