Related
So last night I installed the newest JAC Hero build and it was forcing close on google maps and a few others. In the thread it said to format your ext2 partition so I used paragon and I thought I formated it but now It wont get past the HTC screen. I can go to recovery and fastboot but when i try to push any new update it just updates to the hero rom again. Also if I use ls to list the files it shows nothing in /sdcard but obviously it has stuff since it still will flash the hero rom fine. How can I make a new update override this one when I push it to the phone? I dont have a card reader so I have to use my phone.
You must have your FAT32 partition first, the big one,where you put your update.zip and then a ext2 or ext3 partition of ≈500mb.
have you respect this order ?
Yes, I have a 1gb card and my 600mb fat32 is first then a 400mb ext2.
When you are in adb your ext2 partition is /system/sd
More than likely you need to do this part from my post here: http://forum.xda-developers.com/showthread.php?t=517874
Delete existing apps on SD
Code:
adb shell rm -r /system/sd/app
adb shell rm -r /system/sd/app-private
imfloflo said:
≈500mb.
Click to expand...
Click to collapse
You have 500mb of bacon?!?!
When I try those commands it says no such directory or file for both.
EDIT: I just got it fixed with these commands from brandenk's thread:
adb shell mount /sdcard
adb shell rm /sdcard/update.zip
adb push *filename* /sdcard/update.zip
Charbo said:
When I try those commands it says no such directory or file for both.
Click to expand...
Click to collapse
if you are in recovery you first need to mount the ext partition:
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
phantasm714 said:
if you are in recovery you first need to mount the ext partition:
Code:
mount -o rw /dev/block/mmcblk0p2 /system/sd
Click to expand...
Click to collapse
Ok, so I thought it was fixed but it was stuck at the android screen. Im guessing because of my apps still on the card? When I tried your command it said no such file or directory also so I did mkdir /system/sd and tried again and it said invalid argument.
I got it into android now with the sd card out when i turned it on. So now is there any way i can completly wipe the sd card of all partitions from in windows so I can start over?
EDIT: Got it formatted from the sd card settings on the phone lol... now I can start over thanks for all your help.
I'm hoping someone could help me with loading JAC's 2.2 Hero rom
I've never had any problems updating, but I had never tried a hero rom before
When trying to update i get this error
"Copying files...
E:Can't chown/mod /system/xbin
(No such file or directory)
E:Failure at line 12:
set_perm_recursive 0 2000 0755 0
6755 SYSTEM:xbin
Installation aborted"
Anyone know whats causing this?
There's a handful of people also experiencing this issue
So today i rooted my phone installed JF1.41, i partitioned my sd card IN MY G1, since i have a mac and for some reason it wont partition the card right. Then i did the apps2sd deal... Then i wanted to use a theme, well that screwed everything, and it wouldnt get back to normal or even start again. So completely formatted my card, which now has NO PARTITIONS(i guess just 1), and i think the phone is trying to read files on a partition that dont exist now, and NOTHING is working. Anyone on here that can help? I am rather smart with this stuff, but really am going to need someone to help me. I need my phone tomorrow.
Thanks.
How did you reformat your sdcard? Did you check in parted to see that you in fact only had 1 partition again? I suggest you flash a new updated ROM like Cyanogen 4.2.5. That has apps2sd script built into the rom. It will do it automatically so you don't have to mess with all that.
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
illthinking said:
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
Click to expand...
Click to collapse
you're going to need a second partition for apps2sd to work. I suggest you do that first before you flash a rom, or else you will just have to end up reflashing.
Ok Downloaded Cyanogen4.2.5
This is the problem i keep having when i try to apply the update it say
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
So i think it has to do with the fact it wants to read /dev/block...etc from the partition of the sdcard that is now non existent
problem is i have a mac and cant properly fromat the 2nd partition (ext2)
unless you know of a way
the way i first did it was using some code i got off of here to have the phone do it itself... now that i cant start the phone i cant do the partition
what recovery do you have? I suggest you put this one on your phone.
http://forum.xda-developers.com/showthread.php?t=566669
It partitions your sd card for you.
Also for Cyanogen, you need to flash the htc OTA update one, then flash his update for those to work.
ok...
so i found some plugins for the new Snow Leopard OS for mac called MacFuse 2.0 along with its counterpart fuse-ext2 and i partitioned my card
you might want to upgrade to ext3. it's faster than ext2 and runs smoother
just tried to flash the recovery found here
http://forum.xda-developers.com/showthread.php?t=566669
with no avail and tried to start the phone(power+camera) and said no image
heres what it said for the recovery
/ # mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument
mount: mounting /system/modules/modules.cramfs on / system/modules failed: No such file or directory
mount: mounting /system/xbin.cramfs on /system/xbin failed: No such file or directory
I mean, what i want to know is how to build the file format back on my sd card so itll work, or build it so it will look on my actual phone... People put up the code to have it switch where it reads things from, there MUST be a way to switch it back manually as well
Use fastboot and write the recovery image
here's a link to fastboot
http://developer.htc.com/adp.html
then when thats running plug in your G1 and turn on holding Power and camera when the screen turns on you might have to press back to enable FB but once its enabled type in terminal
Code:
cd *where ever your recovery image is*
fastboot flash recovery *recoveryname*.img
reboot
can someone hook up a quick step by step on how to hook my phone up fastbooted? I have a mac and i can get the phone to say fastboot, but im lost after that... If you want to reroute me to a different thread, please verify that it REALLY has the info before posting it.
i have been trying to find the name of the device and im getting
/dev/tty.Bluetooth-Modem as the device name, but a Permission Denied thing... now i cant just go click something in the phone menus, since i cant get the phone to start, so is there a way to get permissions through the Terminal application?
that error you get when you type mount -a is normal continue as instructed:
flash_image recovery /(whatever your recovery image is called)
if you have adb you could try parted /dev/block/mmcblk0 and type print to see your parttitions.
so i can get it to say it flashes the recovery, but still not starting
so when i try to do any updates it says SDCARD wont mount
any input?
Looks like im going to go for a broken record, until SOMEONE can help me figure my phone out... I need to get it running, and i know someone can figure it out
When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Mdawg112 said:
When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Click to expand...
Click to collapse
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
smw6180 said:
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
Click to expand...
Click to collapse
Ha, I feel stupid now.
Mdawg112 said:
Ha, I feel stupid now.
Click to expand...
Click to collapse
Happens to everyone at times. Don't sweat it
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
jubi23 said:
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
Click to expand...
Click to collapse
Good question. Unfortunately I have no idea. Never seen it fail. theoretically there's a command line you can run in adb shell to mount the FS read/write, but I can't remember it off the top of my head.
Something like mount -o rw /dev/m3blk (as I said I can't remember the exact filesystem name). I'd do a search for 'mount -o' on the forums. It's been posted more than once and I'm too lazy to find it for you
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Yeah, I'm having the same problem as you sometimes. Other times it works. It's very strange! It annoys me. Anyone have any idea on a fix?
jubi23 said:
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Click to expand...
Click to collapse
Yeah that's the one, thanks.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Sounds like you've checked anything else I would have thought of...wish I could help.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Click to expand...
Click to collapse
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
jubi23 said:
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
Click to expand...
Click to collapse
That could be it. ext4 doesn't play nicely with ext3 based stuff. It's 'semi' backward compatible (meaning you can mount ext4 as ext3) but it seems to have some serious inconsistencies that way. I'd recommend a re-partition and then upgrade ext3->ext4 AFTER you install the new ROM.
Heh. I had all KINDS of problems restoring an ext3 based nandroid after upgrading to ext4. Had to repartition and then restore the nandroid to get it to work.
well, loaded recovery, re-partitioned my sdcard, upgraded to ext3 and left it there, still nothing
the sd card wouldnt have any bearing on the ability to adb remount.
the /system partition is stored on the phone itself, so the mount -o ..yadda yadda
remounts the /system partition in this case /dev/block/mtdblock3.
the only reason a sd card would come to play is if youre runnign a2sd, in which case it makes symlinks (shortcuts) to the sdcard, if the sdcard is formatted improperly then a2sd will either cause a bootloop, or crash and then youre phone should boot normally but you wont have access to your ext4 partition (the partition with your apps).
im not sure how to fix a problem with adb remount, perhaps try a new version of the SDK or just a clean one.
good luck
I'm wondering if there is something wrong with my mounting
When i'm in the shell
if i cd /sdcard
then do a ls
nothing is returned
I've also directly copied the recovery image from my computer to the sdcard, and attempted to run the flash_image command and it says no such file or directory
I do have usb debugging enabled and am selected to mount the sdcard, is there some other step or something i'm missing?
nenn, i had actually just a little bit ago downloaded the latest sdk on a completely different machine and still same results
Alrite, so I was able to copy the image recovery from
explorer and flash from.terminal on my phone
Although I'd prefer to work from the pc, anyone have any other possible ideas?! I'm at a loss
-------------------------------------
Sent from my HERO200
Hello guys.
I was looking for a similar guide to link to my friend but didn't find anything, so I decided to write my own.
Personally I didn't find any good guide regarding partitioning from android itself, so I think it's also more unique guide because you can easily make your own partition layout without using PC at all.
Why I should use EXT4 instead of FAT/exFAT?
1. We're running Android, Android is based on Linux. EXT4 is native linux-proposed filesystem, while FAT/exFAT is not.
2. All our internal partitions (/efs /data /system /cache /preload) use ext4, natively.
3. CM has poor exfat support, while fat32 is not recommended for big file systems (over 2 GB) because it doesn't work well with them, thus microsoft implemented exfat.
4. EXT4 has better stability and performance, especially on Android devices, compared to exfat and fat.
When you should not use ext4 over fat/exfat?
- When you for whatever reason use your external sd card in windows environment physically. Android works in MTP mode, you'll use your ext4 external sd card the same way as you use internal one under windows. But if you for whatever reason puts your external sd card f.e. in usb adapter connected with windows then it won't work. So yeah, if you keep your external sd card in your phone then you're fine.
Expert Way (Requires fdisk/mke2fs utilities (busybox), works always):
1. Launch any terminal from Android environment (f.e. Android Terminal Emulator or adb shell through PC)
2. Make sure you have root (su command)
3. Make sure you have all required utilities. Type fdisk --help and mke2fs --help, both commands should print usage. If you get "command not found" then you don't have required utilities. Either install Busybox or CM-Based ROM with native busybox support (tested on ArchiDroid 2.X)
4. Unmount your external sd card (umount /storage/sdcard1)
5. Launch fdisk partitioning program on your external sd card (fdisk /dev/block/mmcblk1)
6. Destroy partition table (o), create new partition , make sure it's primary (p) and first one (1).
7. You can check if you're satisfied with your partition layout (p). When you're done exit and save changes (w)
8. Create ext4 filesystem on your partition (mke2fs -t ext4 /dev/block/mmcblk1p1)
9. Reboot
Android should automatically detect and mount external sd card in ext4 after reboot.
Here you can find a short movie which shows going through expert way recorded by me
Intermediate Way (Requires USB Adapter and some patience, should work like a charm):
1. You'd need USB Adapter or any device which can read micro sd cards on PC
2. Open any linux-supported partitioning program (f.e. partition magic, gparted, parted), it needs to support ext4.
3. Delete all partitions from your external SD Card (typically, one fat/exfat) and create one ext4 partition.
4. In case you'd also want hardswap create 2 partitions, one primary ext4 one and second primary swap one.
Newbie Way (Requires PhilZ Touch Recovery, may not work):
1. Launch PhilZ Touch Recovery
2. Select "Mounts & Storage" => "format /external_sd"
3. Select "ext4" as a filesystem
4. Please note that it can take some time. This way you should get running ext4 filesystem, but personally I didn't test this method, as I prefer more advanced ones .
This guide is more or less universal but I'm using sgs3 external sd card paths so I want to make sure nobody bricks other phones . Personally I suggest using expert way, as it's probably the easiest one.
Hit thanks if it helped, I hope it did .
@JustArchi thanks for the tutorial. Now for the sake of sdcard wearing. I would like to disable Journaling. How do you do that?
EDIT: also i noticed after formatting the externalsd card there is 3 GB occupied by nothing (?) This is normal?
cba1986 said:
@JustArchi thanks for the tutorial. Now for the sake of sdcard wearing. I would like to disable Journaling. How do you do that?
EDIT: also i noticed after formatting the externalsd card there is 3 GB occupied by nothing (?) This is normal?
Click to expand...
Click to collapse
tune2fs -O ^has_journal /dev/block/mmcblk1p1 should do the trick. You can put it in init.d if needed.
Also no, you should get full size of your sdcard. Are you sure that you've firstly destroyed partition table (o) and then created new full-size partition , as showed in the video?
You can use fdisk also to get information about your external sd card and find why is it smaller than it should be.
HI, My 64gb is two partitioned one hardswap and other primary.
Will I lose data on both partitions if I delete partition and format to EXT4?
golti said:
HI, My 64gb is two partitioned one hardswap and other primary.
Will I lose data on both partitions if I delete partition and format to EXT4?
Click to expand...
Click to collapse
You will lose data contained in the partition you are formatting. If you leave the other partitions untouched, you won't lose their data.
golti said:
HI, My 64gb is two partitioned one hardswap and other primary.
Will I lose data on both partitions if I delete partition and format to EXT4?
Click to expand...
Click to collapse
Just don't use (o), as it will destroy everything. Use an option to delete selected partitions (d, if I remember correctly) and create them through n.
System Data
Hi, thanks for te help, but now a have a 1 gb lost by system data or 0.8gb if i disable the journaling, that is right??? Thanks
vazio said:
Hi, thanks for te help, but now a have a 1 gb lost by system data or 0.8gb if i disable the journaling, that is right??? Thanks
Click to expand...
Click to collapse
It depends on your rom and also if you created ext4 properly. I've formatted my 2 GB SD Card to EXT4 and I got 1,80 GB free (yes with journaling). This is because 5%-10% is reserved for "super blocks". Read more -> http://en.wikipedia.org/wiki/Ext4
problem using expert method
Hi Guys,
I am new fairly new to rooting and using terminal emulators.
I have a rooted samsung galaxy note 2 with superSU, busybox and shell terminal emulator. I verified fdisk and mke2fs
(fdisk --help and mke2fs --help) but then when I tried the command
"umount /storage/extSdCard"
I get the error message "Operation not permitted"
Can anyone tell me why this might be?
Thanks
/storage/extSdCard is the path to the external sdcard on my device.
Hottot2 said:
Hi Guys,
I am new fairly new to rooting and using terminal emulators.
I have a rooted samsung galaxy note 2 with superSU, busybox and shell terminal emulator. I verified fdisk and mke2fs
(fdisk --help and mke2fs --help) but then when I tried the command
"umount /storage/extSdCard"
I get the error message "Operation not permitted"
Can anyone tell me why this might be?
Thanks
/storage/extSdCard is the path to the external sdcard on my device.
Click to expand...
Click to collapse
Did you login as root before? (su)
JustArchi said:
Did you login as root before? (su)
Click to expand...
Click to collapse
I did not.
However, I did try again and got the sane result. I used these commands in shell terminal emulator:
su -
mount
umount /storage/extSdCard
result: "Failed: Operation not permitted"
I have verified root with root checker...and after typing the command "su -" I was prompted by supersu to "allow"
I believe this issue will likely be something simple that I am not aware of.
I have tried this on my galaxy note 2 and my tab3 8.0 with the same results.
I really appreciate any help offered.
Hottot2 said:
I did not.
However, I did try again and got the sane result. I used these commands in shell terminal emulator:
su -
mount
umount /storage/extSdCard
result: "Failed: Operation not permitted"
I have verified root with root checker...and after typing the command "su -" I was prompted by supersu to "allow"
I believe this issue will likely be something simple that I am not aware of.
I have tried this on my galaxy note 2 and my tab3 8.0 with the same results.
I really appreciate any help offered.
Click to expand...
Click to collapse
Try to execute su -c "umount /storage/extSdCard"
It worked flawlessly in my case.
Thanks Archi. I was wandering around looking for a solution to the problem with my sd(I'm nooo0b if it goes about Linux/Android ). My Archidroid 2.3.3 did not recognized/mount my external card, so after following your instructions (using the terminal in android) now I can enjoy my 64gb sd card.. Great job!
JustArchi said:
Try to execute su -c "umount /storage/extSdCard"
It worked flawlessly in my case.
Click to expand...
Click to collapse
Ok. That worked. Thanks.
I then tried (su -c "fdisk /dev/block/mmcblk1")
Then...press m for help...or pressing "o" gets me a syntax error.
I have attached a screenshot.
Thanks again
Ryan
Hottot2 said:
Ok. That worked. Thanks.
I then tried (su -c "fdisk /dev/block/mmcblk1")
Then...press m for help...or pressing "o" gets me a syntax error.
I have attached a screenshot.
Thanks again
Ryan
Click to expand...
Click to collapse
Okay, you're user, not root. This is a weird android shell, that's why.
Try to use "su -i" to get root shell, then use fdisk (without su).
JustArchi said:
Okay, you're user, not root. This is a weird android shell, that's why.
Try to use "su -i" to get root shell, then use fdisk (without su).
Click to expand...
Click to collapse
Still didnt work. After typing "su -I" the next line still says "[email protected]:/$"
I was thinking I could try a reinstall of shell terminal emulator...or perhaps you could recommend a different one to use.
I will try again later tonight.
Thanks
Ryan
Hottot2 said:
Still didnt work. After typing "su -I" the next line still says "[email protected]:/$"
I was thinking I could try a reinstall of shell terminal emulator...or perhaps you could recommend a different one to use.
I will try again later tonight.
Thanks
Ryan
Click to expand...
Click to collapse
Try android terminal emulator, you must gain root shell. Typically "su" command does that, "su -l" should as well.
JustArchi said:
Try android terminal emulator, you must gain root shell. Typically "su" command does that, "su -l" should as well.
Click to expand...
Click to collapse
Alright...typed su and gained root....got through ttothe last step.
I typed "mke2fs -t ext4 /dev/block/mmcblk1p1"
and the result was: "mke2fs: invalid option -- t"
I have trying to read about mke2fs and the -t option but no luck so far.
Thanks
Ryan
Hello Archi and thanx for the tutorial
I followed all the steps, done it to the end, but after reboot I couldn't make any folder on SD card.
Card is recognized, formated as EXT4, but for some reason there is no way to put anything to it
Tried again with gparted, ended with same result.
Tried to change ownership, but that also didn't work out...
Now i reverted card to fat32...
Any idea what could be wrong?
btw, using NeatROM 4.4.2 with boeffla kernel and Philz 6.00.8
thanx in advance
Tom-Tom07 said:
Hello Archi and thanx for the tutorial
I followed all the steps, done it to the end, but after reboot I couldn't make any folder on SD card.
Card is recognized, formated as EXT4, but for some reason there is no way to put anything to it
Tried again with gparted, ended with same result.
Tried to change ownership, but that also didn't work out...
Now i reverted card to fat32...
Any idea what could be wrong?
btw, using NeatROM 4.4.2 with boeffla kernel and Philz 6.00.8
thanx in advance
Click to expand...
Click to collapse
Ext4 support is broken in your rom.
Hottot2 said:
Alright...typed su and gained root....got through ttothe last step.
I typed "mke2fs -t ext4 /dev/block/mmcblk1p1"
and the result was: "mke2fs: invalid option -- t"
I have trying to read about mke2fs and the -t option but no luck so far.
Thanks
Ryan
Click to expand...
Click to collapse
Your rom doesn't support mke2fs properly.
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
kcattakcaz said:
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
Click to expand...
Click to collapse
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
zroice said:
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
Click to expand...
Click to collapse
I am rooted, but stock ROM and kernel. MTP is for connecting to a computer? If it is, I don't need that. I have tried
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/extStorageCard
and variants switching the flags and options.
Interesting... I just typed that command in to make sure I didn't make any typos.... and my phone crashed and rebooted. I typed it again to see if it would cause another crash and it appears to have mounted the card! Whwn I type "df" at the prompt it now shows a 28.6 GB filesystem at that location, which has to be my sd card.
Why, how, I don't know. It works, it's all I can say.