Database Info

[Q] Multi-Booting

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

[Q] Pre-flash, some questions

I'm about to flash my first custom ROM on my Desire S.
It's S-OFF, rooted and fully backed up (nandroid, titanium backup, SD to PC).
I tried to read as much as possible abut the flashing process and some of the android internals. Excuse me if my questions are still a bit noobish, I tried to read a lot.
I've decided to try CM7 and repartition my SD card to add an ext4 sd-ext partition.
Before I flash, I still have some questions:
- Where is HBOOT located exactly? /boot ?
- Where is the recovery (ClockworkMod in my case) located? /recovery ?
- Revolutionary installed ClockworkMod. However, ROM Manager also offered me to flash it (that's what I did). Did ROM Manager overwrite the ClockworkMod in /recovery?
- Assuming that /boot and /recovery are critical (from my previous questions), and that they are backed up and available (nandroid backup files) on my PC, can I always push those back with adb in case something goes wrong?
- What's the correct order for the flash + repartition?
Repartition first, allow the wipe (data + everything) to wipe the SD during flashing, copy data back after new ROM is running?
- What's the safest/best way to flash? From HBOOT/recovery? Or ROM Manager? Or do they actually do exactly the same?
I.e. ROM Manager rebooting and starting ClockworkMod?
Sorry for all the questions. I'm pretty sure that the flash will work fine, but I always like to know more about the internals first.

Quark^2 said:
I'm about to flash my first custom ROM on my Desire S.
It's S-OFF, rooted and fully backed up (nandroid, titanium backup, SD to PC).
I tried to read as much as possible abut the flashing process and some of the android internals. Excuse me if my questions are still a bit noobish, I tried to read a lot.
I've decided to try CM7 and repartition my SD card to add an ext4 sd-ext partition.
Before I flash, I still have some questions:
- Where is HBOOT located exactly? /boot ?
- Where is the recovery (ClockworkMod in my case) located? /recovery ?
- Revolutionary installed ClockworkMod. However, ROM Manager also offered me to flash it (that's what I did). Did ROM Manager overwrite the ClockworkMod in /recovery?
- Assuming that /boot and /recovery are critical (from my previous questions), and that they are backed up and available (nandroid backup files) on my PC, can I always push those back with adb in case something goes wrong?
- What's the correct order for the flash + repartition?
Repartition first, allow the wipe (data + everything) to wipe the SD during flashing, copy data back after new ROM is running?
- What's the safest/best way to flash? From HBOOT/recovery? Or ROM Manager? Or do they actually do exactly the same?
I.e. ROM Manager rebooting and starting ClockworkMod?
Sorry for all the questions. I'm pretty sure that the flash will work fine, but I always like to know more about the internals first.
Click to expand...
Click to collapse
Very impressed to see someone actually ask intelligent questions....and seek a real understanding..
Unfortunately its now my dinner time....so I only have a few minutes....so I'll attempt to answer quickly:
YES (boot.img in backup), YES (recovery.img in backup) and unless you play lots of games and require lots of ext space this device has a decent amount of internal storage so that it doesn't require sd-ext partitions (that's just my opinion anyway - these partitions are something from when devices had minimal internal storage)
What I will say is yes you downgraded the CWM version that revolutionary had installed with an older one from ROM Mananager. So you'll be much better of to install EXT4 recovery (which is based on CWM) and overwrite the old CWM, so simply download this file onto your SD card and flash it from recovery over the existing CWM recovery....then when you reboot recovery you'll have the EXT4.

what are the advantages of ext4 recovery exactly? im also running the CWM from the CWMM.

kazen44 said:
what are the advantages of ext4 recovery exactly? im also running the CWM from the CWMM.
Click to expand...
Click to collapse
For a start its based on the same code base as CWM, but, has lots of added functionality, is far more user friendly, is constantly being updated and can be themed! The support is immense as well, just look at the thread.
there's too many to mention, simply read the EXT4 forum link in the page above so see them for yourself!
Just the file system conversion part of it is worth it!

whats the advantage of ext4 on a phone instead of ext3? ive worked with both filesystems quite a lot on my desktop PC. but there does not seem to be a major diffrence. i know that EXT4 supports journaling far better then ext3 does. but thats about the only thing i notice as diffrent on my linux install.

Actually boot and hboot are different things. I'm not 100% sure but I think that the kernel is located in the /boot partition, you are able to format it or replace its content from within the recovery.
Hboot is the initial bootloader that is located in a secure block of eMMC, you can't access it from recovery and can't backup it. If you completely wipe all partitions accessible through recovery, you still can easily install new ROM or restore from backup, even if you lose your recovery you can still restore it through fastboot. Phone with damaged or incorrect hboot is definitely a brick, it won't be accessible through PC connection and won't load up. Normally it's only possible to make permanent damage to the phone if you incorrectly flash hboot or radio image, while it's possible to brick even without messing with them, it's usually caused by faulty hardware (eMMC chip).

Ok thanks all so far.
So, HBOOT resides in eMMC and not is easily accessible (but still flashable).
At least, that's what Revolutionary did, my current HBOOT shows "Revolutionary" in the first line.
The kernel resides in /boot, which is the same for all all regular linux distros.
I think I have a clearer picture of the internals now. Still not 100% clear, but getting there.
I am going to flash 4EXTRecovery first, before trying to flash my first custom ROM.
Ofcourse, repeating the backup cycle, just in case.
I'm only left with these questions (for now ;-):
- What's the best way to flash now? From ROM Manager or 4EXTRecovery (from HBOOT manually)?
- Does the Wiping (everything, data + cache) also clear my SD card? I'm fairly sure it does.

Quark^2 said:
I'm only left with these questions (for now ;-):
- What's the best way to flash now? From ROM Manager or 4EXTRecovery (from HBOOT manually)?
- Does the Wiping (everything, data + cache) also clear my SD card? I'm fairly sure it does.
Click to expand...
Click to collapse
ROM Manager loads recovery in order to flash, so there is no real difference. Flashing from HBOOT is only required for updating hboot itself or radio, I'm pretty sure it's better to use recovery to flash everything else.
Wiping everything formats /boot, /system, /data and /cache partitions, it doesn't wipe SD card (would be kinda stupid if it did actually, as CWM recovery places backup files on SD). I still make SD card backups from time to time, just for convenience.

Evilmystic said:
Actually boot and hboot are different things. I'm not 100% sure but I think that the kernel is located in the /boot partition, you are able to format it or replace its content from within the recovery.
Hboot is the initial bootloader that is located in a secure block of eMMC, you can't access it from recovery and can't backup it. If you completely wipe all partitions accessible through recovery, you still can easily install new ROM or restore from backup, even if you lose your recovery you can still restore it through fastboot. Phone with damaged or incorrect hboot is definitely a brick, it won't be accessible through PC connection and won't load up. Normally it's only possible to make permanent damage to the phone if you incorrectly flash hboot or radio image, while it's possible to brick even without messing with them, it's usually caused by faulty hardware (eMMC chip).
Click to expand...
Click to collapse
Thanks for the correction , I also have a slightly clearer picture of the internals myself.

Evilmystic said:
ROM Manager loads recovery in order to flash, so there is no real difference. Flashing from HBOOT is only required for updating hboot itself or radio, I'm pretty sure it's better to use recovery to flash everything else.
Wiping everything formats /boot, /system, /data and /cache partitions, it doesn't wipe SD card (would be kinda stupid if it did actually, as CWM recovery places backup files on SD). I still make SD card backups from time to time, just for convenience.
Click to expand...
Click to collapse
Thanks for the correction , and on thinking it through of course you're right, I also have a slightly clearer picture of the internals myself.

Firerats + Data2ext Complete Installation Guide: Now works with Sense roms!

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.

Rom 101 + cwm error solutions

Now it's time for the partitions :good:
Let’s start with a list of standard internal memory partitions on Android phones and tablets. These are:
/boot
/system
/recovery
/data
/cache
/misc
In addition, there are the SD card partitions.
/sdcard
/sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices. Let’s now take a look at the purpose and contents of each of these partitions.
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the kernel and the ramdisk. Without this partition, the device will simply not be able to boot. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, other than the kernel and the ramdisk. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it. To learn more about this partition and its contents, see the ‘About Android Recovery’ section of our guide to ClockworkMod recovery.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy S and several tablets – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition, but has become popular in the custom ROM scene. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
With this, we conclude our tour of Android partitions. Now whenever you install a ROM or mod that requires you to wipe certain partitions before the installation, you should be in a better position to know what you’re losing and what not and thus, you’ll know what to backup and what not.

[info] rom 101 and cwm error solutions
Hi guys .You all know me.
I have created this thread for the sole purpose educating every newbie and noob about ROM and it's components...
Here goes
Parts of a ROM
i. The kernel.
Android (like many other Smartphone operating systems) runs on the Linux kernel. The Linux kernel was created in the early 1990’s by a gentleman named Linus Torvalds in Helsinki, Finland. It’s incredibly stable, incredibly friendly, and incredibly difficult for the layman to understand and modify. Thankfully it’s also very popular so it has been ported on to a multitude of hardware, including our Android devices.
Think of the kernel as an interface layer between the hardware and software on your device. The kernel decides when things happen, such as the LED indicator gets lit or when the soft button's LED gets lit. An application sends a request to the operating system to blink the LED. The operating system then sends the request to the kernel, which makes the light flash for the amount of time requested by the OS.
What sounds like a round-about way to get things done is also what makes the system so scalable and robust. Application developers only have to code in a way the operating system understands and the kernel makes it work on the hardware. This also keeps the application running in it’s own user-space and separate from the kernel. That means when you run the latest uber-cool app that wasn’t designed for your particular OS version, or is still very beta and it crashes, the kernel gives you the option to Force Close the application and the kernel can run untouched.
In a standard Android ROM (we will leave developer images and the like for another discussion) the kernel is bundled along with a set of instructions that tell the device how to load the kernel and the OS during boot. This is the boot.img that you see inside a zipped ROM that your not able to easily open. The device knows to extract this image to internal memory (the ramdisk) and follow a series of scripts (init scripts) to load the kernel and then the other portions of the OS. That’s what’s happening while you’re watching the boot animation. Interestingly enough this is done the same way for a PC, your smartphone, an Android tablet, or even a smart Linux powered toaster. If you’re feeling exceptionally geeky, plug your Android phone into the USB port on your PC and let the PC boot from the USB device. No, it doesn’t actually load, but you can watch the animation while it tries to match up the hardware support with what’s inside your PC. As I said, Linux is amazingly scalable and as a result so is Android.
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
Click to expand...
Click to collapse
ii. The operating system.
Once the kernel is loaded, the init scripts tell the Operating System to load. Android is the user interface for a custom built Java virtual machine called Dalvik. Dalvik was written by Dan Bornstein, who named it after the fishing village of Dalvik in Iceland, where his family originated from. The debate of which Java VM is superior is best left for another discussion, so I’ll simply say that DalvikVM is a register-based machine versus true JavaVMs which are stack based.
The Dalvik machine creates executable files (.dex files) which can be interpreted by the OS and run by the end user. These .dex files are OS version dependant. That simply means that applications and core functions built to work with one version of Android may or may not work well with other versions. Google provides the tools through it’s Software Development Kit (SDK) for applications to communicate with the OS.
Click to expand...
Click to collapse
iii. Core functions.
No smartphone would be complete without a set of functions that allow the device to be used as intended. Things like the phone and dialer interface, the calendar, the messaging system are core functions of the Operating System. In Android, these are run on top of the kernel as separate applications. The merits (or lack of) of providing these needed functions as separate applications is once again best left for another discussion, but this is what allows developers like HTC or Motorola to replace the standard functions with alternatives that provide a different look and feel from stock. HTC’s onscreen keyboard or Motorola’s MotoBlur contact list are great examples of this. The “little guy” isn’t left out of the mix either. Handcent SMS or Chomp SMS can integrate into the OS very well, as most of us already know.
An additional set of Core Functions are provided by Google. Popularly called GoogleBits, things like Gmail, sync, Gtalk and the Android Market are applications written by Google that give an extra set of useful functions to the OS. You’ll find these on all smartphones, as well as many other Android devices.
Click to expand...
Click to collapse
iv. Optional applications.
These are applications provided by the manufacturer to give the device even more usability. Things like the Amazon MP3 store, PDF readers, Corporate Calendar etc. allow you to do even more with your device. Remember - Droid Does
Click to expand...
Click to collapse
B. How is a ROM packaged?
In most cases a ROM will come packaged in a .zip file. The recovery image’s kernel (yes, it has one too!) has the ability to unzip and copy the contents into the correct place. Inside this zip file is a folder
Click to expand...
Click to collapse

ROM & IT's COMPONENTS + CWM ERROR SOLUTIONS
ERRORS encountered in CWM Recovery
.
What is CWM Recovery ?
ClockworkMod Recovery is a custom recovery for many Android devices. It is considered to be the most popular recovery for Android due to its easily-ported nature, and integration with ClockworkMod ROM Manager by Koush(Koushik Dutta). The easiest way to recognize it is by the printed name when it first starts, and the background logo of a gear and hat.
Click to expand...
Click to collapse
ERROR STATUS 6
This is usually caused by CR/LF EOL(Windows style End Of Line) in updater-script. Change it to LF EOL(Unix Style EOL) using Linux command: dos2unix updater-script, then re-signing the ZIP, will usually fix this error.
Click to expand...
Click to collapse
ERROR STATUS 7
This is usually caused by a corrupt download, or bad file signature. Re-downloading (or re-signing) the ZIP will usually fix this.
Click to expand...
Click to collapse
We have been consistently seen and heard people facing error “Status 7″ error while trying to flash or install
custom ROMs or firmware packages on their Android smart phones or tablets with ClockworkMod Recovery. Many
of the users are nowadays facing this problem with CWM Recovery while flashing .zip files of modded or custom
Ice Cream Sandwich (ICS) or Jelly Bean (JB) ROMs on their devices. So, you have also downloaded a custom ROM,
placed its .zip file in your phone’s or tablet’s SD card, booted into ClockworkMod Recovery, selected – “install zip
from sdcard” and then chosen the .zip file of the ROM to get it installed on your device. But instead of getting
flashed successfully, if you are facing the issue mentioned below, then just keep reading this article to find out
what’s wrong and fix up the problem :
Finding update package…
Opening update package…
Installing update…
Error in /sdcard/custom-jelly-bean-rom.zip (Status 7)
Installation aborted
Click to expand...
Click to collapse
or the following error right after CWM recovery shows –
Installing update…
assert failed: getprop(“ro.product.device”) == “I9103″ || getprop(“ro.build.product”) == “I9103″ || getprop
(“ro.product.board”) == “I9103″
Error in /sdcard/android-4-1-1-ics-rom-latest.zip (status 7)
Click to expand...
Click to collapse
So, if you are facing any of these errors while trying to install the desired custom ROM package on your Android
phone or tab, then you may try a various things or steps which may turn out to be the workaround of this
problem. Here are a few tips to get this “Status 7” error fixed in ClockworkMod Recovery and flash the ROM
successfully on your device :
(1) First of all, make sure your device’s bootloader is unlocked. If it is already unlocked but you are still
not able to flash the ROM, then just extract the .zip file of the ROM into a new folder, find the boot.img file from
that directory and flash it up on your phone or tablet via fastboot on your PC.
(2) Make sure that you are having the appropriate Radio or Baseband version installed on your device which is
supported by the custom ROM you are trying to flash. Most of the ROMs requires the latest version of Baseband, so
just update or upgrade your device to the latest Baseband version and then try to install the ROM once again.
(3) Update your device to the supported / latest build of official firmware before trying to install the ROM. You can
do it from – Settings > About Phone / Device > Software Update.
(4) Make sure you are having the supported or required kernel installed on your phone or tab. If it’s not, then flash
a new kernel right away and try to install your custom ROM once again.
(5) Is the ROM which you are trying to flash really works ? Find out whether it is working for other users or not.
Click to expand...
Click to collapse

its seems great buddy. Great Info. But as I always say, make it readable. Means highlights heading & important informations.
Edit: Great.. You did it already.
If possible then try to collect the error list & solutions of CWM error. I have searched a lot but in the office I can't open such sites, due to ban at sites. :Crying:

kataria.vikesh said:
its seems great buddy. Great Info. But as I always say, make it readable. Means highlights heading & important informations.
Edit: Great.. You did it already.
If possible then try to collect the error list & solutions of CWM error. I have searched a lot but in the office I can't open such sites, due to ban at sites. :Crying:
Click to expand...
Click to collapse
Okay let me see brother.

Re: [WIP]ROM & IT's COMPONENTS + CWM solutions
To everyone
If you have any suggestions please tell me and I will try to add it. :thumbup:
Sent from my GT-I9103 using xda app-developers app

Re: [WIP]ROM & IT's COMPONENTS + CWM solutions
Nice one..
Sent from my GT-I9103 using xda app-developers app

Buddy, Status 7 Error became part of Status 6 in your above post ^^.
Change the Subject & remove WIP. Also, Add CWM ERROR SOLUTIONS instead of CWM Solutions.

Guys is this thread worthy of being a sticky ??? I fyes how to get it sticked???

kartiknnn said:
Guys is this thread worthy of being a sticky ??? I fyes how to get it sticked???
Click to expand...
Click to collapse
Contact MOD for sticky.

Re: ROM & IT's COMPONENTS + CWM ERROR SOLUTIONS
One of the best threads in sgr forum.. Quite informative for a person like me:thumbup::thumbup:
Sent from my Jellybeaned Galaxy Royale

For mmc
One more Suggestion:
Add two more Post just below to your OP post (ask MOD to add two Post via PM)
In 2nd Post(after OP 1st): add CWM problem & solution while removing the same from Post no 1
In 3rd Post(after 2nd post): Add the follow details:
List of mmc blocks with partitions. Means you can check/know that in which partition what is having.
For example: in mmcblk0p1 - /efs -> Means in Partition One, its has /efs folder.
/tmp ramdisk (null)
/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/data ext4 /dev/block/mmcblk0p6
/prebuilt ext4 /dev/block/mmcblk0p11
/misc emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/emmc vfat /dev/block/mmcblk0p4
/sdcard vfat /dev/block/mmcblk1p1
I don't know much about this but Devs can make me correct.

asked jonny as soon as he creates the two posts I will do the same
thanks vikesh
Edit: Done

Recovery Issue
I am trying to run a recovery in CWM V 6.0.3.1 and here is what I am seeing.
Checking MD5 sums...
Erasing boot before restore...
Restoring system...
Restoring data...
Error while restoring /data!
Anyone know how to remedy this?
My device is a Samsung Galaxy NOte 10.1 and the backup file is on my external sd card.

The Apostle said:
I am trying to run a recovery in CWM V 6.0.3.1 and here is what I am seeing.
Checking MD5 sums...
Erasing boot before restore...
Restoring system...
Restoring data...
Error while restoring /data!
Anyone know how to remedy this?
My device is a Samsung Galaxy NOte 10.1 and the backup file is on my external sd card.
Click to expand...
Click to collapse
Buddy are you sure that your backup was not of TWRP?
if yes then it will not restore.
Or do one thing try restoring by putting the backup in internal storage.
If doesn't work then try a different and properly functioning recovery.
:thumbup:
Best of luck!
Sent from my GT-I9103 using xda app-developers app

Tha TechnoCrat said:
Buddy are you sure that your backup was not of TWRP?
if yes then it will not restore.
Or do one thing try restoring by putting the backup in internal storage.
If doesn't work then try a different and properly functioning recovery.
:thumbup:
Best of luck!
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
Yes I am sure. I wasn't even aware that TWRP was an option for the Note 10.1. I ended up doing a full restore from the base ROM. Then I tried backin git up once I had my settings all dialed in. Here is what I see when I attempt to make a backup on my external sd.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•backinf up of systemn complete...
•backing up data...
•backing up of data complete...
•no /sdcard/ .android_secure found. skipping backup of applications on external storage
•.
•backing up cache...
•backing up of cache complete...
•no external sd-ext found. skipping backup of sd-ext.
•generating MD5 sum...
When I try and backup on the internal sd here is what I get.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•error while making backup image of /system
Any thoughts or suggestions?

The Apostle said:
Yes I am sure. I wasn't even aware that TWRP was an option for the Note 10.1. I ended up doing a full restore from the base ROM. Then I tried backin git up once I had my settings all dialed in. Here is what I see when I attempt to make a backup on my external sd.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•backinf up of systemn complete...
•backing up data...
•backing up of data complete...
•no /sdcard/ .android_secure found. skipping backup of applications on external storage
•.
•backing up cache...
•backing up of cache complete...
•no external sd-ext found. skipping backup of sd-ext.
•generating MD5 sum...
When I try and backup on the internal sd here is what I get.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•error while making backup image of /system
Any thoughts or suggestions?
Click to expand...
Click to collapse
Buddy I am sorry to say that I don't have Note 10.1 . So if you could check out the Note 10.1 forum to see if someone else is having the same thing
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"

The Apostle said:
Any thoughts or suggestions?
Click to expand...
Click to collapse
I feel you should try this.See if you can take backup on internal sdcard or not.

The Apostle said:
Yes I am sure. I wasn't even aware that TWRP was an option for the Note 10.1. I ended up doing a full restore from the base ROM. Then I tried backin git up once I had my settings all dialed in. Here is what I see when I attempt to make a backup on my external sd.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•backinf up of systemn complete...
•backing up data...
•backing up of data complete...
•no /sdcard/ .android_secure found. skipping backup of applications on external storage
•.
•backing up cache...
•backing up of cache complete...
•no external sd-ext found. skipping backup of sd-ext.
•generating MD5 sum...
When I try and backup on the internal sd here is what I get.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•error while making backup image of /system
Any thoughts or suggestions?
Click to expand...
Click to collapse
Have u checked ur memory space?
Thanks,
Disturbed™
? Sent from my Disturbed™ Galaxy S4 using XDA Premium 4 ?
||||||||||||||||||||||||||||||||||||||||||||||●●●●●●●●●●●||||||||||||||||||||||||||||||||||
Wait for my time, U gonna pay for what U have done. - Disturbed™

Disturbed™ said:
Have u checked ur memory space?
Thanks,
Disturbed™
? Sent from my Disturbed™ Galaxy S4 using XDA Premium 4 ?
||||||||||||||||||||||||||||||||||||||||||||||●●●●●●●●●●●||||||||||||||||||||||||||||||||||
Wait for my time, U gonna pay for what U have done. - Disturbed™
Click to expand...
Click to collapse
+1
Sent from my GT-I9103 using xda app-developers app

[root tool] Toshiba Thrive 10.1" ICS

(Now, I know this is not in the right section or even in the device's page, but...)
Forewarning: I am NOT responsible for any damages caused by running this tool. (You ran it, not me.) Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Pio_masaki and I have been working hard for almost a year to get root on the ICS version of the Toshiba Thrive 10.
Last night, I was able to finally sneak past sealime.ko and have it work.
It uses the "root any ICS device" tool, with special modifications specifically for the Thrive 10.
(can't post any links, so it's on the "thrive-hackers" github page.)
Special note: While it is set up for OSX ADB, I have not been able to find any binaries.

Are you saying that we are close to a root method for Thrives running Toshiba ICS?

rohads said:
Are you saying that we are close to a root method for Thrives running Toshiba ICS?
Click to expand...
Click to collapse
Saying there is a method to root it now, yes, we got around sealime.ko. This means we can flash the HC bootloader which is unlocked, which allows custom recovery and kernels/ramdisks (boot.img) to be used.
BTW the link is https://github.com/Thrive-Hackers

congrats guys ! very awesome work !
jdsingles deodexed ROM w/ agat63's 1.3 kernel Suped up w/ CB 6.26.13

More specifically, it bypasses sealime to flash the unlocked bootloader. What we did was we MVd /dev/block/mmcblk0p6 to 0p9. It's a pure fluke Pio and I found out that it works. We found out that sealime was explicitly blocking write to 0p6, so he semi-sarcastically said to move it. I ran the mv command, whadda ya know? It worked!
'Course, getting the tool completed wasn't as simple as that...
PS: Could we get this moved to the Toshiba Thrive Development section?

Have instructions been written for the process?

worked for me
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!

navyguy said:
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!
Click to expand...
Click to collapse
Try fastboot flash:raw.

Is there any need to do a backup before rooting?

TubaMeister said:
Is there any need to do a backup before rooting?
Click to expand...
Click to collapse
Not explicitly, but it wouln't hurt in case your tablet got into contact with allspark.... er, the bootloader didn't flash, and you're stuck in a bootloop.

easy root and CWM recovery
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/

Uh oh
robyn402 said:
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/
Click to expand...
Click to collapse
I installed the drivers, used the root tool, the restore was successful, but now the tablet is stuck in a boot-loop mode.
The root tool was running, there was a line that said the screen would go blank, which it did, and it stayed there for several hours. When I came back to check on it, the tablet was off, so I turned it on. That's when I found the boot loop. It'll get to the home page, tell me that nova launcher has stopped, then loop back to the moving stars section of the boot screen.
Any ideas on what to do now?

DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)

Kyonex said:
DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)
Click to expand...
Click to collapse
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?

