Increase app partition size above 2GB - MTCB Software Development

Hi, I recently got the Joying unit with 16gb. Is there a way to modify the parameter file to utilize all available storage? the file has a [email protected](userdata). What does [email protected] mean? All the other partitions seem to have hex sizes.

Install Malaysk Rom. Automatically allows apps to utilise all available storage.
Sent from my SM-G920F using Tapatalk

Partition sd card. Fat32 and the size you want in ext2. Use link2sd to link apps to sd card

Extract the firmware using the RK3066 IMG MOD TOOL and edit the parameter file. That's where you will find all the partition at. Resize it to your liking and repack it back to img. The easier way of doing it is to extract the stock firmware and the malaysk firmware and replace the stock parameter file with the malaysk parameter file. Repack and flash.

mrmikey05 said:
The easier way of doing it is to extract the stock firmware and the malaysk firmware and replace the stock parameter file with the malaysk parameter file. Repack and flash.
Click to expand...
Click to collapse
That's the step by step guide: http://forum.xda-developers.com/and...d-head-units-qa/internal-storage-fix-t3257827

Related

[ADV](multi)u-boot v0.4

Source code is up at https://github.com/rookie1/u-boot-nc1.2
May 15 - Thanks to verygreen, I've modified multi u-boot to solve SD booting problem. Version bumped to 0.4.
It's reported the previous version has compatibility issues with 2.6.32 kernel. I've updated multi u-boot base on B&N 1.2 source. Now it's flashable using CWM. Boot message should show "(multi)U-Boot v0.4 loading..." after flashing this. Note this zip is for flashing to EMMC. For people using this on SD card, you need to manually copy the u-boot.bin in this zip file to your SD card boot partition.
Download link - http://dl.dropbox.com/u/20480343/multi-uboot-v0.4.zip
Looks like people are requesting different boot orders. I've created this multi-boot capable u-boot for you all
Install instructions
1. If you plan to use a bootable sd card to control the boot, replace u-boot.bin on 1st partition of the sd card with my (multi)u-boot.bin. Remember to make a backup of your original u-boot.bin just in case.
2. If you do not plan to use a bootable sd card, replace the u-boot.bin on 1st partition of the eMMC. Again remember to make a backup.
How to configure boot
normal boot is booting up without pressing any key. alternate boot is booting up with Home key ('n' key) pressed. recovery boot is booting up with both Vol+ and Vol- key pressed.
1. Boot device order
Which device to boot from is controlled by a file called u-boot.order in the same partition as (multi)u-boot.bin. Only the 1st 2 bytes of this file are significant. The first byte tells (multi)u-boot.bin where to look for kernel/ramdisk in normal boot. 2nd byte tells (multi)u-boot.bin where to look for kernel/ramdisk in alternate boot.
Value '0' means sd card, value '1' means eMMC.
For example, if you do "echo 10 > u-boot.order", you are telling (multi)u-boot.bin to load kernel/ramdisk from eMMC in normal boot, and load from sd card in alternate boot.
If this file is not present, both normal and alternate boot will load from the device where u-boot.bin is.
2. Alternate boot kernel/ramdisk file name
In the same partition as (multi)u-boot.bin, you can create 2 new files, u-boot.altimg and u-boot.altram to specify the kernel image and ramdisk file name to load in alternate boot.
In normal boot, (multi)u-boot.bin loads default kernel image (uImage) and default ramdisk (uRamdisk) from the device specified by the 1st byte in u-boot.order.
If either file is not present, the default value (uImage or uRamdisk) will be used.
Example configuration
1. eMMC stock eclair, sd card froyo or hc, and you want to boot normally into eMMC, and press 'n' key to boot into sd card
- put (multi)u-boot.bin into sd card 1st partition
- create a text file named u-boot.order in you sd card 1st partition, which contains 10
2. eMMC stock eclair, sd card froyo or hc, and you want to boot normally into sd card, and press 'n' key to boot into eMMC
- put (multi)u-boot.bin into sd card 1st partition
- create a file named u-boot.order, which contains 01
3. eMMC contains dual boot eclair and froyo (see my dual-boot post), boot normally into stock, press 'n' to boot into froyo
- put (multi)u-boot.bin into eMMC 1st partition
- if you have setup dual boot using my script, create a text file named u-boot.altimg, which contains the word "uFImg" (without quotes), and another text file named u-boot.altram with content "uFRam" (without quotes).
There are other combinations possible, e.g. creating a dual boot froyo and hc sd card without touching stock eMMC, using oc kernel as normal boot and stock kernel as alternate boot, etc.
Awesome, thanks!
Thanks for this! Looking forward to giving it a go this afternoon.
Thanks, this is going to be fun. Much easier than lilo
Works great!
I was going to try my hand at this but didn't know exactly what files to modify when making u-boot.bin. Any pointers on what you modified? Thanks!
ver2go said:
Thanks, this is going to be fun. Much easier than lilo
Click to expand...
Click to collapse
Does anybody even use lilo anymore? Civilized people use grub =P
criley said:
Does anybody even use lilo anymore? Civilized people use grub =P
Click to expand...
Click to collapse
Yes, but grub2... now there is the wrench in the monkey works. Back to lilo is easier than dealing with grub2.
Awesome, thanks.
Sent from my LogicPD Zoom2 using Tapatalk
Ok, what about running NF or HC and stock Eclair on the eMMC, with Stock being the Alternate boot?
fwdixon said:
Ok, what about running NF or HC and stock Eclair on the eMMC, with Stock being the Alternate boot?
Click to expand...
Click to collapse
Sure. Just do the following (assuming you have already got dual boot set up correctly)
- rename uImage (stock kernel) to uImage.stock
- rename uRamdisk (stock ramdisk) to uRamdisk.stock
- rename uFImg (NF kernel) to uImage
- rename uFRam (NF ramdisk) to uRamdisk
- u-boot.altimg should contain "uImage.stock"
- u-boot.altram should contain "uRamdisk.stock"
Btw, my modified u-boot only reads 16 characters from u-boot.altimg and u-boot.altram. So limit your kernel image and ramdisk file name length to less than 16 chars. Otherwise unexpected things can happen.
i would love to do this, but can we get step by step retard noob instructions for windows please? i would like to boot emmc froyo default and sdcard HC with the n key held.
rookie1 said:
Sure. Just do the following (assuming you have already got dual boot set up correctly)
- rename uImage (stock kernel) to uImage.stock
- rename uRamdisk (stock ramdisk) to uRamdisk.stock
- rename uFImg (NF kernel) to uImage
- rename uFRam (NF ramdisk) to uRamdisk
- u-boot.altimg should contain "uImage.stock"
- u-boot.altram should contain "uRamdisk.stock"
Btw, my modified u-boot only reads 16 characters from u-boot.altimg and u-boot.altram. So limit your kernel image and ramdisk file name length to less than 16 chars. Otherwise unexpected things can happen.
Click to expand...
Click to collapse
Awesome! That's what I was thinking, but jsut wanted to get confirmation. Also, good to know on the character limit in the names.
DomSim said:
i would love to do this, but can we get step by step retard noob instructions for windows please? i would like to boot emmc froyo default and sdcard HC with the n key held.
Click to expand...
Click to collapse
rookie1 said:
Example configuration
1. eMMC stock eclair, sd card froyo or hc, and you want to boot normally into eMMC, and press 'n' key to boot into sd card
- put (multi)u-boot.bin into sd card 1st partition
- create a text file named u-boot.order in you sd card 1st partition, which contains 10
Click to expand...
Click to collapse
I'm assuming you already have froyo on the emmc, but the above is all you have to do.
In simple steps
1. Put your HC sdcard in your card reader on your Windows machine.
2. Make a copy of the existing u-boot.bin and save it to your hard-drive somewhere in case you don't like this.
3. Open a text editor and type "10" without the quotes and save the file as u-boot.order
4. Copy the u-boot.bin file out of the zip in the OP over to the sdcard (this will overwrite the original but we backed it up already in step 2)
5. Copy the u-boot.order file to the sdcard
6. Unmount sdcard from Windows and put it in your Nook and boot it up
Enjoy
well, that sounds way easier than i thought. i thought i had to create and move a file onto the emmc portion of the phone, not the sdcard. also, wasnt clean on editing the the order file, thought i needed to hex edit it or something. trying now!
soonereng said:
I'm assuming you already have froyo on the emmc, but the above is all you have to do.
In simple steps
1. Put your HC sdcard in your card reader on your Windows machine.
2. Make a copy of the existing u-boot.bin and save it to your hard-drive somewhere in case you don't like this.
3. Open a text editor and type "10" without the quotes and save the file as u-boot.order
4. Copy the u-boot.bin file out of the zip in the OP over to the sdcard (this will overwrite the original but we backed it up already in step 2)
5. Copy the u-boot.order file to the sdcard
6. Unmount sdcard from Windows and put it in your Nook and boot it up
Enjoy
Click to expand...
Click to collapse
worked! just one question. when booted into emmc froyo, if i mount sd card by dragging down the notifiction menu and select mount, it mounts the "boot" partition for the HC build on the sdcard. im pretty sure that if i load up files in that area for the emmc froyo to use, it will keep HC from booting right? can this be changed so both the emmc froyo build and the sdcard honeycomb build can share the same sdcard partition?
Sweet, a way for us NF users to get a recovery. Thanks for putting this together.
You can switch the partition that is loaded as sdcard by edition the file "vold.conference" in the /etc directory. Add "partition 4" in the second block, similar to what is in the first block. This will enable the emmc and the sdcard o/s yo share the same SD card files yassuming partition 4 is the SD card partition
Sent from my LogicPD Zoom2 using XDA App
Edit: that should be "vold.conf" not conference ... Darn auto-correct.
jasoraso said:
You can switch the partition that is loaded as sdcard by edition the file "vold.conference" in the /etc directory. Add "partition 4" in the second block, similar to what is in the first block. This will enable the emmc and the sdcard o/s yo share the same SD card files yassuming partition 4 is the SD card partition
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
i do not have a vold.conference in my /etc directory. at lease according to root explorer.
DomSim said:
i do not have a vold.conference in my /etc directory. at lease according to root explorer.
Click to expand...
Click to collapse
Yeah, I'm only finding a "vold.fstab" in my /etc.
I'm trying to do the exact same thing as DomSim.
Maybe the vold.conf file is only on eclair. I have eclair on emmc and hc on sd. This trick works c for eclair

