Related
Ok....I've used partition manager to delete my partition on my sd. I tried to make a new fat32 but it failed. So now when I go into usb mode I can't view my files. Understandable BUT I can still view and acess my files using astro. Is there anyway to delete my partion (format) and create a new fat32 partition through the terminal emulator or adb. PLEASE HELP GUYS my sdcard reader just messed up the other day so I'm screwed.
barger01 said:
Ok....I've used partition manager to delete my partition on my sd. I tried to make a new fat32 but it failed. So now when I go into usb mode I can't view my files. Understandable BUT I can still view and acess my files using astro. Is there anyway to delete my partion (format) and create a new fat32 partition through the terminal emulator or adb. PLEASE HELP GUYS my sdcard reader just messed up the other day so I'm screwed.
Click to expand...
Click to collapse
try the post of the script for partitioning yoru sd card from terminal.. or you need a sd card reader for using paragon partition manager, for best results.
Nitro212 said:
try the post of the script for partitioning yoru sd card from terminal.. or you need a sd card reader for using paragon partition manager, for best results.
Click to expand...
Click to collapse
I dont have a script. I need a command that i can run from either Terminal or adb. Im pretty sure there is a command out there that can repartion a sdcard through terminal or adb.
barger01 said:
I dont have a script. I need a command that i can run from either Terminal or adb. Im pretty sure there is a command out there that can repartion a sdcard through terminal or adb.
Click to expand...
Click to collapse
Try this. It is a program that worked great for me when Partition Magic did not. It is called Copy Commander. Burn to disc and boot. You can install from windows but it requires a key so it's limited. But it'll serve it's purpose. It works on XP and Vista.
in this case you might as well burn a ubuntu disk and partition under linux, which works 100% using the phone itself.
A point to note: most new sd cards are formated as a raw fat, i.e. without a partition table or boot sector. If this is the case, windows cannot create the partition table for you and you cannot create partitions using the build-in disk manager. Linux on the other hand is perfectly okay with this and will happily partition it for you.
Binary100100 said:
Try this. It is a program that worked great for me when Partition Magic did not. It is called Copy Commander. Burn to disc and boot. You can install from windows but it requires a key so it's limited. But it'll serve it's purpose. It works on XP and Vista.
Click to expand...
Click to collapse
I burned it and let it boot up but it never recongnized my sd. I mounted it through my phone and clicked refresh a hundred times but nothing=-(
barger01 said:
I burned it and let it boot up but it never recongnized my sd. I mounted it through my phone and clicked refresh a hundred times but nothing=-(
Click to expand...
Click to collapse
Make sure you have usb devices enabled in your bios.
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.
I haven't read too much on the install process, but if I understand correctly it replaced recovery by flashing a kernel to it. Is there any particular reason that we can't use something akin to RecoveryInstaller to install an Ubuntu kernel that will read off of our Micro SD card partitions since it still installs an image to recovery?
4512jth said:
I haven't read too much on the install process, but if I understand correctly it replaced recovery by flashing a kernel to it. Is there any particular reason that we can't use something akin to RecoveryInstaller to install an Ubuntu kernel that will read off of our Micro SD card partitions since it still installs an image to recovery?
Click to expand...
Click to collapse
It doesnt read off the micro sd it reads off internel sd
B80 B90's dont have nvflash nvflash is used to re partition the internal memory to make enough room for the ubuntu install aswell as other things
On a b80-b90 you can do chroot ubuntu through a micro sd and vnc viewer but its slow same with replacing the recovery and reading it from micro sd the method you are talking about has been done through flashing .zips to acces ubuntu or android but it was slow and not as safe.
Sent from my Transformer TF101 using xda premium
Danzano said:
It doesnt read off the micro sd it reads off internel sd
B80 B90's dont have nvflash nvflash is used to re partition the internal memory to make enough room for the ubuntu install aswell as other things
Click to expand...
Click to collapse
Why not make a kernel that mounts the micro sd card as the system then and flash that kernel to recovery? Surely it's possible.
it's of no great importance,through explore we can make the home for the SD.
4512jth said:
Why not make a kernel that mounts the micro sd card as the system then and flash that kernel to recovery? Surely it's possible.
Click to expand...
Click to collapse
Yes but it will be slow
Sent from my Transformer TF101 using xda premium
wfeimobile said:
it's of no great importance,through explore we can make the home for the SD.
Click to expand...
Click to collapse
that's the easiest part, just edit the fstab and will do it, but just as they said before ju can't install ubuntu native if you can't use nvflash.
Danzano said:
Yes but it will be slow
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
not only that, even if that it's possible you will lose the ability to recover your tf in case of any problem
shaola said:
not only that, even if that it's possible you will lose the ability to recover your tf in case of any problem
Click to expand...
Click to collapse
Why not flash the Ubuntu kernel over the Android kernel then if you only want to run Ubuntu on your transformer? You get to keep recovery and the Android system is still there in the event you want to flash an Android kernel to return to the stock system.
Hello guys, I've downloaded Win8 iso, it has boot.img and other files. So i was thinking is there a bootloader for android ? I mean you can choose where to boot from ? External or Internal storage ? I hope you understand. if it's possible I wanna ask one more question. What is the Android's harddrive format ? FAT32 or NTFS ? is there any way to completely format it ? (I mean delete whole things in the device. OS, Framework, Identifiers, Boot Apps etc.). if it's possible to format whole device, I know it uses Linux Kernel right ? so Can't we create a Qemu Image ? then install OS to there ? Thanks for reply.
HI there! Just wanna share about things I've done some time ago..
Background... :fingers-crossed:
I'm interested with ROM development & testing, but.. Ace 2 is my only primary phone which I really need for school things, poking friends *woah* and.. etc. Actually, I can make a CWM backup, flash the ROM and restore the backup after testing. But... seriously! It takes quite lot of time and... yeah.. since I'm testing ROM, I'll keep flashing & reflashing my phone and I get a little worried about its internal memory if I do it too often. So, I decided to make something that let me boot new ROM which I flash on the SD card & switch back to the previous ROM with just a simple reboot.. Yeay!
How it works?
I accomplished my goal by using modified initramfs which run after the kernel initialization and before any of Android system get loaded. It will mount 2nd partition of the SD card. If it find a file named enable_sdboot inside, it will decompress SD ROM's ramdisk.cpio which is stored in that partition, then boot the SD ROM. It will also delete enable_sdboot file immediately after checking, so internal ROM will get booted in next reboot.
Important notes:
SD ROM's ramdisk.cpio must contains modified fstab & some of .rc files, so it won't touch the internal ROM.
Kernel modules are placed on initramfs (/lib/modules), so it'll be easier to change ROMs or the kernel itself.
Limitations: because initramfs is compiled with the kernel, so internal & SD ROM will boot using same kernel.
Preparations
Prepare the Kernel
If you want to use stock ROM (codina) as ur internal ROM & CWM as ur recovery, you can use my precompiled kernel: codina-ace2nutzer-sdboot-stock-unsigned.zip which you can flash via CWM. If you use other internal ROM, you have to compile the kernel by yourself. If you're building Android ROMs, you can add my repo: nieltg/codina-initramfs-sdboot to your local manifest and read this guide. You can also take a look at this repo: nieltg/android_device_samsung_codina as an example.
If you build an out-of-tree kernel, you can follow these steps:
Create a folder named codinaramfs_dir in your kernel source.
Extract my initramfs intermediate: codina-sdboot-intermediates.zip to folder you've just created.
Replace boot.cpio with ur internal ROM ramdisk, so you can boot into it. You can also replace recovery.cpio with recovery system you would like to use.
Configure ur kernel & execute scripts/config --file .config --set-str CONFIG_INITRAMFS_SOURCE codinaramfs_dir/initramfs.list.
NOTE: .config is generated in output directory after configuring. If you change the output directory, you should modify the command before executing.
Compile and execute make INSTALL_MOD_PATH=codinaramfs_dir/modules modules_install to put modules in codinaramfs_dir/modules.
Modify codinaramfs_dir/initramfs.list to include all kernel modules in codinaramfs_dir/modules.
NOTE: I've specified the details in codinaramfs_dir/initramfs.list itself.
Then, recompile ur kernel.
Prepare an SD ROM & ur Device
You have to repartition ur SD card to store ur SD ROM. You also have to modify any ROM you want to install into ur SD card. ROM in SD card should not touch internal ROM. It should work independently. So, there are some modifications you must apply. There are things which you must ensure:
Any flashable zip you apply for the SD ROM extracts to SD partitions instead of internal.
Kernel is not going to be replaced after flashing any flashable zip.
SD ROM mounts appropriate SD partitions instead of internal partitions.
SD & internal ROM look for kernel modules in /lib/modules.
You can read this guide to prepare an SD ROM & ur device, to be exact, ur SD card.
----------
Well.. this is not good enough. You have to understand Linux, shell commands, compilation process, etc to apply this idea correctly. But of course if you're interested, you can help me improve this. Sorry for my English, I'm still studying. And like usual, I'm not responsible if you brick your phone, void your warranty, or any other pain or suffering you may feel as result of applying my idea. You do it all at your own risk!
Thanks to: @ace2nutzer for ur kernel, @Rox & @jereksel for the CWM I took from ur repo, @ishtiaque9 for ur support, everyone who interested with my idea & everyone..
So, anyone interested with my idea?
Seems great to run cm11 and cm12 at the same time
Very grateful idea !! :good:
Good that i've a sd 32gb Class 10 card.. so i can test finally CM12 from sdcard ... very nice job ! :good:
I'm glad to know my idea is being helpful!
@ace2nutzer woow! that's really big!
Actually, I'm using 2 Gb SD card which speed is 2x slower than the internal memory.. (tested using dd)
Quite slow.. but at least, it works.. but now i'm confused.. Is it slow because of the SD or because of my build? hahahaha
nieltg said:
I'm glad to know my idea is being helpful!
@ace2nutzer woow! that's really big!
Actually, I'm using 2 Gb SD card which speed is 2x slower than the internal memory.. (tested using dd)
Quite slow.. but at least, it works.. but now i'm confused.. Is it slow because of the SD or because of my build? hahahaha
Click to expand...
Click to collapse
Depends on class of sdcard.. Mine is class 10 = 10mb/s write speed. Read is as usual faster.. For me: 15 - 20 mb/s.
So u've probably only class 4 or 6.
The emmc in the Phone is class 10.
But of course a kernel can make it a bit faster or slower.. Depends on used config.
With my latest build + read_ahead_kb @ 512kb (writed on ramdisk on device_tunables) i've on ext. Sd card + emmc approxx. 12mb/s write speed
BTW: our Phone supports also 64gb cards.. And maybe even more...
This is a great idea ! I also need a dual boot stock / carbon (stock ROM includes eap sim and some other things I need)
What changes have to be made to use it on codinap (NFC) ?
Sent from my GT-I8160P using XDA Free mobile app
Really good idea, i think need to make an app, which can switch roms.
Maybe this sources will be usefull.
ace2nutzer said:
Depends on class of sdcard.. Mine is class 10 = 10mb/s write speed. Read is as usual faster.. For me: 15 - 20 mb/s.
So u've probably only class 4 or 6.
The emmc in the Phone is class 10.
But of course a kernel can make it a bit faster or slower.. Depends on used config.
With my latest build + read_ahead_kb @ 512kb (writed on ramdisk on device_tunables) i've on ext. Sd card + emmc approxx. 12mb/s write speed
BTW: our Phone supports also 64gb cards.. And maybe even more...
Click to expand...
Click to collapse
Hey.. I found something weird! I'm testing my storage with dd if=/dev/full of=tmp.file bs=1024576 count=10 in my cm-12 (sdboot) & I get:
7.5 Mb/s in /storage/sdcard1 (SD card)
27.55 Mb/s in mmcblk1p3 (SD card data partition)
85.47 Mb/s in mmcblk0p5 (internal data partition)
Hmm.. maybe the kernel caching mechanism that make it really fast?
Btw: I'm using ur kernel (commit d67aa9f) with audit enabled & sdboot modification
Mavireck said:
This is a great idea ! I also need a dual boot stock / carbon (stock ROM includes eap sim and some other things I need)
What changes have to be made to use it on codinap (NFC) ?
Click to expand...
Click to collapse
You should compile a kernel by yourself..
If you develop ROMs, you can include my repo in ur local manifests, modify boot.img (you can extract files from ur stock ROM) & compile to get an sdboot kernel.
If you're building out-of-tree kernel, I'm going to write a guide for it in the first post..
Kirya12347 said:
Really good idea, i think need to make an app, which can switch roms.
Maybe this sources will be usefull.
Click to expand...
Click to collapse
Hmm.. actually, I'm not really sure about that..
If you use this sdboot idea, all you have to do is write a file named enable_sdboot in 2nd partition of ur SD card to switch ROM.
For now, I'm using Terminal Emulator for that.. but it'll be nice to have a simple app which can do that in a single tap..
@nieltg
Why modified kernel not in archive. I download it without any expansion.
P.S. Sorry for bad eng.
Kirya12347 said:
@nieltg
Why modified kernel not in archive. I download it without any expansion.
P.S. Sorry for bad eng.
Click to expand...
Click to collapse
Actually, I just need to modify its initramfs, but initramfs is compiled with the kernel in codina.
So, I have to recompile the kernel to modify the initramfs.. Hmm.. what archive? Could you tell me more specific, please?
nieltg said:
Actually, I just need to modify its initramfs, but initramfs is compiled with the kernel in codina.
So, I have to recompile the kernel to modify the initramfs.. Hmm.. what archive? Could you tell me more specific, please?
Click to expand...
Click to collapse
I mean kernel isn't in flashable zip. It look , for exapmple, like init.d script, without any expansion
Kirya12347 said:
I mean kernel isn't in flashable zip. It look , for exapmple, like init.d script, without any expansion
Click to expand...
Click to collapse
Ohh I see! Actually, that is a raw kernel which you can install by dd-ing to /dev/block/mmcblk0p15..
I haven't thought about flashable zip before, since my idea isn't mature enough for me, I think.. Anyway, thank you for ur idea!
nieltg said:
Hey.. I found something weird! I'm testing my storage with dd if=/dev/full of=tmp.file bs=1024576 count=10 in my cm-12 (sdboot) & I get:
7.5 Mb/s in /storage/sdcard1 (SD card)
27.55 Mb/s in mmcblk1p3 (SD card data partition)
85.47 Mb/s in mmcblk0p5 (internal data partition)
Hmm.. maybe the kernel caching mechanism that make it really fast?
Btw: I'm using ur kernel (commit d67aa9f) with audit enabled & sdboot modification
Click to expand...
Click to collapse
This is a bit weird.. but maybe only achieved by dd ... But i mean with 12mb/s write speed when u're using the Phone .... Tested with:
https://play.google.com/store/apps/details?id=com.a1dev.sdbench&hl=en
As u can see in the Screeshots: only 7.57mb/s .. write speed even on internal SD .. .. if i remove all my kernel tweaks then it's the same ..
btw: u should update your sources from my repo .. that commit is of course great .. but actually since that commit i did some optimizations.. for more speed .. .. approx. + 400 Points on Antutu
ace2nutzer said:
This is a bit weird.. but maybe only achieved by dd ... But i mean with 12mb/s write speed when u're using the Phone .... Tested with:
https://play.google.com/store/apps/details?id=com.a1dev.sdbench&hl=en
As u can see in the Screeshots: only 7.57mb/s .. write speed even on internal SD .. .. if i remove all my kernel tweaks then it's the same ..
btw: u should update your sources from my repo .. that commit is of course great .. but actually since that commit i did some optimizations.. for more speed .. .. approx. + 400 Points on Antutu
Click to expand...
Click to collapse
Thank you! I've tested my SD card with that app in stock ROM and the result of internal & external SD are similar.. So, now I wonder, is my SD class 10? Hmm...
Btw, thank you for ur info! I'm going to recompile soon after finishing my final test.. :crying:
nieltg said:
Thank you! I've tested my SD card with that app in stock ROM and the result of internal & external SD are similar.. So, now I wonder, is my SD class 10? Hmm...
Btw, thank you for ur info! I'm going to recompile soon after finishing my final test.. :crying:
Click to expand...
Click to collapse
I hope you'll make flashable zip also
nieltg said:
Thank you! I've tested my SD card with that app in stock ROM and the result of internal & external SD are similar.. So, now I wonder, is my SD class 10? Hmm...
Btw, thank you for ur info! I'm going to recompile soon after finishing my final test.. :crying:
Click to expand...
Click to collapse
As i said, with a bad configured kernel u can reach only 7mb/s write speed even with class 10.
With read_aehead_kb 512 + good kernel u should have at least 10mb/s write speed with class 10.
personally i've 12mb/s write speed. on internal and ext-sd
Some ideas regarding the subj:
1. mount an images instead of repartition external sdcard
2. (1) can allow to use multiple ROMs.
1) it was just test, but it's quite possible. Right now I use an image file instead of /dev/block/mmcblk0p4 !
Before the all we need to create an image:
Code:
mkdir /storage/sdcard1/ROM
touch /storage/sdcard1/ROM/cache.bin
dd if=/dev/zero of=/storage/sdcard1/ROM/cache.bin bs=1024768 count=10
mke2fs -t ext4 -m 0 /storage/sdcard1/ROM/cache.bin
although, dd from original /dev/block/mmcblk0p4 is also possible.
2) secondly, init.samsungcodina.rc should be edited as follows
Code:
(init.samsungcodina.rc listing)
...
on property:sys.boot_completed=1
write /sys/class/misc/backlightnotification/enabled 0
write /sys/kernel/mm/uksm/run 1
exec /system/xbin/mknod /dev/block/loop250 b 7 250
exec /system/xbin/sleep 5
exec /system/xbin/losetup /dev/block/loop250 /storage/sdcard1/ROM/cache.bin
exec /system/xbin/mount -t ext4 /dev/block/loop250 /cache
3) line with /cache should be commented in fstab
4) now you can check it:
Code:
mount
and get output like:
...
/dev/block/loop250 /cache ext4 rw,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
Click to expand...
Click to collapse
Maybe later I'll continue to work on it.
Any chance that this would be a feature in your kernel @ChronoMonochrome @ace2nutzer?
Sent from my GT-I8160 using Tapatalk
shaqman89 said:
Any chance that this would be a feature in your kernel @ChronoMonochrome @ace2nutzer?
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Actually, repartition extsdcard is too painful for me, I simply don't have enough space on hard drive(not that it's small, but it's always nearly full ) to backup those ~30 Gb data on extsdcard :/ I can add multirom support only if I'll finish my idea, that I posted here.
Kirya12347 said:
I hope you'll make flashable zip also
Click to expand...
Click to collapse
Sure.. I'm going to create that after my final exam...
ace2nutzer said:
As i said, with a bad configured kernel u can reach only 7mb/s write speed even with class 10.
With read_aehead_kb 512 + good kernel u should have at least 10mb/s write speed with class 10.
personally i've 12mb/s write speed. on internal and ext-sd
Click to expand...
Click to collapse
Ohh.. I see.. really sorry for my misunderstanding!
Okay, the fact is I've compiled ur updated kernel source (commit: e59fb17) before my final exam.. hahaha.. n I get better read speed: ~25 Mb/s on internal & ~17 Mb/s on external.. thx!
dunno why.. I still don't get much improvement about the write speed.. because they're nearly full maybe? or because I'm testing on stock ROM.. hmm...
ChronoMonochrome said:
Some ideas regarding the subj:
1. mount an images instead of repartition external sdcard
2. (1) can allow to use multiple ROMs.
Click to expand...
Click to collapse
Thank you very much for ur brilliant idea! If I read this post before, I wouldn't just return my friend's card reader this morning to clean up partitions I've made in my SD.. hahaha
Okay.. just wanna write down my idea that popped from my mind after reading ur post..
How about place all ROMs in directories, like this:
/storage/extSdCard/ROMs
/storage/extSdCard/ROMs/slot1 contains system, data n ramdisk.cpio for ROM 1
/storage/extSdCard/ROMs/slot2 contains system, data n ramdisk.cpio for ROM 2
/storage/extSdCard/ROMs/slotN...
and create symlink to the appropriate slot directory to boot SD ROM, for example: to boot ROM 1, create symlink /storage/extSdCard/.sdboot_slot to ROMs/slot1, etc? Much better than typing this long command: cd /tmp; mkdir l; mount -t ext4 /dev/block/mmcblk1p2 l; cd l; echo > enable_sdboot; cd ..; umount l; each time when I want to boot the SD ROM..
Okay.. time to study again.. I'm going to think about this idea after my exam..