Develop Bugs

Sdcard/0

I just flashed the new 4.2 OTA and it really messed up my Sdcard, Can't restore from backup to minco5 because it moved everything from /sdcard to /sdcard/0 . Anyone know how to disable this "feature"?

Jchapman007 said:
I just flashed the new 4.2 OTA and it really messed up my Sdcard, Can't restore from backup to minco5 because it moved everything from /sdcard to /sdcard/0 . Anyone know how to disable this "feature"?
Click to expand...
Click to collapse
This is default behaviour now due to the multi user capabilities introduced in 4.2 as far as I can tell.

Jchapman007 said:
I just flashed the new 4.2 OTA and it really messed up my Sdcard, Can't restore from backup to minco5 because it moved everything from /sdcard to /sdcard/0 . Anyone know how to disable this "feature"?
Click to expand...
Click to collapse
I also noticed that, I believe this is not related to multiple users feature.. Its kind of first storage.. You can see in all Linux storage are list like 0,1,2,...
To resolve this issue we have to make link in recovery.. So we have to wait clockworkmod release for 4.2
Sent from my Galaxy Nexus using xda app-developers app

sendhiloo7 said:
I also noticed that, I believe this is not related to multiple users feature.
Click to expand...
Click to collapse
You could be right.. the "emulated" folders I note in the file system are related to how Android 4.2 is handling multi-users. Anyway.. smarter people than me are probably best to comment on this next

Try flashing a 4.1.2 rom and check your backups again..
-GNex

Sent from my Galaxy Nexus using xda app-developers app

The developer is aware of the issue: https://plus.google.com/u/1/103583939320326217147/posts/58vuHKcA37d

He flashed an OTA, not AOSP. GN does not "support" multi users. It has to do with the way Google is looking at storage after implementing multi user support. You will not be able to use it on the G-Nexus OTA though. Also, Clockwork needs to be updated.
DONT update to a 4.2 ROM until Koush updates CWM.

And is there a way to remount sdcard back after such update?..

Jchapman007 said:
I just flashed the new 4.2 OTA and it really messed up my Sdcard, Can't restore from backup to minco5 because it moved everything from /sdcard to /sdcard/0 . Anyone know how to disable this "feature"?
Click to expand...
Click to collapse
I had the same problem, but i manager to restore my backup, here is what you have to do:
1- install file manager e.g. Es filemanager..
2- go to /sdcard/0 and find clockmodwork folder
3- Long press on CLockmodwork folder then copy or cut.
4- Go back to /sdcard/ and paste.
5- now reboot to recovery and the phone will see the backup
Note that when copy the folder it will take some time, however it depends on how many backups you have.

Smokeey said:
He flashed an OTA, not AOSP. GN does not "support" multi users. It has to do with the way Google is looking at storage after implementing multi user support. You will not be able to use it on the G-Nexus OTA though. Also, Clockwork needs to be updated.
DONT update to a 4.2 ROM until Koush updates CWM.
Click to expand...
Click to collapse
What about the other custom recovery app TWRP.
Sent from my Galaxy Nexus using xda premium

So...should we move all of our sdcard data to /sdcard/0/...? ES File Explorer doesn't even see the new folder...just the old /sdcard/,

uansari1 said:
So...should we move all of our sdcard data to /sdcard/0/...? ES File Explorer doesn't even see the new folder...just the old /sdcard/,
Click to expand...
Click to collapse
I though the sdcard data is actually located in "/data/media/0/". "/sdcard/" is just symlink from there.

polaris441 said:
I though the sdcard data is actually located in "/data/media/0/". "/sdcard/" is just symlink from there.
Click to expand...
Click to collapse
Lol... I just realized that after exploring further. You're right. Problem solved.

uansari1 said:
Lol... I just realized that after exploring further. You're right. Problem solved.
Click to expand...
Click to collapse
I get an error on restoring system partition...so restoring my cm10 backup is a nonono
Verstuurd van mijn Galaxy Nexus met Tapatalk

I move file or folder from /sdcard/0/ to /sdcard/ my Go backup work agian.
Sent from my Galaxy Nexus using xda premium

Man I wish I'd known this before. But that's the name of the game when you flash............

Yeah, I got burned on that too

This will all be resolved once recoveries catch up.