1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)

DLeach4512 said:
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?
Click to expand...
Click to collapse
also make sure you open the zip and place the update.zip on your card -
From my GSIII - jd's Stock/Rooted/Deodexed 4.3

Kyonex said:
1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)
Click to expand...
Click to collapse
Excellent!
1) I had to extract "update.zip" from the ROM I had downloaded.
2) I re-formatted the card I was using to FAT32 instead of FAT.
3) I was able to get the install started with no trouble after following your directions.
BIG THANK YOU FOR THAT!
I got a successful install message, and then it booted!
Thanks a million!

Problems after Mount Changes
I changed the mount as described on thriveforums.org to allow apks and data to go to the external sd rather than "shared" internal memory.
I now have the situation with less free memory available on the sd card than on internal. The CWM backups went on the physical card- a 32 G one almost full. Will look for a major mfr 64 Gig.
One or so issues with the revised mounts where the external sd card is now internal. They relate to making backups with dalepl's latest CWM 6.0.1: where to put CWM backups for now and are they being made correctly with the revised mounts?
The backup made prior to the mount change looks normal: a single, dated/numbered folder about 2.6 Gb, 6 files: boot.img, cache.ext4.tar, data.ext4.tar, nandroid.md5, recovery.img and system.ext4.tar. However, the one made after the mount change also has a dated, numbered folder of only 15.8 Mb and 7 files: .android_secure.vfat.dup, boot.img, cache.ext4.dup, data.ext4.dup, nandroid.md5, recovery.img and system.ext4.dup. There is a second folder associated with the later bu called "blobs", which is huge --2.76 Gb, 3292 folders and 6581 files. Is this an expected result and any one think it might be a valid bu?
Also, it went on to the external SD (now "internal") and total storage use is now almost 28 Gb out of 30.2. I now have the situation with less free memory available on the sd card than on internal. The stuff there looks ok, pix movies and music plus CWM bups of 5.5 G and App_Backup_Restore archived apks at 2.8 Gb. So, I copied the cwm backups folder to the real internal memory, now sdcard2. I assume this true internal memory might get wiped during a restore so, this is not a valid storage site for this? And, if I put copies on a spare card, will that really work if my downloaded apps are on the original card, eg does the CWM backup copy the external card apps?
As I note, for some reason this 'blobs' folder won't copy easily to a USB via the Thrive or Win 7 pc. It also won't copy to a Win 7 HD partition where I store my Thrive stuff. (Update: I was able to do a wireless transfer to my pc and then, from there, to a spare SD card.)
Any thoughts? Should I go back and change the mounts to default?
BTW, I find FolderMount has no real use with the changed mount on the Thrive unless someone tells me otherwise. With the Thrive mounting the external card as internal, files go to the physical card.

gberpa,
I don't understand your question - it is very long. But I know that custom recovery (CWM / TWRP) itself remounts sdcard and internal memory before wipe process so it will wipe correct memory (only internal memory). If you need to change the ROM you don't need to worry about mounting paths because after wipe mounting paths will be restored to original.

Partition layout of Toshiba Thrive 10.1" ICS
AmEv said:
Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Click to expand...
Click to collapse
Can you give us information on the Toshiba Thrive 10.1" ICS partition layout and their names, please?
We would like to compare it to ours Toshiba Excite Pro (AT10LE-A, tostab12BA). A Dirty Cow enabled KingoRoot has given us a temporary root.
[Q] How Root Toshiba Excite Pro AT10LE-A-108 by dexxxZ
https://forum.xda-developers.com/showthread.php?t=2583677&page=6
Sent from my takee 1 using XDA Labs