Related
i tried hijacking the other 1.4.0 thread but got ignored and didnt want to keep a something stale that was off-topic alive.
so, i have flashed 1.4.0, verified that the kernel is in fact running. i wiped before the update to get rid of other issues i was having with some apps.
now, with 1.4.0 running, it appears that the external sdcard is not mounting while the system is booted. in recovery, it shows up as it should with all of the files. i have an /mnt/sdcard/sdcard2 and i have an an external directory under /sdcard
ive tried with card in before boot and after. i can say that dmesg is in fact seeing the card being removed and pushed in; however it doesnt seem to 'automount' from vold.fstab properly, or something else is jacked.
that being said, i dont seem to have a /devices which is where these things are suppose to be mounting from, is it not?
/sys/devices/platform/sdhci-tegra.2/mmc_host/mmc1
should i add the prefix /sys to both the usbOTG and sdcard to fix this?
or is there something else that is missing? presumably i could also create a symbolic link /devices -> /sys/devices, or does the kernel chroot to /sys at some point so none of this is needed, and i am having a different problem?
thanks for the help,
~marion
ya i noticed mine sd card is doing the same thing wont mount but works in recovery and i know it did work bc i had sdcard access through root explorer on v1.4.0 and now it does not work like it died over night
mine has not worked since moving to 1.4.0.
i originally went from 1.3.2 to 1.4.0 but the update didnt work well through the clockworkmod steps was having problems mounting e: so i went back to 1.3.1 then -> 1.4.0 [after wiping cache/data, and readding an sdcard2] using kernelmanager.
the update worked well, i rebooted to recovery and say that i could mount e:, and files where on the sdcard as expected. when booting to OS external has no files and sdcard2 has no files. also using connectbot for a shell, df shows nothing mounted.
is this because vold.fstab isnt mounting from /sys as described in my earlier post?
still unable to mount external sdcard while xoom is boote in 1.4.0.
Am able to pc-mount, and back up to it via recovery... no one else is seeing anything similar?
In 1.4.0 the sdcard should be in /sdcard/external not sdcard2. The card has to be in before turning it on. They are not hot-swappable.
Sent from my Xoom
Guys this is why Mass Storage has been removed in 1.4.1. Here's basically what's going on. When the device boots, the Sdcard is mounted to data/media/external which is the same as Sdcard/external. The Sdcard mounts before data/media is "fused" to create a virtual internal Sdcard. This is the only reason why you can actually see the external Sdcard inside the internal Sdcard. And this is why gallery can see the external Sdcard. However, in order for the Sdcard to mount as mass storage, Vold.fstab MUST mount the Sdcard at mnt/Sdcard so that Vold service can see it. But, this is the same mount point the internal storage is "fused" to. So when mass storage is done, it attempts to remount the sdcard where it was previously mounted, sdcard/external. But because of the way "fuse" works, it does not let any devices be mounted inside it. This is why I need source to do it right. I can then tell Vold to look some other place for the sdcard mount point. Until then, it's borked and that's why I pulled it.
@bwcorvus: in my first post i said that it wasnt showing up in sdcard2 or external... maybe i wasnt clear enough but its there.
@bigrush: thats exactly what i was seeing, and what i was presuming. i figured the lack of response meant either people werent seeing the issue or noticing it.
that being said... dmesg shows the device showing up if inserted/removed while running. but its showing out of /sys/devices... instead of /devices... changing that in vold.fstab didnt do anything for me as im not sure i have a great grasp on the boot sequence.
~marion
That's odd, mine mounts to external with no issue with 1.4.0
Have CWM v3.1.0.1 installed and can boot just fine but when I install the new CWM, I get "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
This happens with any zip file I'm installing. I get "E:Can't open /sdcard/*.zip (bad)"
I thought maybe I had a bad download so I downloaded and re-downloaded the zip files. Nothing.
I've Rooted using One Click Universal root v4 and during the root process installed CWM 3.1.0.1. No problems. All worked fine.
Was thinking my sdcard might be the problem so I installed on my PC brk's Universal root toolkit v7.1 and tried to use NVflash on Revolver and Prime 2.0.3. Well it just sits there for an hour hung about 30% into it.
Will try brk's Universal root toolkit and attempt recovery install.
Any suggestions/ideas would be greatly appreciated.
Maybe try to format your micro sd card again using the pc.
sdformatter is a good program.
Well I fired up, brk's Universal root toolkit v7.1 and ran the restore recovery and then installed Prime v2.0.1 with success. Installed using NVflash option.
After going through reboots to ensure Prime installed (which looks really good), I decided to try to install the Prime v2.0.3 patch (zip file) using the updated CWM 3.2.0.1.
Well, that didn't work. Got the same error, "E:Can't open /sdcard/*.zip (bad)".
Can't figure this out. Never had this problem before.
Maybe the next course of action is the formatting of the sdcard.
Doesn't the tablet format the card? Or do you recommend using this, sdformatter?
I usually use the PC.
Keep in mind it only work with FAT32 on the micro sd
and you're using the micro sd on the tablet itself correct?
Yes.
Sent from my Transformer TF101 using xda premium
Have exactly same problem, it seem like problem somewhere in CWM 3.1.0.1
In details:
Had rooted 8.5.6.13 with Brk.root.toolkit.v7.1 (that one includes CWM 3.1.0.1),
Put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Loaded in CWM , try to update to 3.2.01 (selected install zip from SDcard) -> got "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Downloaded CWM-ready images from
http://forum.xda-developers.com/showthread.php?t=1334673
and
http://forum.xda-developers.com/showthread.php?t=1341533
Both installed OK (yes, with same CWM 3.1.0.1 !),
Another attempt to update CWM (now on 8.5.6.19)->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Checked root->root disappeared (do not know why), rooted 8.5.6.19 again with Brk.root.toolkit.v7.1,
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Got another 512MB MicroSD, formatted in FAT 32 (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Formatted it in FAT (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Looks like I am stuck on CWM 3.1.0.1 with no chances to update in future, any suggestions would be appreciated.
P.S. MD5 of cwm_recovery-3201_roach-tf101-r1.zip is correct. Transformer of WW version.
Lechaxda-developers said:
Have exactly same problem, it seem like problem somewhere in CWM 3.1.0.1
In details:
Had rooted 8.5.6.13 with Brk.root.toolkit.v7.1 (that one includes CWM 3.1.0.1),
Put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Loaded in CWM , try to update to 3.2.01 (selected install zip from SDcard) -> got "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Downloaded CWM-ready images from
http://forum.xda-developers.com/showthread.php?t=1334673
and
http://forum.xda-developers.com/showthread.php?t=1341533
Both installed OK (yes, with same CWM 3.1.0.1 !),
Another attempt to update CWM (now on 8.5.6.19)->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Checked root->root disappeared (do not know why), rooted 8.5.6.19 again with Brk.root.toolkit.v7.1,
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Got another 512MB MicroSD, formatted in FAT 32 (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Formatted it in FAT (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Looks like I am stuck on CWM 3.1.0.1 with no chances to update in future, any suggestions would be appreciated.
P.S. MD5 of cwm_recovery-3201_roach-tf101-r1.zip is correct. Transformer of WW version.
Click to expand...
Click to collapse
Hi - Here's some things to check:
1) A note from the original post(s) on cwm-3101/3202 in the dev forum:
Code:
Originally Posted by Warboy
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
It does skip internal media unless you put a file called eraseData into the clockworkmod folder on your MicroSD card.
So make sure you've got no file on the MicroSD called eraseData.
2) Have you check the md5sum? Here are the details:
Download
3.2.0.1 roach-tf101-r1
MD5: b28dca7b9dce48627e5e849586f633d1
If you don't know how to do that, then you could download an md5sum verify program for windows if you use it from somewhere, and check the zip file against the md5sum below it, or if you use linux, then just do "$ md5sum 3.2.0.1* and compare it to the md5sum above.
3) I'm not recalling the syntax of cwm errors, but it looks like "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is hopefully where "E" means error, and /sdcard really means /Removable/MicroSD/, which would at least stick you in the right area.
4) Make sure you can unzip this file using 'unzip'/7zip/windows unzip/' or whatever on your PC before you start all this. If you can't unzip it there, then you can't unzip it on the TF. You'll get an error if it won't unzip.
SO: Just make sure you have 1 & 2 & 4 right first and then just for the heck of it rename the long filename to something smaller like cwm3201.zip and put it on a) the microsd and b) /sdcard, and try it again using that name.
Good luck -
Many thanks for your help,
I have stepped again through points above:
1.I did not found any eraseData file neither on MicroSD nor on Internal memory(/,/data,/system) (checked this with RootExplorer), actually I do not completely understood where to search: clockworkmod folder does not exists on those locations.
2.As i wrote, I have checked MD 5, in any case redownloaded file, checked MD5 again: to be precise- MD5 for zip: MD5 (cwm_recovery-3201_roach-tf101-r1.zip) = f71f9b672396be5e494b3d355ed21c9a
MD5 for content (i.e extracted zip): MD5 (cwm_recovery-3201_roach-tf101-r1) = b28dca7b9dce48627e5e849586f633d1
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Lechaxda-developers said:
Many thanks for your help,
I have stepped again through points above:
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Click to expand...
Click to collapse
Are you choosing "apply update from sdcard" or "install zip from sdcard"?
Are you choosing "apply update from sdcard" or "install zip from sdcard"?
Click to expand...
Click to collapse
install zip from sdcard,
Should i rename cwm_recovery-3201_roach-tf101-r1.zip tj update.zip and try another option?
Lechaxda-developers said:
install zip from sdcard,
Should i rename cwm_recovery-3201_roach-tf101-r1.zip tj update.zip and try another option?
Click to expand...
Click to collapse
No "install zip from sdcard is correct" shouldn't have to rename the zip at all.
CWM only read from micro sdcard not internal sdcard that's why you can't see it there.
Have you tried Gnufabio RecoveryInstaller? It install the newer CWM IIRC.
http://forum.xda-developers.com/showthread.php?t=1346180
I think the idea above this is a good one for a first try at this point.
Also: I reread the original post and see that obviously cwm finds the file, attempts to or succeeds in opening it, and then shouts "bad". I see you tried unzipping from the PC, and all the rest.
I wonder if this could somehow be a permissions error and if somehow there are no meaningful permissions either on the sdcard mount (just run $mount in a terminal emulator or adb to see what they are). I'm guessing that well, it's a zip file, so no matter what else cwm must do, it has to unzip the thing and extract the data to someplace. I'd have to go stare at the github code to figure out where that place is, but the target "could" be mounted r/o. It seems like the target can't be the sdcard or you're never be able to write the zip there in the first place.
If there's a github URL in the solarnz/roach post I'll see what it extracts it to and get back to this.
Lechaxda-developers said:
Many thanks for your help,
I have stepped again through points above:
1.I did not found any eraseData file neither on MicroSD nor on Internal memory(/,/data,/system) (checked this with RootExplorer), actually I do not completely understood where to search: clockworkmod folder does not exists on those locations.
2.As i wrote, I have checked MD 5, in any case redownloaded file, checked MD5 again: to be precise- MD5 for zip: MD5 (cwm_recovery-3201_roach-tf101-r1.zip) = f71f9b672396be5e494b3d355ed21c9a
MD5 for content (i.e extracted zip): MD5 (cwm_recovery-3201_roach-tf101-r1) = b28dca7b9dce48627e5e849586f633d1
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Click to expand...
Click to collapse
You have to copy the .zip file to /removeable/micro sd card/ and not to /sd card. For now its not possible to flash something from the internal sd card.
If you allready did this you can try to "toggle signature verification" in Recovery i had to do this when i flashed the su on my sensation xe. you have to do this till it says disabled and then flash the .zip
Hope it helps
Sent from my Revolver powered AsusTransformer using Tapatalk
hachamacha said:
I think the idea above this is a good one for a first try at this point.
Also: I reread the original post and see that obviously cwm finds the file, attempts to or succeeds in opening it, and then shouts "bad". I see you tried unzipping from the PC, and all the rest.
I wonder if this could somehow be a permissions error and if somehow there are no meaningful permissions either on the sdcard mount (just run $mount in a terminal emulator or adb to see what they are). I'm guessing that well, it's a zip file, so no matter what else cwm must do, it has to unzip the thing and extract the data to someplace. I'd have to go stare at the github code to figure out where that place is, but the target "could" be mounted r/o. It seems like the target can't be the sdcard or you're never be able to write the zip there in the first place.
If there's a github URL in the solarnz/roach post I'll see what it extracts it to and get back to this.
Click to expand...
Click to collapse
OK: I grabbed both git's (solarnz and roach) and there is only one spot the error could be coming from originally which is in top-level install.c and is basically just a call to mcOpenZipArchive in Zip.c. If returns an error, then that's apparently the error you got (has E: up front, (bad) in rear, and your stuff in between).
mcOpenZipArchive looks at ~4 criteria to open, and one thing that seems kind of important is that I don't see any changes in this Zip.c file in either git repo so if it fails on solarnz, it "ought" to fail on roach.
What Zip.c checks are these things:
1) Is the file there and openable at all? (based on a few things first on /MicroSD (wheverever you pointed it), or on /sdcard if those other oddball things were setup but you said they weren't.
2) Can it map the memory for this file in shared mem?
3) Did the map return an endpoint(amount of mem) that would hold the entire file?
4) Can it parse the file into mapped mem?
I don't have time to go through more code but if any of those things cause some alarm to go off in your head, then good and there's hope of figuring it out, and if not, well, maybe we can get roach to look it over as if he hasn't got enough going on
The other possible obvious thing might just be that your cwm is corrupt and useless. I've had this happen to me, but have used nvflash to blow another img of it onto the tf. I don't know if you've got that capability or not. Like all errors, it could be a million things, and by the time I finish this paragraph, I hope you've solved it.
Thanks again for advices, solved in 1 minute with
Gnufabio RecoveryInstaller
http://forum.xda-developers.com/show....php?t=1346180
Bad point here I didn’t figured out what was the reason of the problem, I would agree with hachamacha:
The other possible obvious thing might just be that your cwm is corrupt and useless.
Click to expand...
Click to collapse
With only one exception: it was “partly” corrupted (see in my first post, with same CWM I have installed 2 zip- images without any problem), only with conjunction with cwm_recovery-3201_roach-tf101-r1.zip problem appears.
In any case: for guys who having problems "updating CWM with CWM" - just use Gnufabio RecoveryInstaller
I was using XXKPQ Gingerbread. Soon my phone started restarting and giving errors.
When I use ODIN I can put new files in to system folders. I installed XXKPE and clockworkmod, then I used adb remount, adb shell to delete everything under data/data, data/app, sdcard, sd-ext. When I do ls it said folders were empty but after restart everything came back!
Is there a way to mount a file system as a volatile memory? It accepts all the changes I say but it reverts back when unmounted and remounted. I thought it might be permission problem but fix_permissions script does not solve it. Also I heard 0 available memory bugs in the forums but my case is not that either.
On recovery menu, I used clockworkmod options to mount the data folder, I erased everything in it via adb shell, and without restarting I unmounted and mounted again using CWM, the files were there again in adb shell!
Since there are files under data/data and data/app folders, I get crashes of those applications all the time when I try to use the phone. If I install the same application from market it works fine but after restart it reverts back to crashing.
snlzkn said:
I was using XXKPQ Gingerbread. Soon my phone started restarting and giving errors.
When I use ODIN I can put new files in to system folders. I installed XXKPE and clockworkmod, then I used adb remount, adb shell to delete everything under data/data, data/app, sdcard, sd-ext. When I do ls it said folders were empty but after restart everything came back!
Is there a way to mount a file system as a volatile memory? It accepts all the changes I say but it reverts back when unmounted and remounted. I thought it might be permission problem but fix_permissions script does not solve it. Also I heard 0 available memory bugs in the forums but my case is not that either.
On recovery menu, I used clockworkmod options to mount the data folder, I erased everything in it via adb shell, and without restarting I unmounted and mounted again using CWM, the files were there again in adb shell!
Since there are files under data/data and data/app folders, I get crashes of those applications all the time when I try to use the phone. If I install the same application from market it works fine but after restart it reverts back to crashing.
Click to expand...
Click to collapse
Exists even after xxkpe + pit flash?
Try converting to ext4 and formatting and then flash xxkpe + pit.
Having read many such issues now, it seems its MoBo issue. Search around a bit. From what i have read, probably service center's the only one who would be able to help you now.
Try VurrutRom , when you install it the rom exchange the internal sd with the external sd.
you will see that your /data folder is now in the external sd. I hope this fix your problem.
@ggclanlord: This phone had motherboard issues before but this looks more like a protection to me. No matter which rom I install the applications and their settings just stay there. I might try ext4 later as well.
reivaj20 said:
Try VurrutRom , when you install it the rom exchange the internal sd with the external sd.
you will see that your /data folder is now in the external sd. I hope this fix your problem.
Click to expand...
Click to collapse
How do I change the internal sd with external sd? I have found this but it does not say it needs to be Vurrut. Is it somehow easier with Vurrut?
http://forum.xda-developers.com/showthread.php?t=1088474
First of all, why are you trying to clear any partition manually ?
Second, /data is a separate partition altogether neither on internal sd nor external.
Flash a full xxkpe with pit and re-partitioned checked. Then flash CF-root. Your phone should return to normal.
Generally you should not need to manually format partition ever but in case you need there are options under Advanced in CWM.
Hope it helps!
Good luck !
Caution, ROM flashing newbie.
Hey,
I'm currently considering to flash a ROM on my S5830 (running Cyanogen 7.2 Stable currently) and one of the steps is to mount /data, which I thought could be done in mounts&storage in CWM recovery. My question is what the purpose of this is. Maybe because ROM related data is stored there? Thanks!
P.S. Yes, I have searched the answer for this and no, I couldn't find it.
I'm asking this, so I'll know what its use is, so I'll hopefully can solve related problems elsewhen.
The /data partition contains much of the data pertaining to user settings, contacts, applications, etc. If you were to perform a factory reset, this is the partition in your phone's internal storage that gets wiped clean.
Hmm, okay, but why is /data completely empty when I open it with ES File Explorer (hidden files shown)? And why is this unmounted by default if it's this important? Thanks in advance!
Sent from my GT-S5830 using xda app-developers app
That's because your file manager needs root permission to list the contents. In Terminal Emulator, run "su root" followed by "ls /data", and you'll see lots of stuff in there.
Sent from my SPH-D710
YellowApple said:
That's because your file manager needs root permission to list the contents. In Terminal Emulator, run "su root" followed by "ls /data", and you'll see lots of stuff in there.
Sent from my SPH-D710
Click to expand...
Click to collapse
Many thanks for your quick and clear help, appreciate it.
Only one more thing: why is it unmounted by default, and if it's unmounted, why can I still view it? I think I misunderstand what mounted is.
Currently playing with my Ace S5830 running Cyanogen 7.2 Stable
Remcotjuuh said:
Many thanks for your quick and clear help, appreciate it.
Only one more thing: why is it unmounted by default, and if it's unmounted, why can I still view it? I think I misunderstand what mounted is.
Currently playing with my Ace S5830 running Cyanogen 7.2 Stable
Click to expand...
Click to collapse
Good question. Do you have a link to the directions you're trying to follow for reference? The flashing directions are likely referring to mounting the /data folder/partition outside of the normal Android OS (i.e. via ClockworkMod or from a computer). By default /data should be mounted and accessible from Android (assuming you're using root privileges with your file manager or the "ls" command), else you won't have access to most of your contacts, settings, etc.
YellowApple said:
Good question. Do you have a link to the directions you're trying to follow for reference? The flashing directions are likely referring to mounting the /data folder/partition outside of the normal Android OS (i.e. via ClockworkMod or from a computer). By default /data should be mounted and accessible from Android (assuming you're using root privileges with your file manager or the "ls" command), else you won't have access to most of your contacts, settings, etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1808856
Here's it. The installation procedure can be found under Installation procedure, and mount data really is emphasized. And yes, I can mount /data in CWM recovery under mounts and storage, which gives me the impression it's unmounted now. Actually, the only thing which I CAN unmount is /cache. The others, /data, /system, /sdcard and/ sd-ext, all have the option to be mounted.
And after enabling root access in ES file explorer I indeed could view /data
Yup. Since Droid Ace v2 has files that go in /data (you can tell by the presence of a "data" folder in the root of the ROM's zip if you open it up with a file manager), it needs /data to be explicitly mounted prior to install, since it has to put stuff in there. Most ROMs I've used (like CyanogenMod) only use the /system partition (unless you install gapps).
Not sure why the update script doesn't do the mounting, but since I'm no developer (yet), there might be a very legitimate reason for that.
Sent from my SPH-D710
YellowApple said:
Yup. Since Droid Ace v2 has files that go in /data (you can tell by the presence of a "data" folder in the root of the ROM's zip if you open it up with a file manager), it needs /data to be explicitly mounted prior to install, since it has to put stuff in there. Most ROMs I've used (like CyanogenMod) only use the /system partition (unless you install gapps).
Not sure why the update script doesn't do the mounting, but since I'm no developer (yet), there might be a very legitimate reason for that.
Sent from my SPH-D710
Click to expand...
Click to collapse
That makes sence. One more thing then. As my previous ROM was Cyanogen, I also installed gapps, but I can't remember I mounted /data at that time, and installation simply succeeded. Any thoughts? Maybe because I installed gapps after flashing Cyanogen.
Sorry for the late response. It's possible that the Google Apps update package *does* mount /data in its scripts; I have yet to look into it. Or perhaps it does some intermediate thing where they plop some temp installer somewhere and have Android run said installer. I'll have to find that out
Sent from my SPH-D710
I think I got it. I thought that when flashing the ROM one of the lines said mounting /data, so that could have been part of the scripts.
Sent from my GT-S5830 using xda app-developers app
So I was on CleanROM 5.6 and wanted to give 10.1 a shot. I made a backup and downloaded it to my computer via the ROMManager tool. I ran into 2 issues with 10.1 and decided I'd try again later, so I wanted to flash back to my CleanROM backup that I'd just made. Whether via ROMManager or going straight into recovery the process says it can't open the path to the file. I say the path, as this has occurred with the zip image on internal memory and when I've tried on the SD card.
Soooo, now I'm pretty stuck. Thoughts? I felt like it must have related to the new 4.2 file structure but again, this was an issue whether my zip was on internal memory or the card.
Thanks,
BH
The exact process is:
installing [path]
finding update package.
opending update package.
e: cant open [path] (bad)
installation aborted
CWM says it's leaving a log file but I am not seeing it.
Sounds like your filesystem is like this: "/sdcard/0" and if it is, then do the following:
use Root Explorer or a similar program and navigate to /sdcard/0/ press Menu should give you an option for Multi-Select, select all the folders/files in the /0/ directory, hit menu or down on the bottom choose Move (again depends on the browser) back up one level to the main /sdcard/ directory, and hit Paste. It will tell you there is files with the same information (because the ROM rebuilt the file structure) choose Merge, and let it do its thing. Depending on how many files you have, it may take a little while, just be patient.
Click to expand...
Click to collapse
taken verbatim from here:
http://rootzwiki.com/topic/37316-protip-42-and-recoveries/
I'm going to give it a shot now. I wouldn't have thought this would be an issue restoring since the zip was accessible and I even tried flashing from internal mem, but perhaps it's not as much as issue of reading the file as knowing where to extract the data? We'll see.
All in all, if I could just get 10.1 to stop giving me market errors (920) I'd probably just stick with that at the moment. Alas, have tried all of the interweb's solutions for that too.
Will update, thanks.
So I don't have a /0/ dir on the card, but I do have a /1/. Tried moving the contents of /1/ but it failed. May try another file explorer app (this was via CMs). Interestingly, I was able to flash a ClearnROM install zip, which is 4.1.1 based. Why would that work but the constructed backups wouldn't?
update: I can flash anything else regardless of location, and I am using the latest recovery. def seems like something specific to zip backups made/downloaded via the newest means in ROM Manager
monorailmedic said:
So I don't have a /0/ dir on the card, but I do have a /1/. Tried moving the contents of /1/ but it failed. May try another file explorer app (this was via CMs). Interestingly, I was able to flash a ClearnROM install zip, which is 4.1.1 based. Why would that work but the constructed backups wouldn't?
update: I can flash anything else regardless of location, and I am using the latest recovery. def seems like something specific to zip backups made/downloaded via the newest means in ROM Manager
Click to expand...
Click to collapse
Well if the rom zip is on /sdcard or /extsdcard then it will flash fine. If your backups are on /sdcard/1/ then that's literally the same as /0/. Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Well if the rom zip is on /sdcard or /extsdcard then it will flash fine. If your backups are on /sdcard/1/ then that's literally the same as /0/. Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have a similar problem with my file system after flashing from 4.2 back to 4.1 that has me confused.
I flashed to a TW rom after being on CM10.1, and I was using the most recent TWRP when I originally flashed CM10.1. I had the usual problem that everybody seems to have being that the "0" folder was located on my card. I copied the fold over to my normal sdcard folder (unfortunately I used root browser instead of root explorer, which made this much more painful as it does not have the "merge" ability. Root Explorer - accept no substitutes)
After doing the merge though, I have 2 problems.
#1 - My external SDcard is now listed under "storage."
#2 - There is an Sdcard there called "sdcard0 as well as a "extSdCard" in this storage folder with all the same information as the original "0" folder that was on the internal sdcard. Also a bunch of folders named UsbDriveA, UsbDriveB, etc.
Why did this happen? And how should I set up my folders so that it behaves properly? In other words, what does a normal file system look like?
SlimSnoopOS said:
...Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path...
Click to expand...
Click to collapse
So this is where I am confused, does the zip not contain all of the appropriate backup data within itself, and it is looking elsewhere (in the wrong path) for backup data? This seems odd based on the whole idea as well as the size of the file. If this is not the case, when why is whatever scripting is included in the backup looking for an absolute and not a relative path to the data? It should always be relative to the location of the zip file itself.
I really want to try and understand this.
PeterGunz said:
I have a similar problem with my file system after flashing from 4.2 back to 4.1 that has me confused.
I flashed to a TW rom after being on CM10.1, and I was using the most recent TWRP when I originally flashed CM10.1. I had the usual problem that everybody seems to have being that the "0" folder was located on my card. I copied the fold over to my normal sdcard folder (unfortunately I used root browser instead of root explorer, which made this much more painful as it does not have the "merge" ability. Root Explorer - accept no substitutes)
After doing the merge though, I have 2 problems.
#1 - My external SDcard is now listed under "storage."
#2 - There is an Sdcard there called "sdcard0 as well as a "extSdCard" in this storage folder with all the same information as the original "0" folder that was on the internal sdcard. Also a bunch of folders named UsbDriveA, UsbDriveB, etc.
Why did this happen? And how should I set up my folders so that it behaves properly? In other words, what does a normal file system look like?
Click to expand...
Click to collapse
See my attached photo for what your file system should look like. I'm using ES File Explorer and that's my file system.
What do you mean your external SDcard is listed under Settings/Storage? Both of mine are listed, internal storage is first then my external sd card is second. Care to screenshot what you mean?
monorailmedic said:
So this is where I am confused, does the zip not contain all of the appropriate backup data within itself, and it is looking elsewhere (in the wrong path) for backup data? This seems odd based on the whole idea as well as the size of the file. If this is not the case, when why is whatever scripting is included in the backup looking for an absolute and not a relative path to the data? It should always be relative to the location of the zip file itself.
I really want to try and understand this.
Click to expand...
Click to collapse
If you're using CWM, it saves your backups for internal sd card in: /sdcard/CWM/backup and blobs. For your external sd card, it's saved /extsdcard/CWM/backups and blobs. If you flashed any AOSP 4.2 rom, it moves EVERYTHING from your /sdcard/ path to /sdcard/0. See the difference? Example, your music should be in this path /sdcard/Music but instead it's been moved to /sdcard/0/Music on AOSP 4.2. I get what you're saying how it should be looking for where the zip is BUT the multi-user support completely disrupts our entire thinking of how our file system should be because one user could be "rooted" whereas the other user would be completely stock depending on who signed in. It's too early to expect this to just work since Google introduced this in 4.2. It's a take it or leave it thing.
Sent from my SCH-I535 using xda app-developers app
For a standard backup that makes total sense. My confusion is how this happens with a zip, when all of the backup data is confined to that one archive file (or at least should be).
monorailmedic said:
For a standard backup that makes total sense. My confusion is how this happens with a zip, when all of the backup data is confined to that one archive file (or at least should be).
Click to expand...
Click to collapse
When you made a backup with Rom Manager, it saved to /sdcard, since flashing 4.2, everything on /sdcard moved to /sdcard/1/... Rom Manager and any app honestly would have issues when the file location has changed suddenly and without its express permission. It's not the fault of Rom Manager that it can't find the file to restore your backup. Having an updated TWRP or CWM is supposed to help prevent the /sdcard contents from being merged to /sdcard/0, its not supposed to continue looking for the "new" file destination.
SlimSnoopOS said:
See my attached photo for what your file system should look like. I'm using ES File Explorer and that's my file system.
What do you mean your external SDcard is listed under Settings/Storage? Both of mine are listed, internal storage is first then my external sd card is second. Care to screenshot what you mean?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I can see what I said was confusing.
On the root of my device, among the usual folders, there is one named "sdcard" and another named "storage."
In the "sdcard" folder, all of the folders were empty; however, there is a folder named "0" which contained all of my sdcard contents from my internal sdcard.
In the "storage" folder from the root of my file system, it resembles what you have in your screenshot, except there are no asec and obb folders. In the sdcard folder is a replica of the 0 folder. It contains everything that was in my original internal sdcard. The extsdcard contains everything normally found on my external sd card.
When download something with the stock browser, it defaults to the sdcard folder on the root of file system.
I've attached some screenshots. Let me know what you think and thank you for the help.
PeterGunz said:
Sorry, I can see what I said was confusing.
On the root of my device, among the usual folders, there is one named "sdcard" and another named "storage."
In the "sdcard" folder, all of the folders were empty; however, there is a folder named "0" which contained all of my sdcard contents from my internal sdcard.
In the "storage" folder from the root of my file system, it resembles what you have in your screenshot, except there are no asec and obb folders. In the sdcard folder is a replica of the 0 folder. It contains everything that was in my original internal sdcard. The extsdcard contains everything normally found on my external sd card.
When download something with the stock browser, it defaults to the sdcard folder on the root of file system.
I've attached some screenshots. Let me know what you think and thank you for the help.
Click to expand...
Click to collapse
Oh! This is actually funny, we've been looking at the same thing from two different viewpoints. I see what you mean, /Storage and /sdcard are perfectly normal when you see them on the absolute root file system: "/". I always go to /mnt, that's where I have my file explorer default to open when I launch the app. Sdcard0 = sdcard, and various apps will use the names interchangeably. I have exactly the same paths /sdcard and /Storage, and I do see /Storage/sdcard0 and /Storage/extsdcard along with the same empty USB Drive folders. This is just how the "/" directory is split up. There isn't a duplication of files taking up more space than necessary, it's just showing you another path to get to those files. To reiterate, on "/" you can get to your sdcard contents in at least three paths: /mnt, /sdcard, and also /Storage/sdcard0
All that matters is the /sdcard/0 aka /Storage/sdcard0/0 is GONE. Which, in your original post you said no longer exists correct?
Sent from my SCH-I535 using xda app-developers app
I am still not understanding how there is a problem with executing a zip file that contains all the backup data. It doesn't matter where I move this zip file, as it seems it should be all inclusive of the backup data. Why does it matter the path of this file? What is the script looking for during restoration? Shouldn't it be looking within the archive?
I'm sorry, I feel like a tool, but again, I'm obviously missing some very basic part of what is happening when the file is accessed. As it is all inclusive, why is recovery looking for content anywhere outside of the archive?
monorailmedic said:
I am still not understanding how there is a problem with executing a zip file that contains all the backup data. It doesn't matter where I move this zip file, as it seems it should be all inclusive of the backup data. Why does it matter the path of this file? What is the script looking for during restoration? Shouldn't it be looking within the archive?
I'm sorry, I feel like a tool, but again, I'm obviously missing some very basic part of what is happening when the file is accessed. As it is all inclusive, why is recovery looking for content anywhere outside of the archive?
Click to expand...
Click to collapse
Backups cannot be flashed like other ZIP files. They need to be restored using the restore function of your recovery. The problem is that the CWM restore function is looking for its backups where it puts them (not surprisingly). Android 4.2 moved them to another location and you need to move them back.
SlimSnoopOS said:
Oh! This is actually funny, we've been looking at the same thing from two different viewpoints. I see what you mean, /Storage and /sdcard are perfectly normal when you see them on the absolute root file system: "/". I always go to /mnt, that's where I have my file explorer default to open when I launch the app. Sdcard0 = sdcard, and various apps will use the names interchangeably. I have exactly the same paths /sdcard and /Storage, and I do see /Storage/sdcard0 and /Storage/extsdcard along with the same empty USB Drive folders. This is just how the "/" directory is split up. There isn't a duplication of files taking up more space than necessary, it's just showing you another path to get to those files. To reiterate, on "/" you can get to your sdcard contents in at least three paths: /mnt, /sdcard, and also /Storage/sdcard0
All that matters is the /sdcard/0 aka /Storage/sdcard0/0 is GONE. Which, in your original post you said no longer exists correct?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Correct!
You helped me solve my problem. I was so confused for awhile there.
What should I rename my sdcard after copying everything over from "0"?
I just flashed back to 4.2.1 (AOLP) and I cannot find the contents of my internal sdcard anywhere. In fact, when I check storage on the system settings it only shows that I have a little over 12gbs total space on the internal sdcard. The 8gb I have on TW on the internal sdcard are not recognized by the rom. Any thoughts?