Supermanpa said:
Yeah, I got burned on that too
Click to expand...
Click to collapse
The solution is simple, took me forever to copy my backup:
http://forum.xda-developers.com/showthread.php?t=1995585
1. Keep the files where they are and increase the number of 0 directories every time we install a new rom.
2. Use the new Twrp and live with folder 0.
3. Move all our file from 0 folder back to sdcard with a file manager.

CWM problem

I am dealing with some issues here. I have a nandroid of CM10 from a just a couple of days ago, before I f'ed up my phone. The problem is that CWM can't seem to find its own backup?? I keep getting "Couldn't open directory", "No files found". Has anyone else had this issue??
It is the same version of CWM that I used to make the back up in the first place. Very frustrating.

is it the new version of CWM? did you move the backup off your phone then back on to it? if so, did you remember the blob folder?

U on 4.2?
Sent from my Galaxy Nexus using Tapatalk 2

waveboy said:
U on 4.2?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This is same prob for me. I went to 4.2 from jbsourcery but want to go back and i get the same problem. cwm 6.0.1.0
I think there is a newer version of cwm so im going to try that first. but when i go to flash zip from sd card it says
0/
legacy/
obb/
not sure if that has anything to do with it though.....?

myboyblake said:
This is same prob for me. I went to 4.2 from jbsourcery but want to go back and i get the same problem. cwm 6.0.1.0
I think there is a newer version of cwm so im going to try that first. but when i go to flash zip from sd card it says
0/
legacy/
obb/
not sure if that has anything to do with it though.....?
Click to expand...
Click to collapse
Nope same problem with updating to 6.0.1.5.

There are new mounting points in 4.2 because of multi-user-support.
Main user entry point is now /sdcard/0/ folder on your internal storage, all data is moved in there. So you have to manually copy and paste your backups to fit the folder where your custom recovery is expecting those backups.

LuckOne79 said:
There are new mounting points in 4.2 because of multi-user-support.
Main user entry point is now /sdcard/0/ folder on your internal storage, all data is moved in there. So you have to manually copy and paste your backups to fit the folder where your custom recovery is expecting those backups.
Click to expand...
Click to collapse
but all 3 of those points have the same data...I can't copy from legacy to /0 or obb. They all have the backups there. i can't mount sdcard in recovery though....I think the only way is to flash a 4.1 ROM and then do a restore until a recovery comes out with 4.2 mounting support. Am I correct here?

You wouldn't have this problem if you just used TWRP

Sandman-007 said:
You wouldn't have this problem if you just used TWRP
Click to expand...
Click to collapse
my idea didnt work with switching to 4.1 rom. But sandman, the backups from CWM won't work in TWRP though right?

myboyblake said:
my idea didnt work with switching to 4.1 rom. But sandman, the backups from CWM won't work in TWRP thought right?
Click to expand...
Click to collapse
yeah they wont

Sandman-007 said:
You wouldn't have this problem if you just used TWRP
Click to expand...
Click to collapse
well i installed twrp and the restore files still don't come up....i think its time to forget this until cyanogen comes out with a fix for this.....

myboyblake said:
well i installed twrp and the restore files still don't come up....i think its time to forget this until cyanogen comes out with a fix for this.....
Click to expand...
Click to collapse
Cwr backups don't work with TWRP
Edit: sorry didn't see k786 post

Copy your /sdcard/clockworkmod/backup to /data/media/clockworkmod/backup
This is where your stuff is mounted in 4.2
After restoring you will still have problems though. All you stuff that used to be in /sdcard will now be in /sdcard/0 so many things won't work. Again copy or move all contents of /sdcard/0 to /sdcard and you are back to how it was.
I did all the copying from Terminal Emulator because file explorers could not see anything inside /data/media but it's there. Typing 'su' first and then using 'ls' in Terminal Emulator will show what is in there, so use it. Use 'cp - r' to copy the folder. Needless to say you need to be rooted for this.

