Develop Bugs

Interesting Experience with CWM Recover 6.0.2.3

I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?

solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.

milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!

solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much

The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.

edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.

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.

Not able to restore nandroid back up

Hi there,
I was running a RR rom and got a msg about an update for my ROM. So i thought i would try it out. I made a full nandroid back up and after that updated my ROM. After the update my homebutton didnt work anymore. So i thought, lets just restore my back up again. I did a fully factory wipe, i flashed TWRP again on my OP3 because for some reason after the factory wipe i got the Cynogen recovery mode. So i put back TWRP, put my back up on my phone from my laptop, but when i went to "restore" nothing was there. I tried to move my back up from the "sdcard" directory to the root directory but i got an error which didnt specify what the problem was.
Can any1 help me restore my OP3 again?

so when u went to TWRP -> Restore, there was not backup found to restore? but when u check ur phone through file manager its there?

Bradl79 said:
so when u went to TWRP -> Restore, there was not backup found to restore? but when u check ur phone through file manager its there?
Click to expand...
Click to collapse
Thats correct. When i go in the file manager, i see the backup in the sdcard directory along side the TWRP directory. I tried to move it with the file manager, but it gave me an error which was not specefied.

Cainnub said:
Thats correct. When i go in the file manager, i see the backup in the sdcard directory along side the TWRP directory. I tried to move it with the file manager, but it gave me an error which was not specefied.
Click to expand...
Click to collapse
Try to mount data/internalstorage.

Puddi_Puddin said:
Try to mount data/internalstorage.
Click to expand...
Click to collapse
thats already mounted under the tab "mount". Or did you mean in the terminal?

see if u can use this to extract whatever u need then
https://www.youtube.com/watch?v=mKqYUPx4VrY&index=8&list=FL1dLDa3yAfMcdOipOfWp49A

Bradl79 said:
see if u can use this to extract whatever u need then
https://www.youtube.com/watch?v=mKqYUPx4VrY&index=8&list=FL1dLDa3yAfMcdOipOfWp49A
Click to expand...
Click to collapse
ok now i extracted all the files from the tar files, but what is the next step? I tried putting them on my OP3, but that does nothing. My OP3 still doesnt see a back up.

Another thing is something i saw is that in TWRP, when i shut down my OP3, TWRP says that there is no OS installed. Is that normal?

No that is not normal, the extraction is there so u can reinstall things, I will have to take a look at it again, do u know what all partitions u had backed up and did u move the backup location?

Lately backup in twrp recovery sucks.
Yesterday, i want to test another rom. So i wipe cache/dalvik & backup in twrp. I select all except rom img (3gb) and cache (zero). Try the new rom. Does not work for me. So wipe all except sd card & restore my backup.
Error..
I use only twrp 3.0.4.1, so it can not be a conflict in different twrp's versions. It's not the first time....
If you wipe youre phone, including sd card, go to recovery, backup and choose the smallest size file to backup. Recovery creates youre backup folder in TWRP directory. After that you can erase the that backup.

I flashed back oxygen (OMG I forgot how ugly oxygen was) last version, so I got a working phone again but ofc without all my media. I just find it weird that I make a full backup (I had everything checked) and I can't do anything with it.
I did full factory reset, so maybe that's the reason my OS got deleted aswell. What partition has the OS installed?

When I reboot my OP3, I get a msg saying that dm-verity has not started in enforcingmode and may not work properly. What does that mean?

Cainnub said:
When I reboot my OP3, I get a msg saying that dm-verity has not started in enforcingmode and may not work properly. What does that mean?
Click to expand...
Click to collapse
Maybe here you find some help.
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339

TWRP Weird folder names and no .zip file

Hey,
I'm new in this kind of stuff but need help as fast as possible. So I tried to root the phone but let me tell you something else. When I enter TWRT (boot into) and try to install the .zip file it shows weird folder names that I can't see on the computer. I have Win10 if this matters and Android 8.0 or 8.0.1. The folders are:
acct
boot
cache
config
cust
data
license
mnt
and it goes like that. The problem is that about 85 or 90% of these folders aren't visible on my computer when I plug in my phone... The System is mounted in TWRP and everything is mounted. I tried wiping all the data. I have unlocked bootloader. Also when I go to some of these folders I see REALLY strange folder names like: 671hnsuh1b%nqjus Or something like. I've found out that it's encrypted but I just want to root the phone and find the .zip file. Also can someone explain me these acct, boot, license, vendor, version and other folders that aren't visible on my PC? Please help. I'm so confused, not clue what's going on...