[RECOVERY] Making an updated bootable ClockworkMod SD

Edit edit edit edit: I sold my Nook Color in the summer of 2012. If there is anything you need me to edit into this top post I am happy to. Thanks!
Edit edit edit: I still own a Nook Color but I will not be actively editing this thread anymore. Here is the gist of it: You take any bootable Clockwork SD card, paste over the uRecImg and uImage files as needed for newer versions of CWM, and now you have an updated card. I was advised to warn you guys that the 3.0.x.x versions of CWM are not compatible with newer NC devices that have different partition tables. I was also asked to post the following:
eyeballer said:
Download 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image ... no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Click to expand...
Click to collapse
But I do want to point I disagree with the statement that "you really only need the 1GB image"... I use my CWM SD to make nandroid backups before major changes, so it makes a difference to have the full size of your SD available.
---- end of edit. Happy hacking!
I just wanted to report that I was able to take files from two different threads and use them to create a bootable SD card with ClockworkMod 3.0.1.0 and now 3.0.2.8. The advantage of this version is that it works for both ext3 and ext4 ROMs. I successfully flashed an ext4 version of Honeycomb and then restored back to my nandroid backup of auto-nooted Eclair.
EDIT: Direct links to 3.0.2.8 bootable images here: http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/
Source of those files is this post: http://forum.xda-developers.com/showpost.php?p=13283643&postcount=34
Credit to DizzyDen.
Image writer here: https://launchpad.net/win32-image-writer
NEW INSTRUCTIONS
1) Obtain the image for your SD card size here, containing any version of CWM:
(This link is now broken.)
http://legacyschool.us.to/nookdev/clockwork/0.7/
(source: http://forum.xda-developers.com/showthread.php?t=922870)
2) Obtain the correct uImage and uRamdisk files for CWM 3.0.2.8. The way I did this was to flash CWM 3.0.2.8 from ROM Manager and then mount my /boot partition to copy out the files uRecImg and uRecRam. But for the benefit of those of you here who can't flash CWM successfully, I've attached the files here.
3) Burn the SD card as instructed. Leave the SD mounted in your computer afterwards.
4) Rename your copy of the new uRecImg to uImage and replace the uImage file on the SD.
Rename your copy of the new uRecRam to uRamdisk and replace the uRamdisk file on SD.
5) Eject the SD from your computer, pop it into your Nook Color, reboot and verify that you indeed manage to boot into the new desired version of ClockworkMod. Upon completion I had a bootable 3.0.2.8 SD card.
OLD INSTRUCTIONS BELOW
I haven't seen anyone here post an SD image for 3.0.1.0, so here is what I did instead:
1) Obtain the image for your SD card size here, containing CWM 3.0.0.5 at time of writing:
http://legacyschool.us.to/nookdev/clockwork/0.7/
(source: http://forum.xda-developers.com/showthread.php?t=922870)
2) Also get the newer version of ClockwordMod in .zip format:
3.0.1.0 is here: http://muffinworld.net/android/nookcolor/clockwork/cwmr_3.0.1.0.zip
(source: http://forum.xda-developers.com/showthread.php?t=971197)
3) Burn the SD card as instructed. Leave the SD mounted in your computer afterwards.
4) Unzip the files uRecImg and uRecRam from the newer CWR zip.
Rename uRecImg to uImage and replace the uImage file on the SD.
Rename uRecRam to uRamdisk and replace the uRamdisk file on SD.
5) Eject the SD from your computer, pop it into your Nook Color, reboot and verify that you indeed manage to boot into the new desired version of ClockworkMod.
Enjoy!
EDIT: Post #4 below contains IMG files created using this method for ClockworkMod 3.0.1.0. Thanks to DizzyDen.
http://forum.xda-developers.com/showpost.php?p=11999569&postcount=4
Thanks, I will be trying this out later today probably.
Nice post and great info. I just did this as a test run last night myself and was going to make a thread explaining what to do but you have now saved me the time in doing that.
I can say this works great as I have flashed and restored backups between ext4 and ext3 builds. I went from Nook OS, to HC, back to Nook, over to CM&, back to Nook all wiht no issues.
Updated SD IMG files
NOTE: 3.0.2.8 images in POST 34 of this thread... ALL credit still goes to OP
All credit goes to OP... all I did is updated the original SD *.0.7.img files with OP's results....
I renamed them to *.3.0.1.0.img to distinguish which version of CWR image and ramdisk files are being utilized. I also compressed to rar to distinguish these are not CWR flashable zip files.
NOTE: 4 gig fixed 03/18/11... My apologies for my initial mistake... thank you for those who caught it and reported.
M5 Checksums:
RAR's:
Code:
128mb_clockwork-3.0.1.0.rar
049C0B4437473100FB294968CAC08CF9
1gb_clockwork-3.0.1.0.rar
D95324AE63DDAEC713B30A69CEE61C9B
2gb_clockwork-3.0.1.0.rar
4E8F088D17246750DA628133F177F91F
4gb_clockwork-3.0.1.0.rar
EA6C8FA2B7932113E59EF61448425B0C
8gb_clockwork-3.0.1.0.rar
5C80CBCFC09E47A50D9EC04EFA70DE9C
GZ's (only available on RapidShare due to file type):
Code:
128mb_clockwork-3.0.1.0.img.gz
C2531B8AF258C06BD794A3EC08ABC2D1
1gb_clockwork-3.0.1.0.img.gz
26ABB66BFEEA76C8AD0ABBA97EDC964E
2gb_clockwork-3.0.1.0.img.gz
3D8F05F0F6FF39271F5F82DBCC4403A3
4gb_clockwork-3.0.1.0.img.gz
8A13A55E045F23F3D3BE5354EDEC26B5
8gb_clockwork-3.0.1.0.img.gz
48D8CB4B93E57FC121C8082CB23FD98F
IMG's:
Code:
128mb_clockwork-3.0.1.0.img
297793ED7B371BB116F4B27AF095E18D
1gb_clockwork-3.0.1.0.img
D104AE6297662664C339D08BDFAED858
2gb_clockwork-3.0.1.0.img
B2EB4B7C24C1D8A1414BE9FE6BF697F4
4gb_clockwork-3.0.1.0.img
147A648D285815C7C175E42612B5E4A2
8gb_clockwork-3.0.1.0.img
8AD83B4ED74541AAB75103843E990088
RapidShare mirrors (folder includes .gz files):
RapidShare mirrors (folder includes .gz files)
NOTE: there's also a 16 GB version on RS... just can't upload that large file here.
Thank you!
You are very welcome... and thank you!
I suppose I could compress the img's to gz for those with linux exclusively... if anyone would like this... just let me know.
Awesome many thanks for the effort Dizzy. Will make life alot easier for many folks I'm sure.
If anyone has or is willing to flash the most current CWR ( 3.0.1.3) to there device and then pull the uRecImg and uRecRam files and post them would be great. Then we can update our current 3.0.1.0 sdcards to 3.0.1.3.
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
hellomynameis said:
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
Click to expand...
Click to collapse
I'm assuming you are seeing 3.0.0.5 as the version on the internal mem and not a bootbale sdcard. If it is from the internal mem then yes you are a bit behind on the most current version of CWR. and should get updated to the most current version. To get more current you will need to check this thread out first to get to 3.0.1.0. from there you should be able to use Rom Manager to update to 3.0.1.3.
http://forum.xda-developers.com/showthread.php?t=971197
I tried updating... but ROM Manager says 3.0.1.0 is still the newest.
Has anyone modified a Recover Ramdisk (uRecRam) that maps the FS to allow CWR to flash/install files to the SDcard vs. EMMC partitions? If so would you be willing to share as I suspect a good number of folks would be very grateful as would simplifiy greatly installing things like Gapps to SDcard installs...
hellomynameis said:
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
Click to expand...
Click to collapse
Getting the same thing... and I haven't installed CWM to the internal memory. At least not that I know of
I'm going to try burning the image again.
hellomynameis said:
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
Click to expand...
Click to collapse
Curious did you happen to use the 4Gb image file. If so you would be correct I just saw a post from someone else saying they used the 4Gb file and it installs 3.0.0.5 still
@Dizzy if you happen to see this any chance you can look into and correct the 4Gb file you posted. It is still installing 3.0.0.5 supposedly. Here is a link to the person who ran into the prob
http://forum.xda-developers.com/showthread.php?p=12192636#post12192636
4 gig files fixed....
4 gig files still having old uimage files reported and fixed... my apologies for any inconvenience....
Post 4 fixed with new files and MD5's
cmstlist said:
http://muffinworld.net/android/nookcolor/clockwork/cwmr_3.0.1.0.zip
Click to expand...
Click to collapse
This URL does not work. Anyone able to provide an alternate?
swapdotavi said:
This URL does not work. Anyone able to provide an alternate?
Click to expand...
Click to collapse
You'd get better response asking in the muffin thread... this thread is about updating your CWR SD's... with images pre-made in post 4.
swapdotavi said:
This URL does not work. Anyone able to provide an alternate?
Click to expand...
Click to collapse
Swapped webhost....was down for about 24 hours. I wanted everyone to know the files are fine now.
Sorry fellas, I'm a little behind the power curve here. So why would i need a bootable CWM-SD? Would it be useful for flashing and restoring a backup if your NC accidentally got zapped with the 1.2 update, then you could pop in your CWM-SD and restore back to 1.1? I'm just running Auto-nooter stock rom right now, will it work with stock? I turned off Wi-Fi for now, but would like to turn it back on. Would be nice if I could revert back to 1.1 if I got the OTA accidentally.
Can we get the files to make a bootable SD card with CWR 3.0.2.8?
Thanks,
Andy