meranto said:
Copy your /sdcard/clockworkmod/backup to /data/media/clockworkmod/backup
This is where your stuff is mounted in 4.2
After restoring you will still have problems though. All you stuff that used to be in /sdcard will now be in /sdcard/0 so many things won't work. Again copy or move all contents of /sdcard/0 to /sdcard and you are back to how it was.
I did all the copying from Terminal Emulator because file explorers could not see anything inside /data/media but it's there. Typing 'su' first and then using 'ls' in Terminal Emulator will show what is in there, so use it. Use 'cp - r' to copy the folder. Needless to say you need to be rooted for this.
Click to expand...
Click to collapse
None of that is necessary with TWRP, it just works like normal on JB 4.2 lol
Sent from my Galaxy Nexus using xda premium

myboyblake said:
but all 3 of those points have the same data...I can't copy from legacy to /0 or obb. They all have the backups there. i can't mount sdcard in recovery though....I think the only way is to flash a 4.1 ROM and then do a restore until a recovery comes out with 4.2 mounting support. Am I correct here?
Click to expand...
Click to collapse
Copy your /sdcard/clockworkmod/backup to /data/media/clockworkmod/backup
This is where your stuff is mounted in 4.2
Click to expand...
Click to collapse
Exactly!
None of that is necessary with TWRP, it just works like normal on JB 4.2 lol
Click to expand...
Click to collapse
Yes, but only since the new TWRP-Version. With installed older versions you get same issues as with cwm.

new /0 after every new ROM flash

every time I flash a new rom I get a new 0 folder. Right now I have my titanium backups on /0/0/0. Wtf google??
How to solve this?

There are many, many threads on this.

Thanks for the solution.

U need to upgrade to the newest clockwork mod or twrp. They both have the fix for that now.
Sent from my Galaxy Nexus using xda premium

This keeps happening every single rom I flash also. And I am on the las test TWRP release for my VZW Gnex. Any other suggestions?
Sent from my Galaxy Nexus using xda premium

jumpman1229 said:
This keeps happening every single rom I flash also. And I am on the las test TWRP release for my VZW Gnex. Any other suggestions?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This problem has been fixed in TWRP 2.3.2.1 here so ensure that you are running this version not an older one.
Or you may download GooManager from Play Store then install the latest TWRP recovery from it to ensure that you get the latest version

ahmadallica said:
This problem has been fixed in TWRP 2.3.2.1 here so ensure that you are running this version not an older one.
Or you may download GooManager from Play Store then install the latest TWRP recovery from it to ensure that you get the latest version
Click to expand...
Click to collapse
Yup! I'm on 2.3.2.1 which is the latest for the VZW Gnex (toro) and I still have that 0 folder problem every single time I flash a new 4.2 ROM. I even move all the contents of /data/media/0 to /data/media such as my Titanium Backup folders and it simply can't find the files. I noticed every boot up the 4.2 roms also make new "Android" and "Music" and "Movies" folders and when you delete them, the browser, gallery and other things won't work. This is very frustrating. I've searched high and low and I seem to be finding the same answer. Make sure you are on the latest TWRP and that'll fix the problem. It hasn't. Any other suggestions?
Sent from my Galaxy Nexus using xda premium

jumpman1229 said:
Yup! I'm on 2.3.2.1 which is the latest for the VZW Gnex (toro) and I still have that 0 folder problem every single time I flash a new 4.2 ROM. I even move all the contents of /data/media/0 to /data/media such as my Titanium Backup folders and it simply can't find the files. I noticed every boot up the 4.2 roms also make new "Android" and "Music" and "Movies" folders and when you delete them, the browser, gallery and other things won't work. This is very frustrating. I've searched high and low and I seem to be finding the same answer. Make sure you are on the latest TWRP and that'll fix the problem. It hasn't. Any other suggestions?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Actually I have a GSM GNex and I can confirm that the 0 folder problem is fixed with me using the latest TWRP (2.3.2.1). Check here for the thread of TWRP at the Verizon section maybe you can find why you still have the 0 folder problem
Regarding Titanium backup, this software is great and you can choose where to let it look for the backup instead of the regular /sdcard/TitaniumBackup/ location. All you have to do is:
1- Start/Run Titantium Backup
2- Go to Settings (the three upper right vertical dots)
3- Select "Preferences"
4- Under "BACKUP SETTINGS", click the first option which is "Backup folder location"
5- Click on "DETECT!"
6- Choose "SD card"
Then automatically it will search your SD card for the Titanium Backup and display it all for you.
Hope this helps

