UPDATE: This can't be used with CM10 Alpha 4 (or later) as it is due to the new partitioning system.
____
I made this thing time ago and I thought to share.
What it does is to boot a stock ROM from the external SD card. It's nothing special, I simply changed few things here and there. I did it because I needed a stock ROM for a couple of minutes and this was the faster way to get it.
I'm using CM and I made this with that in mind, so, don't use while using a stock ROM. It won't mess your current setup, but it won't work.
You need to change kernel to boot the stock ROM (reboot recovery > flash zip. Simple and fast). That's because, as you probably now, kernels made for stock ROMs are not compatible with CM.
Prepare you SD card
You need first to repartition your external SD like this:
Code:
1° partition (mmcblk1p1): FAT - it will be the usual external SD
2° partition (mmcblk1p2): ext4 - /system (make it around 300MB big, 254MB will be more or less the space used)
3° partition (mmcblk1p3): ext4 - /data
I can't help you with this, I did it with adb and parted (the command is available in CWM). Look for instructions on the web, it's full of guides out there. Your external SD card is /dev/block/mmcblk1 (mmcblk0 is the internal one).
If you'll use the zip linked to flash the ROM, the two partitions (mmcblk1p2 and mmcblk1p3) will be automatically converted, unless they are already two ext4/ext3/ext2 partitions.
It shouldn't matter which kernel you are currently using and it should be safe flashing it, the only important thing is to have three partitions. If mmcblk1p2 or mmcblk1p3 are not detected, the installation will be aborted (it means that your SD card is not partitioned). Nothing else will be touched.
If you don't want to use the zip, mount mmbclk1p2 and copy the ROM there.
/dbdata will be the usual one (it's not used in CM. This will also makes Samsung apps a lot faster when using a slow SD card), same for /cache.
The flashable ROM is a stock XXLE4 + su/Superuser.apk.
How to use the additional ROM
To use the ROM on your SD, flash kernel-stock-SD.zip (see below) from recovery.
To go back to the real ROM you have to flash its kernel. Here below you can find CM10 Alpha 2 kernel, flashable from recovery. If you have doubts, reflash the entire ROM, it won't wipe your data.
I only mentioned CM10 because it's what I'm using, but this thing should work with CM9 too.
Things to know
I built the kernel using the latest Samsung sources with inbuilt ext4 support (and ext3/ext2 compatibility). Nothing else was changes, so I think there's no need to publish the sources, they are available here.
I attached the tools I use to unpack/repack boot images (they are a modified version of skin1980's tools):
Code:
./unpack.pl boot.img
./repack.sh [gz|lzma|bzip2|xz]
To see the changes I made, compare "out/android" with the stock XXLE4 ramdisk and the other two directories with CM10 boot.img ramdisk.
I changed recovery.fstab accordingly, but I can't tell you if flashing stuff from CWM while using the additional ROM will work as expected. You should read the updater-script to know it for sure.
I can only tell you that dhiru's builds will be flashed into the real /system partition and not your SD card.
Backups should work too, but I didn't try.
Of course, performances depends on your SD card. Mine is not that good I think, I took it from an old phone and I really don't know anything about it. The ROM is still usable, but apps that intensely use databases are slow (not Samsung apps, those will use /dbdata). Maybe disabling journaling will help (search for more info).
The Galaxy SL screen will last more than usual because I intentionally added a delay (3 seconds, SD cards are detected after a while) and of course because of the slower load.
Please, use this if you have some experience.
Note: dual booting two ROMs with a single kernel is possible, but only if they use the same kernel image. See this and this.
Downloads
XXLE4-CWM.zip: CWM flashable ROM
kernel-stock-SD.zip: kernel to boot the ROM from the external SD, flashable from recovery
kernel-CM10-Alpha2.zip: CM10 Alpha 2 kernel, flashable from recovery
Wow ! thats dualboot for i9003 ! sweet gud to see development back in action
Good work.
The class of an SD card can be misleading. It is only a measure of the sequential Write access and that doesn't tell the whole story. Class 10 cards are great for cameras and applications that write or read sequential data, such as saving a picture and transferring a file. They are not so good for random access which is what the Android OS does when operating. In fact the random access speed for class 10 cards is lower than class 4 or 6 cards. From what I have seen, the sweet spot for smartphones is class 6.
Awesome. Only if we could achieve dual boot without flashing kernel everytime. But anyways awesome guide. Thanks.
Reminded me of dual booting of maemo and android on my brother's n900.
Whats the benefits of dual boot? I heard about it but i dont have an idea
juztinlee said:
Whats the benefits of dual boot? I heard about it but i dont have an idea
Click to expand...
Click to collapse
Dual Booting means you can have two OS's (here firmware) on the phone at the same time. You can choose on which you want to go. This, besides being awesomely cool, is really helpful in many scenarios.
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
santoshsadani009 said:
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
Click to expand...
Click to collapse
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
loSconosciuto said:
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
Click to expand...
Click to collapse
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
Ya a Universal kernel will do the trick.If later then we can achieve dual boot then the people who were holding back from CM9 or CM10 can flash that for features and a stock rom for stability and camera.
shriomman said:
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
Click to expand...
Click to collapse
As long as the kernel is the same, yes.
If you want, here you can find the unpacked boot.img I (probably) used to dual boot CM10 and CM9 (SD).
There's no zImage in there, use the one you prefer, CM10 and CM9 are using the same kernel.
EDIT:
I almost forgot. "out/ramdisk/2ndROM" is for the ROM stored in your SD card, so you have to adjust the mount points there (already done in the one linked). "out/ramdisk/android" should be the "stock" ramdisk.
recovery will work only for the primary ROM in this case, maybe with some scripting you can make it works for both the ROMs, but I won't do it (if it's something possible).
The tools I posted will automatically take care of the additional ramdisk.
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
nick0016 said:
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
Click to expand...
Click to collapse
I don't know what happened to the links, probably I deleted the files by mistake on dev-host. Sadly I no longer have them and I currently don't have the time to make them again.
Anyway, I suggest you to follow other guides in order to replace only the corrupted memory instead (we have two different memories). This one for example, but there are other guides probably.
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
nick0016 said:
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
Click to expand...
Click to collapse
The guide I linked is fine then.
It explains how to repartition your SD card and the script Dipu K attached to his post is to use the newly created partition inside your external SD for /data. It's not to swap internal and external SD.
As I said, we have two memories, /data is in one, /system, kernel and other things are in the other memory. The corrupted one must be the one which holds /data.
Try to do as explained in the guide, if the problem persists, I'll see what I can do to help.
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
nick0016 said:
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
Click to expand...
Click to collapse
The content of /data is generated, there's nothing like what you asking for.
Maybe the problem is that the script posted in the guide copies the content of the old /data partition to the new partition inside the SD card. Wiping data shouldn't work because the path to the SD card is not specified.
Try the script attached. I zipped it to be able to upload it here, but it's not flashable. Since you've been able to follow the guide I assume you know how to use adb.
Wipe the content of the data partition you created inside you SD card (/dev/block/mmcblk1p2). You could reformat it with make_ext4fs, use a computer and so on. What's important is that it's ext4 formatted.
While in recovery, run:
Code:
adb shell mount /system
adb shell mkdir -p /system/etc/init.d/
adb push [I]PATH_TO[/I]/remount_data /system/etc/init.d/
adb shell chmod 777 /system/etc/init.d/remount_data
I'm sorry, but I currently don't have much free time to help more than this. With no logs or access to the device it's really hard for me to know what's the problem.
Related
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Good question ..............i think there is no answer for this question
rvd_516 said:
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Click to expand...
Click to collapse
some resources would have to be used by both ROMs..
with the current hacks it can't be done easily.
i guess some way of ramdisking the shared resources will have to be used.
basically, if you think about a hack for defy ask first:
can it be done in a completely open (=bootloader not locked) phone like nexus ?
if yes, ask:
is it WORKING?
if yes also, so maybe it can be done.
nevertheless, it's easy enough to create a script to backup & restore NANDROIDS.
but then every switch between roms will take like 25+ minutes, so it won't be a real multiboot.
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
ephumuris said:
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
Click to expand...
Click to collapse
I think there are two possibilities for this to happen: first of all, we should try NAND boot for the primary ROM, and try somehow to load the secondary ROM from the internal memory (it'll be faster than the SD Card, I think). The problem here would be allowing the bootloader to read from internal memory instead of NAND. I know this can be done based on the number of WinMo-Android and iOS-Android dual boot solutions, with a menu to choose which system to load, in the boot screen.
The second option is the method used by Wing Linux to run Android on old WinMo devices. In this method, you MUST boot in WinMo (or, in our case, in the primary ROM), then open the app that loads Android (the secondary ROM, for us). Android does NOT run emulated in this method, but, since the device can't dual boot directly, the app sends a signal for the device to restart running from the bootloader to the SD Card (for us, internal memory). This second option is, somehow, like the System Recovery app (not 2ndInit), that has an option that reboots directly into Recovery. So, if we can tell the phone to load from custom Recovery (which is, in fact, in internal memory, not in NAND), I think it's possible to make it load an entire ROM from the internal memory (without having to mount it everytime and waiting for the dalvik-cache to load).
However, it's surely a hard work to do.
Yes one from nand and one from sd card..........good......can we partition nand and use it both on the nand itself??
it should really work if we use virtual images or sdcard-partitions instead of system, data and cache partitions.
This can be changed in the init.rc-file(of 2nd-init).
The creator of the 2nd-init-bootmenu should implement this feature.
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
Did you try it?
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
even i like to know tht did u tried tht?
I managed to boot from virtual system,data and cache partitions with the 2nd-boot-option of bootmenu like ep3 said.
It was a bit difficult because android-init remounts /dev so the changes will be lost but now I found a way.
And: I got recovery working for the virtual system so you don't need to prepare your images, BUT: only the wipe and restore are working. "install zip" will still affect your real system.
My scripts need some testing but after that I will release a first version.
the multboot works for me i writed a cutsom boot sh and init.rc and woila WORKS!
NOT PUBLUC because it not works for all rom
---------- Post added at 04:59 PM ---------- Previous post was at 04:36 PM ----------
this is a dualboot rom
http://forum.xda-developers.com/showthread.php?t=1225179
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
I uploaded a new version of my multiboot-script(v0.2)
changelog:
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
Download:
http://www.multiupload.com/UT0TLPR3ZW
m11kkaa said:
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
Click to expand...
Click to collapse
Thanks for your work.
Did the 2nd android system boots from sdcard?
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
Ask pedrodh http://forum.xda-developers.com/member.php?u=2098689
He can help.
Nice work, thanks i will add this soon, in the future bootmenu versions
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
I released a dual boot version that uses 2nd-boot a few months back, hadn't have much time to improve it since.
I was using loop-back mount with /system and bind mount with /data since it's much more space efficient than just use an ext3 image.
Awesome job. I think u shud create a new thread for it. Dual booting cm7 and miui :O
Sent from my Moto Defy
This thread serves as a guide to install both firerats and data2ext mods on a single rom and have them work simultaneously.
I do not take any credit for the creation of any files mentioned or attached, nor methods for the installation of each individual mod, nor roms, gapps, or otherwise mentioned content. All credit goes to those who created each mod, rom, gapps, and the methods for installing each individually. I only claim responsibility for my own research and the order and hierarchy of steps below that combine these incredible feats of development into a working system of internal storage expansion and space management.
Even though it is impossible to brick your phone using the guide below, I am not responsible if you break your device, because you have willfully chosen on your own to void your warranty by rooting your phone and installing the mods mentioned below.
To make firerats work with data2ext simultaneously, follow these over-detailed instructions EXACTLY. This is written so that anyone who has never held a smartphone in their lives can understand and do this right the first time, so those of you that know what you're doing, sorry about the length, but it should be pretty easy for you.
Note: I've uploaded some pertinent files from the following steps and added all links to all files needed so you don't have to go find them yourself. I did not include any roms, gapps, or the freespace app from the Play Store(just download from your phone, or from the link in step 6d). Links for all necessary files are in their respective steps below. The only links to a rom or gapps are for ICS. Otherwise you'll have to find and use your own downloaded roms and the correct gapps for your rom. If you would rather use the links below to download the files instead of using the ones I provided, be my guest.
I've updated this guide to make installation much easier and work with Sense roms!
Now on to the good stuff!!
Steps 1 through 7a are written for you to collect the files necessary, and to prepare your phone, sd card, and recovery for the correct method of installation of the collected files.
Steps 8 through 10 are to install the mods.
Preparation
1. Be sure to start from scratch!!! This means an UNPARTITIONED, FULLY WIPED sd card, fully wiped and rooted phone, and fully wiped recovery. Fresh file downloads for roms, gapps, and other mods you like wouldn't hurt either. If your phone is not rooted, go here, it's the best and easiest root method I've found.
1a. If you already have a partitioned sd card, insert it into your computer via a microsd adapter or other means(you cannot use your phone for this; it will not recognize that it's partitioned), delete the partitions and wipe the card using partition management software on your computer. I recommend EASEUS Partition Manager 9.1.1 Home Edition(Windows users only). If you use this program, after you delete partitions on your sd card, you will be left with unallocated space. Create a partition that takes up the entire unallocated space and set it as a Primary and FAT32 file system(remember, only do this to your sd card, NOT THE C: DRIVE!!!!).
2. Boot to recovery(hold down home, press and release power, then release home once recovery shows up)
2a. Be sure you have a recovery that supports flashing unsigned .zip files. If your recovery does not support flashing unsigned .zip files, flash a rom and then the corresponding gapps that are signed(cyanogenmod roms and gapps are the easiest way to go), boot into rom, sign in, download rom manager from Market/Play Store, open rom manager, flash clockworkmod recovery, and boot to recovery.
3. Make sure you are using latest 5.5.0.4 recovery, found here.
3a. If you are not already using the 5.5.0.4, flash the 5.5.0.4.zip in your current recovery(or follow the instructions from step 2a if you cannot flash unsigned .zip files) and reboot back into recovery.
4. In your new recovery, make sure you wipe everything, and go to advanced>partition SD card. Choose whatever size you want to have as internal storage(the 'M' means Megabyte, if you didn't already know...). I use 1024M or 2048M(i.e. 1Gb or 2Gb), depending on what mood I'm in, but it works with any of them. Then choose 0M swap size and wait for it to process.
5. Wipe everything once again(just to be safe), including sd-ext, and place your rom and preferred gapps on sd card, along with any other flashable modifications you like to use(I use the sd card speed boost, which can be found here. 2048Kb works best for my card, a 16Gb Class 4).
Note: For ICS users only! I use official, larger ICS gapps, found here(download the one next to 4.0.X, the link will be: '20120429'). The smaller gapps, as well as the current best ICS rom, can be found in whoshotjr2006's thread, here.
6. Make sure you have the latest firerats(1.5.8), which can be found here.
6a. Don't use any of the alphas or betas. Just 1.5.8. Download only the recovery-v1.5.8-CustomMTD_S.zip and boot-v1.5.8-CustomMTD_S.zip and place on sd card. Create a .txt file named 'mtdpartmap' and type 'mtd XXX XX'. These X's represent the size in numbers that you want your /system and /cache partition sizes to be, and therefore will not actually be used. See step 6b or 6c, depending on what rom you'll be using, for information on how to determine the correct partition sizes/numbers to use. DON'T KEEP THE X's IN THE FILE! REPLACE THEM WITH THE NUMBERS YOU WILL USE AFTER YOU DETERMINE WHAT YOUR /SYSTEM AND /CACHE SIZES SHOULD BE!
6b. For ICS users: If you are using the official, larger gapps, type 'mtd 190 60' into the text file and save to sd card. If you are using smaller gapps, type 'mtd 190 30'. Proceed to step 7.
6c. For Non-ICS users: To find out what numbers to replace the X's with in your mtdpartmap.txt, first wipe everything and install only the rom and gapps you'll be using this mod with. Then boot into rom, sign in, and follow step 6d. After you do this, however, you will need to repeat steps 5 and 6a, then proceed to step 7.
6d. You can download 'freespace' from the Play Store, which needs root access, and will show you the total size and space remaining for each of the /system, /data, /cache, /sdcard, and /ext partitions, so you can change the numbers in your mtdpartmap file to what you want the /system and /cache to be that best suits the rom you want to flash. The first number after 'mtd' is for the /system partition, the second number is for /cache. You can't change the /data, because it is dependent on what you set the system and cache sizes to, and will be set to what you partitioned the sd card to anyways. Also, keep at least a 5Mb allowance over what you need for both /system and /cache partitions as you will run into force closing problems if there is no breathing room, especially for the /cache partition.
7. The data2ext thread and .zip file can be found here.
7a. Download the unCoRrUpTeD_data2extV2.2.zip at the bottom of the post and place on sd card. DO NOT FLASH!!!
Summary of what should be accomplished after following steps 1 through 7a: You should now be using CWM Recovery 5.5.0.4, have a partitioned sd card, wiped everything, and placed the boot-v1.5.8-CustomMTD_S.zip, recovery-v1.5.8-CustomMTD_S.zip, unCoRrUpTeD_data2extV2.2.zip, mtdpartmap.txt, the rom and correct gapps, as well as any other mods you want to use onto your sd card. If all of this is true, move to step 8. If not, go back and find what you missed.
The Installation Process
8. Flash recovery-v1.5.8-CustomMTD_S.zip, then under mounts and storage, wipe /system, /cache, and /data in that order.
8a. Reboot to recovery(go to advanced>reboot recovery).
9. Flash rom, gapps, and whatever other mods you have or like, then flash boot-v1.5.8-CustomMTD_S.zip, then unCoRrUpTeD_data2extV2.2.zip, and reboot.
Note: the firerats installation thread for the HeroCDMA says to flash boot-v1.5.8-CustomMTD_S.zip after anything that changes the kernel specifications, but the unCoRrUpTeD_data2extV2.2.zip does not change these. The thread also says that adb is necessary to reboot; it's not. After wiping /system, /cache, and /data, just go to advanced>reboot recovery. It will work just fine, I promise. Newer recoveries don't need to use adb for this step.
10. Reboot immediately after signing in for data2ext to take effect.
That's it! You're all done! Set up your phone the way you want and start installing apps!
Summary of steps 1 through 10: By now, you should be using 5.5.0.4 recovery, have a partitioned sd card, have placed all necessary files, your rom, gapps, and other mods onto your sd card, flashed the correct files in the correct order and rebooted, signed in, and rebooted after signing in. You should now be looking at the home screen(or lockscreen) of your rom, and if you check storage from settings, you should see internal storage showing the size you partitioned the sd card to be in step 4.
Hopefully this wasn't too confusing...good luck!
If you have any questions, don't hesitate to post in this thread!
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Hammerfest said:
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Click to expand...
Click to collapse
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
goliath714 said:
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
Click to expand...
Click to collapse
I think 1.59 alpha... after a system crash a few months ago, i havent had the need to re-bookmark the firerats mediafire folder... I really should, and seeing as most file share hosts are closing down or restricting free access to files I really should re-download and archive them... god knows how many things I have lost because of the MAFIAA fiasco's...
Yeah that might be a good idea. Personally I've never used any alphas or betas so I really don't have any input for them lol
Sent from my HeroC using XDA
Bumping my own thread...lets get some more views for this thing! If you haven't tried it yet, or have questions about it, or simply don't know what it does, send me a message or post on this thread! It's really a very useful mod for those of you that use or like installing lots of apps...
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Hmoobphajej said:
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
Click to expand...
Click to collapse
You have to unmout the partition first.
#Root-Hack_Mod*Always\=LTE
App2sd
Yea, I got that too, is it not working for you.
If not, add "/system/etc/init.d/40data2ext --enable" That made it work for me. Don't add "".
after reboot and the memory still hasn't change then go back in to terminal manager and add the above line and then reboot, should work then, never got firerats to play nice with the script, so i just use data2sd
laie1472 said:
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
goliath714 said:
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
Click to expand...
Click to collapse
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
fforward72 said:
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
Click to expand...
Click to collapse
You can install from the market
Sent from my HERO200 using xda app-developers app
ajrty33 said:
You can install from the market
Sent from my HERO200 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot!
laie1472 said:
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
How? The firerats mod allows you to change the /system and /cache partition sizes, but from what I can find, data2ext only applies the /ext partition to the /data partition to make the phone utilize the /ext partition as /data, and doesn't allow for modification of the /system and /cache partitions.
Updated
Edit: Updated again to fix minor wording issues and make links much prettier!
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Sent from my HERO200
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed".
Any ideas?
dankdank11 said:
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Click to expand...
Click to collapse
Firerats has nothing to do with recovery. It's about resizing partitions. Recovery functions on a level above, so whatever you do with firerats won't affect it. TWRP is a great recovery program.
Tux2609 said:
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed". Any ideas?
Click to expand...
Click to collapse
Try again. Go through the instructions verbatim, as outlined. I wouldn't deviate in any way.
Data2SD MOD: Moves /data partition to External SD, noticeable performance increase
All files attached are flashable .zips Installation instructions updated.
clemsyns cpu OC 1800 kernel is out! Good stuff!
Symlink added to /data2 (internal storage now found as /sdcardi)
You will need to disable journaling using the guide in post #3 if you are on CleanROM 2.1 to 2.3
as the rom does this as standard. If not you will get error!
I have had nothing to do with the development of this MOD, all credit goes to TweakerL
Also a huge thanks to scrosler for the fantastic CleanROM
Thanks to clemsyn for the amazing kernel!
Feel free to go to original thread and give your thanks: http://forum.xda-developers.com/showthread.php?t=1803252
and also to seek information, the thread is full of it.
What/Why/How?
This MOD was developed to aid the I/O-issues the Transformer Prime has and the Infinity inherited. Since it was a known fact that the internal
storage was slow/poor, TweakerL decided to try mounting the /data partition to the MicroSD card. Hence an obvious necessity
will be that you have a fast MicroSD card. Several have been tried and there is no real conclution as to what is the best in regards
to manufacturer or class (a class 6 card can have better random write speeds than a class 10 card), I use a Sandisk 64GB UHS-I
class 10 card and so does several others with good results.
The way this works is that you change the ramdisk so that it mounts /data to the second partition of your micro sd. Your internal
storage (the old /data partition) will be mounted as /data2.
Requirements
1. Unlocked and Rooted
2. You MUST repartition your Micro SD. The .zip you flash will mount /data to mmcblk1p2, which basically says "mount /data to the
second partition in the external SD." also, the ramdisk expects that partition to be ext4, so essentially:
Make sure you have an external SD with at least two partitions and that the second partition is formatted to ext4. I use fat32 on the first partition
because it's recognized by most devices.You will also need to make both partitions "primary" partitions. I personally use Gparted to repartition
my stuff, but feel free to use whatever you like. Even if you're on windows you can still use gparted by using virtualbox, or you can use a tool
called MiniTool Partition Wizard, I haven't tried it myself but it is reported to be good.
3. Research your Micro SD, find out if it has good random write speeds. There is no use in this mod if you card is slower than your internal
memory.
4. Although it's not a requirement it is a recommendation to have gone through the Nvflash procedure. It has saved alot of people from bricks
and is just great to have.
5. Verify that the .zip is compatible with your ROM, if it is not listed feel free to ask for a version for your preferred ROM.
Disclaimer
I take no responsibility for whatever happens to your device using this MOD, it is flashing a kernel so take precautions!
Installation
1. Boot to recovery, flash your preferred ROM
2. Reboot to initial setup (Don't run through)
3. Reboot to recovery, flash the matching Data2SD.zip
4. Disable journaling (Optional on all ROMs except CleanROM)
5. Reboot
When it reboots you will get a blue progress bar and it will be just as you flashed a new rom, you'll get the device setup screen.With my
MicroSD I get about twice the Random Write speed with this mod; Internal=0.20mb/s External=0.40mb/s . We will have a look at doubling
these figures further down (I currently have Random write speed average of 0.8mb/s).
Reverting
Flash a ROM
Feel free to ask any questions!
MD5 checksum for cm10-1025data2sd : 78b9e62e27204efeb0bdd3c926c4a30a
MD5 checksum for CleanROM2-3Data2SD: 60eef4e666ec97216ee0801189233719
MD5 checksum for clemsyn's 600 OC kernel ver8: e07b4a5a5f7ae2976a86460e5309199a
MD5 checksum for clemsyn's 650 OC kernel ver8: cf6d36da2d26db2e72c1c110a87cad7f
MD5 checksum for clemsyn's 650 OC kernel ver22: 1ec0e9c5c5ac7b012e3095f03f7dd234
Modded Recovery
Enough with the screenshots, I think people know what it's all about by now!
TWRP 2.3.1.0 Data2SD Edition
Modded by flumpster, thanks a million!
Attached is a version of the latest TWRP recovery, the only mod done is changing where
it mounts /data so it backs up the correct partitions!
Backup to External will backup to your first partition (fat32 maybe) and backup to internal will
backup to your ext4/2 partition.It is recommended to back up to external which is the fat partition.
If you backup to internal which is now the ext partition and something goes wrong with that partition
you wont have access to your backup.
Instructions:
You must remove the old twrp settings from your prime for this to work correctly. Delete any
TWRP folders that are in sdcard, data2/media and removable/sdcard. If you have backups there
already that you want to keep leave the backups folder in the TWRP directories and then just
delete the files that are in the root of the TWRP folder to get rid of the settings left behind.
If you are on a windows pc just extract the zip somewhere and run the bat file and then follow the
onscreen instructions. It will flash it for you. If not, navigatate to the fastboot folder, find the .blob
and flash the usual way with fastboot.
I have tested it myself but would love some feedback on this as I am currently the only one testing.
Disabling journaling!
This is a mod that flumpster tested and found to work fine. I have tested it to and it is fast as a shark. It is somewhat
controvertial though, someone thinks disabling journaling on the ext4 file system could cause crashes. Also if you are
plagued with random reboots it can cause data loss. I've been running it for a couple of days without issues and getting fantastic results.
Here is a description on how to do it if you want to try:
To Disable Journaling in EXT4
Go into TWRP and then open a command prompt on your computer where adb is.
Type adb shell and enter it then type the following commands one at a time.
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk1p2
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk1p2
e2fsck -f /dev/block/mmcblk1p2
Watch out for the fourth line, after tune2fs - that is a capital O not a zero. The one further along the line is a zero.
To check if it has worked type the follwing after them
tune2fs -l /dev/block/mmcblk1p2 | grep features
If you don't see has_journal in the output all is good.
And the size of the ext4 partition should be?
I was planning on taking a stab at porting this project to the TF700 this weekend. Thanks for your work! Going to test ASAP.
maxrdlf95 said:
And the size of the ext4 partition should be?
Click to expand...
Click to collapse
That is up to you really, the ext4 partition will be your new "internal storage" so if you if you need to store alot there like big games etc. you'll need more. If like me you have little use for internal storage you increase the size of first partition. I have 49gb fat 32 as my first partition and 11gb ext4 as my second.
I transfer movies etc. from a windows machine to the fat32 partition.
Good question though, I should have mentioned it in the OP.
Sent from my ASUS Transformer Pad TF700T using xda premium
The mysterious CheckROM that you've mentioned twice is just CleanROM, right?
Kisakuku said:
The mysterious CheckROM that you've mentioned twice is just CleanROM, right?
Click to expand...
Click to collapse
Yes, of course. Thank you for pointing that out, I've used CheckROM on another device so it got mixed up. OP updated.
fordwolden said:
Data2SD MOD: Moves /data partition to External SD
Click to expand...
Click to collapse
This looks very interesting!
fordwolden said:
Disabling journaling!
Click to expand...
Click to collapse
Actually the ROM does this during install. However on 2.0 it was causing issues with the latest TWRP so I temporarliy took it out.
It ended up being a twrp issue. IM going to put it back in for version 2.1 (with will be 10.4.4.18 based) and revert to the old version of twrp. The newer 2.3.x builds dont seem as reliable at this time.
But good write up!
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Edit: No longer applicable, sd-ext backup no longer supported. Modded TWRP recovery in post #2
fordwolden said:
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Click to expand...
Click to collapse
heh... i was just going to ask about that. thanks for the clarification.
fordwolden said:
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Click to expand...
Click to collapse
People really use Nandroid? lol :angel:
scrosler said:
People really use Nandroid? lol :angel:
Click to expand...
Click to collapse
Some feel more comfortable doing it! I feel like it's "bringing a knife to a gunfight"! False safety.
Since the 12/10 update to .18 that I installed just yesterday my performance skyrocketed. I don't experience any lag anymore, no hickups, much faster loading etc. I suddenly don't feel like this tablet was a waste of money anymore
It's all stock and normal.
So if you don't have this update yet, try it out before trying anything like this.
Would there be any way of getting this working on a rooted stock FW?
I saved root before updating to JB so I'm going to stay unlocked for as long as I have warranty.
Moning2 said:
Since the 12/10 update to .18 that I installed just yesterday my performance skyrocketed. I don't experience any lag anymore, no hickups, much faster loading etc. I suddenly don't feel like this tablet was a waste of money anymore
It's all stock and normal.
So if you don't have this update yet, try it out before trying anything like this.
Click to expand...
Click to collapse
Gospel singers from the General section? Now that's a first for me! I'm glad you're happy with your tablets,
now try downloading CleanROM 2.1 while multi-tasking on your device, still happy? I bet you want to unlock
before the download is finished!
New version for CleanROM 2.1 coming up, sorry for the delay. Been getting some sleep and my Inet connection
is about as stable as Uranium!
New version has symlinked /data2 partition so your internal storage will now be found in /sdcardi. Just for ease
of use.
rikc said:
Would there be any way of getting this working on a rooted stock FW?
I saved root before updating to JB so I'm going to stay unlocked for as long as I have warranty.
Click to expand...
Click to collapse
You meant going to stay locked, right! No, sorry this is not possible for locked bootloaders.
fordwolden said:
You meant going to stay locked, right! No, sorry this is not possible for locked bootloaders.
Click to expand...
Click to collapse
Ok, thanks, that's clear!
I want this on stock rooted unlocked ROM
fordwolden said:
New version for CleanROM 2.1 coming up, sorry for the delay. Been getting some sleep and my Inet connection
is about as stable as Uranium!
.
Click to expand...
Click to collapse
Oh come on, Uranium has been around Earth for four and a half billion years and it's still here, can't be that unstable
Gesendet von meinem GT-N7000 mit Tapatalk 2
*** The sdcard card created by this thread is not compatible with the original sdcard installation of CM10/CM10.1.
This is a work-in-progress and things are changing very fast so you may lose some of your data as we moved from one version to another.
After a brief discussion with leapinlar few weeks back, this is a new CM10.1 sdcard installation based on that discussion.
Features:
Dual boot stock and CM10.1.
Using only three partitions to allow stock to boot properly.
/data is stored in emmc while /system is in sdcard (Caveat: Doing stock factory reset inside stock will wipe out data of both the stock and CM10.1)
Can be flashed with ROM from this thread starting cm-10.1-20130130-UNOFFICIAL-hummingbird.
/data maximum size is now only limited by the size of the emmc.
For installation instructions follow this post. Thanks Diogenes5.
CWM Image file: sdcard-cwm-hummingbird-hybridv2.zip. Date Posted: 2/2
Data Wipe/Factory Reset now working.
Backup/Restore to/from both emmc and sdcard now also working. (/boot will not be backup and restored)
uImage.20130613.hybrid.hd.zip and update.20130613.ramdisk.hybrid.hd.zip *** latest ***
Fixed: Intermittent boot problem
cyanoboot now working for lg display.
update-20130221.zip
cyanoboot modified to pass serial number to kernel command line for android to properly report a valid number instead of unknown.
update-20130204v2.zip
Fixed device booting to stock recovery instead from the stock ROM.
update-20130204.zip
cyanoboot modified to allow CM10.1 (cm-10.1-20130203-hummingbirdv2 and above) rebooting directly to its menu.
Older downloads:
CWM Image file: sdcard-cwm-hummingbird-hybrid.zip.
Update: Download View attachment update-20130201.zip and extract uImage and ramdisk.stock to the boot partition of the SD card created from the above file. You can now delete kernel.stock as it is no longer being used.
Stock now booting normally.
Added Boot from SD alternate in cyanoboot menu.
Thanks to leapinlar for the suggestions above.
TODO: Wipe/Backup/Restore operations under CWM.
Only CM10.1 ROM dated 1/30/13 and above will work properly with this new SD card installation.
Currently this installation is compatible only with leapinlar Stock recovery tool provided in this thread.
This hack/trick is already superceded by the above post.
BEWARE: This hack/trick should be used only by HD owners who are very familiar with SD card installation of CM10/CM10.1. This may or may not work. Using this tools could brick your device, you have been warned!!!
Prerequisite: Working CM10/CM10.1 SD card installation from this thread.
Instructions
Download the attached hybrid.zip file.
Make a backup copy of /boot/uImage before copying all the files to the /boot partition of the SD card.
Insert SD card to the HD and let the device boot from it.
Hold the 'n' button of the device until the cyanoboot menu is shown.
Press the 'n' button multiple times until 'Initialize Hybrid' is highlighted.
Hold the 'n' button for at least 3 seconds to activate it.
Wait until the device rebooted (Depending on the speed of the SD card, you may have to wait for a long time).
Enjoy a faster and smoother CM10/CM10.1
Note: To uninstall, delete ramdisk.hybrid*, ramdisk.sync*, ramdisk.sys*, ramdisk.data* and u-boot.altboot from the SD card. Delete both cm_system.img and cm_data.img from the EMMC to recover the 2GB of storage space.
Technicals/Details
uImage - updated cyanoboot for hybrid booting.
Boot menu descriptions
Boot Hybrid - uses ramdisk.hybrid as the ramdisk.
Initialize Hybrid - uses ramdisk.sync as the ramdisk.
Sync System: SD -> EMMC - uses ramdisk.sys-sync as the ramdisk.
Sync Data: SD -> EMMC - uses ramdisk.data-sync-emmc as the ramdisk.
Sync Data: EMMC -> SD - uses ramdisk.data-sync-sd as the ramdisk.
Default Boot Image - uses u-boot.altboot as configuration file.
ramdisk.sync - will check whether cm_system.img and cm_data.img are present in /emmc. If not create the two files with sizes 800MB and 1200MB respectively. Loop mount both files and copy the contents of partition 2 and partition 3 of the SD card. Rename ramdisk.hybrid.copy to ramdisk.hybrid to enable the cyanoboot menu Boot Hybrid. Store the value 1 to the file u-boot.altboot to enable default booting from hybrid/EMMC.
ramdisk.hybrid.copy - will be renamed automatically by ramdisk.sync to ramdisk.hybrid to enable booting from cyanoboot menu and default booting when the value 1 is stored in u-boot.altboot
ramdisk.sys-sync.copy - should be manually renamed to ramdisk.sys-sync to enable cynoboot menu Sync System: SD -> EMMC. This is needed to update cm_system.img after a CM10/CM10.1 update of the SD card by CWM.
ramdisk.data-sync-emmc.copy and ramdisk.data-sync-sd.copy - should be manually renamed to ramdisk.data-sync-emmc and ramdisk.data-sync-sd to enable syncing data both ways. (Not included yet)
u-boot.altboot - created with a value of 1 by ramdisk.sync. Changing the value to 0 will default to normal SD boot. Value can be changed while in the cyanoboot menu.
Pros/Cons
Pros
Very fast and smooth interface.
SD card can be unmounted and removed.
Cons
SD card is always needed during boot time.
Update should be done to the SD card first before syncing with EMMC.
Consumed 2GB of spare EMMC storage.
Reboot to recovery sometimes is not working and will reboot to EMMC/Stock recovery.
Bokbokan, if you get this working so that you can get the SD down to 3 or less partitions, I have a trick to let it boot to stock with the card still in.
Sent from my HD+ running CM10 on SD with XDA Premium
Is there a speed gain for those whose cards are already faster than nand, or that's mostly for those what have slow(er) cards?
leapinlar said:
Bokbokan, if you get this working so that you can get the SD down to 3 or less partitions, I have a trick to let it boot to stock with the card still in.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
I can try booting from the stock using customized kernel and a ramdisk sourced from the EMMC but so far haven't tested it because of my bricked stock. Did not bother to restore it yet since this make my device easier to boot/reboot from SD.
What trick do you have up your sleeve?
Stevethegreat said:
Is there a speed gain for those whose cards are already faster than nand, or that's mostly for those what have slow(er) cards?
Click to expand...
Click to collapse
This is very useful for those having very slow/moderate card speed. For faster card the benefit is to allow the device continue running even without the card except during boot time.
Very cool! Will play with this shortly!
bokbokan said:
I can try booting from the stock using customized kernel and a ramdisk sourced from the EMMC but so far haven't tested it because of my bricked stock. Did not bother to restore it yet since this make my device easier to boot/reboot from SD.
What trick do you have up your sleeve?
Click to expand...
Click to collapse
Actually there are two ways.
The first is to put the stock ramdisk in the SD boot partition. For me I don't run your CM10 so it was easy for me to make it boot to stock by putting it in the CWM SD card. Then I select SD and it boots to stock. But that does not help CM10 users because they need ramdisk to be for CM10.
But for CM10 users, you can install Quick Boot from the Play Store and install it in CM10. Then tell Quick Boot to boot to bootloader and it boots to stock. But with verygreen's/your CM10 SD partition structure, stock hangs at 99%. That is because stock chokes on 5 partitions on the SD. That is why I was saying that if you could get down to 3 partitions, you could boot to stock from CM10.
But on my HD+, which I do run CM10, I changed the partition structure so it only has 3. But I don't expect users to do that. It needs to be built into the SD from you and verygreen. That is why I like your idea of putting some things on emmc so the partitions can get down to 3.
But I will briefly explain what I did to customize my HD+ CM10 SD. I deleted partition 4 and 5, normally the sdcard partition and the extended partition that holds it. Then I moved partition 2 and 3 to the end of the SD. Then I expanded partition 1 to fill the space. So I have a large fat32 partition 1 and partitions 2 and 3 the same size as original at the end of the SD. Then I modified vold.fstab in /system/etc to point to partition 1 for sdcard instead of 5. And now the hard part. I modified the CWM SD so it also points to partition 1 for sdcard so it can find updates. I also removed the /boot entry so a nandroid would not backup my sdcard as part a backup. The /boot was not backing up/restoring properly anyway.
This is highly customized and I don't think users should do this, but it works.
The down side is your boot files are mixed in with your sdcard files and are vulnerable to tampering by the user. But the Nook Tablet SD installs do this, which is where I got the idea. And on the positive side, Windows can now see sdcard when plugged in directly and stock can use the card as an external SD with no modifications.
One of the challenges for you and verygreen would be how to dynamically build the SD with this structure for varying SD sizes. I had to do it all manually and I don't think you would want users to do have to do that.
So this is just some ideas for future configurations.
Edit: One idea is if you could put /system and /data both on emmc, and create sdcard as p2, then you could have the boot files and sdcard files separate. And it makes it easy to create the SD dynamically. But you do not get the advantage of Windows seeing the partition or stock seeing sdcard without modification.
I do have my HD customized that way. I have my CWM card modified for stock with a big fat32 p2 to use for stock external SD and then modify the stock vold.fstab through symlinking. And I put the stock ramdisk on the SD boot partition like I described earlier. That way I never have to take the SD out. Stock and CWM are available in the boot menu.
.
Sent from my HD+ running CM10 on SD with XDA Premium
Wow! This is great!
[edit - some more thoughts]
Spent some more time playing with this - the performance is vastly, vastly improved over my sdcard. Virtually all lag is gone. The actual conversion process was an absolute snap, and everything is running perfectly. Really, really excellent work.
Now, to upgrade, I assume that I boot into recovery, install the system, then *on next boot* choose the sync to EMMC option? Is that what you suggest?
DebauchedSloth said:
Wow! This is great!
[edit - some more thoughts]
Spent some more time playing with this - the performance is vastly, vastly improved over my sdcard. Virtually all lag is gone. The actual conversion process was an absolute snap, and everything is running perfectly. Really, really excellent work.
Now, to upgrade, I assume that I boot into recovery, install the system, then *on next boot* choose the sync to EMMC option? Is that what you suggest?
Click to expand...
Click to collapse
Yes that is what you should do.
bokbokan said:
Yes that is what you should do.
Click to expand...
Click to collapse
Worked like a charm.
CyanoBoot is not useable
I have used leapinar's sdcards as well as yours for cm10 and cm10.1 but I have always had this problem where on boot, I can sort of see the screen for cyanoboot, but it is compressed and distorted at the top of tablet. I can not operate the cyanoboot menus at all and pushing n seems to do nothing.
I have copied the hybrid zip files to /boot but the tablet just skips through cyanoboot and boots cm10.1.
How do I get cyanoboot viewable and to function properly?
msprag13 said:
I have used leapinar's sdcards as well as yours for cm10 and cm10.1 but I have always had this problem where on boot, I can sort of see the screen for cyanoboot, but it is compressed and distorted at the top of tablet. I can not operate the cyanoboot menus at all and pushing n seems to do nothing.
I have copied the hybrid zip files to /boot but the tablet just skips through cyanoboot and boots cm10.1.
How do I get cyanoboot viewable and to function properly?
Click to expand...
Click to collapse
The way you describe the screen is normal with the flash of distorltion at the top. As soon as you see that flash press and hold the n key until the boot menu comes up. If it does not come up, you may have a defective n key.
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
The way you describe the screen is normal with the flash of distorltion at the top. As soon as you see that flash press and hold the n key until the boot menu comes up. If it does not come up, you may have a defective n key.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
I missed adding that in my original question. When the distortion pops up and I press n, the screen goes blank and then nothing ever happens, just a blank screen. I have tried this with 3 different sandisk 4gb class 4 cards and the behavior is the same. My n button seems to work fine under stock, CM, and in CWM; it only seems to be a problem when trying to access cyanoboot.
Do you still think it could be the n button, and if so would there be a way to use ADB to do the hybridization check?
If this is the button how do I get B&N to replace it? "well ya see it works fine until I try to hack your loader and install a third party ROM, can I have a new one?"
msprag13 said:
I missed adding that in my original question. When the distortion pops up and I press n, the screen goes blank and then nothing ever happens, just a blank screen. I have tried this with 3 different sandisk 4gb class 4 cards and the behavior is the same. My n button seems to work fine under stock, CM, and in CWM; it only seems to be a problem when trying to access cyanoboot.
Do you still think it could be the n button, and if so would there be a way to use ADB to do the hybridization check?
If this is the button how do I get B&N to replace it? "well ya see it works fine until I try to hack your loader and install a third party ROM, can I have a new one?"
Click to expand...
Click to collapse
You say this happens with my CWM for stock version too? The latest version? Some users were having that problem on an earlier version of my CWM. Bokbokan said earlier that the HD comes with two different screens and my earlier version was failing on one kind of screen. I revised the image and it fixed the problem.
Sent from my HD+ running CM10 on SD with XDA Premium
Re: [Nook HD] CM10/CM10.1 SD/EMMC Hybrid Installation
leapinlar said:
You say this happens with my CWM for stock version too? The latest version? Some users were having that problem on an earlier version of my CWM. Bokbokan said earlier that the HD comes with two different screens and my earlier version was failing on one kind of screen. I revised the image and it fixed the problem.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
I tried again with different cards using the hummingbird-v3.img from bokokan's HD CM10/10.1 thread. I also used the 6025 for emmc stock rev2 4gb img from your root/gapps thread on a freshly formatted sdcard and I always get the distorted screen.
There is nothing actually being written to the nook correct? Cyanoboot is the u-boot.bin file on the sdcard? Since I have had this problem all along is there a bad file from an early attempt I am not aware of that is on the internal? When I remove any cards the nook boots normally although I used your OTA plus gapps on the stock.
Sent from my Barnes & Noble Nook HD using xda premium
Re: [Nook HD] CM10/CM10.1 SD/EMMC Hybrid Installation
msprag13 said:
I tried again with different cards using the hummingbird-v3.img from bokokan's HD CM10/10.1 thread. I also used the 6025 for emmc stock rev2 4gb img from your root/gapps thread on a freshly formatted sdcard and I always get the distorted screen.
There is nothing actually being written to the nook correct? Cyanoboot is the u-boot.bin file on the sdcard? Since I have had this problem all along is there a bad file from an early attempt I am not aware of that is on the internal? When I remove any cards the nook boots normally although I used your OTA plus gapps on the stock.
Sent from my Barnes & Noble Nook HD using xda premium
Click to expand...
Click to collapse
As I said earlier, the jagged distortion at the top of the screen is normal for everyone. And nothing important is being written to internal memory. All files for booting are on the card. I am thinking you may have the second screen manufacturer that bokbokan has not been able to test. Can you run an experiment?
Boot to CM10 and open the terminal emulator app. Type su enter. The prompt should change to a # after you grant superuser access. Then type dmesg. This should be done right after booting so the data is fresh. The screen should scroll a lot of data across the screen. Scroll to the beginning of that data and look for a line that starts "kernel command line:". In that line there should be a statement that says "display.vendor=". Tell us what it says after the equal sign.
I know just enough about this to guess that line is what we want to look at. Bokbokan will have to tell us for sure.
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
Boot to CM10 and open the terminal emulator app. Type su enter. The prompt should change to a # after you grant superuser access. Then type dmesg. This should be done right after booting so the data is fresh. The screen should scroll a lot of data across the screen. Scroll to the beginning of that data and look for a line that starts "kernel command line:". In that line there should be a statement that says "display.vendor=". Tell us what it says after the equal sign.
I know just enough about this to guess that line is what we want to look at. Bokbokan will have to tell us for sure.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
Kernel command line: vmalloc=768M init=/init rootwait omap_wdt.timer_margin=20 androidboot.hardware=hummingbird display.vendor=LGD boot.fb=b2600000
Re: [Nook HD] CM10/CM10.1 SD/EMMC Hybrid Installation
msprag13 said:
Kernel command line: vmalloc=768M init=/init rootwait omap_wdt.timer_margin=20 androidboot.hardware=hummingbird display.vendor=LGD boot.fb=b2600000
Click to expand...
Click to collapse
That is the second device he could not test. That is probably the problem. When he catches up with these posts maybe he can do something. His and my device say display.vendor=AUO.
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
As I said earlier, the jagged distortion at the top of the screen is normal for everyone. And nothing important is being written to internal memory. All files for booting are on the card. I am thinking you may have the second screen manufacturer that bokbokan has not been able to test. Can you run an experiment?
Boot to CM10 and open the terminal emulator app. Type su enter. The prompt should change to a # after you grant superuser access. Then type dmesg. This should be done right after booting so the data is fresh. The screen should scroll a lot of data across the screen. Scroll to the beginning of that data and look for a line that starts "kernel command line:". In that line there should be a statement that says "display.vendor=". Tell us what it says after the equal sign.
I know just enough about this to guess that line is what we want to look at. Bokbokan will have to tell us for sure.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
You beaten me on this. Thinking to post the same thing. :laugh:
Well, this one was not really asked for, but I need it for my other testing, and I imagine people might be interested in having the option.
This is also a bit more like a proof of concept (and a bit crude at that), even though fully functional - Stock ROM fully bootable from sdcard.
I don't think a lot of people would use this as a daily driver, but it certainly beats having stock on sdcard vs needing to restore stock in EMMC every time you need to test one little thing (or you might buy a few more Nooks, I guess. B&N would certainly appreciate that ).
Limitations and differences from real stock:
- currently there's no access to emmc storage partition as I wanted the setup to remain as vanilla as needed at first
- adb is on by default, though (As root).
- You can actually change files in /system as much as you want - secure mode is off.
For ovation (Nook HD+) You'll need a special ovation image that you'll need to write to an sdcard, at least 4G in size. (gunzip and use dd or winImage)
For hummingbird (Nook HD) You'll need a special hummingbird CWM image that you'll need to write to an sdcard, at least 4G in size. (gunzip and use dd or winImage)
Also get the the stock image (see below) and either place it to internal storage or reboot from the card and use adb push it to /sdcard (basically it's like you install CM ROM, refer to user-friendly thread in General if you cannot follow my condensed instructions here, only use different file name). Note this already has gapps and other stuff, so you don't need any additional installs other than stock at the beginning.
Stock images:
For ovation: stock-ovation-2.2.0.zip (If you are upgrading from 2.1.1 or before, you also need to flash cyanoboot-ovation-2.zip)
For hummingbird: stock-hummingbird-2.2.0-new.zip (If you are upgrading from 2.1.1 or before, you also need to flash cyanoboot-hummingbird-1.zip)
So after you install this thing, reboot. CWM will warn you that the image is not rooted. Decide for yourself if you want to root on the spot or not.
The dimmed Cyanoboot logo will stay on for quite a while (52 seconds for me) - don't worry, it's doing something.
You'll be able to adb in about halfway through that.
Then you'll see familiar Nook Stock white booting screen, this one will stop at 99% - again no fears, it takes quite a while here till the thing rebuilds the caches, on my class4 sandisk it takes 2m40s
Once it's done - you'll be prompted to register and all that.
Now you are done, enjoy.
Now I also have a script to automate creation of the stock zips for sdcard install, so you no longer need o wait for me to create these files
History:
Old Stock images:
For ovation: stock-ovation-2.1.0.zip stock-ovation-2.1.1.zip - these need a special old ovation image
For hummingbird: stock-hummingbird-2.1.1.zip - these need a special old hummingbird CWM image
This is awesome. This way if users want to dual boot, they can put stock on SD, CM10.1 on emmc and not worry about resetting stock. That way they can add things to stock /system directly. Curious to see if the CWM root works.
Thanks for this.
Sent from my Nook HD+ running CM10.1 on emmc.
verygreen said:
Once it's done - you'll be prompted to register and all that.
Click to expand...
Click to collapse
I hope I can just backup existing data partition from emmc stock and restore to sd card stock (via tar or possibly CWM) and the result will run without starting from scratch.
fanoush said:
I hope I can just backup existing data partition from emmc stock and restore to sd card stock (via tar or possibly CWM) and the result will run without starting from scratch.
Click to expand...
Click to collapse
You should be able to, if you backup with the emmc CWM and advance restore just data with SD CWM.
Sent from my Nook HD+ running CM10.1 on emmc.
Nice to see more options. Having something that I do not need is better than etc etc, you know that, right.
Sent from my BN NookHD+ using Tapatalk 4 Beta
leapinlar said:
You should be able to, if you backup with the emmc CWM and advance restore just data with SD CWM.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Playstore, "Nandroid Manager" should work nicely, You can specify the location of the CWM backup.
Hello, I am/was planning to install this alongside my CM10.1 EMMC setup, but now that I reread this thread -again- it doesn't seem to have a way to dual boot. I mean when SD would be inserted it would boot to Stock, when not it would boot to CM, but the ideal would to be able to switch from one OS to another w/t having to add/remove the SD card quite as frequently, no?
Stevethegreat said:
Hello, I am/was planning to install this alongside my CM10.1 EMMC setup, but now that I reread this thread -again- it doesn't seem to have a way to dual boot. I mean when SD would be inserted it would boot to Stock, when not it would boot to CM, but the ideal would to be able to switch from one OS to another w/t having to add/remove the SD card quite as frequently, no?
Click to expand...
Click to collapse
You can dual boot if you go to my post here:
http://forum.xda-developers.com/showthread.php?p=42295360.
Follow the directions there and it will put the cyanoboot menu on the SD. Then you can change the default to boot to emmc instead of SD if you want. Just remember the terminology is backwards though, stock means emmc and CM10.1 means SD.
Then every time it boots with the SD inserted it will boot to emmc and if you want it to boot fully to SD, just press the n key to get to the menu and choose CM10.1 (SD).
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
You can dual boot if you go to my post here:
http://forum.xda-developers.com/showthread.php?p=42295360.
Follow the directions there and it will put the cyanoboot menu on the SD. Then you can change the default to boot to emmc instead of SD if you want. Just remember the terminology is backwards though, stock means emmc and CM10.1 means SD.
Then every time it boots with the SD inserted it will boot to emmc and if you want it to boot fully to SD, just press the n key to get to the menu and choose CM10.1 (SD).
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Whoah! That's exactly what I was looking for, didn't know it would work with "Stock-SD" .
Thanks, as always, leap
Now all it remains is to find a way to enable "unknown sources" to this rom and I'll be set (the method used for "emmc-stock" doesn't work here unfortunately).
Again thanks (both to VG and leap, and to the rest of the community that may have helped )
Hello, sorry to double post (and bump this thread) but I found out why's it impossible to enable "unkown sources" using the "extras.zip" that is been given to leaplinlar's thread. Apparently it searches for the EMMC partition whereupon it tries to enable the changes (install zeam, enable "unknown sources", etc). Given that this install uses the SD-card one would only need to redirect "uknown sources" script to search (and run on) SD card.
Given my non-experience in writing android-scripts I found a hard time to do just that, so if leap or anyone else would be able to modify the script (and post it as a flashable zip if possible) so that to run on an external stock setup, I think, it's something that belongs in this thread as it's the only thing missing from VeryGreen's experimental rom (it actually runs perfectly, root included, it only lacks "unknown sources")...
Again thanks, to all involved, for your work.
Stevethegreat said:
Hello, sorry to double post (and bump this thread) but I found out why's it impossible to enable "unkown sources" using the "extras.zip" that is been given to leaplinlar's thread. Apparently it searches for the EMMC partition whereupon it tries to enable the changes (install zeam, enable "unknown sources", etc). Given that this install uses the SD-card one would only need to redirect "uknown sources" script to search (and run on) SD card.
Given my non-experience in writing android-scripts I found a hard time to do just that, so if leap or anyone else would be able to modify the script (and post it as a flashable zip if possible) so that to run on an external stock setup, I think, it's something that belongs in this thread as it's the only thing missing from VeryGreen's experimental rom (it actually runs perfectly, root included, it only lacks "unknown sources")...
Again thanks, to all involved, for your work.
Click to expand...
Click to collapse
Yes, after your last post, I decided to modify the zip to make it possible to do that. I just need a little time to get it done.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Yes, after your last post, I decided to modify the zip to make it possible to do that. I just need a little time to get it done.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Hey, thanks, that's much appreciated :good:
Take your time...
leapinlar said:
You can dual boot if you go to my post here:
http://forum.xda-developers.com/showthread.php?p=42295360.
Follow the directions there and it will put the cyanoboot menu on the SD. Then you can change the default to boot to emmc instead of SD if you want. Just remember the terminology is backwards though, stock means emmc and CM10.1 means SD.
Then every time it boots with the SD inserted it will boot to emmc and if you want it to boot fully to SD, just press the n key to get to the menu and choose CM10.1 (SD).
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Just one thing to add (sorry for the double post): This solution does not work as it interferes with VG's method to boot stock from SD. Upon replacing the boot files, it would simply refuse to boot to Stock (SD), it will hang on the selection screen. The EMMC setup -of course- will boot just fine, so I guess that/this need to be reworked as well ... sadly.
Thanks anyhow
any help would be appreciated, i tried installing this the other day to a 4gig sd card, and somehow messed up the 10.1 emmc rom to were it wouldnt boot into it anymore. i thought i did everything right but i guess i didnt.
any words of wisdom? thanks
TheNeck said:
any help would be appreciated, i tried installing this the other day to a 4gig sd card, and somehow messed up the 10.1 emmc rom to were it wouldnt boot into it anymore. i thought i did everything right but i guess i didnt.
any words of wisdom? thanks
Click to expand...
Click to collapse
Did you take the SD out when you tried to boot to CM10.1? If you did and it would still not boot to CM10.1, just reflash the CM10.1 emmc ROM zip again. That should fix CM10.1.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Did you take the SD out when you tried to boot to CM10.1? If you did and it would still not boot to CM10.1, just reflash the CM10.1 emmc ROM zip again. That should fix CM10.1.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
i already reflashed cm10.1 and its working fine now, my question now, why did it mess up my cm10.1 installing stock 2.1.0 from sdcard?
Stevethegreat said:
Just one thing to add (sorry for the double post): This solution does not work as it interferes with VG's method to boot stock from SD. Upon replacing the boot files, it would simply refuse to boot to Stock (SD), it will hang on the selection screen. The EMMC setup -of course- will boot just fine, so I guess that/this need to be reworked as well ... sadly.
Thanks anyhow
Click to expand...
Click to collapse
It should not have been a problem. I have not tested it since I don't have his SD set up yet. Did the menu come up? And you choose CM10/CM10.1? And held n for at least 3 seconds?
Sent from my Nook HD+ running CM10.1 on emmc.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
TheNeck said:
i already reflashed cm10.1 and its working fine now, my question now, why did it mess up my cm10.1 installing stock 2.1.0 from sdcard?
Click to expand...
Click to collapse
It should not have messed it up. What is the name of the zip you flashed for stock and where did you get it?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
It should not have messed it up. What is the name of the zip you flashed for stock and where did you get it?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
i downloaded the file stock-ovation-2.1.0.zip from the original post.
TheNeck said:
i downloaded the file stock-ovation-2.1.0.zip from the original post.
Click to expand...
Click to collapse
And you flashed it with early7.1 CWM after booting with it once?
And how was CM10.1 messed up? You took the SD out of the slot when you tried to boot to CM10.1, right?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
And you flashed it with early7.1 CWM after booting with it once?
And how was CM10.1 messed up? You took the SD out of the slot when you tried to boot to CM10.1, right?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
i wrote the 7.1 image to the sd card, i didnt flash it
with the SD out, CM10.1 is just stuck in a reboot loop