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?
Alrighty, so I know that going from ics to a jb rom it moves your internal storage to /0/ or /emulated(I don't have my phone in front of me right now, so I don't know exactly what it is)
But I was wondering if there was a way to move everything to where it is normally on a jb rom
Reason behind this question is because if I go to /0/ there's another /0/0/ etc...
It's just getting confusing.
Maybe a script that moves everything?
Or would it be easier to back everything up and just to a complete internal wipe etc.. on it?
Thanks!
If it's just for convenience, then you could just move the folder, change the owner and permissions back to default and rename it. On my GS3, the location is /storage/sdcard0, but it's not a big deal because I have /sdcard linked to /storage/sdcard0.