ahmadallica said:
Actually I have a GSM GNex and I can confirm that the 0 folder problem is fixed with me using the latest TWRP (2.3.2.1). Check here for the thread of TWRP at the Verizon section maybe you can find why you still have the 0 folder problem
Regarding Titanium backup, this software is great and you can choose where to let it look for the backup instead of the regular /sdcard/TitaniumBackup/ location. All you have to do is:
1- Start/Run Titantium Backup
2- Go to Settings (the three upper right vertical dots)
3- Select "Preferences"
4- Under "BACKUP SETTINGS", click the first option which is "Backup folder location"
5- Click on "DETECT!"
6- Choose "SD card"
Then automatically it will search your SD card for the Titanium Backup and display it all for you.
Hope this helps
Click to expand...
Click to collapse
It worked! You are a life saver! Didn't know I could point Titanium to another location. That's exactly what I needed. Thanks
Sent from my Nexus 7 using xda premium

Any idea how to access cwm nandroid backups too? I cant find them anywhere (but i see them in cwm)

tylerdurden83 said:
Any idea how to access cwm nandroid backups too? I cant find them anywhere (but i see them in cwm)
Click to expand...
Click to collapse
If CWM is unable to find the nandroid backup because it is moved within the new 0 folder(s), then here is what I have done when I was in the same problem :
1- Download any file explorer (I used ES File Explorer)
2- CUT (or copy if you have a lot of free storage) the "clockworkmod" folder from within the 0 Folder(s) and paste it to the main /sdcard/ location, so both the 0 Folder and the clockworkmod folder will be at /sdcard/ location now.
3- Reboot into recovery and CWM should find the nandroid backup because it is back to its correct place as it was before being moved into the 0 Folder.
I recommend that you make a copy of the clockworkmod folder to your PC before attempting any of the above steps just in case something went wrong while copying or cutting (moving) the folder so you can try copying it again. In other words, make a backup of this clockworkmod backup
Hope this helps

ahmadallica said:
If CWM is unable to find the nandroid backup because it is moved within the new 0 folder(s), then here is what I have done when I was in the same problem :
Click to expand...
Click to collapse
I think that I expressed myself wrong. If i go into cwm, and click restore, i see two cwm backups no problem. But, with a file explorer with root priviledges, they are literally nowhere to be found, i checked everywhere....

tylerdurden83 said:
I think that I expressed myself wrong. If i go into cwm, and click restore, i see two cwm backups no problem. But, with a file explorer with root priviledges, they are literally nowhere to be found, i checked everywhere....
Click to expand...
Click to collapse
Oh sorry for misunderstanding you earlier.
I haven't encountered this before but you may try a file explorer which has a search function (such as ES File Explorer) so you search for "clockworkmod" folder or something in the whole sdcard. I hope it will find the backups for you this way.

tylerdurden83 said:
I think that I expressed myself wrong. If i go into cwm, and click restore, i see two cwm backups no problem. But, with a file explorer with root priviledges, they are literally nowhere to be found, i checked everywhere....
Click to expand...
Click to collapse
How everywhere did you get? They must be there somewhere...
Did you try under
/mnt/sdcard
? That's the actual directory, the various others are symlinks to it.

Clancy_s said:
How everywhere did you get? They must be there somewhere...
Did you try under
/mnt/sdcard
? That's the actual directory, the various others are symlinks to it.
Click to expand...
Click to collapse
/mnt/sdcard is a symlink. The physical file location is /data/media (or /data/media/0 in 4.2 and higher).
Edit: Specifically, the physical internal storage is found at /data/media.
/data/media is fuse mounted as /mnt/shell/emulated.
/mnt/shell/emulated/0 is then symlinked to /storage/emulated/legacy.
/storage/emulated/legacy is then symlinked to /sdcard, /mnt/sdcard, and /storage/sdcard0.
So the files seen in /sdcard are files physically located at /data/media/0. As such, files in /data/media can use space, but not be seen when looking in /sdcard.

