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 everyone, looking for a little guidance.
Phone: Android G1 (Rogers Canada Dream) running Cyanogen 4.2.15.1, been running fine since 4.2.6.1
Removed SD card while it was on and it rebooted... when it restarted it showed no applications and said the SD card was inaccessible and required a format. After rebooting a few times with no success I bit the bullet and formatted it... all apps are gone except for the ones that are on that image for Cyanogen. I have no market app to download new apps and when I plug it into my PC and mount it I don't see it show up as a drive like it did so I have no way to get the apps back on.
Has anyone had this happen before? Phone still works but I need to get it back to a state where I can get access to the SD and install the market... Any suggestions appreciated!!
There is a thread on the HERO section of Modaco site called "no adb, no sd". I think the 1st post on the last page MIGHT help. There are adb commands you can run to see if the phone has randomly stopped accessing the SD. Worth a shot.
PM me if you have trouble finding the thread n I'll have a look when I'm at my laptop.
Sent from my HTC Hero using XDA App
I misunderstood I think.
So it is now showing an sd present? Have you tried formatting in a pc?
Tried reboot without the sd in, then insert once fully booted again?
Sent from my HTC Hero using XDA App
I remove the SD Card, formatted it in my PC put it back in the phone and I can store pics and vids on it and access them but cant see or access it from the PC when in the phone. I also have no file browser so I cant install any apps or even access the market icon is gone).
D RoiD said:
Hi there! I had posted on the forum with the G1 issue where my SD card seemed to have died.
http://forum.xda-developers.com/showthread.php?t=738105
I have since removed the SD card and reformatted it, I can store pics and vids and replay them so the card is fine. I tried letting it boot up then adding the SD card when booted, that caused it to reboot, same issue...
Not having access to the card, I cant install any apps or browse the SD to install from there... really sucks
I'd be willing to blow it away and restart too and install CyanogenMod-5.0.8 but I need some guidance.
Click to expand...
Click to collapse
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
ddotpatel said:
I got your message pal....
Ok,.... So pictures and videos taken with your phone camera DO save to your SD?.... and you CAN access them on your phone OR if you put your SD into your PC/Lappy?... But not when trying to "mount SD"?
Or have I got that completely wrong?.... Did you put pics&vids onto it through your PC, and thats the only access you get to it?
Click to expand...
Click to collapse
Pics taken DO save to me SD. I Can access them from a PC is I remove the SD and put it in the PC. Not when I plug the phone in via USB then tell it to mount.
I just did a low level format, same issue.
UPDATE: Just tried the Android System Recovery and Toggle USB-MS and it shows on my laptop now! Going to try the recovery backup now.
aha,... so its just a mounting issue, not that the hardware has turned itself off.
Once when using an older ROM (maybe Villain 10?) we had this same issue, not able to mount SD,... going into Settings --> Connect to PC --> and turning off Notify/ask me solved the problem.
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
D RoiD said:
I just partitionned it using:
parted /dev/block/mmcblk0
print (to verfiy we know what size card we are dealing with, the details should be straight forward)
rm 1
rm 2
mkpartfs primary fat32 0 7500
mkpartfs primary ext2 7500 7948
quit
upgrade_fs
reboot recovery
Then put CyanogenMod-5 For Dream/Magic on the SD and renamed it update.zip
I'm in Android System recovery now and just did a nandroid backup.
I should be able to WIPE then FLASH UPDATE IMAGE right?
Click to expand...
Click to collapse
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
akapoor said:
Yes, if you have the ROM image on the SD Card (FAT32 partition), you can go flash the image.
Click to expand...
Click to collapse
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
D RoiD said:
Stupid question but when I wipe will it delete my contacts as well?
I assume yes but...
Click to expand...
Click to collapse
If your contacts are saved in the phone's memory, then yes. Any settings, apps, configurations that are stored on the phone will all be gone.
A wipe pretty much gives you the factory settings. (As if you just bought the phone) So you'll have to re-signin into your Google Account and let the Contacts Sync, etc..
EDIT: Depending on what you are flashing (flashing and wiping are two different things), you may not even need to wipe.
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
D RoiD said:
Hmmm I tried flash update image and got:
E: Cant open /sdcard/update.zip (No such file or directory)
When I mount it in system recovery I see the LOST.DIR and update.zip
Click to expand...
Click to collapse
Try this:
-Confirm the Image-
1) Make sure you have the full image you are going to flash. (Compare MD5 Hashes and/or just redownload the image)
2) Make sure the image you are flashing is the in the ROOT directory of your SDCard. In other words, it shouldn't be in any folder.
-Flash the Image-
1) When in Recovery, choose to flash an image.
2) Depending on what recovery you have, you may have to select/find the Image you want to flash.
3) Flash the image
-Wipe (Depends)-
1) If you are coming from a different ROM base (ie anything -> cyan), you'll want to wipe.
2) After the phone successfully flashes the image, wipe the phone.
Reboot.
Let me know how it goes.
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
D RoiD said:
I pulled the new image from: Latest version: 5.0.8-DS - 06/19/2010
Download: http://cyanogen-upda...8-DS-signed.zip
but it says no such file or DIR... weird...
The only partition I can see on my PC to put it on is the main partition...
I just downloaded the file and renamed it update.zip
Click to expand...
Click to collapse
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
akapoor said:
I just realized the main reason that you posted this topic. From what I am assuming, either:
a) Your SD Card reader is dead
b) The software isn't recognizing the SD Card reader.
Best bet at this point is to setup ADB (ADB For Dummies) and flash the image from your computer. It can get a slight bit complicated, but just slowly go through each step for installing ADB.
Once ADB is set up, you can flash the image from the computer.
Click to expand...
Click to collapse
The SD card reader in my phone? It has to work if I can read an write to it ( tested photos and videos) and in recovery I was able to make a backup.
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
D RoiD said:
If its the software I need to flash it then right? ADB does make me nervous as I only used it once... I just tried using the terminal emulator on the phone to flash a recovery image I had made while back:
cd /sdcard
flash_image recovery /sdcard/recovery-backup.img
and got the message "error writing recovery: Permission denied"
Click to expand...
Click to collapse
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
akapoor said:
If you can view the pictures that you saved on the SD card from the phone, then both the software and hardware are functioning correctly.
Regarding the permission denied:
1) What happens if you "su - " in terminal?
2) First try one(1) ^ and then try to reinstate the permissions. (In recovery, go to console and type : fix_permissions)
Not sure otherwise.
Click to expand...
Click to collapse
Ok I did a wipe and now I see the SD when mounted on the PC with the phone on.
I have my market icon back so I can reinstall my crap.
I'll leave it as is for a bit but appreciate everyones input!!!
Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.
Though i didn't understand a word(being an internee dentist) it will be useful to others.appreciate your efforts!!
Sent from my GT-I9003 using xda app-developers app
This is what i call a complete and useful guide.
This should become a sticky.. now... NOW!
+1 for sticky, superb info.
that would be a really nice sticky
i had the motherboard changed..
Thanks Dipu K for your efforts.
I've tried this solution in my I9003, and I have only a problem: When reboot the phone, /data is copied into de Ext4 partition on SD card, but all aplications have errors because isn´t possible to unmount /data,
Here is the messaje in remnt-log (only a few lines):
Code:
...
3. Make Directory --->
4. Mount new data partition from external SD --->
5. Copy the current files in /data
6. Remove current files in /data
7. Unmount /data
umount: can't umount /data: Device or resource busy
8. Remove dir /data as a safety measure
9. Linking external sd data partition as /data
10. Final Mount status --->
...
What can I do to correct this?
Thanks
bfsa said:
...
What can I do to correct this?
Thanks
Click to expand...
Click to collapse
Finally, I've changed a line on 00remnt, and seems to work properly: busybox umount -l /data 2>> /system/remnt-log
Where can I get make_ext4fs? Sadly the same case has happened to me...
Hi Guys.
I am using alpha 4 from last one month and experience was awesome but from last 1 week I am getting lot of FC for lot of services like exchange service gapps what's up camera and lot more. I am not sure why FC issue started happening from last one week.
History :
I was using CM 10 alpha 1 then alpha 2 then alpha 3 and now on alpha 4.
I really fed up with Force close issue from last one week . I tried reboot but still 80% of apps and services getting FC. Please guide me on this .
Sent from my GT-I9003 using xda app-developers app
Sent from my GT-I9003 using xda app-developers app
hi all, i have a galaxy i9003 with a corrupted or completely dead (not sure) internal memory chip. I have come to this conclusion after 3 days of trying to install custom and stock roms. I can access recovery and download mode but i cant install any ROM, the phone keeps rebooting after the SAMSUNG (whole screen black except SAMSUNG in the middle). All i have is atm this http://forum.xda-developers.com/showthread.php?t=1351056 installed on my phone via ODIN. I dont have knowledge about ADB, can somebody help me out with instructions more?
Pre-requisites:
- Rooted Phone
Click to expand...
Click to collapse
Is there a solution without a rooted phone or can I root it somehow, even if the there is a hardware defect? I got an error with /dev/block/mmcblk1p that rfs can't be written.
I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...
allxx said:
I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...
Click to expand...
Click to collapse
Please do send us a report, I'd appreciate it very much. Have to deal with a similar situation as well for an old i9003. I've tried to employ the steps mentioned here but could not get it to work as well.
Hi everybody!
Had to remove the internal SD to install everything on the external one by following the mentioned post. Nothing else worked.
http://forum.xda-developers.com/showthread.php?t=1651619
can anyone here recomended me custom rom that already with swap sdcard?
Dipu K said:
Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.
Click to expand...
Click to collapse
Somebody's Samsung Galaxy SL i9003 had wiped the internal SD card by itself! Is this even possible that it just wipes/formats on it's own? Is there any advice? The contacts appear to still be there.
*** The sdcard card created by this thread is not compatible with the original sdcard installation of CM10/CM10.1.
This is a work-in-progress and things are changing very fast so you may lose some of your data as we moved from one version to another.
After a brief discussion with leapinlar few weeks back, this is a new CM10.1 sdcard installation based on that discussion.
Features:
Dual boot stock and CM10.1.
Using only three partitions to allow stock to boot properly.
/data is stored in emmc while /system is in sdcard (Caveat: Doing stock factory reset inside stock will wipe out data of both the stock and CM10.1)
Can be flashed with ROM from this thread starting cm-10.1-20130130-UNOFFICIAL-hummingbird.
/data maximum size is now only limited by the size of the emmc.
For installation instructions follow this post. Thanks Diogenes5.
CWM Image file: sdcard-cwm-hummingbird-hybridv2.zip. Date Posted: 2/2
Data Wipe/Factory Reset now working.
Backup/Restore to/from both emmc and sdcard now also working. (/boot will not be backup and restored)
uImage.20130613.hybrid.hd.zip and update.20130613.ramdisk.hybrid.hd.zip *** latest ***
Fixed: Intermittent boot problem
cyanoboot now working for lg display.
update-20130221.zip
cyanoboot modified to pass serial number to kernel command line for android to properly report a valid number instead of unknown.
update-20130204v2.zip
Fixed device booting to stock recovery instead from the stock ROM.
update-20130204.zip
cyanoboot modified to allow CM10.1 (cm-10.1-20130203-hummingbirdv2 and above) rebooting directly to its menu.
Older downloads:
CWM Image file: sdcard-cwm-hummingbird-hybrid.zip.
Update: Download View attachment update-20130201.zip and extract uImage and ramdisk.stock to the boot partition of the SD card created from the above file. You can now delete kernel.stock as it is no longer being used.
Stock now booting normally.
Added Boot from SD alternate in cyanoboot menu.
Thanks to leapinlar for the suggestions above.
TODO: Wipe/Backup/Restore operations under CWM.
Only CM10.1 ROM dated 1/30/13 and above will work properly with this new SD card installation.
Currently this installation is compatible only with leapinlar Stock recovery tool provided in this thread.
This hack/trick is already superceded by the above post.
BEWARE: This hack/trick should be used only by HD owners who are very familiar with SD card installation of CM10/CM10.1. This may or may not work. Using this tools could brick your device, you have been warned!!!
Prerequisite: Working CM10/CM10.1 SD card installation from this thread.
Instructions
Download the attached hybrid.zip file.
Make a backup copy of /boot/uImage before copying all the files to the /boot partition of the SD card.
Insert SD card to the HD and let the device boot from it.
Hold the 'n' button of the device until the cyanoboot menu is shown.
Press the 'n' button multiple times until 'Initialize Hybrid' is highlighted.
Hold the 'n' button for at least 3 seconds to activate it.
Wait until the device rebooted (Depending on the speed of the SD card, you may have to wait for a long time).
Enjoy a faster and smoother CM10/CM10.1
Note: To uninstall, delete ramdisk.hybrid*, ramdisk.sync*, ramdisk.sys*, ramdisk.data* and u-boot.altboot from the SD card. Delete both cm_system.img and cm_data.img from the EMMC to recover the 2GB of storage space.
Technicals/Details
uImage - updated cyanoboot for hybrid booting.
Boot menu descriptions
Boot Hybrid - uses ramdisk.hybrid as the ramdisk.
Initialize Hybrid - uses ramdisk.sync as the ramdisk.
Sync System: SD -> EMMC - uses ramdisk.sys-sync as the ramdisk.
Sync Data: SD -> EMMC - uses ramdisk.data-sync-emmc as the ramdisk.
Sync Data: EMMC -> SD - uses ramdisk.data-sync-sd as the ramdisk.
Default Boot Image - uses u-boot.altboot as configuration file.
ramdisk.sync - will check whether cm_system.img and cm_data.img are present in /emmc. If not create the two files with sizes 800MB and 1200MB respectively. Loop mount both files and copy the contents of partition 2 and partition 3 of the SD card. Rename ramdisk.hybrid.copy to ramdisk.hybrid to enable the cyanoboot menu Boot Hybrid. Store the value 1 to the file u-boot.altboot to enable default booting from hybrid/EMMC.
ramdisk.hybrid.copy - will be renamed automatically by ramdisk.sync to ramdisk.hybrid to enable booting from cyanoboot menu and default booting when the value 1 is stored in u-boot.altboot
ramdisk.sys-sync.copy - should be manually renamed to ramdisk.sys-sync to enable cynoboot menu Sync System: SD -> EMMC. This is needed to update cm_system.img after a CM10/CM10.1 update of the SD card by CWM.
ramdisk.data-sync-emmc.copy and ramdisk.data-sync-sd.copy - should be manually renamed to ramdisk.data-sync-emmc and ramdisk.data-sync-sd to enable syncing data both ways. (Not included yet)
u-boot.altboot - created with a value of 1 by ramdisk.sync. Changing the value to 0 will default to normal SD boot. Value can be changed while in the cyanoboot menu.
Pros/Cons
Pros
Very fast and smooth interface.
SD card can be unmounted and removed.
Cons
SD card is always needed during boot time.
Update should be done to the SD card first before syncing with EMMC.
Consumed 2GB of spare EMMC storage.
Reboot to recovery sometimes is not working and will reboot to EMMC/Stock recovery.
Bokbokan, if you get this working so that you can get the SD down to 3 or less partitions, I have a trick to let it boot to stock with the card still in.
Sent from my HD+ running CM10 on SD with XDA Premium
Is there a speed gain for those whose cards are already faster than nand, or that's mostly for those what have slow(er) cards?
leapinlar said:
Bokbokan, if you get this working so that you can get the SD down to 3 or less partitions, I have a trick to let it boot to stock with the card still in.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
I can try booting from the stock using customized kernel and a ramdisk sourced from the EMMC but so far haven't tested it because of my bricked stock. Did not bother to restore it yet since this make my device easier to boot/reboot from SD.
What trick do you have up your sleeve?
Stevethegreat said:
Is there a speed gain for those whose cards are already faster than nand, or that's mostly for those what have slow(er) cards?
Click to expand...
Click to collapse
This is very useful for those having very slow/moderate card speed. For faster card the benefit is to allow the device continue running even without the card except during boot time.
Very cool! Will play with this shortly!
bokbokan said:
I can try booting from the stock using customized kernel and a ramdisk sourced from the EMMC but so far haven't tested it because of my bricked stock. Did not bother to restore it yet since this make my device easier to boot/reboot from SD.
What trick do you have up your sleeve?
Click to expand...
Click to collapse
Actually there are two ways.
The first is to put the stock ramdisk in the SD boot partition. For me I don't run your CM10 so it was easy for me to make it boot to stock by putting it in the CWM SD card. Then I select SD and it boots to stock. But that does not help CM10 users because they need ramdisk to be for CM10.
But for CM10 users, you can install Quick Boot from the Play Store and install it in CM10. Then tell Quick Boot to boot to bootloader and it boots to stock. But with verygreen's/your CM10 SD partition structure, stock hangs at 99%. That is because stock chokes on 5 partitions on the SD. That is why I was saying that if you could get down to 3 partitions, you could boot to stock from CM10.
But on my HD+, which I do run CM10, I changed the partition structure so it only has 3. But I don't expect users to do that. It needs to be built into the SD from you and verygreen. That is why I like your idea of putting some things on emmc so the partitions can get down to 3.
But I will briefly explain what I did to customize my HD+ CM10 SD. I deleted partition 4 and 5, normally the sdcard partition and the extended partition that holds it. Then I moved partition 2 and 3 to the end of the SD. Then I expanded partition 1 to fill the space. So I have a large fat32 partition 1 and partitions 2 and 3 the same size as original at the end of the SD. Then I modified vold.fstab in /system/etc to point to partition 1 for sdcard instead of 5. And now the hard part. I modified the CWM SD so it also points to partition 1 for sdcard so it can find updates. I also removed the /boot entry so a nandroid would not backup my sdcard as part a backup. The /boot was not backing up/restoring properly anyway.
This is highly customized and I don't think users should do this, but it works.
The down side is your boot files are mixed in with your sdcard files and are vulnerable to tampering by the user. But the Nook Tablet SD installs do this, which is where I got the idea. And on the positive side, Windows can now see sdcard when plugged in directly and stock can use the card as an external SD with no modifications.
One of the challenges for you and verygreen would be how to dynamically build the SD with this structure for varying SD sizes. I had to do it all manually and I don't think you would want users to do have to do that.
So this is just some ideas for future configurations.
Edit: One idea is if you could put /system and /data both on emmc, and create sdcard as p2, then you could have the boot files and sdcard files separate. And it makes it easy to create the SD dynamically. But you do not get the advantage of Windows seeing the partition or stock seeing sdcard without modification.
I do have my HD customized that way. I have my CWM card modified for stock with a big fat32 p2 to use for stock external SD and then modify the stock vold.fstab through symlinking. And I put the stock ramdisk on the SD boot partition like I described earlier. That way I never have to take the SD out. Stock and CWM are available in the boot menu.
.
Sent from my HD+ running CM10 on SD with XDA Premium
Wow! This is great!
[edit - some more thoughts]
Spent some more time playing with this - the performance is vastly, vastly improved over my sdcard. Virtually all lag is gone. The actual conversion process was an absolute snap, and everything is running perfectly. Really, really excellent work.
Now, to upgrade, I assume that I boot into recovery, install the system, then *on next boot* choose the sync to EMMC option? Is that what you suggest?
DebauchedSloth said:
Wow! This is great!
[edit - some more thoughts]
Spent some more time playing with this - the performance is vastly, vastly improved over my sdcard. Virtually all lag is gone. The actual conversion process was an absolute snap, and everything is running perfectly. Really, really excellent work.
Now, to upgrade, I assume that I boot into recovery, install the system, then *on next boot* choose the sync to EMMC option? Is that what you suggest?
Click to expand...
Click to collapse
Yes that is what you should do.
bokbokan said:
Yes that is what you should do.
Click to expand...
Click to collapse
Worked like a charm.
CyanoBoot is not useable
I have used leapinar's sdcards as well as yours for cm10 and cm10.1 but I have always had this problem where on boot, I can sort of see the screen for cyanoboot, but it is compressed and distorted at the top of tablet. I can not operate the cyanoboot menus at all and pushing n seems to do nothing.
I have copied the hybrid zip files to /boot but the tablet just skips through cyanoboot and boots cm10.1.
How do I get cyanoboot viewable and to function properly?
msprag13 said:
I have used leapinar's sdcards as well as yours for cm10 and cm10.1 but I have always had this problem where on boot, I can sort of see the screen for cyanoboot, but it is compressed and distorted at the top of tablet. I can not operate the cyanoboot menus at all and pushing n seems to do nothing.
I have copied the hybrid zip files to /boot but the tablet just skips through cyanoboot and boots cm10.1.
How do I get cyanoboot viewable and to function properly?
Click to expand...
Click to collapse
The way you describe the screen is normal with the flash of distorltion at the top. As soon as you see that flash press and hold the n key until the boot menu comes up. If it does not come up, you may have a defective n key.
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
The way you describe the screen is normal with the flash of distorltion at the top. As soon as you see that flash press and hold the n key until the boot menu comes up. If it does not come up, you may have a defective n key.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
I missed adding that in my original question. When the distortion pops up and I press n, the screen goes blank and then nothing ever happens, just a blank screen. I have tried this with 3 different sandisk 4gb class 4 cards and the behavior is the same. My n button seems to work fine under stock, CM, and in CWM; it only seems to be a problem when trying to access cyanoboot.
Do you still think it could be the n button, and if so would there be a way to use ADB to do the hybridization check?
If this is the button how do I get B&N to replace it? "well ya see it works fine until I try to hack your loader and install a third party ROM, can I have a new one?"
msprag13 said:
I missed adding that in my original question. When the distortion pops up and I press n, the screen goes blank and then nothing ever happens, just a blank screen. I have tried this with 3 different sandisk 4gb class 4 cards and the behavior is the same. My n button seems to work fine under stock, CM, and in CWM; it only seems to be a problem when trying to access cyanoboot.
Do you still think it could be the n button, and if so would there be a way to use ADB to do the hybridization check?
If this is the button how do I get B&N to replace it? "well ya see it works fine until I try to hack your loader and install a third party ROM, can I have a new one?"
Click to expand...
Click to collapse
You say this happens with my CWM for stock version too? The latest version? Some users were having that problem on an earlier version of my CWM. Bokbokan said earlier that the HD comes with two different screens and my earlier version was failing on one kind of screen. I revised the image and it fixed the problem.
Sent from my HD+ running CM10 on SD with XDA Premium
Re: [Nook HD] CM10/CM10.1 SD/EMMC Hybrid Installation
leapinlar said:
You say this happens with my CWM for stock version too? The latest version? Some users were having that problem on an earlier version of my CWM. Bokbokan said earlier that the HD comes with two different screens and my earlier version was failing on one kind of screen. I revised the image and it fixed the problem.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
I tried again with different cards using the hummingbird-v3.img from bokokan's HD CM10/10.1 thread. I also used the 6025 for emmc stock rev2 4gb img from your root/gapps thread on a freshly formatted sdcard and I always get the distorted screen.
There is nothing actually being written to the nook correct? Cyanoboot is the u-boot.bin file on the sdcard? Since I have had this problem all along is there a bad file from an early attempt I am not aware of that is on the internal? When I remove any cards the nook boots normally although I used your OTA plus gapps on the stock.
Sent from my Barnes & Noble Nook HD using xda premium
Re: [Nook HD] CM10/CM10.1 SD/EMMC Hybrid Installation
msprag13 said:
I tried again with different cards using the hummingbird-v3.img from bokokan's HD CM10/10.1 thread. I also used the 6025 for emmc stock rev2 4gb img from your root/gapps thread on a freshly formatted sdcard and I always get the distorted screen.
There is nothing actually being written to the nook correct? Cyanoboot is the u-boot.bin file on the sdcard? Since I have had this problem all along is there a bad file from an early attempt I am not aware of that is on the internal? When I remove any cards the nook boots normally although I used your OTA plus gapps on the stock.
Sent from my Barnes & Noble Nook HD using xda premium
Click to expand...
Click to collapse
As I said earlier, the jagged distortion at the top of the screen is normal for everyone. And nothing important is being written to internal memory. All files for booting are on the card. I am thinking you may have the second screen manufacturer that bokbokan has not been able to test. Can you run an experiment?
Boot to CM10 and open the terminal emulator app. Type su enter. The prompt should change to a # after you grant superuser access. Then type dmesg. This should be done right after booting so the data is fresh. The screen should scroll a lot of data across the screen. Scroll to the beginning of that data and look for a line that starts "kernel command line:". In that line there should be a statement that says "display.vendor=". Tell us what it says after the equal sign.
I know just enough about this to guess that line is what we want to look at. Bokbokan will have to tell us for sure.
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
Boot to CM10 and open the terminal emulator app. Type su enter. The prompt should change to a # after you grant superuser access. Then type dmesg. This should be done right after booting so the data is fresh. The screen should scroll a lot of data across the screen. Scroll to the beginning of that data and look for a line that starts "kernel command line:". In that line there should be a statement that says "display.vendor=". Tell us what it says after the equal sign.
I know just enough about this to guess that line is what we want to look at. Bokbokan will have to tell us for sure.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
Kernel command line: vmalloc=768M init=/init rootwait omap_wdt.timer_margin=20 androidboot.hardware=hummingbird display.vendor=LGD boot.fb=b2600000
Re: [Nook HD] CM10/CM10.1 SD/EMMC Hybrid Installation
msprag13 said:
Kernel command line: vmalloc=768M init=/init rootwait omap_wdt.timer_margin=20 androidboot.hardware=hummingbird display.vendor=LGD boot.fb=b2600000
Click to expand...
Click to collapse
That is the second device he could not test. That is probably the problem. When he catches up with these posts maybe he can do something. His and my device say display.vendor=AUO.
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
As I said earlier, the jagged distortion at the top of the screen is normal for everyone. And nothing important is being written to internal memory. All files for booting are on the card. I am thinking you may have the second screen manufacturer that bokbokan has not been able to test. Can you run an experiment?
Boot to CM10 and open the terminal emulator app. Type su enter. The prompt should change to a # after you grant superuser access. Then type dmesg. This should be done right after booting so the data is fresh. The screen should scroll a lot of data across the screen. Scroll to the beginning of that data and look for a line that starts "kernel command line:". In that line there should be a statement that says "display.vendor=". Tell us what it says after the equal sign.
I know just enough about this to guess that line is what we want to look at. Bokbokan will have to tell us for sure.
Sent from my HD+ running CM10 on SD with XDA Premium
Click to expand...
Click to collapse
You beaten me on this. Thinking to post the same thing. :laugh:
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