[ADV][DEV][CWM]Copy Nook Stock to SDcard Image[5/9]

Hi again everyone,
I've noticed that some people have been inquiring about getting their Stock Nook Color rom onto an SDcard. And due to legal issues with distributing the B&N rom. It would not be wise to just "dd" the stock partitions to an .img file and post it for everyone to share. On top of the fact that each Nook has the /rom and /factory partition which stores each devices unique id's. So to work around that, here's an image file with a flashable .zip that will move your stock partitions to your SDcard via a modded CWM that is preinstalled with the .img file. Hope I'm not confusing anyone?!
**DISCLAIMERS: Please read and accept all that is noted below in red**
1-I do not take responsibility for whatever happens to your Nook Color. You are doing this at your own risk. If you are unsure about what's going on here. Then I'd suggest leave your Nook how it is!
2-I tried not to mess with the /rom partition because it stores very important unique device identifiers in that partition. But no matter what I did, it kept stalling on boot. However, I did leave the /factory partition alone. Which stores a rombackup.zip of your device id's. So I would suggest backing up these two very important partitions and store it somewhere safe!
3-On the above note. This is very important. Do not try and use this SDcard on any other nook than your own. I'm not sure what will happen. But I really don't want to find out.
4-Never, ever have the same Nook Stock rom running at the same time for any reason. This will intefere with the B&N servers and send a signal to De-authorize and wipe your nook. On top of that. It might just brick your nook from ever registering again!
5-This is mounting your internal partitions to copy over to the SDcard partitions. So again, if you are unsure or hesitant or not brave enough to touch your EMMC partitions. Please drop your SDcard that you were about to burn and walk away, slowly...
6-I assume you accept all the above. If so, please continue reading for the fun stuff!
Credits:
Rookie1 (for the initial eclair2dualboot script)
Nemith (for CWM Recovery used)
NOOK Stock to SD v0.1
What we have here is an .img file with partitions already created and ready for you to transfer your Stock Nook rom over to your SDcard. I would like to thank rookie1 for his initial script for moving Stock Eclair to Dualboot. I just took that and modified the script to work with the SDcard install. The script will still make use of your internal 5gb emmc Media partition as well. This will also modify all the necessary files on the fly to work with your Nook SDcard Rom (eg. uRamdisk, vold.fstab...etc).
I made the .img file around 7.4 gb so that people won't have issues burning it to an 8gb card. If you want to get use of the full 8gb or 16gb card. Use EASUS partition tool to extend the /sdcard (8th) partition.
FYI: I still for some reason or another can't grasp the CWM Recovery progress bar! Totally lost when it comes to inserting the correct values in the edify script. It extends past where it should end. I'm sure it's something very simple and maybe my mind is just too tired or better yet lazy to figure it out. So if anyone can advise me on the issue, please do.
Instructions and Pre-requisites:
**Backup your NOOK!!!!!**
1-You need a Nook Color with stock rom on EMMC already registered (root it now if you wish)
2-An 8gb uSDcard or larger
2-Download Nook Stock 2 SD v0.1
3-Unzip and follow directions from Nookdevs.com to burn the .img file to your SDcard
4-Power off Nook
5-Place the SDcard that you just burned stock2sd_v0.1.img to in your Nook and power on
6-It will boot to CWM Recovery. Now choose to "install zip from sdcard"
7-Now select "choose zip from sdcard"
8-Choose "stock2sd_v0.1.zip" and confirm "yes"
9-Sit back and wait... be patient! This will take a while.
10-When finished it will say "Can you believe it! It's stock Nook on your SDcard!"
11-Leave SDcard in Nook and go back to CWM main menu and choose to "reboot system now"
12-Enjoy your Stock Nook rom on your SDcard! Now go flash all the other roms to your EMMC!
Edit 5/9: I noticed that some people have issues with the .img file when uncompressed. So I've uploaded an alternative file to try if the first didn't work. The new file is a 7zip file. It offered better compression so the file size is much smaller as well. Hope this helps out the few that had issues.
Download:
stock2sd_v0.1a.zip
MD5-4aecd4f8fc4d7c40bbe392d8cb970853
4shared | Rapidshare
Update: 5/9 stock2sd_v0.1.img.7z
MD5: b72dd3cc0413b6fdadf899cfdf48b24e
4shared | Rapidshare
Click to expand...
Click to collapse
For anyone that has an alternative rom on your EMMC already. Mr_fosi wrote a nice write up on how to backup your current rom, restore to stock, copy stock to SD, and then revert back to your original setup on EMMC. Don't forget to give him a thanks for the great write up!
Mr_fosi's Guide
Hey, if I've helped in someway. Please show your appreciate with a thanks in one way or another!
Thanks,
Racks
Will try this as soon as I get a new SD card... have been wanting to be able to do this for a while, thanks!
Thanks for this!
Sent from my NookColor using XDA Premium App
Would this be the correct steps for getting rooted Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC and want to restore it when we are done. Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music.
First of all thanks for making this.
1) Use Titanium Backup "Batch" option to "Run Backup all user apps + system data".
2) Have ClockworkMod 3.0.1.0 (or higher) in EMMC. Use ROM Manager v4.2.0.2 (or higher) to "Backup Current ROM". I like to append a PhV6.2 to the end of the file name. This procedure is referred to as making a Nandroid backup.
3) Mount your current sd card on a pc and copy the folder TitaniumBackup to it. Open the folder clockworkmod on the sd card and copy the Nandroid backup folder made in step 2) to the pc. This is for backup purposes. Not used in the procedure.
4) Use the procedure in thread "[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM" to change your EMMC ROM back to stock. There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot). Not sure which one to use? Perfer the doesn't replace CWM, will this work with the procedure in this thread to move "Nook Stock to SDcard Image[5/3]"?
5) Use the procedure in thread "ManualNooter 4.5.2 (For Stock 1.2)" to root your nook.
6) Use the procedure in this thread "[ADV][DEV][CWM]Nook Stock to SDcard Image[5/3]" to move the rooted 1.2 to the sd card.
7) Install original sd card. Manually Boot into EMMC Recovery (ClockworkMod 3.0.1.0 or higher - hold Power button + n button for 6 seconds). Restore the Nandroid backup folder made in step 2).
OP udated with download link.
Thanks,
Racks
Will buy an SD and give this a shot.
Quick confirmatory questions:
- Having read the OP, it seems as though you are not intentionally modifying the partitions or their contents on the EMMC, correct?
- I haven't looked at the script, but what you wrote here says that they are only mounted and copied, yes?
- Finally, this does not change the read/write flag on any of the partitions on the EMMC?
Thanks for the work on this, I sure hope it works when I try it!
lschroeder said:
... Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC ... Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music...
.
Click to expand...
Click to collapse
Eventual goal is to replace Phiremod V6.2 EMMC with a ROM based on CM7.1.x that has sleep fixed, wifi staple, bluetooth range extended - bluetooth keyboard functioning with wifi, hardware accelerated with over clocking at 1200/1300 and a rooted Stock 1.2 for the magazine and other reader features. Guess I am asking for a lot but I have faith in you developers!
mr_fosi said:
Will buy an SD and give this a shot.
Quick confirmatory questions:
- Having read the OP, it seems as though you are not intentionally modifying the partitions or their contents on the EMMC, correct?
- I haven't looked at the script, but what you wrote here says that they are only mounted and copied, yes?
- Finally, this does not change the read/write flag on any of the partitions on the EMMC?
Thanks for the work on this, I sure hope it works when I try it!
Click to expand...
Click to collapse
1-Not modifying anything on EMMC
2-Yes mounted then copied
3-It shouldn't change any or the read/write flags on your EMMC
Thanks,
Racks
Awesome.
This looks to be worth undoing my nice CM7 install, reverting back to 1.1 (then upping to 1.2) for. I would very much like to get some of the stock functionality back and this looks like a great way to do it without having to modify my EMMC partition table.
The dual-boot option looked promising as well but I really don't want to mod the partitions on this thing, especially since I use CM7 most of the time.
lschroeder said:
Would this be the correct steps for getting rooted Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC and want to restore it when we are done. Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music.
First of all thanks for making this.
1) Use Titanium Backup "Batch" option to "Run Backup all user apps + system data".
2) Have ClockworkMod 3.0.1.0 (or higher) in EMMC. Use ROM Manager v4.2.0.2 (or higher) to "Backup Current ROM". I like to append a PhV6.2 to the end of the file name. This procedure is referred to as making a Nandroid backup.
3) Mount your current sd card on a pc and copy the folder TitaniumBackup to it. Open the folder clockworkmod on the sd card and copy the Nandroid backup folder made in step 2) to the pc. This is for backup purposes. Not used in the procedure.
4) Use the procedure in thread "[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM" to change your EMMC ROM back to stock. There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot). Not sure which one to use? Perfer the doesn't replace CWM, will this work with the procedure in this thread to move "Nook Stock to SDcard Image[5/3]"?
5) Use the procedure in thread "ManualNooter 4.5.2 (For Stock 1.2)" to root your nook.
6) Use the procedure in this thread "[ADV][DEV][CWM]Nook Stock to SDcard Image[5/3]" to move the rooted 1.2 to the sd card.
7) Install original sd card. Manually Boot into EMMC Recovery (ClockworkMod 3.0.1.0 or higher - hold Power button + n button for 6 seconds). Restore the Nandroid backup folder made in step 2).
Click to expand...
Click to collapse
I don't think it matters which restore to stock .zip you use. This script will basically copy what ever setup you have on your EMMC to your SDcard. Your steps are correct as I see it. Please advise if the steps you took worked or not.
Thanks,
Racks
I am getting a corrupt error when unzipping img with winrar. I have download 3 times different download places.
patgnds said:
I am getting a corrupt error when unzipping img with winrar. I have download 3 times different download places.
Click to expand...
Click to collapse
Thanks for advising. I'm checking the download now. Anyone else have the same issue?
The problem seems to be in the reported size of the original file within the zip.
In mine (downloaded from the hated Rapidshare):
- Compressed size: 120,494 kb
- Original size: 807,167,488,681,452 kb
Maybe a corrupt compression?
Same issue...corrupt, download size is 4k.
Sent from my HTC Vision using XDA Premium App
mr_fosi said:
The problem seems to be in the reported size of the original file within the zip.
In mine (downloaded from the hated Rapidshare):
- Compressed size: 120,494 kb
- Original size: 807,167,488,681,452 kb
Maybe a corrupt compression?
Click to expand...
Click to collapse
Thanks for the advise. I'll take down the link until further notice. Sorry for this everyone.
Thanks,
Racks
Edit: I've just downloaded it to my mac at work and used Stuffit Deluxe to unzip it. And it unzipped and mounted fine for me. I'll see if I can rezip this one and reupload.
The MD5 of the file I have matches the one posted in the OP, so I am fairly sure the download wasn't corrupted. It seems to be a problem with the original file uploaded.
A quick re-zip might fix the issue.
I did burn the rom and installed the zip from cwr it worked.
So you must have been able to unzip the IMG? Can you share the zip file you used and post it's MD5?
Dual boot setup.
Does this copy all partitions on the emmc or just the first boot partitions? I have dual boot setup with stock on the second boot. If I could just copy the whole setup to an sd card it would be pretty slick. Thanks for your hard work.
1CF71B239DB860A36CD70C3FB8F70FEC
partitions
boot
rom
factory
system
data
cache
sdcard

