Related
I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
jdubdieslo said:
I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
Click to expand...
Click to collapse
wipe sd: ext partition- deletes your apps on your ext partiton
wipe sd: davlik-cache wipes your cache on your sd
part sd: fat32+ext2+swap makes the three partitions you need to run hero roms
parted sd: fat32 only- just partitions your memory card for a fat32 for stock roms like cyanogen
convert ext2 to ext3- does exactly what it says. makes ext2 to ext3
repair ext filesystem- do this after you choose to convert ext2 to ext3
fix apk uid mismatches- does exactly what it says
fix rotate- fixes auto rotate issues some roms have
usb mass storage on- allows you to access your fat32 part of your sd from the recovery
usb mass storage off- turns off the mounting of your sd from the recovery
to flash it using the recovery flasher app, just look at the unlockr's video and substitute the recovery image name for the one that is in the video. Voila.
Hope this helps
Applause...
Getting a straight answer sometimes is the most difficult part of installing a rom.
thelastgoodbrother said:
Applause...
Getting a straight answer sometimes is the most difficult part of installing a rom.
Click to expand...
Click to collapse
lol thats very true but come on if you can't do the research to figure out the basic youll be posting another thread the next day but this time it'll be called "stuck on the g1 screen" lol sometimes not giving a straight answer may save their phone... but thats just my opinion
So use part sd: fat32+ext2+swap when useing hero rom... what if i use hero rom & go back to cyanogen can i leave it that way or do i need to parted sd: fat32 only? also if i did part sd: fat32+ext2+swap And then did part sdnly fat32 would it override the part sd: fat32+ext2+swap. another question i dont even know what ext 2 is so moving it to ext 3 would be? sorry guys im new at this.. just wanted to clarify this. is fat32 letting me store apps to sd? because i removed the sd card while phone was on & notices it froze; i put it back in removed & rrplaced battery and it was fine again.. also i noticed i part sd: fat32+ext2+swap again before i read your replies to see what it would do and everything on my sd card was goin..
also what is swap i saw an app that saved a swap file on sd..
thanks everyone for you help. loving the android community. as soon as i get some extra cash i will be donating to people that helped me make my android stand out from any one's android on my end of the computer. thanks
jdubdieslo said:
So use part sd: fat32+ext2+swap when useing hero rom... what if i use hero rom & go back to cyanogen can i leave it that way or do i need to parted sd: fat32 only? also if i did part sd: fat32+ext2+swap And then did part sdnly fat32 would it override the part sd: fat32+ext2+swap. another question i dont even know what ext 2 is so moving it to ext 3 would be? sorry guys im new at this.. just wanted to clarify this. is fat32 letting me store apps to sd? because i removed the sd card while phone was on & notices it froze; i put it back in removed & rrplaced battery and it was fine again.. also i noticed i part sd: fat32+ext2+swap again before i read your replies to see what it would do and everything on my sd card was goin..
also what is swap i saw an app that saved a swap file on sd..
thanks everyone for you help. loving the android community. as soon as i get some extra cash i will be donating to people that helped me make my android stand out from any one's android on my end of the computer. thanks
Click to expand...
Click to collapse
If you are running a hero rom and want to go to cyanogen, you can leave the fat32+ext2+swap. Just make sure that you wipe your sd partition and davlik cache using the options in the recovery image. Do this every time you are flashing any new rom for that matter, whether it's a different hero rom or a stock rom.
Ext is the partition of your memory card that stores all your apps. This was necessary for the g1 because it only had like 80 mb of memory for apps. The mytouch has nearly 300 so apps2sd is not really necessary, but most custom ROMs include this anyway. Ext3 is what most of these ROMs operate on. Ext2 is an old outdated version that no one really uses anymore and ext4 is even newer than ext3 but is not really necessary.
Fat32 only does not let you store your apps on your sd. It does not have the ext partition to let that happen. I don't know why your phone froze when you took your sd card out. It shouldn't have. When you part your memory card, whether its just fat32 or the combo fat, ext, and swap your memory card gets wiped and formatted to whatever you have, so of course you will lose all your contents on the memory card. It wipes and reformats all 3 partitons, or just the one if you are doing only the fat32.
As for swap, this is necessary for hero. Hero phones have 288 mb of ram and the mytouch only has 192mb so if you don't have this, the phone lags so bad and hangs up and you get constant load screens. The app you saw is known as swapper. Yes it does put a swap file on your sd card, but if you go into advanced settings, it lets you use your swap partition of your memory card, which is what you should always choose.
Keep them questions rolling, I like being able to contribute whenever I can.
tazz9690 said:
If you are running a hero rom and want to go to cyanogen, you can leave the fat32+ext2+swap. Just make sure that you wipe your sd partition and davlik cache using the options in the recovery image. Do this every time you are flashing any new rom for that matter, whether it's a different hero rom or a stock rom.
Ext is the partition of your memory card that stores all your apps. This was necessary for the g1 because it only had like 80 mb of memory for apps. The mytouch has nearly 300 so apps2sd is not really necessary, but most custom ROMs include this anyway. Ext3 is what most of these ROMs operate on. Ext2 is an old outdated version that no one really uses anymore and ext4 is even newer than ext3 but is not really necessary.
Fat32 only does not let you store your apps on your sd. It does not have the ext partition to let that happen. I don't know why your phone froze when you took your sd card out. It shouldn't have. When you part your memory card, whether its just fat32 or the combo fat, ext, and swap your memory card gets wiped and formatted to whatever you have, so of course you will lose all your contents on the memory card. It wipes and reformats all 3 partitons, or just the one if you are doing only the fat32.
As for swap, this is necessary for hero. Hero phones have 288 mb of ram and the mytouch only has 192mb so if you don't have this, the phone lags so bad and hangs up and you get constant load screens. The app you saw is known as swapper. Yes it does put a swap file on your sd card, but if you go into advanced settings, it lets you use your swap partition of your memory card, which is what you should always choose.
Keep them questions rolling, I like being able to contribute whenever I can.
Click to expand...
Click to collapse
ao since ext 2 is outdate we want to convert ext 2 to ext 3 then repair ext filesystemafter words.. so if you convert ext 2 to ext 3 is there only a ext 3 now or both ext 2 and it adds a ext 3? also what does dalvik mean? also i thought apps to sd was a big deal because if you switch roms all your apps are still there, but if you wipe ext partition then you lose the apps so the real reason is just for phone with low ram and cant store many apps at once.. intresting..and wats up with not wipe data/factory reset after installing roms? whats the reason behind that, i notice my IME keyboard is no longer there when i do that.. im trying to think of more questions lol. thanks a million.
jdubdieslo said:
ao since ext 2 is outdate we want to convert ext 2 to ext 3 then repair ext filesystemafter words.. so if you convert ext 2 to ext 3 is there only a ext 3 now or both ext 2 and it adds a ext 3? also what does dalvik mean? also i thought apps to sd was a big deal because if you switch roms all your apps are still there, but if you wipe ext partition then you lose the apps so the real reason is just for phone with low ram and cant store many apps at once.. intresting..and wats up with not wipe data/factory reset after installing roms? whats the reason behind that, i notice my IME keyboard is no longer there when i do that.. im trying to think of more questions lol. thanks a million.
Click to expand...
Click to collapse
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
yeah it is safest way to wipe and reformat the sd card before flashing a new rom.
tazz9690 said:
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
Click to expand...
Click to collapse
Previously I got a 2GB micro-sd card. so no problem for me to move my music, photos, videos and backup apps to my pc.
But i just bought a 8GB card 2 weeks ago and man, backup all before flashing a rom is pain in the a** . but can't help flashing this and that ROMs hee hee
so no choice. yesterday I flashed Eugene's supermagic rom. awesome!
cheers
tazz9690 said:
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
Click to expand...
Click to collapse
so when going to another rom should you part the sd before or after the rom is loaded? and honestly im running out of questions.. i got one that is throwing me off.. i have my phone in fastboot and in device manager it show andriod bootloader (cant remember the exact device); i type in the cmd
cd desktop
cd fastboot
then the code for the custom splash and i get
< waiting for device > and it just sits there. nothing will happen. & my splash is still stock.. the file is at the rights bytes and i have the folder on my cd on the desktop and the driver i beleive is installed correctly on the cp. what am i doing wrong?
I think the Title should be Changed, Something Like Recovery-101. Know Your Phone.
Alot of great Info for New comers
jdubdieslo said:
so when going to another rom should you part the sd before or after the rom is loaded? and honestly im running out of questions.. i got one that is throwing me off.. i have my phone in fastboot and in device manager it show andriod bootloader (cant remember the exact device); i type in the cmd
cd desktop
cd fastboot
then the code for the custom splash and i get
< waiting for device > and it just sits there. nothing will happen. & my splash is still stock.. the file is at the rights bytes and i have the folder on my cd on the desktop and the driver i beleive is installed correctly on the cp. what am i doing wrong?
Click to expand...
Click to collapse
Part the sd before you load the rom onto the phone. if it has apps2sd and you try to part your memory card after, you will get stuck at the splash more than likely because you are missing key components that are stored onto the sd, like all your apps for example that come with the ROM.
In fastboot, when it's plugged in, on the phone does it say "Fastboot USB"?
You might want to try to reupload the drivers for the fastboot. That may be why it's hanging. I never use fastboot through the desktop. I always use fastboot through the SDK folder on my C:\ drive. It always worked for me that way. For some reason I could never get it to work with the "cd destop" but thats just me.
tazz9690 said:
Part the sd before you load the rom onto the phone. if it has apps2sd and you try to part your memory card after, you will get stuck at the splash more than likely because you are missing key components that are stored onto the sd, like all your apps for example that come with the ROM.
In fastboot, when it's plugged in, on the phone does it say "Fastboot USB"?
You might want to try to reupload the drivers for the fastboot. That may be why it's hanging. I never use fastboot through the desktop. I always use fastboot through the SDK folder on my C:\ drive. It always worked for me that way. For some reason I could never get it to work with the "cd destop" but thats just me.
Click to expand...
Click to collapse
i figured taht was the right order part sd then load rom because i did it and it worked lol, and since it worked i never tried it rom the part sd. so do cyanogen roms have app2sd? and does the cyanogen rom have a overclocker built in now because i tried to use my overclock widget and it doesnt work and the phone seems as if its running faster even with out my widget..
and yes it says fastboot usb & ive tried uninstalling & reinstall the drivers mutliple times and still get < waiting for device > so if i do it on the c:/ drive were do i place the fastboot folder? /c:/fastboot? and what would the code be?
cd c:/
cd Fastboot
thent he other code that i have saved at home the flash_splash one? i cant remember it.
one really dumb question. i rooted my pops mytouch lol because he was complaining about the mytouch stock because of numerous things. so i rooted it to 4.2.2 and out of all things he is now complaining about the stock ringtones.. lol. anyone know where to get the stock ringtones? if not its cool i told him id make sum ringers with ringdroid for him like the temptations and willie nelson lol.. thanks all for your support.
jdubdieslo said:
i figured taht was the right order part sd then load rom because i did it and it worked lol, and since it worked i never tried it rom the part sd. so do cyanogen roms have app2sd? and does the cyanogen rom have a overclocker built in now because i tried to use my overclock widget and it doesnt work and the phone seems as if its running faster even with out my widget..
and yes it says fastboot usb & ive tried uninstalling & reinstall the drivers mutliple times and still get < waiting for device > so if i do it on the c:/ drive were do i place the fastboot folder? /c:/fastboot? and what would the code be?
cd c:/
cd Fastboot
thent he other code that i have saved at home the flash_splash one? i cant remember it.
one really dumb question. i rooted my pops mytouch lol because he was complaining about the mytouch stock because of numerous things. so i rooted it to 4.2.2 and out of all things he is now complaining about the stock ringtones.. lol. anyone know where to get the stock ringtones? if not its cool i told him id make sum ringers with ringdroid for him like the temptations and willie nelson lol.. thanks all for your support.
Click to expand...
Click to collapse
Cyanogen's rom has dynamic apps2sd. If it senses that you have a partition, it will do apps2sd. If you don't have an ext, it will save it to the phone, so it will work that way too.
For the fastboot, do you even have your computer set up for the use of ADB and fastboot? Like having the latest SDK downloaded and set up for your computer? That might be why it says, waiting for devices. When you do cd fastboot, afterward type fastboot devices and see if in the cmd it says "HTC Bootloader" or "Android Bootloader" I am not sure which one it is.
As for the ringtones, here is the link for the download in Cyanogen's 4.2.2 threat http://n0rp.chemlab.org/android/audio-resources.zip That downloads a zip of all the stock ringtones. Just upzip the file and place it on the root of your sd card.
tazz9690 said:
Cyanogen's rom has dynamic apps2sd. If it senses that you have a partition, it will do apps2sd. If you don't have an ext, it will save it to the phone, so it will work that way too.
For the fastboot, do you even have your computer set up for the use of ADB and fastboot? Like having the latest SDK downloaded and set up for your computer? That might be why it says, waiting for devices. When you do cd fastboot, afterward type fastboot devices and see if in the cmd it says "HTC Bootloader" or "Android Bootloader" I am not sure which one it is.
As for the ringtones, here is the link for the download in Cyanogen's 4.2.2 threat http://n0rp.chemlab.org/android/audio-resources.zip That downloads a zip of all the stock ringtones. Just upzip the file and place it on the root of your sd card.
Click to expand...
Click to collapse
thats good to know. so if you ext 2 will cm use ext 2 & if you converted it will it use ext 3? also how can i tell what i have ext 2 or ext 3 other than knowing if i click convert to ext 3? i downloaded the SDK and used the usb folder when the computer was looking for drivers & it says it installed drivers successfully; so now when im in fastboot usb on my phone the computer in device manager shows bootloader (cant remember exactly what it says untill i get home); & when my phone is in recovery the driver shows ADB (cant remember the exact name till i get home also); and then i do the codes because my fastboot & sdk folders are on my desktop; when i downloaded the sdk folder i dont think i did anything with it as far as isntalling it, what does the sdk folder do? lol. sorry..
thanks for the ringtones my pops says mucho gracias.
jdubdieslo said:
thats good to know. so if you ext 2 will cm use ext 2 & if you converted it will it use ext 3? also how can i tell what i have ext 2 or ext 3 other than knowing if i click convert to ext 3? i downloaded the SDK and used the usb folder when the computer was looking for drivers & it says it installed drivers successfully; so now when im in fastboot usb on my phone the computer in device manager shows bootloader (cant remember exactly what it says untill i get home); & when my phone is in recovery the driver shows ADB (cant remember the exact name till i get home also); and then i do the codes because my fastboot & sdk folders are on my desktop; when i downloaded the sdk folder i dont think i did anything with it as far as isntalling it, what does the sdk folder do? lol. sorry..
thanks for the ringtones my pops says mucho gracias.
Click to expand...
Click to collapse
I don't think any builds use ext2 anymore. They all either use ext3 or ext4. You have to make an ext2 first though, before you can convert it to ext3. Same goes for ext4, you have to have ext3 before you can upconvert to it. Just use ext3 just to be safe. If you go into "Parted" through the recovery image by typing in "parted /dev/block/mmcblk0" in adb shell, then typing 'print' it will show how big your fat32 is, it'll say which ext you have as well as your size, and the same for linux swap.
For a SDK, the folder stores the drivers needed for fastboot and adb in it. You should save it to the root of your C:\ drive because it makes things easier. I recommend you set up SDK using this thread guide: http://forum.xda-developers.com/showthread.php?t=532719
Setting up the Android 1.5r2 SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows-1.5_r2" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows-1.5_r2\tools
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
Those are basically what you need to look at.
jdubdieslo said:
I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
Click to expand...
Click to collapse
Don't mean to hijack your thread OP, but I do have a question that I hope someone can answer. When partitioning the SD card, you choose the option I put in Bold. After that, could you use this link:
http://forum.xda-developers.com/showthread.php?t=535914
To adjust the different sizes of the 3 partitions? I know that in order to run any Hero ROMS, your SD card has to be partitioned with at least 3 (fat32+ext2+swap) parts. This is the only part that still confuses me when it comes to adequately rooting.
If you are using ubuntu, you create the partitions you want, as well as the size. If you use the recovery image, you would just be adding an unnecessary step because it will just get deleted when you make your partitions again with Ubuntu.
tazz9690 said:
I don't think any builds use ext2 anymore. They all either use ext3 or ext4. You have to make an ext2 first though, before you can convert it to ext3. Same goes for ext4, you have to have ext3 before you can upconvert to it. Just use ext3 just to be safe. If you go into "Parted" through the recovery image by typing in "parted /dev/block/mmcblk0" in adb shell, then typing 'print' it will show how big your fat32 is, it'll say which ext you have as well as your size, and the same for linux swap.
For a SDK, the folder stores the drivers needed for fastboot and adb in it. You should save it to the root of your C:\ drive because it makes things easier. I recommend you set up SDK using this thread guide: http://forum.xda-developers.com/showthread.php?t=532719
Those are basically what you need to look at.
Click to expand...
Click to collapse
So if u have a ext 3 how do u get ext 4? Also wat is linux swap? And yea i didnt do all that im sure thats why i was getting < waiting for device >. I will let u know the outcome of the splash screen... thanx.
jdubdieslo said:
So if u have a ext 3 how do u get ext 4? Also wat is linux swap? And yea i didnt do all that im sure thats why i was getting < waiting for device >. I will let u know the outcome of the splash screen... thanx.
Click to expand...
Click to collapse
If you want ext3, you have to go into parted like I stated in a previous post and create your partitions that way. From there, to upgrade to ext3, you type "upgrade_fs". You now have ext3. If you want ext 4, after that you would type
"tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2"
That's just too much work for me. I am fine with ext3. If you want a more in depth explanation, go to this thread: http://forum.xda-developers.com/showthread.php?t=534714&highlight=wipe+partition
Linux swap, I believe I explained in one of my early posts. The mytouch only has 192 mb of ram. The Hero's have 288 and so do the 32A board Sapphire phones like the HTC Magic and the Rogers Magic. Since we were unfortunate to get that low of Ram, if you try to run a hero rom without the linux partition, the phone will lag, freeze, and get load screens constantly. Using a linux swap partition makes it possible to run the Hero ROM's at a decent speed, though it will not be as fast as if you had the actual HTC Hero phone or a 32A Sapphire.
Hi everybody,
i am sure, that everybody except me seems to know how to install this awesome recovery...
I already renamed the zipfile to PG88IMG.zip, have put it into the root of the sd card, rebooted, the bootloader says 'parsing PG88IMG.zip', then nothing happens...
So, could someone please enlihgten me how to flash this thing? (if possible without creating an expensive brick ;-)) thanks a lot
Who told you to do that?
EDIT:
This should be a one click zip.
http://forum.xda-developers.com/showthread.php?t=1130004
Hi,
wow, that was fast ;-) thanks a lot...
Hmm, no, i already installed ClockworkMod via the method i described above.
i also -successfully- installed the saga LBC mod - both are running fine.
Now i want to just replace the ClockworkMod, (not the LBC Mod - i know how to install a new ROM ;-)) with 4ExtRecovery.
basically the question is:
how can i flash 4ExtRecovery from within the bootloder.
the PG88IMG.zip Method seems to fail here...
you know, i basically followed the instructions found the lbd mod homepage
[lbc-mod-homepage]/custom-recovery/modded-clockworkmod-recovery/
install-instructions for on this page
(i cannot post links to outside the forums, sorry)
can somebody help me?
EDIT:
yes, i found the one-click-zip but dont want to use it; i don't want to flash via the adb tool, i don't know why, just personal preferences ;-)
glubber008 said:
Hi,
wow, that was fast ;-) thanks a lot...
Hmm, no, i already installed ClockworkMod via the method i described above.
i also -successfully- installed the saga LBC mod - both are running fine.
Now i want to just replace the ClockworkMod, (not the LBC Mod - i know how to install a new ROM ;-)) with 4ExtRecovery.
basically the question is:
how can i flash 4ExtRecovery from within the bootloder.
the PG88IMG.zip Method seems to fail here...
you know, i basically followed the instructions found the lbd mod homepage
[lbc-mod-homepage]/custom-recovery/modded-clockworkmod-recovery/
install-instructions for on this page
(i cannot post links to outside the forums, sorry)
can somebody help me?
EDIT:
yes, i found the one-click-zip but dont want to use it; i don't want to flash via the adb tool, i don't know why, just personal preferences ;-)
Click to expand...
Click to collapse
................... You'll need to extract the images from the zip images and I suspect, with respect that you don't know what your doing.
So leave that method well alone!
yes, of course - i don't know how to flash this recovery ;-)
i already know that
that's the reason, why i'm asking here, you know... ;-)
try doing this
1.put the zip on your sd card
2.reboot into recovery
3.go to install from sd card
4.choose the zip from sd card
5.select the zip file & choose yes
the phone should flash the recovery & restart again into recovery
choose reboot
ah, thanks a lot ;-)
btw, exploring the zip, i found the following in the updater-script:
assert(getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga" || getprop("ro.product.board") == "saga");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
So, you are right, it flashes the recovery.img correctly to the recovery partition, then reboots again into recovery, all understood now, thanks again...
btw:
i might be new to android, but not to computers - i am actually a programmer ;-)
that's why i'm usually asking before doing something i don't understand completely...
anyways,
it worked, thanks again for pointing me into the right direction
Ah,
i found out, that the PG88IMG.zip method only works, if there's an android-info.txt file in the archive, so it seems, that the parser of the hboot checks the contents of this file and if this thing is valid, it continues to the builtin flash routine.
That's the reason, why this method fails with the 4Extrecovery zip file.
on the other hand, if you want to flash from the recovery system, there must be a folder called META-INF with 'some' defined structure in it, a file called updater-script (i dont know, what this update-binary file is - it is a binary ELF executable, maybe the interpreter? maybe the compiled form of the updater-script? - will run 'strings' on it...); anyways, this file is then executed and contains basically the information how to install / flash this thing.
So, thanks for helping me doing the first steps on this awesome platform ;-)
EDIT:
it seems, the update-binary file is the interpreter for the updater-script:
the relevant strings are:
wrong updater binary API; expected 1, 2, or 3; got %s
failed to open package %s: %s
META-INF/com/google/android/updater-script
Ok, enough for today... ;-)
EDIT2:
...and update-binary is part of the recovery, as found here for example:
https://github.com/arco/android_bootable_recovery/blob/gingerbread/updater/install.c
nice, nice...
EDIT3:
...currently building my own recovery, this thing is plain c, so not a big problem for me, we'll see...
EDIT4:
..flashed this thing, it's working, so i guess i can now start hacking on it ;-)
is it possible to install 4EXTRecovery to desire s with s-on? and how?
realies said:
is it possible to install 4EXTRecovery to desire s with s-on? and how?
Click to expand...
Click to collapse
no, it is not possible
you need s-off to install recovery
does CWM have to be removed to install this?
greenster4470 said:
does CWM have to be removed to install this?
Click to expand...
Click to collapse
No. Use CWM to flash it like any other mod! It'll automatically re-start recovery, and you'll in be in your shiny new 4EXT recovery.
As log as we are on this topic, I have a few doubts too:
1) Can I use my CWM nandroid backups with 4EXT without any conversion?
2) Will the paid 4EXT app from the android market automate the changeover process?
3) As our phones have a decent internal memory, it is advisable to convert the partitions to ext3/4 including the SD card or not and if done will a ROM/backup have to be reflashed?
4) Other benefits over CWM?
Could someone please enlighten me. Thanks
harshs23 said:
As log as we are on this topic, I have a few doubts too:
1) Can I use my CWM nandroid backups with 4EXT without any conversion?
2) Will the paid 4EXT app from the android market automate the changeover process?
3) As our phones have a decent internal memory, it is advisable to convert the partitions to ext3/4 including the SD card or not and if done will a ROM/backup have to be reflashed?
4) Other benefits over CWM?
Could someone please enlighten me. Thanks
Click to expand...
Click to collapse
Answers:
1) Yes you can.
4EXT will restore CWM backups to the file system they were taken in (most probably ext3 {default of CWM}). But you can even restore old ext3 backups as ext4 without any data loss or corruption with 4EXT Recovery. You'll need to tweak a few things, but i can help you if you want.
2) Yes it will, and so will the free app, 4EXT Recovery Updater..
I suggest you try out the free app first, which includes the features of the paid app for the first 3 days, and then still remains functional enough to let you update your recovery whenever you want. Then you can go ahead and purchase the paid app from the market.
3) No, do not try to change SD Card file system. Just convert the system, data and cache partitions to ext4. No need to touch the SD card, as it works only in the Fat32 format.
4) There are numerous benefits.
Prominent ones include MD5 cheksum verification, Theming support, option to remain in recovery after flashing zips or taking backups, better interface and menus, auto ROM name detection and labeling of Backups unlike CWM and great developer support from Madmaxx.
I suggest you read THIS.
Hope this helps you.
Thank you, make a lot more sense to me now.
enigmaamit said:
Answers:
1) Yes you can.
4EXT will restore CWM backups to the file system they were taken in (most probably ext3 {default of CWM}). But you can even restore old ext3 backups as ext4 without any data loss or corruption with 4EXT Recovery. You'll need to tweak a few things, but i can help you if you want.
2) Yes it will, and so will the free app, 4EXT Recovery Updater..
I suggest you try out the free app first, which includes the features of the paid app for the first 3 days, and then still remains functional enough to let you update your recovery whenever you want. Then you can go ahead and purchase the paid app from the market.
3) No, do not try to change SD Card file system. Just convert the system, data and cache partitions to ext4. No need to touch the SD card, as it works only in the Fat32 format.
4) There are numerous benefits.
Prominent ones include MD5 cheksum verification, Theming support, option to remain in recovery after flashing zips or taking backups, better interface and menus, auto ROM name detection and labeling of Backups unlike CWM and great developer support from Madmaxx.
I suggest you read THIS.
Hope this helps you.
Click to expand...
Click to collapse
Everyone in doubt about 4EXT, go through enigmaamit's post, you will be sorted. Have flashed the new recovery and am totally satisfied. No clobbering needed... LOL
4EXT Recovery Control
https://market.android.com/details?id=ext.recovery.control
Although the free version is available, I highly recommend an investment in the application that supports this incredible recovery. The added features in the market version outweigh the free version drastically.
harshs23 said:
Everyone in doubt about 4EXT, go through enigmaamit's post, you will be sorted. Have flashed the new recovery and am totally satisfied. No clobbering needed... LOL
Click to expand...
Click to collapse
@ Harsh, regarding my earlier commitment on helping you with the partition conversion and advanced restore:
Before you do any of this,
1. Take a nandroid backup. The whole procedure below is utterly harmless but you should develop a habit of doing this whenever you play around with anything.
2. Make sure you have at least 50% charge, and preferably have it plugged into your laptop. The reasons are pretty obvious.. first, you dont want to run out of charge while doing something as grass-root level as this, and secondly, having hooked it up to a laptop, adb access is available to start with. (i'm assuming you have adb set up on your pc)
3. Make sure you have adequate free space on your sd card. I would recommend around 1.5 to 2 GB. This is because when changing a file system the recovery first backs up your data from the partition onto the sd card, formats the partition into the new file system and then moves the data back into the partition after that into the new file system (ext4, in our case). So you need to give enough room for the recovery to be able to temporarily cache the contents of the partitions on the sd card. Hope this is clear to you.
EDIT: Don't worry about insufficient space on your sd card...since the 2.2.7 version, 4ext calculates the actual required free space needed for a conversion of a selected partition before it even starts doing that. If space needed is too low it won't do the conversion.
Let us begin:
1.) To convert existing file system:
To convert your existing file system, go into recovery and see what the partitions are right now. You'll see four partitions: 1. system, 2. data, 3. cache, 4. sd card
Next to these you'll see the file system they're on. I'm guessing it will look something like ext4, ext3, ext3, fat32 respectively, if you're coming from ClockWorkMod recovery. What you need to do to convert the ext3 partitions to ext4 is go to the EXT3 - 4EXT - EXT4 option in the menu and once inside, choose the first option (convert l change a backup -> ext4).
In that sub-menu, choose the partition you want to convert. (2nd, 3rd and 4th options SYSTEM, DATA & CACHE respectively). The execute menu will prompt you regarding going ahead. Select Yes - do it!
Now the process that i had described earlier will begin and at the end you'll have all your original data on the ext4 file system on whichever partition you selected.
Do the same for each partition that is in ext3 format.
2.) To change file system for old backups:
Again, if you want to change one of your old backups that you took while on CWM Recovery (which were most probably taken in ext3 default format), you need to convert them to ext4, otherwise 4EXT Recovery will restore them to their default file system (another neat feature of this recovery) as a safeguard against restore onto contrasting file systems.
To do this, go to EXT3 - 4EXT - EXT4 menu > then convert l change a backup -> EXT4 > THEN change one of your backups > now select the backup you want to change to ext4 > at the prompt menu, select Yes, do it!
Once you've done this, you'll get a hang of what all the other sub menus are for... You'll figure them out on your own in no time.
Whew! That was long and tedious... But i've tried to be as elaborate as i can for all those users new to 4EXT and apprehensive about migrating. I've also posted this in the Development section in the relevant thread.
I remember how i was before i converted for the first time and there was no detailed guide available.
Hope this has helped!!
P.S. Thanks to Madmaxx for the tips and inputs that helped me write this mini tutorial.
enigmaamit said:
@ Harsh, regarding my earlier commitment on helping you with the partition conversion and advanced restore:
Before you do any of this,
1. Take a nandroid backup. The whole procedure below is utterly harmless but you should develop a habit of doing this whenever you play around with anything.
2. Make sure you have at least 50% charge, and preferably have it plugged into your laptop. The reasons are pretty obvious.. first, you dont want to run out of charge while doing something as grass-root level as this, and secondly, having hooked it up to a laptop, adb access is available to start with. (i'm assuming you have adb set up on your pc)
3. Make sure you have adequate free space on your sd card. I would recommend around 1.5 to 2 GB. This is because when changing a file system the recovery first backs up your data from the partition onto the sd card, formats the partition into the new file system and then moves the data back into the partition after that into the new file system (ext4, in our case). So you need to give enough room for the recovery to be able to temporarily cache the contents of the partitions on the sd card. Hope this is clear to you.
EDIT: Don't worry about insufficient space on your sd card...since the 2.2.7 version, 4ext calculates the actual required free space needed for a conversion of a selected partition before it even starts doing that. If space needed is too low it won't do the conversion.
Let us begin:
1.) To convert existing file system:
To convert your existing file system, go into recovery and see what the partitions are right now. You'll see four partitions: 1. system, 2. data, 3. cache, 4. sd card
Next to these you'll see the file system they're on. I'm guessing it will look something like ext4, ext3, ext3, fat32 respectively, if you're coming from ClockWorkMod recovery. What you need to do to convert the ext3 partitions to ext4 is go to the EXT3 - 4EXT - EXT4 option in the menu and once inside, choose the first option (convert l change a backup -> ext4).
In that sub-menu, choose the partition you want to convert. (2nd, 3rd and 4th options SYSTEM, DATA & CACHE respectively). The execute menu will prompt you regarding going ahead. Select Yes - do it!
Now the process that i had described earlier will begin and at the end you'll have all your original data on the ext4 file system on whichever partition you selected.
Do the same for each partition that is in ext3 format.
2.) To change file system for old backups:
Again, if you want to change one of your old backups that you took while on CWM Recovery (which were most probably taken in ext3 default format), you need to convert them to ext4, otherwise 4EXT Recovery will restore them to their default file system (another neat feature of this recovery) as a safeguard against restore onto contrasting file systems.
To do this, go to EXT3 - 4EXT - EXT4 menu > then convert l change a backup -> EXT4 > THEN change one of your backups > now select the backup you want to change to ext4 > at the prompt menu, select Yes, do it!
Once you've done this, you'll get a hang of what all the other sub menus are for... You'll figure them out on your own in no time.
Whew! That was long and tedious... But i've tried to be as elaborate as i can for all those users new to 4EXT and apprehensive about migrating. I've also posted this in the Development section in the relevant thread.
I remember how i was before i converted for the first time and there was no detailed guide available.
Hope this has helped!!
P.S. Thanks to Madmaxx for the tips and inputs that helped me write this mini tutorial.
Click to expand...
Click to collapse
Thank you very much for the detailed tutorial, I think the following 3 posts should be compiled and made a stickied tutorial for all the others here and to come.
http://forum.xda-developers.com/showpost.php?p=18562457&postcount=14
http://forum.xda-developers.com/showpost.php?p=18593426&postcount=18
http://forum.xda-developers.com/showpost.php?p=18565951&postcount=437
With your and madmaxx's help, I have changed over to 4EXT without a single hitch. Thanks once again.
harshs23 said:
Thank you very much for the detailed tutorial, I think the following 3 posts should be compiled and made a stickied tutorial for all the others here and to come.
http://forum.xda-developers.com/showpost.php?p=18562457&postcount=14
http://forum.xda-developers.com/showpost.php?p=18593426&postcount=18
http://forum.xda-developers.com/showpost.php?p=18565951&postcount=437
With your and madmaxx's help, I have changed over to 4EXT without a single hitch. Thanks once again.
Click to expand...
Click to collapse
You're more than welcome. This is what all of us are here for...
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.
UPDATE: This can't be used with CM10 Alpha 4 (or later) as it is due to the new partitioning system.
____
I made this thing time ago and I thought to share.
What it does is to boot a stock ROM from the external SD card. It's nothing special, I simply changed few things here and there. I did it because I needed a stock ROM for a couple of minutes and this was the faster way to get it.
I'm using CM and I made this with that in mind, so, don't use while using a stock ROM. It won't mess your current setup, but it won't work.
You need to change kernel to boot the stock ROM (reboot recovery > flash zip. Simple and fast). That's because, as you probably now, kernels made for stock ROMs are not compatible with CM.
Prepare you SD card
You need first to repartition your external SD like this:
Code:
1° partition (mmcblk1p1): FAT - it will be the usual external SD
2° partition (mmcblk1p2): ext4 - /system (make it around 300MB big, 254MB will be more or less the space used)
3° partition (mmcblk1p3): ext4 - /data
I can't help you with this, I did it with adb and parted (the command is available in CWM). Look for instructions on the web, it's full of guides out there. Your external SD card is /dev/block/mmcblk1 (mmcblk0 is the internal one).
If you'll use the zip linked to flash the ROM, the two partitions (mmcblk1p2 and mmcblk1p3) will be automatically converted, unless they are already two ext4/ext3/ext2 partitions.
It shouldn't matter which kernel you are currently using and it should be safe flashing it, the only important thing is to have three partitions. If mmcblk1p2 or mmcblk1p3 are not detected, the installation will be aborted (it means that your SD card is not partitioned). Nothing else will be touched.
If you don't want to use the zip, mount mmbclk1p2 and copy the ROM there.
/dbdata will be the usual one (it's not used in CM. This will also makes Samsung apps a lot faster when using a slow SD card), same for /cache.
The flashable ROM is a stock XXLE4 + su/Superuser.apk.
How to use the additional ROM
To use the ROM on your SD, flash kernel-stock-SD.zip (see below) from recovery.
To go back to the real ROM you have to flash its kernel. Here below you can find CM10 Alpha 2 kernel, flashable from recovery. If you have doubts, reflash the entire ROM, it won't wipe your data.
I only mentioned CM10 because it's what I'm using, but this thing should work with CM9 too.
Things to know
I built the kernel using the latest Samsung sources with inbuilt ext4 support (and ext3/ext2 compatibility). Nothing else was changes, so I think there's no need to publish the sources, they are available here.
I attached the tools I use to unpack/repack boot images (they are a modified version of skin1980's tools):
Code:
./unpack.pl boot.img
./repack.sh [gz|lzma|bzip2|xz]
To see the changes I made, compare "out/android" with the stock XXLE4 ramdisk and the other two directories with CM10 boot.img ramdisk.
I changed recovery.fstab accordingly, but I can't tell you if flashing stuff from CWM while using the additional ROM will work as expected. You should read the updater-script to know it for sure.
I can only tell you that dhiru's builds will be flashed into the real /system partition and not your SD card.
Backups should work too, but I didn't try.
Of course, performances depends on your SD card. Mine is not that good I think, I took it from an old phone and I really don't know anything about it. The ROM is still usable, but apps that intensely use databases are slow (not Samsung apps, those will use /dbdata). Maybe disabling journaling will help (search for more info).
The Galaxy SL screen will last more than usual because I intentionally added a delay (3 seconds, SD cards are detected after a while) and of course because of the slower load.
Please, use this if you have some experience.
Note: dual booting two ROMs with a single kernel is possible, but only if they use the same kernel image. See this and this.
Downloads
XXLE4-CWM.zip: CWM flashable ROM
kernel-stock-SD.zip: kernel to boot the ROM from the external SD, flashable from recovery
kernel-CM10-Alpha2.zip: CM10 Alpha 2 kernel, flashable from recovery
Wow ! thats dualboot for i9003 ! sweet gud to see development back in action
Good work.
The class of an SD card can be misleading. It is only a measure of the sequential Write access and that doesn't tell the whole story. Class 10 cards are great for cameras and applications that write or read sequential data, such as saving a picture and transferring a file. They are not so good for random access which is what the Android OS does when operating. In fact the random access speed for class 10 cards is lower than class 4 or 6 cards. From what I have seen, the sweet spot for smartphones is class 6.
Awesome. Only if we could achieve dual boot without flashing kernel everytime. But anyways awesome guide. Thanks.
Reminded me of dual booting of maemo and android on my brother's n900.
Whats the benefits of dual boot? I heard about it but i dont have an idea
juztinlee said:
Whats the benefits of dual boot? I heard about it but i dont have an idea
Click to expand...
Click to collapse
Dual Booting means you can have two OS's (here firmware) on the phone at the same time. You can choose on which you want to go. This, besides being awesomely cool, is really helpful in many scenarios.
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
santoshsadani009 said:
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
Click to expand...
Click to collapse
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
loSconosciuto said:
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
Click to expand...
Click to collapse
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
Ya a Universal kernel will do the trick.If later then we can achieve dual boot then the people who were holding back from CM9 or CM10 can flash that for features and a stock rom for stability and camera.
shriomman said:
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
Click to expand...
Click to collapse
As long as the kernel is the same, yes.
If you want, here you can find the unpacked boot.img I (probably) used to dual boot CM10 and CM9 (SD).
There's no zImage in there, use the one you prefer, CM10 and CM9 are using the same kernel.
EDIT:
I almost forgot. "out/ramdisk/2ndROM" is for the ROM stored in your SD card, so you have to adjust the mount points there (already done in the one linked). "out/ramdisk/android" should be the "stock" ramdisk.
recovery will work only for the primary ROM in this case, maybe with some scripting you can make it works for both the ROMs, but I won't do it (if it's something possible).
The tools I posted will automatically take care of the additional ramdisk.
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
nick0016 said:
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
Click to expand...
Click to collapse
I don't know what happened to the links, probably I deleted the files by mistake on dev-host. Sadly I no longer have them and I currently don't have the time to make them again.
Anyway, I suggest you to follow other guides in order to replace only the corrupted memory instead (we have two different memories). This one for example, but there are other guides probably.
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
nick0016 said:
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
Click to expand...
Click to collapse
The guide I linked is fine then.
It explains how to repartition your SD card and the script Dipu K attached to his post is to use the newly created partition inside your external SD for /data. It's not to swap internal and external SD.
As I said, we have two memories, /data is in one, /system, kernel and other things are in the other memory. The corrupted one must be the one which holds /data.
Try to do as explained in the guide, if the problem persists, I'll see what I can do to help.
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
nick0016 said:
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
Click to expand...
Click to collapse
The content of /data is generated, there's nothing like what you asking for.
Maybe the problem is that the script posted in the guide copies the content of the old /data partition to the new partition inside the SD card. Wiping data shouldn't work because the path to the SD card is not specified.
Try the script attached. I zipped it to be able to upload it here, but it's not flashable. Since you've been able to follow the guide I assume you know how to use adb.
Wipe the content of the data partition you created inside you SD card (/dev/block/mmcblk1p2). You could reformat it with make_ext4fs, use a computer and so on. What's important is that it's ext4 formatted.
While in recovery, run:
Code:
adb shell mount /system
adb shell mkdir -p /system/etc/init.d/
adb push [I]PATH_TO[/I]/remount_data /system/etc/init.d/
adb shell chmod 777 /system/etc/init.d/remount_data
I'm sorry, but I currently don't have much free time to help more than this. With no logs or access to the device it's really hard for me to know what's the problem.
As of 28/12/2013, I no longer have this phone. My threads will stay open for all who want to assist others. I've had a great time being a member of the O3D community, so thank you all!
For questions, requests or any other remarks, please don't send me PM, I will not answer. Instead, please post properly in the thread, so that anybody can read and benefit or even assist.
02/07/2013:New version 2.1 (fixed compatibility issues with Gingerbread present in v2.0). Switch_ROM in v2 is now a single script. All other scripts integrated into a "Recovery" equivalent. Fixed bug in wipes. Renamed "bin" folder to "img" (seemed more appropriate). Old v1.0 users must delete their existing DualBoot folder. Don't forget to backup your boot1.img and boot2.img from the old "bin" folder.
Our top developer, Berni987654321, developed a method to dual-boot our phones (follow the link to his page and press his "Thanks" button, he deserves it)! Thanks to him we can preserve our stock ROM with full 3D support and at the same time try out modern Jellybean ROMs like CM10, PACman, perhaps even KitKat some day!
However, dual booters were facing two problems:
1. Switching ROMs was cumbersome and time consuming since it required to reboot into recovery, flash a kernel and reboot again to the other ROM.
2. Recovery only backs up and restores the primary ROM. If someone wanted to try out different secondary ROMs, he would have to set them up from scratch every time.
3. Factory Reset and wipes don't work for secondary ROM in Recovery
This is where I've come in. I have written scripts that fill in these gaps.
Download and unzip the file attached and copy the DualBoot folder anywhere in your phone. It is necessary that all files are kept inside the folder and that the path (all directory names) to this folder contains no spaces.
Usage instructions are on the second post.
In order to keep SMS and Call Logs synchronized between the two ROMs, I use SMS Backup +. Naturally, it needs to be installed in both, primary and secondary ROMs.
You can't install just any kernel for your secondary ROM. You can only use one from Berni's page. Still, you can overclock using CM10 modules by Iodak.
Ilie321 and Defcomg have made a working FM radio app for ICS and JB. Attached at the end of this post there is a modified flashable zip that installs the radio straight into a secondary CM10 ROM. Use it after every Nightly upgrade.
For a long time I've wanted to integrate a "Fix Permissions" option into the Dual Boot Tools script but never found the time. Here you can find a wonderful script and run it with Script Manager after your secondary ROM has booted.
!! 3D support for CM10 !!
We may not be able to view in 3D, but we can shoot!
Defcomg has successfully ported ArcCamera to CM10 / 10.1 based ROMs, fixing at the same time orientation problems for all 3rd party cameras (e.g. Instagram). Attached you will find ARC+V30B_LIBS_CM10+_DualBoot.zip which is modified to flash directly to the secondary ROM. You need to flash it after every Nightly upgrade.
Hit Defcomg's "Thanks" button (Original thread)!
Stock ICS v30a Kernel:
If you have already updated your primary ROM to P920 ICS v28b or v30a, you will need the attached "Kernel-ICS-v30a.zip". Download and copy it to your phone. Follow instructions in 2nd post.
IMPORTANT: Official P920 ICS has locked bootloaders, so before you can boot into CM10 you also have to flash Wkpark's v1.25a bootloaders. OS_Hacking's Tool is an easy way to do that.
New CM10.1 Kernel
With the old CM10.1 Kernel, Bluetooth doesn't work. Attached you will find a new BT-fixed 10.1 kernel modified for Dual-Boot!
ADB driver not installing when in recovery!
It has been reported that after installing ICS on the phone, the computer cannot install the ADB driver when phone is in recovery mode, although ADB works normally when in USB Debugging mode.
Solution:
1. Open Device Manager and connect phone in recovery.
2. Right-click on LGE COSMO USB Device (in Other Devices) and select "Update driver software"
3. Select "Browse my computer for driver software"
4. Select "Let me pick from a list..."
5. Select "ADB Interface"
6. Select "Android Platform Sooner Single ADB Interface" and hit "Next"
7. Say "Yes" to the warning and wait for the driver to install
8. You may have to reboot the computer
Instructions on setting up the ROMs:
In this guide, I will concentrate on how to setup your EXTERNAL SD, because the latest CM10 and CM10.1 kernels modified by Berni expect to find partitions there!
First of all, you need to have ADB installed on your PC and CWM (or other recovery) on your phone. You also need to have unlocked bootloader if you are running ICS. There are other threads that explain how to do all that.
1. BACKUP your EXTERNAL SD card. IT WILL BE ERASED!
2. Download the primary and secondary ROMs of your choice
3. Do the necessary modifications to the secondary ROM as instructed by Berni (Do NOT use Windows Notepad for this. It corrupts the script. Download and use Notepad++ instead).
4. Download the kernels that match your ROMs (as described in Berni's guide).
5. Copy all to your INTERNAL SD (as I said, the external sd will be erased).
6. Boot into recovery, connect to PC via ADB and prepare partitions as instructed by Berni (this is when your card loses all data).
... Detailed Setup Instructions:
Some people reported trouble when trying to partition external SD cards larger than 8GB. So, I rewrote Berni's guide and added a little trick to help.
Follow this guide to partition your EXTERNAL SD card:
1. Turn off your phone. Keep Vol- 3D and Power keys until the LG logo shows. Release all keys. Wait a few sec.
2. You are now in Recovery. Connect your phone to PC with a USB cable, press Windows Start Menu, type:
cmd
Click to expand...
Click to collapse
and hit enter.
3. In the new window that has opened type:
adb shell
cd /dev/block
parted mmcblk1
print
Click to expand...
Click to collapse
For a 32 GB card, you'll get something like this:
Code:
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk1: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 [b]1049kB 31.4GB[/b] 31.4GB primary fat32 lba
Write down the Start and End numbers
For cards larger than 8GB, the End Number is shown in GB. Multiply it by 1000 to cnvert it to MB (31400MB in our example). Make sure you use values in MB and NOT in GB in the commands below.
4. Type
rm 1
mkpartfs primary fat32 1049kB 29400MB ///!!! Instead of 1049kB, type the Start number you wrote down. Instead of 29400, type your End number minus 2000MB !!!
mkpartfs primary ext2 29400MB 30100MB ///!!! Instead of 29400, type the end of your 1st partition. Instead of 30100, type the end of 1st partition plus 700MB !!!
mkpartfs primary ext2 30100MB 31300MB ///!!! Instead of 30100, type the end of your 2nd partition. Instead of 31300, type the end of 2nd partition plus 1200MB !!!
Click to expand...
Click to collapse
At this point, because not all cards have exactly the same capacity, you need to know exactly how much space you have left. Type:
print free
Click to expand...
Click to collapse
You get somehing like:
Code:
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk1: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
32.3kB 1049kB 1016kB Free Space
1 1049kB 29.4GB 29.4GB primary fat32 lba
2 29.4GB 30.1GB 700MB primary ext2
3 30.1GB 31.3GB 1200MB primary ext2
31.3GB 31.4GB [b]87.7MB[/b] Free Space
Note the size of your last free space (87.7MB here). Anything larger than 67.1MB will be sufficient.
Type:
mkpartfs primary ext2 31300MB 31387.7MB ///!!! 31300MB is the end of 3rd partition. 31387.7MB is the end of 3rd partition plus the remaining free space !!!
print
Click to expand...
Click to collapse
this time you get:
Code:
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk1: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 29.4GB 29.4GB primary fat32 lba
2 29.4GB 30.1GB 700MB primary ext2
3 30.1GB 31.3GB 1200MB primary ext2
4 31.3GB 31.4GB 90MB primary ext2
5. Turn off your phone and boot again into recovery.
Type:
adb shell
cd /dev/block
mke2fs -T ext3 mmcblk1p2
mke2fs -T ext3 mmcblk1p3
mke2fs -T ext3 mmcblk1p4
Click to expand...
Click to collapse
Your new partitions are now ready!
7. Flash the ROMs (you may want to keep your original ROM and flash only the secondary one)
8. Flash your primary kernel and reboot to system.
Rebooting will now load your primary ROM.
Partitioning the easy way!
Instead of step 6, you may put your microSD card to your PC using a Card-Reader. Then you may use MiniTool, EaseUS or other freeware partitioning tool to create your partitions. Shrink your main partition and make three new PRIMARY EXT3 partitions AFTER your main one. The 1st (system2) must be 700MB. The second (data2) at least 1GB (you can make it larger if you like to install lots of apps)! The 3rd one (cache2) should be around 100MB. So, do the math and make sure you have shrunk your fat32 partition according to your needs first. After you're done, eject your card from the PC, put it in your phone and continue to step 7.
Important: If for your own reasons you need to create more than the 4 primary partitions mentioned above, then you must convert your card to GPT (GNU Partitioning Table). Minitool has that option. This is because the default MBR (Master Boot Record) partitioning does not support more than 4 primary partitions on the same medium. This is also how the internal memory of our phones is divided into a large number of partitions (P920: 15, SU760: 17) and they are all primary.
New: Easiest partitioning ever!
A new app, AParted, has appeared on PlayStore. You can use it to create both MBR type (up to 4 primary) and GPT type (up to 128 primary) partitions.
Instructions on ROM switching:
1. Go to Play Store and install SManager
2. Download the attachment from 1st post, unzip it and place the DualBoot folder on your phone (anywhere you like)
3. Unzip your primary kernel, place boot.img into your DualBoot/img folder and rename it to boot1.img
4. Do the same for your secondary kernel, but rename it to boot2.img
5. Run SManager, browse to your DualBoot folder and select "Switch_ROM".
6. Mark favourite and su options and run the script.
Your phone will now reboot to your secondary ROM. Use the same script to go back to your primary ROM.
7 (optional). SManager has a homescreen widget system. It lets you add buttons in your homescreens that will directly run the linked script (it has to be put in favourites first).
Alternatively, you may download Flashify from Play Store and flash your desired Kernel.img from there. The advantage is that you may keep and test different kernels for the same ROM without having to rename them or put them in the IMG folder (less initial setup). The disadvantage is that it requires more clicks to switch every time.
Instructions on Backup/Recovery/Wipe:
These scripts work for EXTERNAL SD ROM installations!
1. For full functionality, you must be on PRIMARY ROM (you can't expect to wipe or restore a running system)!
2. Make sure you have at least 2GB free space on your external SD if you want to make a backup.
3. Inside your DualBoot folder there is a script: "Recovery_Tools". Run the script with SManager (make sure you have the SU and Wlck buttons pressed). For Wlck to work, you must first enable it from SManager settings.
4. You will now enter the Dual Boot Recovery Tools. There are several options. Type the number you want and press enter. All functions are pretty self-explanatory.
It's very important to know that every backup overwrites the previous! The backup is kept in /sdcard/_ExternalSD/ROMs/rom2_backup. If you want to keep more than one backups, you can always rename the folder, but remember to change the name back if you want to restore your ROM.
The "Advanced" option takes you to the "Wipes" menu. For a Factory Reset, you must wipe Data2 and Cache2. For a Full Format, in order to clean-install a new ROM, you may also wipe System2.
Remove Dual Boot - Regain card space:
This is pretty simple:
1. Backup the contents of your SD card.
2. Boot to your primary ROM
3. Go to System Settings/Storage and select Erase SD card.
Case scenario / Easy migration to dual boot:
Say you have already installed CM10 in a single boot setup but you miss the 3D features and you want to restore your good old gingerbread backup or flash the new P920 ICS, but keep your CM10 setup as a secondary ROM in dual boot.
1. Make sure you have at least 4GB free in your external SD.
2. While still in CM10, use SManager to browse to your DualBoot folder, run the "Recovery_Tools" script and select option to "Backup/Migrate ROM1".
(Go fry some bananas cause this will take around 6-7min!)
3. Now backup your external SD to your PC and reboot to recovery.
4. Follow the guide to partition your external SD.
5. Restore your Gingerbread or P920-ICS backup or flash your favorite ROM and reboot into it.
6. Restore your external SD backup from PC.
7. Run the "Recovery_Tools" again and use the "Restore ROM2" option.
(Eat your fried bananas cause this will take another 6-7 min!)
Your original CM10 installation is now relocated to external SD as your secondary ROM. Use my instructions on ROM switching to boot into it.
Wow man, this is awesome!
I'm bussy right now but I'll try it out as soon as i can.
Thanx thanx thanx thanx......
this is awesome!!thank you so much for this...one of the reasons i don't use dual booting is that the switching process is not efficient
and now its much better..so thank you again
Re: [DualBoot][Tools]Essential tools for Berni's method
Great job mate, you just made my life a lot easyer.
Thanks
Sent from my LG-P920 using xda app-developers app
Re: [DualBoot][Tools][Guide]Essentials for Berni's method
Some people experienced trouble partitioning external cards larger than 8GB. Specifically, the 4th partition (cache) wouldn't fit. So, I rewrote Berni's guide on partitioning, adding one extra trick to do the job without problems!
Sent from my 3D phone
Re: [DualBoot][Tools][Guide]Essentials for Berni's method
Added a way to migrate your single boot CM10 installation to dual boot without losing your settings!
Sent from my 3D phone
dreccon said:
Added a way to migrate your single boot CM10 installation to dual boot without losing your settings!
Sent from my 3D phone
Click to expand...
Click to collapse
Thank you. You are awesome
Very good bro, just find a way to put script shortcut in powermenu, that would be real cool. I think it can be done by editing android.policy.jar
Re: [DualBoot][Tools][Guide]Essentials for Berni's method
Added support for the new P920 ICS v28b.
Sent from my 3D phone
It just occured to me that there is yet another way to easily switch ROMs without using my scripts! Whoever is interested may try it.
This method is ideal for those who use Xbsall's prerooted v28b. That rom comes with milaq' 2nd init recovery which lives in the system partition. The recovery partition remains with stock recovery which is practically useless. So, 1st of all make sure you have wkpark's v1.25a bootloader (a prerequisite to boot into both ICS and CM10). Then flash the secondary boot.img into the recovery partition. This way every "normal reboot" will take you to your primary ROM and every "reboot to recovery" (or pressing vol-down at bootup) will take you to the secondary ROM. To go to milaq's recovery you would press vol-down at normal bootup while keys are flashing or run the dedicated app from android. So, there you have it: a fully functional dual-boot android. Ofcourse, this can apply to any ROM that can be fitted with 2nd init recovery.
Any questions?
dreccon said:
Added support for the new P920 ICS v28b.
Sent from my 3D phone
Click to expand...
Click to collapse
yaaaa great man i love it :good::good::good::good:
Hey dreccon , say that i want to keep cm10 as my primary ROM and v28b as my secondary , if you can also include those steps in your main post i'd really appreciate it.
Thank you for this great contribution.
Re: [DualBoot][Tools][Guide]Essentials for Berni's method
boltthrower56 said:
Hey dreccon , say that i want to keep cm10 as my primary ROM and v28b as my secondary , if you can also include those steps in your main post i'd really appreciate it.
Thank you for this great contribution.
Click to expand...
Click to collapse
Sorry, can't do that! It's not that it can't be done, but you would need a v28b kernel modified to look for the system partitions in the SD card. I don't know how to do this. Berni does! That's why all the modified kernels are on his page and not here!
What you can do right now is to migrate your existing CM10 to the card. I've written instructions on 1st post.
Sent from my dual-booting ICS/JB O3D!
dreccon said:
Sorry, can't do that! It's not that it can't be done, but you would need a v28b kernel modified to look for the system partitions in the SD card. I don't know how to do this. Berni does! That's why all the modified kernels are on his page and not here!
What you can do right now is to migrate your existing CM10 to the card. I've written instructions on 1st post.
Sent from my dual-booting ICS/JB O3D!
Click to expand...
Click to collapse
Allright , thanks anyway...
I'll pm bernie and ask about modifying the kernel.
I already did a little research about it , i think i can do it easily , i just need someone to point me out to the right direction.
Thank you very much for the Scripts they work really good and fast...:good:
ADB can not get started with the recovery, I tested with CMW and TRWP (terminal), any ideas?
infernum said:
ADB can not get started with the recovery, I tested with CMW and TRWP (terminal), any ideas?
Click to expand...
Click to collapse
Are you using ICS as your primary ROM? It seems that there is a driver problem in ICS. I'm using v28b and my computer can't install drivers when I connect phone in recovery, although everything works perfect when it's booted in Android. All I can tell you is to try updated drivers (the link has been posted in v30a thread. If it still doesn't work, you'll have to use TWRP console instead of ADB. If this is your case you'll need further instructions cause the commands in TWRP console are a little different than ADB.
Sent from my dual-booting ICS/JB O3D!
Also, see if updating Android SDK makes any difference.
Sent from my dual-booting ICS/JB O3D!
dreccon said:
Are you using ICS as your primary ROM? It seems that there is a driver problem in ICS. I'm using v28b and my computer can't install drivers when I connect phone in recovery, although everything works perfect when it's booted in Android. All I can tell you is to try updated drivers (the link has been posted in v30a thread. If it still doesn't work, you'll have to use TWRP console instead of ADB. If this is your case you'll need further instructions cause the commands in TWRP console are a little different than ADB.
Sent from my dual-booting ICS/JB O3D!
Click to expand...
Click to collapse
I can get into adb from fastboot , recovery and debugging with defcomg super light ROM ?
Sent from my LG-P920 using xda premium