help
ahmadallica said:
If CWM is unable to find the nandroid backup because it is moved within the new 0 folder(s), then here is what I have done when I was in the same problem :
1- Download any file explorer (I used ES File Explorer)
2- CUT (or copy if you have a lot of free storage) the "clockworkmod" folder from within the 0 Folder(s) and paste it to the main /sdcard/ location, so both the 0 Folder and the clockworkmod folder will be at /sdcard/ location now.
3- Reboot into recovery and CWM should find the nandroid backup because it is back to its correct place as it was before being moved into the 0 Folder.
I recommend that you make a copy of the clockworkmod folder to your PC before attempting any of the above steps just in case something went wrong while copying or cutting (moving) the folder so you can try copying it again. In other words, make a backup of this clockworkmod backup
Hope this helps
Click to expand...
Click to collapse
i flashed PA rom for first time, using TWRP and now i cant find Nandroid backup, any suggestion where can i find it

aNewNoob said:
i flashed PA rom for first time, using TWRP and now i cant find Nandroid backup, any suggestion where can i find it
Click to expand...
Click to collapse
Did you do your nandroid backup using CWM? If yes, then it will not be compatible with TWRP.
Did you use the latest TWRP 2.3.2.1 ? If not then your nandroid backup should be in sdcard/0/ after flashing PA with android 4.2 so TWRP will no longer find it. You have to copy or move the TWRP folder from within "0 Folder" to the main sdcard/ location then TWRP will recognize it again. And remember to update your TWRP to the latest version to avoid this problem again.
I hope I have covered most of the possibilities regarding your case. If not then please provide more details

Cilraaz said:
/mnt/sdcard is a symlink. The physical file location is /data/media (or /data/media/0 in 4.2 and higher).
Edit: Specifically, the physical internal storage is found at /data/media.
/data/media is fuse mounted as /mnt/shell/emulated.
/mnt/shell/emulated/0 is then symlinked to /storage/emulated/legacy.
/storage/emulated/legacy is then symlinked to /sdcard, /mnt/sdcard, and /storage/sdcard0.
So the files seen in /sdcard are files physically located at /data/media/0. As such, files in /data/media can use space, but not be seen when looking in /sdcard.
Click to expand...
Click to collapse
My /data seems empty...
Same for /mnt/shell...
/storage/emulated/legacy isn't, i see the sdcard content there, but no cwm folder

ahmadallica said:
Did you do your nandroid backup using CWM? If yes, then it will not be compatible with TWRP.
Did you use the latest TWRP 2.3.2.1 ? If not then your nandroid backup should be in sdcard/0/ after flashing PA with android 4.2 so TWRP will no longer find it. You have to copy or move the TWRP folder from within "0 Folder" to the main sdcard/ location then TWRP will recognize it again. And remember to update your TWRP to the latest version to avoid this problem again.
I hope I have covered most of the possibilities regarding your case. If not then please provide more details
Click to expand...
Click to collapse
So I just got the chance to flash a 4.2 and like I said it created a new 0 folder under data/media/0. I deleted the 0 folder so I would only have data/media but when I go to open the browser it doesn't do a thing. Even the gallery. And when I reboot, I see it creates the same folders I just deleted. What gives?
Sent from my Galaxy Nexus using xda premium

jumpman1229 said:
So I just got the chance to flash a 4.2 and like I said it created a new 0 folder under data/media/0. I deleted the 0 folder so I would only have data/media but when I go to open the browser it doesn't do a thing. Even the gallery. And when I reboot, I see it creates the same folders I just deleted. What gives?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have no idea why your TWRP on your verizon GNex is not helping you get rid of these 0 folders. I checked the changelog of TWRP 2.3.2.1 for the thread at the Verizon section and the Original (GSM) section and they are identical!
Anyway I have never deleted or do anything to data/media/ even for 0 Folders. I used to move the data from within the /sdcard/0/ location to /sdcard/ then delete this 0 folder on the sdcard, nothing else. I checked my 4.2 GNex now and yes there is a 0 folder in data/media/ but this is not affecting my sdcard and how apps like Titnatium and TWRP are finding the backups and related files.
You may find this guide useful as well

Can't restore?! Please help

I rooted my phone today and did a CWM backup - I then flashed CM10 and then tried to do a restore but when I try it I get the following error "Couldn't open directory, No files found"
Yet when I browse my files I can see the back up I made in the CWM folder - why won't it restore this?
Any thoughts?
Thanks in advance!

