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,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Good question ..............i think there is no answer for this question
rvd_516 said:
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Click to expand...
Click to collapse
some resources would have to be used by both ROMs..
with the current hacks it can't be done easily.
i guess some way of ramdisking the shared resources will have to be used.
basically, if you think about a hack for defy ask first:
can it be done in a completely open (=bootloader not locked) phone like nexus ?
if yes, ask:
is it WORKING?
if yes also, so maybe it can be done.
nevertheless, it's easy enough to create a script to backup & restore NANDROIDS.
but then every switch between roms will take like 25+ minutes, so it won't be a real multiboot.
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
ephumuris said:
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
Click to expand...
Click to collapse
I think there are two possibilities for this to happen: first of all, we should try NAND boot for the primary ROM, and try somehow to load the secondary ROM from the internal memory (it'll be faster than the SD Card, I think). The problem here would be allowing the bootloader to read from internal memory instead of NAND. I know this can be done based on the number of WinMo-Android and iOS-Android dual boot solutions, with a menu to choose which system to load, in the boot screen.
The second option is the method used by Wing Linux to run Android on old WinMo devices. In this method, you MUST boot in WinMo (or, in our case, in the primary ROM), then open the app that loads Android (the secondary ROM, for us). Android does NOT run emulated in this method, but, since the device can't dual boot directly, the app sends a signal for the device to restart running from the bootloader to the SD Card (for us, internal memory). This second option is, somehow, like the System Recovery app (not 2ndInit), that has an option that reboots directly into Recovery. So, if we can tell the phone to load from custom Recovery (which is, in fact, in internal memory, not in NAND), I think it's possible to make it load an entire ROM from the internal memory (without having to mount it everytime and waiting for the dalvik-cache to load).
However, it's surely a hard work to do.
Yes one from nand and one from sd card..........good......can we partition nand and use it both on the nand itself??
it should really work if we use virtual images or sdcard-partitions instead of system, data and cache partitions.
This can be changed in the init.rc-file(of 2nd-init).
The creator of the 2nd-init-bootmenu should implement this feature.
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
Did you try it?
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
even i like to know tht did u tried tht?
I managed to boot from virtual system,data and cache partitions with the 2nd-boot-option of bootmenu like ep3 said.
It was a bit difficult because android-init remounts /dev so the changes will be lost but now I found a way.
And: I got recovery working for the virtual system so you don't need to prepare your images, BUT: only the wipe and restore are working. "install zip" will still affect your real system.
My scripts need some testing but after that I will release a first version.
the multboot works for me i writed a cutsom boot sh and init.rc and woila WORKS!
NOT PUBLUC because it not works for all rom
---------- Post added at 04:59 PM ---------- Previous post was at 04:36 PM ----------
this is a dualboot rom
http://forum.xda-developers.com/showthread.php?t=1225179
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
I uploaded a new version of my multiboot-script(v0.2)
changelog:
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
Download:
http://www.multiupload.com/UT0TLPR3ZW
m11kkaa said:
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
Click to expand...
Click to collapse
Thanks for your work.
Did the 2nd android system boots from sdcard?
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
Ask pedrodh http://forum.xda-developers.com/member.php?u=2098689
He can help.
Nice work, thanks i will add this soon, in the future bootmenu versions
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
I released a dual boot version that uses 2nd-boot a few months back, hadn't have much time to improve it since.
I was using loop-back mount with /system and bind mount with /data since it's much more space efficient than just use an ext3 image.
Awesome job. I think u shud create a new thread for it. Dual booting cm7 and miui :O
Sent from my Moto Defy
Hi Friends!
I have a 16GB class4 card, recently i faced some problems when i can't see the apps installed on my card(partritioned in ext4), so instead of worrying about it all i did was reinstalling the apps in the remaining space of the card(i was still experimenting with ROMs, And i accept I'm a Sloth), this happened to me for a couple of times. Now, I don't want to lose my data in the FAT32 part and want to know that if there's any way of formating the ext partrition without disturbing the FAT32 one
Thanks in advance for sharing your wisdom with me!!
(and i know i would look like a complete idiot if there's something largely famous solution of it, I don't know of *PS- I'm aware of backing up and restoring data but thats not the solution i need)
Easiest way is to boot into recovery and wipe sdext
cdesai said:
Easiest way is to boot into recovery and wipe sdext
Click to expand...
Click to collapse
yeah this is the most simple way to format sd-ext
Sent from my g3
Kyorarom Infinity
powered by g3mod
Kyorarom Infinity kernel
Boot into recovery - mounts and storage - wipe sd-ext
hi
i was thinking of upgrading my phone (one V) to Kitkat [http://forum.xda-developers.com/showthread.php?t=2785779]
so my current version of CWM is 5.8 do i hav to update it to 6.0 [http://forum.xda-developers.com/showthread.php?t=1871243]
if yes, can you plz tell me wat are d ways to update it. I hav read few post but am still confused.
and the installation process for Kitkat rom is same as any other rom or does it hav different steps to complete installation.
waiting for reply !!!
download cwm zip > put to sd card > reboot recovery > flash zip > advanced > reboot recovery > done
axljohn said:
download zip > put to sd card > reboot recovery > flash zip > advanced > reboot recovery > done
Click to expand...
Click to collapse
and wat about the CWM ???
Neel009 said:
and wat about the CWM ???
Click to expand...
Click to collapse
Dont forget to flash a gapp too that is for your google play.
I had no problem with CWM until now but I needed an ext4 partition for a rom (slimkat) and CWM failed.
I then installed 4ext and everything worked. (except the ROM on my phone hehe)
So if you need an ext4 partition for your rom, I would not recommend CWM based on my experience.
axljohn said:
download zip > put to sd card > reboot recovery > flash zip > advanced > reboot recovery > done
Click to expand...
Click to collapse
download zip its that cwm.
Neel009 said:
and wat about the CWM ???
Click to expand...
Click to collapse
it can be done with any zip.
---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------
AoDev said:
I had no problem with CWM until now but I needed an ext4 partition for a rom (slimkat) and CWM failed.
I then installed 4ext and everything worked. (except the ROM on my phone hehe)
So if you need an ext4 partition for your rom, I would not recommend CWM based on my experience.
Click to expand...
Click to collapse
didnt have any problems on my side.. i think all partitions on any phone is ext4.. what phone did u use?
axljohn said:
it can be done with any zip.
---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------
didnt have any problems on my side.. i think all partitions on any phone is ext4.. what phone did u use?
Click to expand...
Click to collapse
my question was ''do i need to upgrade my Clock Work Mode recovery to 6.0 before flashing kitkat rom ??
if yes then how to update ??''
plz reply !!!
Neel009 said:
my question was ''do i need to upgrade my Clock Work Mode recovery to 6.0 before flashing kitkat rom ??
if yes then how to update ??''
plz reply !!!
Click to expand...
Click to collapse
1) yes
2) search it in your device's forums. a little searching won't hurt
axljohn said:
1) yes
2) search it in your device's forums. a little searching won't hurt
Click to expand...
Click to collapse
i used rom manager to update my cwm recovery to 6.0 or 6.1 but its still 5.8.x. then i manually searched and found out about this verzion [http://forum.xda-developers.com/showthread.php?t=1871243]
help me update my CWM recovery manually.
plz !!!
axljohn said:
it can be done with any zip.
---------- Post added at 11:16 AM ---------- Previous post was at 11:13 AM ----------
didnt have any problems on my side.. i think all partitions on any phone is ext4.. what phone did u use?
Click to expand...
Click to collapse
It's an HTC Sensation. I tried first with CWM and rom manager. But the partition was not recognized when installing (Slimkat) .
Then, I found this about creating partition: http://forum.xda-developers.com/showthread.php?t=2125513
Where you can read:
These two methods are the best ones to use. Other means could result in sd-card damaging, or other problems. Do not use:
ROM Manager, CWM Recovery, Windows Minitool Partition Wizard etc.
Click to expand...
Click to collapse
And for me it happened to be true
(The SD was not damaged, just the partition not working).
Neel009 said:
i used rom manager to update my cwm recovery to 6.0 or 6.1 but its still 5.8.x. then i manually searched and found out about this verzion [http://forum.xda-developers.com/showthread.php?t=1871243]
help me update my CWM recovery manually.
plz !!!
Click to expand...
Click to collapse
PM the OP for that version.. I guess the thread's already closed because there's no links.. And I also found that your device has no support (officially, at least) for CMW v6.x.x.x. Sorry man.
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
AoDev said:
It's an HTC Sensation. I tried first with CWM and rom manager. But the partition was not recognized when installing (Slimkat) .
Then, I found this about creating partition: http://forum.xda-developers.com/showthread.php?t=2125513
Where you can read:
And for me it happened to be true
(The SD was not damaged, just the partition not working).
Click to expand...
Click to collapse
The "partition" you're talking about there is SD partition, right? To use that partition you must format the partition's file system to ext4, not fat32 (default SD file system). Maybe it "didn't work," just the in the wrong file system.
axljohn said:
The "partition" you're talking about there is SD partition, right? To use that partition you must format the partition's file system to ext4, not fat32 (default SD file system). Maybe it "didn't work," just the in the wrong file system.
Click to expand...
Click to collapse
Yes, correct. The conclusion is that I was able to make a correct ext4 partition with 4ext recovery only, I thought it could be useful to the OP regarding his question about CWM.
AoDev said:
Yes, correct. The conclusion is that I was able to make a correct ext4 partition with 4ext recovery only, I thought it could be useful to the OP regarding his question about CWM.
Click to expand...
Click to collapse
Except that all phone partitions are ext4 by default. It's the phone partitions OP is concerned of, not SD partitions. I think..
Are you saying that some recoveries have different file systems other than ext4?
axljohn said:
Except that all phone partitions are ext4 by default. It's the phone partitions OP is concerned of, not SD partitions. I think..
Are you saying that some recoveries have different file systems other than ext4?
Click to expand...
Click to collapse
He asked if the steps to install kitkat are the same and more info about CWM. I just explain the problem I had when I did exactly what the OP wants to do, in the same situation.
It would crash during the install because there was no ext4 partitions on the sdcard. I don't know why, this part I don't understand. I never had to do something like that until now. So after investigating the matter I realised that I had to create an ext4 partition (1GB) on my SD card. (it had 1 Fat32 partition)
I tried with different tools. CWM included. They failed. I stepped upon the post I mentioned before. I installed 4ext. I created a 1GB ext4 partition on the SD Card. The install was successful and I enjoy my phone again with KitKat. (but in the end I removed Slimkat due to some bugs and installed this one http://forum.xda-developers.com/showthread.php?t=2530073, which works perfectly so far)
That's all about my experience installing a kitkat based rom which is the OP goal. As mentioned before, I don't know why it needed this ext4 partition for the installation. My knowledge does not go that far, but the result is there.
AoDev said:
He asked if the steps to install kitkat are the same and more info about CWM. I just explain the problem I had when I did exactly what the OP wants to do, in the same situation.
It would crash during the install because there was no ext4 partitions on the sdcard. I don't know why, this part I don't understand. I never had to do something like that until now. So after investigating the matter I realised that I had to create an ext4 partition (1GB) on my SD card. (it had 1 Fat32 partition)
I tried with different tools. CWM included. They failed. I stepped upon the post I mentioned before. I installed 4ext. I created a 1GB ext4 partition on the SD Card. The install was successful and I enjoy my phone again with KitKat. (but in the end I removed Slimkat due to some bugs and installed this one http://forum.xda-developers.com/showthread.php?t=2530073, which works perfectly so far)
That's all about my experience installing a kitkat based rom which is the OP goal. As mentioned before, I don't know why it needed this ext4 partition for the installation. My knowledge does not go that far, but the result is there.
Click to expand...
Click to collapse
since u flashed kitkat in ur htc sensation and u hav done it right, u can guide me to do so......
here is what i understood regarding the kitkat rom
i have to to do partition of my SD card (the link was helpful !!!)
CWM version does not do any help for kitkat rom (i guess !! am still confused about CWM recovery because the link for one v's CWM 6.0 is dead and in Kitkat rom's link it does not say anything or about the CWM version how to flash it )
my question is
after partition, did you completed the "using the ext partition" and then you flashed it using CWM and what version of CWM did you use ?
and my CWM version is 5.8 should i use it to flash kitkat (without getting bricked) ??
Sorry for asking so many question. My roms thread does not have the details that i generally find in other thread. I want to flash Kitkat so badly.
It does not matter if the rom works or not, still its worth a shot. just want to make sure i do everything right from my side without damaging my handset.
AoDev said:
He asked if the steps to install kitkat are the same and more info about CWM. I just explain the problem I had when I did exactly what the OP wants to do, in the same situation.
It would crash during the install because there was no ext4 partitions on the sdcard. I don't know why, this part I don't understand. I never had to do something like that until now. So after investigating the matter I realised that I had to create an ext4 partition (1GB) on my SD card. (it had 1 Fat32 partition)
I tried with different tools. CWM included. They failed. I stepped upon the post I mentioned before. I installed 4ext. I created a 1GB ext4 partition on the SD Card. The install was successful and I enjoy my phone again with KitKat. (but in the end I removed Slimkat due to some bugs and installed this one http://forum.xda-developers.com/showthread.php?t=2530073, which works perfectly so far)
That's all about my experience installing a kitkat based rom which is the OP goal. As mentioned before, I don't know why it needed this ext4 partition for the installation. My knowledge does not go that far, but the result is there.
Click to expand...
Click to collapse
Neel009 said:
since u flashed kitkat in ur htc sensation and u hav done it right, u can guide me to do so......
here is what i understood regarding the kitkat rom
i have to to do partition of my SD card (the link was helpful !!!)
CWM version does not do any help for kitkat rom (i guess !! am still confused about CWM recovery because the link for one v's CWM 6.0 is dead and in Kitkat rom's link it does not say anything or about the CWM version how to flash it )
my question is
after partition, did you completed the "using the ext partition" and then you flashed it using CWM and what version of CWM did you use ?
and my CWM version is 5.8 should i use it to flash kitkat (without getting bricked) ??
Sorry for asking so many question. My roms thread does not have the details that i generally find in other thread. I want to flash Kitkat so badly.
It does not matter if the rom works or not, still its worth a shot. just want to make sure i do everything right from my side without damaging my handset.
Click to expand...
Click to collapse
Sorry.. Even I don't understand the question anymore. But as far as I know, ext4 partitions on an SDcard is never related to flashing ROMs.. It is only used for Link2SD and such..
Yes, so, somehow it looks like during the installation, these Kitkat roms were expecting an ext4 partition on the SD Card.
If you look in Internet, you can find things like that for example:
(Damn, my xda noob account does not let me post links, search youtube and use this video ID: ?v=bUMhn6geaUM
They talk about this ext4 partition on the SD card, why they do it and what they use to do it. (Partition Magic)
Maybe if I had just removed my SD card , the install script would not have tried to use the SD card, but let's not add more confusion
As I said, CWM (I had 5.8) did not work to create a correct ext4 partition on my SD Card. (the install failed again)
The funny thing is I even paid 2$ for CWM xd
I replaced CWM by 4ext recovery. website: 4ext.net (install the 4EXT Recovery Updater)
Then I created the ext4 partition on the SD Card and both kitkat roms I tried were installed successfully.
(In 4ext recovery, install from zip, select your rom zip, go.)
btw, I backed up everything before (but I guess it's obvious) , once, I had to reinstall my backup from recovery because it would not boot.
Hi guys I ask you because I do not find anything around
I have a cell phone with B63M romextralite2013 installed by CWM5504 with good result but now I wanted to put on the Link2SD to raise a bit of memory to device, but doing primary fat32 partition and tried ext2 / ext3 / ext / 4 / fat32 always gives me a script error installation that can not 'be created mount: no such device would know where I am wrong? and yet I do partitions with mini tool partition 9 I tried also in recovery mode to make the partition but the result is always the same ....
I should not put a rom cooked new reliable that has everything ???? if you could tell me a rom reliable and guidance ??
thanks for the answers
sorry for my english I'm Italian and I'm helping with google translator
Thanks for all
up plese