Hey, I know how to get ext2 and "upgrade_fs" via console to get ext3 ... but How do you make a ext4 partition? Thanks.
parted will not create ext3/ext4 partitions...see beginning of post
to upgrade, enter:
upgrade_fs
you now have journaling(aka ext3)! if ext3 is all you want, skip next two commands.
you want ext4?
enter:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=534714
hope this helps
You need the newest Amon Ra recovery of course, it has the option to upgrade to 4 after upgrading to 3:
http://forum.xda-developers.com/showthread.php?t=566669
Cyan 1.4 is pretty old now
Ace42 said:
You need the newest Amon Ra recovery of course, it has the option to upgrade to 4 after upgrading to 3:
http://forum.xda-developers.com/showthread.php?t=566669
Cyan 1.4 is pretty old now
Click to expand...
Click to collapse
thanks bro, I feel dumb since I have Amon's old recovery never thought to look if he had an upgraded version :/ ... anyway how's the darkstar theme port to eclair 2.1 coming?
You stick it into your computer and run the command "mkfs.ext4 /dev/whatever".
Related
Hi, i try to flash Cyan's new rom v4.0.1, but i keep getting this error message in my recover console:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After trying unsuccesfully to flash the rom, my sdcard can no longer be seen in my phone and it became write-protected, unable to move files into the sdcard. Appreciate your help....
Edit: Yeah solved this menacing but simple problem which i found out is my sd card fault. Since i couldn't access sdparted in the recovery console, i had to use Ubuntu to partition my sd card again. Sighs... now i have to replace everything back into phone. Thanks anyways for those who gave advice.
is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.
you dont flash a rom in consol
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?
david1171 said:
is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.
Click to expand...
Click to collapse
yes my sdcard is fat32(1st partition) and my 2nd partition is ext3 whilst the last is a linux-swap partition...
oshizzle1991 said:
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?
Click to expand...
Click to collapse
Using Cyan's Recover 1.4. How do you flash from the console? commands?
Scholesville said:
Using Cyan's Recover 1.4. How do you flash from the console? commands?
Click to expand...
Click to collapse
Have you tried using the CM Updater?
Scholesville said:
yes my sdcard is fat32 and my 1st partition is ext3.
Click to expand...
Click to collapse
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again (alt w)
: run a filesystem check from the menu. If it tells you to run it manually,
drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
: flash
Enjoy!!
Hope this helps!!!
yourtravelboy said:
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
Hope this helps!!!
Click to expand...
Click to collapse
The problem is i can't even mount mount my 2nd partition, and everytime i write the command > # mount -o rw /dev/block/mmcblk0p2 /system/sd < , it justs says no such file or directory found.
I also can't go into parted in the recovery console so the now the problem is i can't even reformat my card. I'm going to try Ubuntu and reformat my card and partition it again. Sighs...
please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..
q2box said:
please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..
Click to expand...
Click to collapse
Yes, since i was not able to access parted in the recovery console, my only choice was to use Ubuntu: Partition Editor. When i diagnose my sdcard, i manage to format only my ext3 partition so my fat32 remain unchanged. You need to go download Ubuntu OS, then try to install or LiveCD the Ubuntu. There is a thread under android development which will guide you on how to do this...
Ok so i have no clue what to do to get this fixed and what i don't get is i see all these ppl with there G1s and the versions being able to boot without problems. I have done a full format of the SD card. I partition it in parted
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
print (to make sure all went ok)
quit
upgrade_fs
reboot recovery
wipe
repair
apply update.zip
I can do this i dont know how many times and I still get a bootloop. If I flash any build before the ones listed in the title it boots fine. All of Drizzys roms boot fine. I would stay on Drizzys Elite v0.5 if it didn't have the text problems but i need my texting so I hope the new builds fix that. Any ideas how to fix this.
do u have the right spl?
Both my radio and SPL are from here
http://code.google.com/p/sapphire-port-dream/
did you make sure to see that the radio,spl were actually applied, check the versions
it looks like they are. I held the cam and power button and this is what it says
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA100000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
via fastboot and command prompt =
fastboot erase system -w
fastboot erase boot
then use console in recovery mode to format EXT3 partition on SD card
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
In recovery mode "repair ext filesystems"
and then try reflashing rom again!
or just use this command from the console of recovery
mke2fs -j /dev/block/mmcblk0p2
gtrplr71 said:
or just use this command from the console of recovery
mke2fs -j /dev/block/mmcblk0p2
Click to expand...
Click to collapse
lol seems easier that way...
Prod1702 said:
Ok so i have no clue what to do to get this fixed and what i don't get is i see all these ppl with there G1s and the versions being able to boot without problems. I have done a full format of the SD card. I partition it in parted
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
print (to make sure all went ok)
quit
upgrade_fs
reboot recovery
wipe
repair
apply update.zip
I can do this i dont know how many times and I still get a bootloop. If I flash any build before the ones listed in the title it boots fine. All of Drizzys roms boot fine. I would stay on Drizzys Elite v0.5 if it didn't have the text problems but i need my texting so I hope the new builds fix that. Any ideas how to fix this.
Click to expand...
Click to collapse
I can't actually help you with this, but I just wanted to point out that your linux-swap partition should be around ~96MB for the new Hero ROMs to run smoothly.
thanks for the replys guys but that didnt work milesman I still get a bootloop on them. I did find out that i can get JACs 1.6r2b to work but not r2a. So there has to be something that was moved over that makes it so i am having problems booting.
anyone else have any ideas. i am starting to think that there might be some kinda of problem with the build but am not sure what it could be.
wipe your ext3. hero roms need a clear ext3 in order to boot properly.
heres the commands
go to console
hit enter
type this with no quotes "mount -o rw /dev/block/mmcblk0(thats a zero, dont type this) /system/sd hit enter
then type " rm -rf /system/sd/* (yes you need that) hit enter
"reboot recovery"
and that will take you to the recovery screen then apply the update and repair the extensions and your good to go
Oshizzle1991 hmm i dont know how many times i have done this, but like i said. I have formated the whole SD card more then 10 times and repartitioned it so that pretty much wipes my ext3 since the SD car is being formated. Still a no go. I am pretty much giving up right now unless there is something i havent done that wasnt been said in the other posts.
lol might be a dumb question but did you wipe the phone too? you know, alt w? lol. some people forget to do that because they only remember the ext2/3 partitions.
downgrade to RC29/RC7 and start the process over again if you reallllllly want it. That's basically guaranteed to get it to work...
oshizzle1991 yea i have wiped also the commands that milesman has said to use with adb in fastboot erases all data from the phone its self. so that is pretty much wiping everything. I don't really feel like I should have to start the root all over again going back to RC29 since all hero roms work but these newer ones. I am trying JACs 1.8 right now to see if that works but if that doesn't work I think i am going to give up on hero and stick with CM roms.
edit: JACs 1.8 loads fine for me so i don't know what he changed from 1.6r2a and 1.7r2 to 1.8 but all is fine now thanks for all the reapplies. Mod you can close this thread.
ME TOO!!!!!!!
i dont know why, but i had (kind of) the same problem too. all my rooting life, i used JAC's hero roms, then when i tried to use drizzy's or someone else's, it always goes into a bootloop.
Yea i spent hours and hours trying to get them to work. not sure what it is but it seems to be fine now with the 1.8. I am sure it was my erorr somewhere in the line. I have flash roms on my phone over 50 times now and i know how to do all this as if my life depended on it.
How do i go from JACxHEROv1.7r2 back 2 1.5 cupcake on the G1?
wrong forum. Q&A will get you a lot less flaming.
grandomegabosses said:
wrong forum. Q&A will get you a lot less flaming.
Click to expand...
Click to collapse
And will stop me from going insane.
cellington77 said:
How do i go from JACxHEROv1.7r2 back 2 1.5 cupcake on the G1?
Click to expand...
Click to collapse
Just Wipe clean your EXT partition ,
*mount -o rw /dev/block/mmcblk0p2 /system/sd (enter)
*rm -rf /system/sd/* (enter)
*reboot recovery
and install any 1.5 cupcake rom you want....
wipe ext3 from console in recovery(mount system/sd) (rm -rf /system/sd/*)
then wipe (alt+w)
then flash
hey guys,
i have my phone all set up with ext3 but i haven't done anything with my phone in months and forgot how to do it. one time someone gave me a link (to another site) that had all the commands to wipe ext's and the commands to put ext's in place.
can anyone please put me in the right direction
Recovery image in my sig.
evilkorn said:
Recovery image in my sig.
Click to expand...
Click to collapse
i don't have the same recovery...i have the cyanogen one.
trexxcrap2 said:
hey guys,
i have my phone all set up with ext3 but i haven't done anything with my phone in months and forgot how to do it. one time someone gave me a link (to another site) that had all the commands to wipe ext's and the commands to put ext's in place.
can anyone please put me in the right direction
Click to expand...
Click to collapse
I'm sorry if I sound harsh or anything, but is it that hard to read sticky'ed posts? I mean, I know this is the question and answer section, but it's sticky'ed on here too! http://forum.xda-developers.com/showthread.php?t=535232
xAbstract said:
I'm sorry if I sound harsh or anything, but is it that hard to read sticky'ed posts? I mean, I know this is the question and answer section, but it's sticky'ed on here too! http://forum.xda-developers.com/showthread.php?t=535232
Click to expand...
Click to collapse
that link does not have the commands.
what i'm looking for is like this -
mkpartfs primary fat32 0 7437
mkpartfs primary ext2 7437 7937
mkpartfs primary linux-swap 7937 7969
but more detailed.
trexxcrap2 said:
what i'm looking for is like this -
mkpartfs primary fat32 0 7437
mkpartfs primary ext2 7437 7937
mkpartfs primary linux-swap 7937 7969
but more detailed.
Click to expand...
Click to collapse
why not just switch to amon ra's 1.5.2 recovery
Here's a good guide for creating ext2/ext3/ext4 patitions through console or adb on your phone
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
The commands to clean out your partition is as follows from console/adb in recovery
Code:
mount /system/sd (enter)
cd /system/sd (enter)
rm -R * (enter)
umount /system/sd (enter)
hiddengopher said:
why not just switch to amon ra's 1.5.2 recovery
Click to expand...
Click to collapse
Like I told him to do in my first post.
I have created EXT2 partition of 1024 GB, after that try to convert from recovery (Amon_RA) to EXT3 and got no errors.
On the nexus I see:
/dev/block/mmcblk0p2 on /sd-ext type ext2 (rw,noatime,nodiratime,barrier=1,data=
when try to convert using command shell - adb shell sdparted -ufs ext I got error that the partition is already EXT3
It's very possible that the partition is already EXT3, but the ROM you're using doesn't recognize it correctly.
What command did you use?
mount, im with MIUI rom but also had this with CM nightly
I use EXT2 and it works fine with MIUI or Darktremor Apps2sdext
britoso said:
I use EXT2 and it works fine with MIUI or Darktremor Apps2sdext
Click to expand...
Click to collapse
I know, everything works fine but my partition is EXT3 and recognized as EXT2 by the ROM
Try to take out the card and read by any Linux PC, check that the EXT3 is indeed valid.
If yes - disregard the mount message. Might be some Toolbox issues.
I've just checked my own report, and unsurprisingly, mount reports my EXT3 as EXT2. No ill effects, though. Using Apps2EXT for a long while now. And I'm on Enomther's, and just checked - Busybox 1.17 mount does the same (lack of) recognition.
Jack_R1 said:
Try to take out the card and read by any Linux PC, check that the EXT3 is indeed valid.
If yes - disregard the mount message. Might be some Toolbox issues.
I've just checked my own report, and unsurprisingly, mount reports my EXT3 as EXT2. No ill effects, though. Using Apps2EXT for a long while now. And I'm on Enomther's, and just checked - Busybox 1.17 mount does the same (lack of) recognition.
Click to expand...
Click to collapse
Will check this, thanks