jackryan57 said:
I rooted my phone today and did a CWM backup - I then flashed CM10 and then tried to do a restore but when I try it I get the following error "Couldn't open directory, No files found"
Yet when I browse my files I can see the back up I made in the CWM folder - why won't it restore this?
Any thoughts?
Thanks in advance!
Click to expand...
Click to collapse
Hmm...not sure if it's related, but the only time my CWM backup didn't restore was some MD5 mismatch error. I renamed the backup to "backup.tar" (if you're using *.tar and not /blobs) after I read that worked on a thread, and wala, it worked! Unsure if that's what your issue is, though.

ikjadoon said:
Hmm...not sure if it's related, but the only time my CWM backup didn't restore was some MD5 mismatch error. I renamed the backup to "backup.tar" (if you're using *.tar and not /blobs) after I read that worked on a thread, and wala, it worked! Unsure if that's what your issue is, though.
Click to expand...
Click to collapse
I just tried what you said and it still doesn't work - I did notice that my backup is a file folder not just a file - so I don't think renaming the folder to a .tar will actually do anything to it?

Is there any other way to restore from a back up I have on my phone but that CWM doesn't seem to see??

You could try moving the file with a file manager or make sure permissions are good.
Sent from my SAMSUNG-SGH-I747 using xda premium

Push it with Odin? Or just grab the stock rooted file from the stickies and push that with Odin.
Sent from my SGH-I747 using xda app-developers app

What would I be looking for as far as permissions go?

jackryan57 said:
I just tried what you said and it still doesn't work - I did notice that my backup is a file folder not just a file - so I don't think renaming the folder to a .tar will actually do anything to it?
Click to expand...
Click to collapse
Hmm..it's been a while since CWM--do you have any folder called blobs? If so, then my tip to rename to "backup.tar" won't work. Basically, you're right. If you don't have a *.tar backup, then I got nothing. CWM used to be *.tar only, then defaulted to /blobs, and now is defaulting back to *.tar with the option of /blobs.

join the club...
http://forum.xda-developers.com/showthread.php?t=2101424
No idea what's going on with this crap. I've lost every backup now for two weeks, the worst of which was my stock backup.

i may have ended up finding a solution to the problem here, if yours is similar enough to mine.
http://forum.xda-developers.com/showthread.php?t=2101424

EFS Partition Backup and More [All G2 Variants]

LG G2 EFS Backup Zip
Background
The G2 has no built in EFS backup partitions. EFS contains things like your MEID or IMEI... your data profiles.. radio settings. The EFS cannot be replaced... it is unique to your phone only... backing up your OWN EFS is highly recommended.
I have added EFS backup to the IOroot scripts so that everyone that roots will have a copy of their EFS partitions on the computer you run IOroot from. Regardless, this current thread will still be a good "heads up" and an alternative for those who insist on using other shady root methods or for those who just want another way to back things up. ​Backing up EFS
In TWRP, flash the LG_G2_Backup_EFS.zip attached in this thread. LG_G2_Backup_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/. Please check to make sure the backup zip worked and actually made a .zip file. Any issues please list what recovery and version you are using and please post the recovery.log.
Backup your efsbackupflashable.zip somewhere else besides your internal SD!!! Email.. cloud.. PC..
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflashable.zip in your /sdcard/EFS_Backup folder.
If flashable zip wasn't created or to manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
​
Backup ALL Partitions
Well almost all... I am attaching another zip which backs up most of your phones partitions.. excluding system/data/cache and some other useless partitions. Backing up all partitions isn't as important as backing up the EFS but it can't hurt. Never know when you may need it.. especially those who like to poke around with their phone and try new things.
Run the zip in recovery.. it will make backup .img files on your internal sdcard in a new folder named "backupz"... remember to copy your backups off the internal sdcard.​

Wow nice find and quick work! I wonder what the chances are of messing you current info up, so your backup would actually be necessary?

drkow19 said:
Wow nice find and quick work! I wonder what the chances are of messing you current info up, so your backup would actually be necessary?
Click to expand...
Click to collapse
Even if the chances are really small, it is always nice to have a backup.
Having to restore with QPST or other similar methods is not fun at all.

Thanks autoprime.
this was pretty fast considering i just saw you post this in irc

I'm on Verizon. It did make a folder but it was empty. No zip inside. Checked with es file explorer

bckrupps said:
I'm on Verizon. It did make a folder but it was empty. No zip inside. Checked with es file explorer
Click to expand...
Click to collapse
Same situation here.

bckrupps said:
I'm on Verizon. It did make a folder but it was empty. No zip inside. Checked with es file explorer
Click to expand...
Click to collapse
jasonsf said:
Same situation here.
Click to expand...
Click to collapse
hmm k... this happened on the LG OG as well... then some people had it working on CWM.. some people had to flash an AOSP rom first.. seems random. If someone can provide me the recovery.log after flashing the efs zip that would help. I'm going to bet its an issue with 7z packing the zip the new flashable zip for some reason or another.
i uploaded a new zip which will still try to make the flashable zip.. while also backing up the individual efs partitions.
redownload the new zip to backup efs img files.
To manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st2

autoprime said:
hmm k... this happened on the LG OG as well... then some people had it working on CWM.. some people had to flash an AOSP rom first.. seems random. If someone can provide me the recovery.log after flashing the efs zip that would help. I'm going to bet its an issue with 7z packing the zip the new flashable zip for some reason or another.
i uploaded a new zip which will still try to make the flashable zip.. while also backing up the individual efs partitions.
redownload the new zip to backup efs img files.
To manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modem_st2
Click to expand...
Click to collapse
I have the recovery boot loop issue and was just using your zip to test out ADB Sideload in TWRP. I'll wait until my phone is working before I give your tool another try. Too many variables right now.
Jason

For w/e its worth this is not working on my att g2. There does not appear to be a /tmp folder
also on att the paths should be
/dev/block/platform/msm_sdcc.1/by-name/modemst1
/dev/block/platform/msm_sdcc.1/by-name/modemst2
(no "_")

jasonsf said:
Same situation here.
Click to expand...
Click to collapse
Same thing happens to me on VZW. Here is the recovery.log
http://pastebin.com/jhyHJ0Yz

jug6ernaut said:
For w/e its worth this is not working on my att g2. There does not appear to be a /tmp folder
also on att the paths should be
/dev/block/platform/msm_sdcc.1/by-name/modemst1
/dev/block/platform/msm_sdcc.1/by-name/modemst2
(no "_")
Click to expand...
Click to collapse
I can confirm this information on my AT&T G2. Maybe the script can be modified as such (unconfirmed):
Code:
# backup partitions
EFS_PREFIX=modem_st # Assume Verizon model (with underscore)
if [ -e /dev/block/platform/msm_sdcc.1/by-name/modemst1]; then # Use AT&T model nomenclature
EFS_PREFIX=modemst
fi
/sbin/busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/${EFS_PREFIX}1 of=/tmp/efs1.img;
/sbin/busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/${EFS_PREFIX}2 of=/tmp/efs2.img;

jug6ernaut said:
For w/e its worth this is not working on my att g2. There does not appear to be a /tmp folder
also on att the paths should be
/dev/block/platform/msm_sdcc.1/by-name/modemst1
/dev/block/platform/msm_sdcc.1/by-name/modemst2
(no "_")
Click to expand...
Click to collapse
Ugh.. sorry about this. I must have been in HTC mode.. they use the "_" derpppp.
updated the zip.. see how that goes.

mine did not create a .zip file. On At&t, but still thanks a ton! will keep these two efs.img's stored on my dropbox so that I always have a backup.
Anyway to make these two into a flashable zip manually? I'm sure the code is in the script somewhere I just don't feel like looking haha

This now works for me autoprime. It created efs1.img, and efs2.img on VZW. Thx!

Got my two image files, both 3mb....thanks! I am on ATT.

im on verizon. works great. kudos

Confirm works on ATT.
Sent from my LG-D800 using Tapatalk 2

I have updated the zip in the OP... it now creates a proper flashable backup zip as well as teh 2 efs img files.
thanks to @jug6ernaut for testing all of my broken zips :highfive:

In TWRP the zip fails every time..... attached photo of error.
Sent from my VS980 4G using XDA Premium HD app

anyone else have the error that @mouf32 is having? I have some users on IRC that say it's working just fine. And there's been 50+ downloads with no other issues.
@mouf32 have you tried to redownload the file? maybe the zip got messed up or is corrupted?