Develop Bugs

I think CWM screwed me

I should be able to flash a backup I made with CWM recovery in CWM recovery, correct? Or would I have to adb push it?
I moved to 4.2.1 but not a fan of it at this point and want to go back using a backup (4.1.2) I made with CWM, but it won't flash. So at this point I'm trying to save my photos, notes, texts, and my titanium backup of apps and do a complete wipe using wugs (unroot/relock then reroot/unlock). Or should I be able to get away with just doing a format on my sdcard/system/cache/data and data/media (options in CWM)? Since going to 4.2.1 I have also lost a significant amount of free space.
BTW I have tried TWRP before and went back because I didn't like the layout but damn if your recovery can't even handle its own backups what the hell is it good for? TWRP here I come again.

you know it moves everything to a folder called 0 on the internal memory, right...?

A lot of the following is probably overkill but what I'd do is...
1. Backup everything I wanted to keep when in Android 4.2.1 onto my PC (Nandroid backups, photos, music, etc.)
2. Flash the factory 4.1.2 image
3. Boot up to make sure it's working
4. Restore nandroid in CWM
Chances are there are easier ways of doing this but I'd be happy knowing that is 100% right then have the potential for it going wrong

derekwilkinson said:
you know it moves everything to a folder called 0 on the internal memory, right...?
Click to expand...
Click to collapse
Bud I have tried to flash it out of every folder I have access to in CWM Recovery
The folder's I have tried, after choosing install zip from sdcard:
sdcard/0/clockworkmod/backup/ - 4 backups in here but wont flash any of them - says no files found when I try to flash one
sdcard/clockworkmod/backup/ - can actually see 2 backups in here (ones I don't want, just wanted to see where they were placed in 4.2)
sdcard/legacy/ - no files found
But stupid me did just realize the CWM backups I have been creating aren't zips? So I need to figure out how to get to sdcard/clockworkmod/backup and place my backup folders here. So I will be able to see them when I choose Backup and Restore - Restore

CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back

EddyOS said:
CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back
Click to expand...
Click to collapse
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.

The best way to upgrade to 4.2.1 from 4.1.2 is
1.Flash all factory images from fastboot apart from recovery,@ recovery step flash twrp 2.3.3.0 and you are all set to no '/0' bug,
2. Downgrade to 4.1.2 ? Flash factory images of 4.1.2 , just keep the recovery as twrp 2.3.3.0, at present it is the best possible recovery for maguro for handling the '/0' bug , it doesnot delete the layout file.
And restoring nandroids in between the versions can make every file very clumsy, take some time and flash stock images to get rid of that.

BaMaDuDe87 said:
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.
Click to expand...
Click to collapse
After downgrading you will still have the /0/ folder with all data. So many apps wont recognize that the backups are there available to be restored. You can just point to the "new" backup location that now exists in the /0/ directory.
Example: Titanium backup will tell you there is no restore data unless you go into preference and point it to the right folder in /0/.
Example 2: Nova launcher will not see the backups. Manually move them via Root explorer or similar from the /0/data/ to the /data/
..and so on.

I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Or use Wugs to take back to stock, then fastboot unlock, root, add CWM recovery might be the easier way at this point. Restore nandroid and everything else. Then add TWRP and remove CWM.
Sorry trying to talk this out with you guys and wrap my head around what I am in for. I know it's not hard, just frustrating to think I could possibly lose some things.

Better Recovery TWRP
BaMaDuDe87 said:
I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Click to expand...
Click to collapse
Not to be bossy but the latest version of TWRP seems to do a better job handling user folder /0. Its also touchscreen and [email protected]$$ so there is really no comparison....:highfive:

Yea I tried it, thought I was more comfortable with CWM and this bit me in the ass, so TWRP it is when I get everything straightened out

How to Re-install and Restore a CWM recovery file?

I was experimenting with the xposed framework and got stuck in a boot loop after restarting for a second time to install some more modules. The safe mode booting didn't work and neither did the included restore zip file for getting out of it. I tried to restore from the backup on the phone, but it already had the xposed framework in it and it got into a boot loop too!
I tried to adb sideload the backups that I made, and that didn't work either.
I keep backups, made from CWM Recovery, and I pull these to my computer using a WiFi file explorer. (I don't have enough storage to keep two alternative backups so I always have the second stored on my computer)
Anyway, I cant seem to get the restore file that I uploaded to my computer (a restore image) to reload on to my phone and restore. I have attempted to transfer it back to the phone into the folder it came from, but the file wont flash as a zip and it doesn't show up to be restored if I select the restore feature. (BTW-The restores have plenty of SD room to restore on, that isn't the issue)
I realize that the WiFI File Explorer that I use may be zipping the files, so shouldn't I be able to "install zip" in CWM recovery and it restores the image? (apparently not, can you explain why, and what I can do?)
Can I get access to the mnt/shell/emulated/clockworkmod/backup/ to put the file there to be restored again?
Or,.. How do I put the restore file on my phone (in the correct place) to be restored again?
Is my problem being caused by where I am pulling/pushing the file from(mnt/shell/emulated/clockworkmod/backup/)?
What am I missing/doing wrong?
Nexus 4
CM11 installer version xnpq08q
Rooted Unlocked
CWM Recovery

[Q] Need HELP

Hi,
I am running Carbon Mod Nightly Rom, I was looking at the Volume Blaster Mod (http://forum.xda-developers.com/showthread.php?t=2563209) to raise the volume up on the external speaker. I edited the file system/etc/snd_soc_msm/snd_soc_msm_2x. Somehow I screwed the file up after editing. After I edited it and rebooted, it gets stuck at the Carbon Logo and doesn't go any further :crying:. I have a nandroid backup, but I didnt backup until after I edited the file (before reboot). So I'm wondering can I or how do I replace the edited file (snd_soc_msm_2x) with the original file. I have the original file on the SD card in the phone. I went into the TWRP Recovery and into file manager, but I could not locate the location of the edited file from within there (system/etc/snd_soc_msm/snd_soc_msm_2x). Can someone please help me restore this one file so that my phone will boot up or tell me how would be the best way of getting my phone up and working again ASAP. Oh, I have tried exploring the backup created with Nandroid Backup Manager, well I found the file thats corrupted and opened it with File manager, select all- then delete, then pasted the contents from the working file, and then try to save, and I get an error "Operation Failed". So any help would be greatly appreciated.!!
Thanks in Advance

If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.

DocHoliday77 said:
If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.
Click to expand...
Click to collapse
Dirty Flash? I'm new to all this, so I need some help with the slang. I can explore the contents of the Nandroid backup, are there anyway possible to delete a file in the Nandroid backup and replace it with another file?? If I can do that, then I can replace the corrupted file and then restore from backup. I just dont want to reflash the clean ROM and then have to manually restore all my apps, sms and photos...
If I flash the backup Rom that has the corruted file, and before reboot, can I use the file manager to pull the clean file from the external card and replace the one that corrupted in the root folder. If I can do this, then it should boot normally. Otherwise if I boot with the corrupted file it gets hung after it processes all the apps. (Gets hung on Starting Apps).

I figured it out!!! What I did was I went into recovery, and selected the recovery nandroid backup file that was corrupted. Instead of restoring all the available options, I unchecked System. So it restored everything but the system data. The system data already installed was from the newly installed rom that was working, so by leaving the system unchecked it didnt install the corrupted system from backup! I hope I explained this where you can understand it.
Thanks for all the help DocHoliday77!! I'm just glad that worked and I dont have to manually install everything back over!!
:victory:

Restore KitKat Nandroid Backup with Lollipop Bootloader

Hi,
I have upgraded from KitKat to Lollipop on my T805. However, before upgrade I forgot to copy out some files that I have saved in Private Mode. Now I would like to restore them. Fortunately, before upgrade I have created nandroid backup of my KitKat system in TWRP. (I have backed up everything except Cache and Recovery.) Now I would need to go back to restore my KitKat backup temporarily.
Can I just restore nandroid backup of KitKat in TWRP when I am on Lollipop Bootloader? Or will I need to flash KitKat Bootloader first? If so, where can I find one? I have tried to search forums for KitKat T805XXU1AANFB Bootloader, but I was not successful. I found only unlocked bootloaders at https://autoroot.chainfire.eu/ but I am not sure if it is safe to flash them. I don't care about tripping knox since it's been already tripped.
Thanks in advance for you advice.

No need to downgrade bootloader.

Great, I'll try to restore then.
Odoslané z GT-I9505 pomocou Tapatalku

[email protected] said:
Great, I'll try to restore then.
Odoslané z GT-I9505 pomocou Tapatalku
Click to expand...
Click to collapse
I'm not sure why you'd need to restore though. Why can't you access your private files via lollipop, dont you have the same setup?

The files are not available in Lollipop. In KitKat, I had rooted stock ROM. As for Lollipop, I have installed IronROM. This ROM has secure storage disabled. I guess this could be the reason why the files are not available. Another reason could be that in installing IronROM I had to do clean install (only sdcard was not wiped).
Odoslané z SM-T805 pomocou Tapatalku

Are the files stored in a certain folder? When you say secure storage do you mean it got limited access to a folder? if yes that's easy to fix

Surely if you're rooted you can access these files anyway?
Also the ro.securestorage.support =false flag is a simple ramdisk or build.prop edit or just flash a stock kernel this will re-enable secure storage.

Kahun said:
Are the files stored in a certain folder? When you say secure storage do you mean it got limited access to a folder? if yes that's easy to fix
Click to expand...
Click to collapse
I'm not sure how the Private Mode works exactly. I just know that when I enter the Private Mode, a new "root" folder is mounted in Samsung's "My Files" file manager. Also, in the "storage" folder a new folder appears, namely "private". When I tried to find the files while the private mode was turned off, I was not able to find them. In my current Lollipop ROM (which has secure storage disabled), there is also a folder named "privatemode" in the "mnt/shell" folder. The "privatemode" folder contains the files that probably appears in private mode. But I can' tell for sure since the names of the files are encrypted and I guess their content is also encrypted.
However, I am not sure if these files were visible also in my KitKat ROM with secure storage enabled. And I don't know if the files could be used (decrypted), if they would be simply copied into the new ROM.
ashyx said:
Surely if you're rooted you can access these files anyway?
Click to expand...
Click to collapse
Possibly, but I didn't know where to find them. Now I know I would look into mnt/shell folder, and if there was some content in the privatemode folder, I would give it a try and copied them into the new ROM.
ashyx said:
Also the ro.securestorage.support =false flag is a simple ramdisk or build.prop edit or just flash a stock kernel this will re-enable secure storage.
Click to expand...
Click to collapse
While it is probably true, in the ROM description it is stated that secure storage enabled doesn't work with Xposed Framework. Probably it was also true on KitKat. When I wanted to enter Private Mode, I had to uninstall Xposed, restart the device, do what I needed in Private Mode, install Xposed back and restart to get the framework activated. Not very handy Now, with secure storage disabled, I can use Private Mode together with Xposed Framework. :victory:
----------------
Anyway, since I considered restoring backup quite easy and definite way how to get my files back, I have already done it. Since I was at work, I didn't have time to tinker around, but I had a plenty of time to do restore/backup thing. Now, I am already back on my Lollipop, having the missing files restored. Everything works just as before.
------------------
I would like to also share my experience with restoring the backup. Interestingly, after restoring the backup of KitKat system, not everything went smoothly. For example, the internal storage was not properly mounted. I could see content of "sdcard" folder in My Files file manager but other apps (including ES File Explorer with root permissions) saw "sdcard" folder empty. But when looking into the data/media folder, everything was there.
Moreover, when trying to uninstall Xposed Framework in order to get Private Mode activated, after restart I got stucked at Samsung logo, and had to power off the device, boot into TWRP recovery, and manually rename /system/bin/app_process.orig back to /system/bin/app_process (as I learned here http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053).
I guess these problems could be caused by not wiping Dalvik Cache and Cache partitions after restore. Otherwise, it would be unpleasant surprise that a system that worked fine prior to backup, would not work so flawlessly after restore. But since I was able to do what I needed, I consider it mainly as an interesting experience.
Once again, thank you very much for your help, expertise and interest to help my solve my problem. It really is a good feeling to see such willing spirit.

When reverting to kitkat from lollipop you need to wipe the data partition or it doesn't boot as the setup is different. Art vs dalvik etc.

ashyx said:
When reverting to kitkat from lollipop you need to wipe the data partition or it doesn't boot as the setup is different. Art vs dalvik etc.
Click to expand...
Click to collapse
This is where I am stuck at too. I have a sm-t700. I unintentionally let the auto update happened and it is now 5.02. I would like to go back to kitkat (4.42). I then flashed the T700XXU1ANL2 stock firmware via odin. After reboot, I am stuck at the samsung logo. My question is: how do I get to recovery? Only combination that works is home+power+vol dn to the download mode....

Power off then hold HOME + VOL UP + POWER in that order until recovery boots.

ashyx said:
Power off then hold HOME + VOL UP + POWER in that order until recovery boots.
Click to expand...
Click to collapse
I was not able to power off (power + vol dn) neither.

bluesky997 said:
I was not able to power off (power + vol dn) neither.
Click to expand...
Click to collapse
It's not power off its a hard reset and ALWAYS works no matter what state the tablet is in.
If it doesn't your tablet is dead.

Titanium Backup fails to see backup files

I just upgraded my N4 to Jasmine MM ROM. I installed TiBu and pro key. I go to preferences and browse to my SD card. There are 312 files in the folder. Then go to batch/run restore missing apps + all system data and the list is blank! Any ideas? BTW, it worked fine the first time and I was able to restore but then I screwed up the install trying to flash Xposed framework (did not do a nandroid!) so now that I've re-flashed the ROM, I get the above behavior. I don't think it should flag the files as having been restored should it? Restore all apps with data list is also blank.

In TB, go to preferences/Backup folder location, then click on Storage provider: Filesystem(click to change). Then click Filesystem storage. Scroll down and click storage. Then click on your sd card. Then finally click on the TB folder and click use the current folder. That should fix it. You have to do this everytime you switch to a new rom. Hope this helps.