You need to use the format data option to decrypt the internal storage. Better use SD card or USB OTG to flash the root file. Anyway don't wipe the oeminfo or vendor partition in any case and take a backup of all partition beforehand.

kksnis said:
You need to use the format data option to decrypt the internal storage. Better use SD card or USB OTG to flash the root file. Anyway don't wipe the oeminfo or vendor partition in any case and take a backup of all partition beforehand.
Click to expand...
Click to collapse
Well, I already used this option. The format data option and it's still the same. Maybe the version of my twrp helps: 3.1.1-1

Aspect13 said:
Well, I already used this option. The format data option and it's still the same. Maybe the version of my twrp helps: 3.1.1-1
Click to expand...
Click to collapse
Strange. What is the android version?Did you had any lock screen set before formatting? Can you please share a screenshot or log during formatting, if you have any. Anyway you can use adb sideload to flash the .zip file.Cheers

kksnis said:
Strange. What is the android version?Did you had any lock screen set before formatting? Can you please share a screenshot or log during formatting, if you have any. Anyway you can use adb sideload to flash the .zip file.Cheers
Click to expand...
Click to collapse
My android version is 8.0 so it's oreo. I've also noticed that the 3.1.1-1 version of twrp is the only one from what I tried that I can install the newer versions gave me an error. I had lock screen and it was code not a fingerprint but I wasn't prompt for a code after booting into twrp. Adb sideload seems to fail all the time so I can't do it :/.
The logs from wiping data are:
Updating partition details...
..done
Full SELinux support is present.
MTP Enabled
Starting ADB Sideload feature...
Starting ADB Sideload feature... (And it failed now wipe logs.):
Fomatting Data using mkfs.f2fs...
Done.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
...done
So yea I'm so sad tbh with this... I'll try to install new twrp after the wipe if the wipe didn't help and will tell you if I get an error when I try to boot into NEW twrp.
EDIT: Ye still an error.
Maybe you have a link to the newest working twrp?

Nevermind got it. Downloaded the modded twrp by TEAM MT I guess from here: https://forum.xda-developers.com/honor-8-pro/development/wip-twrp-3-1-1-0-duk-t3625798 Works perfectly and SOLVED!

I can't back up the rom via twrp

I have a moto g8 xt2045-1 and I intend to install a custom rom, however when I try to make a backup, it always fails. Saying that there is no permission for the operation (operation not permitted), Also because of that, I can't even access my phone's internal memory through recovery. Instead of folders (Android, downloads, etc.) there are only several folders with a lot of mixed letters. So from what it looks like, twrp needs permission, but how can I do that?
Or I could also just install another one, but I can't find another recovery anywhere
AI'm using version 3.5.0-10_0 of twrp .. I hope you can help me

Did you mount all partitions before backing up? maybe a partition is read only ( like system) and that is why no permission.

mrsiri said:
Did you mount all partitions before backing up? maybe a partition is read only ( like system) and that is why no permission.
Click to expand...
Click to collapse
When this problem occurred, I thought it could be that, but unfortunately it is not.... All partitions are mounted as read and write, but still giving the same error.... And not to mention that the recovery is not even able to read the internal memory of the cell phone (in this case, the 'sdcard' folder) it gives that same error that occurs on the redmi note 8, where all the memory is encrypted.

Do you have Magisk Installed? Did you check the "preserve force encryption" checkbox when installing?

I have magisk installed yes, but I do not remember having marked anything during the installation, because there was no option. But can I still check this option?

mrsiri said:
Do you have Magisk Installed? Did you check the "preserve force encryption" checkbox when installing?
Click to expand...
Click to collapse
.

Go to magisk manager and look under advanced settings. maybe it was already checked as default when you installed. I guess you'll have to root again with that unchecked.
If you have that ticked, check out this guide and follow it: https://forum.xda-developers.com/t/fixed-how-to-remove-data-encryption-in-twrp.3757595/

mrsiri said:
Go to magisk manager and look under advanced settings. maybe it was already checked as default when you installed. I guess you'll have to root again with that unchecked.
If you have that ticked, check out this guide and follow it: https://forum.xda-developers.com/t/fixed-how-to-remove-data-encryption-in-twrp.3757595/
Click to expand...
Click to collapse
Okay, for now, thank you very much