I'm recently soff using the moonshine method. I've been playing around with different ROMs and recently flashed a 4.2.2 ROM Jellybeer (I think it was.) I had a gnex before the DNA and remember that 4.2.2 changes the file structure somehow and adds a folder "0" in you sdcard partition. I played with Jellybeer and decided to go back to Viper Rom and after booting into recovery my backups where gone. Remembering from my gnex flashing that the file structure changes I booted back into jellybeer and used root explorer and saw that I now had a folder "0" on the sdcard partition with my files in it. After searching in just the sdcard partition I found my backups in the TWRP folder. (I'm using the touchwork mod recovery). I had to move them to the "0" folder, then TWRP folder in order to see them in recovery. Also, I use titanium for some backup of apps which I had to direct titanium to see them in the new "0" folder. Now, when I reboot into recovery to flash something or backup/restore something it has to be in the "0" folder. Is there a way to revert this? or an RUU to flash the device back to stock? I know in 4.2.2, this is the way the file structure is going to be to allow the use of user accounts so each user has there own folder. I remember on the gnex that the CWM recovery was modified to take this into account so backups wouldn't get lost.
Also, let this be a warning for those flashing 4.2.2 roms, the file structure gets changed and if you don't know how to get them back you might get stuck.
Anyway, anyone have a solution for this? Thanks
hobby31 said:
I'm recently soff using the moonshine method. I've been playing around with different ROMs and recently flashed a 4.2.2 ROM Jellybeer (I think it was.) I had a gnex before the DNA and remember that 4.2.2 changes the file structure somehow and adds a folder "0" in you sdcard partition. I played with Jellybeer and decided to go back to Viper Rom and after booting into recovery my backups where gone. Remembering from my gnex flashing that the file structure changes I booted back into jellybeer and used root explorer and saw that I now had a folder "0" on the sdcard partition with my files in it. After searching in just the sdcard partition I found my backups in the TWRP folder. (I'm using the touchwork mod recovery). I had to move them to the "0" folder, then TWRP folder in order to see them in recovery. Also, I use titanium for some backup of apps which I had to direct titanium to see them in the new "0" folder. Now, when I reboot into recovery to flash something or backup/restore something it has to be in the "0" folder. Is there a way to revert this? or an RUU to flash the device back to stock? I know in 4.2.2, this is the way the file structure is going to be to allow the use of user accounts so each user has there own folder. I remember on the gnex that the CWM recovery was modified to take this into account so backups wouldn't get lost.
Also, let this be a warning for those flashing 4.2.2 roms, the file structure gets changed and if you don't know how to get them back you might get stuck.
Anyway, anyone have a solution for this? Thanks
Click to expand...
Click to collapse
You don't think that maybe your "question" should go in..........the Q&A Section?
Moved to Q&A
hobby31 said:
Anyway, anyone have a solution for this? Thanks
Click to expand...
Click to collapse
Check out the TWRP thread in original development (last couple pages). Beaups provided a couple different solutions to return the file structure back to 4.1.x
http://forum.xda-developers.com/showthread.php?p=40600897
Sent from my HTC6435LVW using Tapatalk 4 Beta
Related
just rooted my evo3d, everything went great and i even git CWM to install the first time correctly. heres where i think i went wrong-
i downloaded rom manager and i attempted to use it and it worked great. to me it seemed like it worked because i was able to choose my phone and even flashed the CWM over the original one i had. i made a backup of my stock rom and tried a rom from the dev forum, didnt like it and tried to switch back and got the MD5 mismatch error when i tried to restore my stock rom. now, i thought i would try to flash the original CWM which was blue over the CWM(orange) and then attempted to get the rom to restore. that was also a fail. what can i do? i read that installing busy box could effect this? any help would be appreciated.
sucks but it happens download the RUU from here and reroot if you need too
FIXING MD5 MISMATCH
adb shell
# cd /sdcard/clockworkmod/backup/name_of_backup
# rm nandroid.md5
# md5sum *img > nandroid.md5
gaaah i dont have ADB installed on my mac. is there not a simpler way? anyway to fix this?! i dont think i need to reroot honestly..
Nope sorry.
I may have found a way to fix the MD5 issue.
Well, it worked for mine.
I saved a backup of the stock ROM before I installed the needle kernel.
it was named 2011-08-01-23.53.47
The I saved another backup of the ROM with the needle kernel/
it was named 2011-08-02-19.06.28 w/ needlekernel
What happened was that on the sd card the backup folder was named 2011-08-02-19.06.28 w/ then inside that folder was another folder named needlekernel . And that folder contained the backup files.
It seems that putting the space in the name caused it to create another folder within the backup folder instead of just having the backup files in there. I kept getting the MD5 mismatch when I tried to restore that backup.
So I took the files out of the needlekernel folder and put them in the 2011-08-02-19.06.28 w/ folder. I then deleted the needlekernel folder. The last thing was to take the (space)w/ off of the end of the folder name so it was just as the program named it to begin with.. 2011-08-02-19.06.28
After doing that I was able to restore the backup through ROM Manager. So apparently it's best not to add anything to the backup name when saving it.
One other thing I'll mention. When I restored the backup with the needle kernel in it it put the stock kernel back in the ROM.
Hope this helps anyone with the MD5 issue.
So I've made a couple Nandroid Backups and I am unable to find them in any of my directories. The reason I ask is because I'd like to rename a couple of them before I forget what I was running. I usually use ROM Manager (i know.. this is the only thing i use it for) to rename my backup files. It's just easy that way. RM isn't seeing my recent backups.. I dl'd CWM Manager app and it sees the backups if I go into "restore".. but there is no way to rename them. Also.. when i go into my phones files and into clockworkmod folder.. i still only see a couple old backups.. none of my new ones are anywhere to be found.
So i guess I'm wondering wtf the backups went to, and how do i find them in my directory? Thanks, appreciate any info I get
also if someone has a good alternative to ROM Manager for renaming backup files.. I would appreciate that as well, thanks guys!
I get the option of backing up to either sd or ex_sd. I don't suppose that gotcha?
As far as renaming, I use the ancient method of keeping a separate .txt file with the nandroid name appended with ROM and kernel. I have to edit the text file when I change ROMs or kernels, but all un-appended backups subsequent to the last appended ROM/kernel are still from that preceding combination.
Capiche?
geomax45 said:
I get the option of backing up to either sd or ex_sd. I don't suppose that gotcha?
As far as renaming, I use the ancient method of keeping a separate .txt file with the nandroid name appended with ROM and kernel. I have to edit the text file when I change ROMs or kernels, but all un-appended backups subsequent to the last appended ROM/kernel are still from that preceding combination.
Capiche?
Click to expand...
Click to collapse
I've haven't gotten the option to where my backups are kept. Regardless I'm still unable to find the backups anywhere I'm my directory.
sent from my Galaxy SII
Backups are in clockworkMod folder. in /sdcard or sdcard/external_sd/ depending on your kernal. the newer kernals have external sdcard as an option.
Strange that you cant find them. Delete the CWM folder and take another backup?
Maybe sdcard is full and backups arent getting saved?
MotoMudder77 said:
Backups are in clockworkMod folder. in /sdcard or sdcard/external_sd/ depending on your kernal. the newer kernals have external sdcard as an option.
Strange that you cant find them. Delete the CWM folder and take another backup?
Maybe sdcard is full and backups arent getting saved?
Click to expand...
Click to collapse
It is strange. Both my SD cards have plenty of space. The part that bugs me is that the app CWM Manager see's the backups if I choose restore, but yet I cannot find those files ANYWHERE in my phone. Believe me I've opened my clockworkmod folder countless times hoping to see them. When I boot into recovery and choose restore.. I only see the two new ones... then to get the old backups in recovery I have to choose restore from external SD. So My backups are there on the phone. They are just hiding somewhere and I have no idea where else to look. I'm really just trying to rename them. I know where to find em in recovery if I need to.. but it's bugging me I don't know where to find em in my phone directory.
Have you tried another file manager?
Sent from my GT-I9100 using xda premium
geomax45 said:
Have you tried another file manager?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I've tried using RootExploer as well as the stock file manager app. Even when I plug the phone into my PC via USB and search that way I cannot find the backups. Its driving me mad LOL
Not sure it should make too much of a difference but 1 of the two "missing" backups was taken with stock illusion kernel, the other backup I'm missing was taken with the new Siyah kernel 2.6.11.
sent via Galaxy SII
Backups SHOULD be in:
/sdcard/clockworkmod/backup
or
/emmcs/clockworkmod/backup (which is /sdcard/external_sd/clockworkmod/backup on Samsung firmwares - when in CWM itself it's /emmc, same for CM7)
So.. after days of confusion I found the files.. thanks to everyone for replying. There was another "clockworkmod" folder in my external SD card. I didn't realize that as I kept opening up the first clockworkmod folder I saw... at the very bottom. Below my music, with a couple other zips, was the other clockworkmod folder... same as the one on my SD card- clockworkmod> backup> ..zips!
FINALLY!
thank for all the replies!
So I recently S-Off'd and unlocked my DNA thanks to the great work of the moonshine team. I've flashed and stuff before with my old incredible, I used CWM recovery with that too. I liked it on my INC so that's my recovery of choice on the DNA. But appears stuff has changed. Basically:
- I can't just pluck my backups to and from the SDcard anymore, and I figured out how to get them off, but the "free" way requires some ADB commands I couldn't quite locate. Basically, how do I pull the backups using ADB?
- .zip files and such don't show up in CWM recovery. Before I flashed a new ROM, on stock, when in CWMR the files would show up and I would proceed like usual. Now (I was on the latest CM build) I put a PAC zip on the root of the SDcard went into CWRM but it wouldn't show up. Not even in CM file manager app. But If i plugged it in to a PC it would show up. BUT after I flashed CM, the CM and gApps zips were not visible anywhereoutside of CWMR. Eventually, the only way i could install PAC was through sideloading it through ADB per CWMR. Basically, Zips don't show up where they are supposed to all of the time.
Lastly, this is just a general question, but I pressed the factory reset/wipe data option in CWRM, but photos and music, and a few files on the root of the SDcard still carried over. Is this normal? I went from CM10.1 to a clean install of PAC.
Thanks all!
Edited my first post for clarity, hopefully explains the questions better.
Probably because CM10.1 is Android 4.2.2; which supports profiles. Thus, it creates a /0 folder on the sdcard where all the other directories are placed.
When you switch between Sense ROMs and AOSP, you need to be aware of the difference between the sdcard layout of 4.1.1 and 4.2.2 or you'll never find all of your files.
The issue isn't that recovery doesn't see the files, it's that it defaults to the wrong folder. Use the folder up shortcut (very top above the first file or folder in the TWRP install file explorer list) and browse up to /data/media and you'll see your files. Make sure you go all the way up to the "/" directory so you get to /data, because there are data subfolders in lower directories but you need the file path /data/media
Sent from my HTC6435LVW using Tapatalk 4 Beta
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Also, if you check the TWRP recovery thread in original development beaups posted a command to fix this problem from happening, once you run the commands TWRP will open to the right location by dedault
Sent from my HTC6435LVW using Tapatalk 4 Beta
I am having issues with TWRP and partition on the device. I downloaded a new rom, which is in /SDCARD/Download directory. I can see it just fine using Root Explorer.
When I boot recovery, my /SDCARD/Download shows files that didn't exist before. Not only is the newly downloaded rom file (with .zip extension) not there, an OLD rom file is, one that existed before I wiped it and started over from a TWRP backup.
Its almost like there are 2 entire partition living on the device. Oh and one other thing: I just started from scratch again (not a recovery) and already have 8GB of space taken. Its under the "OTHER" tab in Phone Storage.
Is there anyway I can just delete everything and start from scratch? Will installing a stock T Mobile RUU do this? If I go that route, do I need to unlock the bootloader again / root again?
Have you flashed to and from 4.2 roms? You can find the other files in twrp by going up to the root folder and then data/media. You could ruu to get rid of it but it'll pop up again if you flash from 4.1.2 to 4.2.2 and back.
Sent from my HTC One using Tapatalk 4
Had this happen to me when I tried a 4.3 Rom and went back to stock T-mo Rom. Used a file explorer to find file O(I think) and transferred all my files back to original sdcard folder.
Sent from my HTC One using XDA Premium 4 mobile app
Well I think I found the problem. I was browsing my sd card using root browser looking for a Rom file (trickdroid.zip). I saw it before in the sdcard/download folder when using the file browser in twrp. But now it's not there.
So I start to pry through other folders and I notice a new folder: "0" zero. A folder called 0 with and entire sdcard folder structure within it. I look in the new download folder and there is.my missing file.
I'm curious how this new zero folder came to be. I have a theory, I did reinstall a Rom without wiping and I think that did it. I usually always wipe but specifically didn't this time because I have a twrp backup that I need to save.
I.take it the OS is now using the regular sdcard path? How can I tell twrp to look in that path for the backup (if I move it there)? When you hit restore in twrp I don't think it lets you browse for the backup. It assumes it's in the "default" spot...
Sent from my HTC One using xda app-developers app
A little background first. Flashed stock recovery and my original first backup in order to take OTA for Marshmallow. OTA wouldn't take so I downloaded / installed MM update successfully. Currently at 6.0, 3.38.502.12. Then, re-unlocked bootloader (S-ON) and flashed TWRP 3.0.2.0. I then immediately created a full backup successfully before rooting.
Since that point, I've been unable to create another backup. I've also had countless problems trying to flash anything at all like custom ROMs and such. Keep having to revert to my unrooted backup post-MM update. The problem had to occur somewhere after my first successful TWRP backup post-MM update and now. Puzzling part is that I restored this same successful backup then without leaving TWRP, I immediately tried to do another backup and it fails the exact same way.
Recovery.log shows:
* MD5 Created.
Backing up System...
Error opening: '/system/app/Ds' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I've tracked this down and it does indeed appear to be a directory "Ds". Inside as a sub-directory called 'oat' with Ds.apk inside of that, which is the Dolby Audio service.
I'm completly stumped. Any ideas?
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
sirvalence said:
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
Click to expand...
Click to collapse
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
grandpajiver said:
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
sirvalence said:
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
Click to expand...
Click to collapse
So worth the 25 dollars. But you need your system up and rooted for that to work.
But yeah, the dev edition SID 01 worked for me.
Made it way easier to work with and taking that ruu was magic.
Oh, also, do you have an sdcard? There is always the rom.zip method... placing the appropriate 0PJAIMG.ZIP in the root of the sdcard then rebooting into download mode works nicely.
Sent from my HTC One M9 using XDA-Developers mobile app