[Q] Flash memory on Allview A4 you

I would like to install a Rom on Allview A4 you in such manner that I can format the flash memory the way I want. In this moment I'm having 2Gb for media files and 2Gb for system files( 1.2Gb for system and 0.8Gb for apk).
Help with memory....
tudoras.rt said:
I would like to install a Rom on Allview A4 you in such manner that I can format the flash memory the way I want. In this moment I'm having 2Gb for media files and 2Gb for system files( 1.2Gb for system and 0.8Gb for apk).
Click to expand...
Click to collapse
I can help you with memory and you doesn't need to be rooted or to have custom rom.......but you will loose any guarantee.... because you wil make modification in system memory..... you have to download sp flash tool ... and drivers for cdc serial and after you downloaded all this files you must install inf file aand you will also need stock firmware for allview A4 you but you don't need to flash all files which are included in folder only mbr and ebr files which must be edited with this program:ROM Ebr changer..be sure to take v2.0:.......or I will edit them for you.....After you did that and flashed this 2 files on the phone you must do a factory reset because the system must set the new partitions size........My email is [email protected] send me pm if you don't understand something and I will tell you about custom roms on this phone.......

galaxy tab a (7 inch) swap internal and external sd lollipop

hello,
I have a samsung galaxy tab a.
this is a nice device but only has 8 gb of internal memory. it runs android 5.1
I'm trying to switch the internal and external sd memory. (to get more internal memory)
first of all the device needed to be rooted. I have done this, without any problem..
then I started searching how to switch the memory. I have tried different apps for this but they where not working.
after this I tried to swap the memory manually. I read somewhere this can be done in the vold.fstab file.
I didn't found this file.
after reading more about the topic I found out that the mounting for android 5.1 is done in the boot.img file.
I looked for how to unpack this file, and I'm doing this now with cygwin and android kitchen 0.224
I can unpack the boot.img but have a few questions.
1) the mounting should be done in fstab.<devicename>...... the device name is Galaxy Tab A (2016) but I can not find fstab.galaxy Tab A (2016), but fstab.goldfish and fstab.sc8830 is it possible the mounting is done in one of thes files ? (they are found in the root of the boot.img
2) what should I change in these files?
3) afther I have changed the mounting, how can I with android kitchen repack the boot.img
thank for any help
best regards,
Bart

Categories

Resources