Related
Did not get any help in cyanogenmod thread, so creating a separate thread here.
I am in trouble. After I updated my ROM to cyanogenmod 3.6.7.2 (with his recovery image 1.3.1 and latest radio) I get a message saying: "Removed SD Card" in the notification and I am getting force closes in apps which access sd card.
Why did it remove my sd card? I have the following partition structure"
c (formatted fat32) 2GB - this is what used for upgrading the radio and rom.
83 (formatted ext4) 6GB
c (formatted fat32) 7GB
82 (mkswapped) whatever left off from 16GB card.
Is this structure causing the issues? I used Linux 2.6.30 and e2fsprogs 1.41.7 to format ext4 and dosfstools 3.0.2 to format fat32 FSs.
I ran fix_permissions from recovery console because I was getting FCs in powermanager (which logs files on SD card).
Also, if I boot into the recovery console, I can mount /sdcard and it automatically mounts the first fat32 partition on /sdcard. I can 'fdisk -l' and see all my partitions are there. So, its not a hardware issue. Some sort of chicken&egg because of apps2sd.
I just mounted the partition2 (which is ext4) in recovery console and I can see there are "app app-private dalvik-cache lost+found" folders on it. So, it looks like normally initialized.
Does anybody know what's going on here? Appreciate your help!
It's the same response you've been getting in the other section.
Try backing up your data on your computer, and completely formatting your card to fat32.
From there, instead of making the partitions on the computer, use the Recovery Console (accessed from Cyano's Recovery) and re-create the partitions as you like.
Ok, I delete the 3rd and 4th partitions, and it seems to be working fine now. So, it seems like there is an assumption about the partition structure in the code somewhere.
devsk said:
Ok, I delete the 3rd and 4th partitions, and it seems to be working fine now. So, it seems like there is an assumption about the partition structure in the code somewhere.
Click to expand...
Click to collapse
So you are all good now?
What exactly did you do? Just remove the 3rd & 4th partition, without formatting?
akapoor said:
So you are all good now?
What exactly did you do? Just remove the 3rd & 4th partition, without formatting?
Click to expand...
Click to collapse
Yeah, I just removed the 3rd and 4th partitions from recovery console and the card is recognized and working fine. Now, I need to find out why is it hard coded like that.
It seems like something doesn't like more than 3 partitions on the SD card. I now have 3 partitions with 'c' (fat32), '83' (ext4) and 'c' (fat32) codes and it seems to work fine.
An ext partition of more than 1.5gb can cause problems
Most roms will not work with the way you had it set up (at least not well)
They follow a 3 partition scheme as such
FAT32 > EXT > SWAP
B-man007 said:
An ext partition of more than 1.5gb can cause problems
Most roms will not work with the way you had it set up (at least not well)
They follow a 3 partition scheme as such
FAT32 > EXT > SWAP
Click to expand...
Click to collapse
I've heard this repeated elsewhere but nobody ever actually says what the problem is with partitions greater than 1.5gb. I'm very curious to know, because I haven't noticed anything wrong.
Except that /sdcard won't automount if my sd card has 4 partitions defined on it. As soon as I mark the 4th one empty and reboot, it's fine again. But that has nothing to do with the size of the ext fs on partition 2. Something with vold is funky, because I can mount /sdcard manually from adb.
So heres the low-down:
My (4GB) SD Card is partitioned as so:
1.8GB fat32
1GB ext2 (system)
1GB ext2 (data)
I've put the latest basefiles (20091116) in the fat32 partition along with the senseHERO 1.3.3 build. i boot up haret go through the installer for the data. finish all the steps and once it starts to boot, i either get "android_power wakeup" or "ERROR: CANNOT LINE EXECUTABLE 's/system/bin/sh' "
it wont boot into the build and it's kinda buggin me out man.
so if anyone has any idea on what i should do please help. thanks people
Not sure what the issue is, but your ext2 partitions are much much larger than they need to be.
TheKartus said:
Not sure what the issue is, but your ext2 partitions are much much larger than they need to be.
Click to expand...
Click to collapse
yeah i'm gonna fix that. lol. so when running the vogue installer i hit volume down to start it. then do i hit volume down to wipe data or end. or do i basicly hit volume down all the way till it says press any key to boot?
Giggles 312 said:
yeah i'm gonna fix that. lol. so when running the vogue installer i hit volume down to start it. then do i hit volume down to wipe data or end. or do i basicly hit volume down all the way till it says press any key to boot?
Click to expand...
Click to collapse
First time around you want to run the recovery, then you want wipe data and and backup. Then you should be good to go.
Android power wakeup sounds like it's not using the proper init.rc file, confirm that you have the init.hero.rc in your init folder on the sdcard.
Giggles 312 said:
So heres the low-down:
My (4GB) SD Card is partitioned as so:
1.8GB fat32
1GB ext2 (system)
1GB ext2 (data)
I've put the latest basefiles (20091116) in the fat32 partition along with the senseHERO 1.3.3 build. i boot up haret go through the installer for the data. finish all the steps and once it starts to boot, i either get "android_power wakeup" or "ERROR: CANNOT LINE EXECUTABLE 's/system/bin/sh' "
it wont boot into the build and it's kinda buggin me out man.
so if anyone has any idea on what i should do please help. thanks people
Click to expand...
Click to collapse
TheKartus said:
First time around you want to run the recovery, then you want wipe data and and backup. Then you should be good to go.
Click to expand...
Click to collapse
yup thats what i've been doing all this time, but still getting the android_power wakeup error. i dug into some older threads and found nothing really to my benifit, but i realized that its not vilord's backup method thats killing me, its either the build or my phone.
Giggles 312 said:
yup thats what i've been doing all this time, but still getting the android_power wakeup error. i dug into some older threads and found nothing really to my benifit, but i realized that its not vilord's backup method thats killing me, its either the build or my phone.
Click to expand...
Click to collapse
The nuclear option always seems to work... repartition the SD card, redownload the basefiles and a sytem file and just start from scratch.
mssmison said:
Android power wakeup sounds like it's not using the proper init.rc file, confirm that you have the init.hero.rc in your init folder on the sdcard.
Click to expand...
Click to collapse
ok. thats a step in the right direction, but i forgot to mention that imma COMPLETE NOOb at working with android and linux. imma windows man XD and i just got into the swing of useing a smartphone. so yea XD where is this init.hero.rc you speak of? and how would i "fix" it?
BTWS mssmison i used you ext2 partition backup on a donut build and it was flawless. made everything so much smoother and perfect. thats why i wanna do this to a hero build so i can have a hero android phone without actually coughing up my hard earned cash on one ... yet
power wake up errors also can be caused by bad permissions set for /bin could you possibly upload a logcat?
jamezelle said:
power wake up errors also can be caused by bad permissions set for /bin could you possibly upload a logcat?
Click to expand...
Click to collapse
i would if i knew how. being a noob sucks :/
i have a kaiser
p1: Fat32 1.8 gig
p2: Ext2 200 mb
When i start haret it keeps giving me mdp_dma_to_middi: busy.
wont go further then this...
being a n00b to...
n0r said:
i have a kaiser
p1: Fat32 1.8 gig
p2: Ext2 200 mb
When i start haret it keeps giving me mdp_dma_to_middi: busy.
wont go further then this...
being a n00b to...
Click to expand...
Click to collapse
your going to need a data partiton as well(another ext2 partition). Make both ext2 partitions 256mb and the rest fat32.The dma_mddi error happens to me and it boots fine..but the screen rotates upside down when you open the keyboard.
ajclai08 said:
your going to need a data partiton as well(another ext2 partition). Make both ext2 partitions 256mb and the rest fat32.The dma_mddi error happens to me and it boots fine..but the screen rotates upside down when you open the keyboard.
Click to expand...
Click to collapse
ok thnx!
I read on another post this resolution: 288x384
maybe ittl help you?
n0r said:
ok thnx!
I read on another post this resolution: 288x384
maybe ittl help you?
Click to expand...
Click to collapse
no, hero based builds all have to be 320x480
Giggles 312 said:
i would if i knew how. being a noob sucks :/
Click to expand...
Click to collapse
This thread is funny.
the screen flips down when you open keyboard because zimage24.. use zimage23 and that will be fixed... search it at deprecated in vogue-android
I would like step-by-step info on how to format my SD card to have an EXT2 partition.
I currently use Windows 7.
What tools or downloads are required? I've searched a bit but can't find a tutorial.
Thnx in advance!
Damnit.. My company required encryption of the data on my Nexus S when I was testing ICS Beta with Email / Exchange.
Went ahead and encrypted the device.
Then, I wanted to install ICS Combo Beta 11, so I formatted /system /data /boot and tried to install from /sdcard/*.zip.
No luck.
Clockworkmod recovery cannot mount /sdcard anymore.
Wanted to try and format it, but the clockworkmod tries to mount it first, before formatting
HELP!
I'm stuck with only recovery now and no way to get the update package installed
Is there a way to install from zip via the command line?
You should be able to use fastboot to load the rom on your device. I haven't tried it this way before but it should work:
Code:
fastboot update rom.zip [-w if you want to erase data too]
Give it a spin.
The SDCard not being able to be mounted has been covered a few times but I can't recall the proper fix by heart - search around and you'll definitely get some results that can help you with that.
Greetz
Sounds like it's busted.
Sent from my Nexus S using xda premium
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Si_NZ said:
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Click to expand...
Click to collapse
Thought about that, but what filesystem? FAT32?
Sure
Greetz
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
dr911 said:
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
Click to expand...
Click to collapse
Definately backed up..
This was a real scare.. I couldn't mount or format from clockworkmodrecovery. All I had was the adb shell and the builtin /sbin commands.
LUCKILY I found this article;
http://forum.cyanogenmod.com/topic/...mmcblk0++mkfs++ext2__fromsearch__1#entry56396
It didn't exactly match what I was experiencing, but the key was the parted program.
Using it, I was able to reformat my media (partition 3) and am now able to repush things to it.
Stupid sdcard encryption..
Reinstalling ICS Beta 11 now
Blood pressure slowly decreasing.. damn that was a nightmare
So some lessons learned;
DON'T try to partition your SDCARD from clockworkmod or Windows or Mac. The USB storage presented to your computer is a single partiton from you mmcblk0 sd storage. If you partition it, you've got a partition inside a partition which will only make sense to your windows/mac system. Inside of Android, the partition is essentially corrupted and it won't mount.
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
parted is the only way to fix it. from parted do mkfs type fat32 partiton 3 (media) that will reformat the partition correctly and give you access from Android and external USB hosts.
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
nauckwj said:
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
Click to expand...
Click to collapse
That means, I should check my SD Card, which I formatted under OSX with Disk Utility?
Maybe I'll do it next time I flash a new ROM, because for now it works fine.
nauckwj said:
Blood pressure slowly decreasing.. damn that was a nightmare
Click to expand...
Click to collapse
Yeah, I had a similar situation a few weeks after I got my beloved NS when I tried Whispercore. The hole NS got encrypted and formatting the system partition in CWM didn't work, but what I read it was luckily due to a problem with the CWM version. Flashing a newer Version of CWM solved the problem. First I was dying!
So, when I encrypted with ICS and got this problem I calmed down much faster
Si_NZ said:
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
Click to expand...
Click to collapse
My problem was I used the Windows fdisk partitioning utility to repartition my /sdcard partition. That was part of the problem. I did also read how some people were repartitioning the /sdcard partition, which is kind of weird. I can understand why someone might want to reformat it as an ext4 filesystem, but why would you want to partition a partition?
The /sdcard partition is actually the third partition on your mmcblk0 device. If you partition it, most utilities will fail to recognize it as a valid media device anymore, because they expect to be able to read the filesystem data structures when they mount it. These won't exist if a partition table is sitting at the beginning of the blocks.
I couldn't reformat from within CWM because it first tries to mount the partition. if it fails to mount, CWM won't reformat it. Only way to reformat it was with parted, unless you have a working system installation.
Last night I was also able to reformat it from within ICS. Had to do a full factory-wipe from within ICS, then it indicated the sdcard was no longer valid and asked me if I wanted to reformat it. Once I said yes, all was back to normal.
Fun fun
I bypassed dead internal memory on a GT-I9000M.
Symptoms:
- Your GT-I9000M is not booting or bootlooping no matter what firmware you are flashing it with.
- In recovery, you are seeing I/O errors on /dev/block/mmcblk0p1
- Trying to repartition and format the internal storage with fdisk or parted and mkfs.whatever fails.
To recover:
- Partition and format your 16GB+ external microSD with at least two primary partitions, vfat on the first one and rfs (or whatever fs is supported by your firmware) on the second one.
- Acquire a stock ROM, in my case I used JL2
- untar the PDA portion of your ROM of choice (you want zImage and factoryfs.rfs)
- Extract initramfs from zImage ( https://github.com/mistadman/Extract-Kernel-Initramfs )
- grep for /dev/block/mmcblk, there should be 4 .rc files containing references to it as well as within the binary file /init.
- use a text editor to replace all occurances of "mmcblk0" with "mmcblk1" (and vice-versa if you feel so inclined) in the .rc files.
- use a hex editor to replace "mmcblk0" with "mmcblk1" in /init.
- create cpio archive of your modified initramfs with `find . | cpio -H newc -o > ../initramfs.img`
- repack kernel and initramfs ( http://forum.xda-developers.com/showthread.php?t=789712 ), you should have a new_zImage now.
- Mount the factoryfs.rfs as a loop `mount -o loop,rw -t vfat factoryfs.rfs /mnt/loop`
- Modify vold.fstab - this topic is well covered elsewhere (swap sdcard and sdcard1, swap mount points), then umount your loop
- Flash factoryfs.rfs and zImage using your favorite method.
That's it! Your phone will now boot and complain forevermore that the external memory is corrupt. ToDo: use third partition on external microSD as external_sd...
To recap:
We're telling android's init and whatever .rc scripts contain references to the broken partitions on the internal storage /dev/block/mmcblk0 to point to an appropriate partition on the external microSD card /dev/block/mmcblk1. You can actually do anything you want with the partition structure as long as it's consistent throughout init and in vold.fstab. Different ROMs do it differently.
I am not responsible for misuse of your hex editor, lack of backups, etc. I highly recommend the unbrickable mod.
Corrupt internal storage
Hi b0nafide,
My internal storage is also corrupted (i9000). I'm getting the same errors you descripe in your post. I'm trying your solution in wich you install android on your external SD. I bought a 8GB cat10 SD card....
But I'm stuck at the step: 'Extract initramfs from zImage ( [//github.com/mistadman/Extract-Kernel-Initramfs] )'. When I start the script nothing happens, except for my terminal closing. I'm using a virtualy installed Ubuntu distribution (Backtrack 5).
Do you have a tip? Perhaps you can help me through Teamviewer???
Hope do hear from you... I want to use my phone again
Greatings, Eldoro
My sgs is dead.
Please b0nafide, can you upload this modificated kernel (zImage and factoryfs.rfs) just for noobs like me?
Yes that woud be great. ..
Sent from my GT-I9300 using xda app-developers app
Here also an i9000 with reboot
Have done allot, stock rom, other pit files...
Is there a way to do this with a i9000 ?
and yes an image for us ?
and is the phone then normale... or is the internal storage still broken ?
Thanxs
Anyone can help us?
grimorct said:
Anyone can help us?
Click to expand...
Click to collapse
???
Anyone with working solution for this on i9000? I'll try to pack JW4 following this guide
grozni said:
Anyone with working solution for this on i9000? I'll try to pack JW4 following this guide
Click to expand...
Click to collapse
Yesterday, I made a flasheable pack of JW4, but it doesn't run. Now i'ḿ trying to modify JVU, but a strange thing happen when i'm repacking zImage...the script spends a lot of time in order to make it, and i can't be able to verify the correct pocess of new_zImage.
It's my first post in XDA, because normally I use HTCMANIA... I'm Spanish...and my English it isn't so good. Even, I should said that it isn't my phone...i'm repairing a friend's phone, so it's difficult for me to explain or speak about different ROMs or kernels....sorry
It's very important to advice that the scripts posted should be modified to get it run...because I found different problems to execute on Ubuntu.
Now it's 1:30 am...i'm trying "ext_JVU"....tomorrow i'll tell you the results.
Anyway i'll try to upload it, to reach different conclusions...
sesetxu said:
Anyway i'll try to upload it, to reach different conclusions...
Click to expand...
Click to collapse
Please do, I'll try flashing immediately and get back with results. How did you format external sd card?
I'm willing to try aswell... almost gave up hope.
Sent from my GT-I9300 using xda app-developers app
Hello friends!!!
I've the CODE (PDA file in ODIN) modified to execute android in ext-sdcard.
I do it as the first post said....but it doesn't run for me...
Anyway here is...Yo must get the MODEM and CSC os the stock firmware
XDA block the urls for me...for this reason its haven´t the WWW ...
Stock firmware..only to get MODEM and CSC: 4shared.com/zip/W1NeYAPA/I9000XXJVU_I9000OXAJVU_OXA.html?
Code modified to run in sdcard external: rapidshare.com/files/3786190721/ext_XXJVU.tar.md5
To solve my problems, i'll try to generate an CWMfile flasheable to try it...but now i'm hopeless....
Good luck men!!
sesetxu said:
Good luck men!!
Click to expand...
Click to collapse
Great work men!! It works for me. After flashing I got error in picture I posted (same error as before when writing to internal storage with stock rom). I just hit reboot but honestly I was not thinking it will boot. Thing I noticed when I start camera I get message turn off usb storage first. My files app shows no sd card inserted. How did you format your sd card? I'm using 8gb class 6 sd card
grozni said:
Great work men!! It works for me. After flashing I got error in picture I posted (same error as before when writing to internal storage with stock rom). I just hit reboot but honestly I was not thinking it will boot. Thing I noticed when I start camera I get message turn off usb storage first. My files app shows no sd card inserted. How did you format your sd card? I'm using 8gb class 6 sd card
Click to expand...
Click to collapse
I've modified all to use an sdcard with the folowing partitions:
1st primary fat32 which is internal sd card (4 gb)
2nd primary reiserfs which is /data (2 gb)
3rd primary fat 32 as external sd card
Try it...and I am happy to help you
sesetxu said:
I've modified all to use an sdcard with the folowing partitions:
1st primary fat32 which is internal sd card (4 gb)
2nd primary reiserfs which is /data (2 gb)
3rd primary fat 32 as external sd card
Try it...and I am happy to help you
Click to expand...
Click to collapse
I will try this layout. At first I prepared sdcard with 2 partitions which currently boot into Android but storage isn't working:
1st primary fat32 (6gb)
2nd primary ext4 (2gb)
You said raiserfs, should be that rfs type partition?
Update: I just noticed that both partition on my sdcard are fat32. First partition which should be internal storage I had to format again (not sure why). After this internal storage is still not available when in Android. I guess some mounting point is not good. Second fat32 partition is where the data is I guess (picture attached)
Exactly the same result as grozni. Same errors upon installing but booting into android. Amazing work! Also formatted 2 partitions. WiFi also not working btw. Hangs on obtaining ip...
Sent from my GT-I9300 using xda app-developers app
eldoro said:
Hangs on obtaining ip...
Click to expand...
Click to collapse
Same here
Is imposible to start Andoird without a rfs partition to mount /data (or ext4, for ROMs wich has fixed the troubles with ext4/rfs file systems...)
I can´t start the phone, because i get an added problem (my system can't format rfs data..but i don't know why)
I'm going to review the file /system/etc/vold.fstab who manages the mount points of the internal and external storages.
If anyone gets the correct configuration...please post it..
Tomorrow is Monday...and although I'm Spanish, I have a job (****ing crisis)...and i haven't so much time as weekend
Edit: wifi sockets are created over /data partition, if there is any problem in this partition is probably to get troubles obtaining IP
sesetxu said:
Is imposible to start Andoird without a rfs partition to mount /data (or ext4, for ROMs wich has fixed the troubles with ext4/rfs file systems...)
Click to expand...
Click to collapse
If I understand correctly samsung rfs and reiserfs are not the same thing? Why you use raiserfs on sdcard layout?
sesetxu said:
Edit: wifi sockets are created over /data partition, if there is any problem in this partition is probably to get troubles obtaining IP
Click to expand...
Click to collapse
That is the reason
Update: One more thing I forgot to mention. When I try to format USB storage (internal sd) I get message sd card removed
I am running Cyanogenmod 9.1 on the Samsung Galaxy Tab 2 7.0, WiFi IR version. Does anyone definitively know how to run your apps from the external SD card? I have tried numerous workarounds but all have failed to produce any results, I have no idea where the problem even resides. Thanks.
I've the same problem with directory bind, its an issue with the multi user on the ROMs. The emulated SD card messes everything up I think
Sent from my GT-P3110 using xda app-developers app
babyrammer said:
I am running Cyanogenmod 9.1 on the Samsung Galaxy Tab 2 7.0, WiFi IR version. Does anyone definitively know how to run your apps from the external SD card? I have tried numerous workarounds but all have failed to produce any results, I have no idea where the problem even resides. Thanks.
Click to expand...
Click to collapse
Have you tried Link2SD?
I think you might be right, that seems to be the error I get when I try to use App 2 SD.
I went and got Link 2 SD, followed all the instructions (partitioned my external SD into 2 primary FAT32 parts) and it told me I was able to move apps, but I get error messages whenever I try [INSTALL_FAILED_INSUFFICIENT_STORAGE] which I don't really understand, I have plenty of space.
babyrammer said:
I think you might be right, that seems to be the error I get when I try to use App 2 SD.
I went and got Link 2 SD, followed all the instructions (partitioned my external SD into 2 primary FAT32 parts) and it told me I was able to move apps, but I get error messages whenever I try [INSTALL_FAILED_INSUFFICIENT_STORAGE] which I don't really understand, I have plenty of space.
Click to expand...
Click to collapse
Your second partition really needs to be ext3 or ext4. Primary partition fat32
Root2SD says in its instructions FAT32 should work, which is why I tried that first. When I did EXT3 and EXT4 it told me it couldn't mount it as it isn't compatible with my device :/ I even tried to manually mount it in Clockworkmod but even after that I got the same error messages.
babyrammer said:
Root2SD says in its instructions FAT32 should work, which is why I tried that first. When I did EXT3 and EXT4 it told me it couldn't mount it as it isn't compatible with my device :/ I even tried to manually mount it in Clockworkmod but even after that I got the same error messages.
Click to expand...
Click to collapse
What are you using to partition your sdcard with? Hopefully not CWM. If you are, try TWRP instread. There is also a Windows tool "Mini Partition" I think that is also recommended for that task.
Actually I was just using Mini Partition, I saw it recommended somewhere else.