The strangest thing happened on my wifi Nexus 7 2013. I'm running Android 5.0 (Lollipop), unlocked and rooted (using Nexus Root Toolkit), with TWRP.
TWRP was working just fine until yesterday. afternoon. I ran a backup around noon and everything was fine. I could access and manage the backup folder under 'TWRP' from Root Explorer, ES File Explorer, and my computer (through USB cable). Copying, etc., all was working fine.
Then, later in the afternoon, I did another build and things are different. The backup completed just fine, but after rebooting I can't see the backup folder from my computer or Root Explorer, so I can't copy it to my computer or a OTG flash drive. I see it in ES File Explorer, but its icon has a big question mark and when I tap it to open the folder, I get an "Open As" dialog. I can't remove the folder (is it still a folder?), or rather the removal doesn't 'stick'; in other words, the folder keeps coming back. The only way I can remove the backup is from the File Manager within TWRP itself. All backups after the one I did yesterday afternoon now behave that same way now. They're taking up a lot of unusable space like this.
It's the strangest thing. I actually ended up going back to stock and root again, just to see if that makes a difference. But what's really odd now is the TWRP folder itself now has the question mark. So this behavior persists even with completely starting fresh.
Does anyone have any idea what's going on here? I *believe*, but I'm not entirely sure, that TWRP was updated from 2.8.0.x to 2.8.1 between these backups. Could it have something to do with that? How do I copy the backup folder to my computer or a flash drive for safekeeping outside of my Nexus?
Thanks!
Ron
I'm having this same issue right now. I need to restore from a backup but I am unable to access the twrp folder as it is corrupted or something. Reflashed stock 5.0 and the issue persists. Nexus 5 though.
Okay I fixed the issue, this is what I did.
- Wiped everything in twrp
- Flashed factory 4.4.4 image
- Flashed previous version of twrp
- The folder was now normal, so I added my old backup to it
- Restored from backup and all is good.
If I had to guess, it looks like a lollipop issue. I also had problems with recovery changing back to stock when lollipop was installed. I'm sticking to my perfect 4.4.4 setup or now.
I just replaced TWRP with ClockworkMod recovery, and I'm seeing the exact same thing there! The ClockworkMod folder has a big question mark and is essentially inaccessible. I wonder if this is a Lollipop issue.
--Ron
I *think* I resolved the problem (thanks to this post in the Nexus 5 forum):
Open a terminal emulator application and enter the following two-line command (press enter after each line):
Code:
su
restorecon -FR /data/media/0
After doing that and rebooting, the TWRP and ClockworkMod folders seem normal again and I can access them, and the backups in them, as normal.
--Ron
I think it is a lollipop issue. It doesn't seem to like custom recovery. My folder stopped working after trying to transfer a backup to it from my computer. I also had to flash twrp twice or more because it would keep reverting to stock recovery after reboot.
Related
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.
My GNEX had to go back to Samsung after a system wipe completely fecked up my phone, anyway I got it back on Thurs evening. This morning I decided to unlock and root, I used Android Toolkit and that seemed to do the trick, then decided to install CWM and that installed fine but I cannot flash recovery, it sits there with the progress bar displaying 0 -100 but never moves, I gave up and installed TWRP, that works fine I can get to recovery mode and decided to do a nandroid backup which it says was successful, done this twice now and both nandroids according to the finish info says they are 600+ Mb in size but I'd like to pull one of them from my phone to my PC so I can then up that to one of my online storage areas. Problem is every root explorer app I install either hangs when accessing the Data folder or it says there's nothing in there, the nandroid must be somewhere as I can see my storage capacity has dropped. Any suggestions?
TIA
Chuffer said:
My GNEX had to go back to Samsung after a system wipe completely fecked up my phone, anyway I got it back on Thurs evening. This morning I decided to unlock and root, I used Android Toolkit and that seemed to do the trick, then decided to install CWM and that installed fine but I cannot flash recovery, it sits there with the progress bar displaying 0 -100 but never moves, I gave up and installed TWRP, that works fine I can get to recovery mode and decided to do a nandroid backup which it says was successful, done this twice now and both nandroids according to the finish info says they are 600+ Mb in size but I'd like to pull one of them from my phone to my PC so I can then up that to one of my online storage areas. Problem is every root explorer app I install either hangs when accessing the Data folder or it says there's nothing in there, the nandroid must be somewhere as I can see my storage capacity has dropped. Any suggestions?
TIA
Click to expand...
Click to collapse
Aren't they in the /TWRP folder of your internal storage?
AndyYan said:
Aren't they in the /TWRP folder of your internal storage?
Click to expand...
Click to collapse
I looked in the TWRP folder it was empty, hence the reason I asked on here, I was stumped. I did try using Android Toolkit again and it's made a backup to my PC of 7 partitions it says, it is 472Mb in size, I have a separate backup of my efs partition/folder which I did before trying to do the nandroid backup. I've just installed a custom rom and all's well so I'll try another nandroid backup and see how it goes.
TIA
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
I just purchased the G3 a few days ago, am up and running with V20C rooted with TWRP custom recovery.
For the life of me, after doing 2 backups, I can't find the TWRP backup folder/files?!
I've done dozens of backups and restores using TWRP on many different phones but have yet to encounter this problem.
I know that the backup's exist because my storage space keeps going down every time I try to backup.
Has anyone had this issue before?
Thanks in advance!
zohan99 said:
For the life of me, after doing 2 backups, I can't find the TWRP backup folder/files?!
Click to expand...
Click to collapse
It should be at:
/sdcard/TWRP/BACKUPS
or
/storage/emulated/0/TWRP/BACKUPS
Thanks for the reply. Obviously, I checked there, but the folders don't exist.
There is a TWRP file in the root folder, size is 0 bytes. This is really odd..
zohan99 said:
Thanks for the reply. Obviously, I checked there, but the folders don't exist.
There is a TWRP file in the root folder, size is 0 bytes. This is really odd..
Click to expand...
Click to collapse
What does > TWRP(Recovery) > Restore > Select Storage / very top line, go through options it gives and you should find your Backup, if it exists in TWRP.
After searching a bit online, I was able to figure it out.
Booted into recovery, then plugged in USB cable. All of a sudden, the TWRP folder magically appeared on my computer, and I was able to copy the backup files.
No idea as to why this is happening..
zohan99 said:
After searching a bit online, I was able to figure it out.
Booted into recovery, then plugged in USB cable. All of a sudden, the TWRP folder magically appeared on my computer, and I was able to copy the backup files.
No idea as to why this is happening..
Click to expand...
Click to collapse
Hi, I had the same identical problem and I found this thread searching for a solution. Not a single file manager could find the twrp folder but it existed, I could'nt create a new folder with that name in storage/sdcard. In the meantime I found a topic in which an user finds his backups in DATA/MEDIA/(etc), I tried and it works, but still apps like titanium and others couldn't access that folder! In a moment tried to set selinux mode to permissive and immediately titanium sees the nandroid! I think this is a VERY IMPORTANT info, I have stock rom bumped and rooted, can anyone copy this post to a more important troubleshooting topic?
Edit: I see some nexus 4 users had the same problem, this could be caused by lollipop instead of the g3 environment or the root method or so
Hi everyone,
I am having a lot of trouble restoring my GSM Galaxy Nexus to it's former glory. I installed CM12 and CWM recovery earlier but CM12 suddenly stopped working. My phone started rebooting over and over so I decided it was to time to flash the stock ROM. I flashed the stock ROM with WugFresh's root toolkit. And it worked fine besides the fact that writing the system.img took 30 mins, which is very unusual. I rebooted my device and CM12 showed up again... ?!. I tried flashing it by hand with ADB but no luck either. CM12 was still there. I've been busy 3 days now and suddenly realised that CM12 created new root folders after a factory reset which I did multiple times. So for example, my sdcard contains one root with a folder, named "0", that contains the files om my phone before the factory reset. The problem is that this folders contains the system and CM12 ROM too. So I have like four '0' folders, and the 'deepest' one contains the system and ROM. Assuming that if you flash a stock ROM, it will install in the root of my SD-card, but doesn't boot because it didn't overwrite the CM12 ROM in the deepest '0' directory [IMG]. If only CM12 was working, I could manualy delete all the unneccesary '0' folders... I really have no idea how to continue from now on and I really need your help [IMG]
So I need to remove all the 0 folders and place the OS back in the sdcard's root, or I have to somehow tell android to place the stock rom in the same directory as CM12, or I need to somehow wipe the complete sdcard so I can install a new recovery and flash the stock rom... I have no idea how however.
Edit: I tried: adb shell rm -r /sdcard/0 and it is gone but if I reboot Recovery and look into my folders everything is there again...
epilogue:
- Maybe the fact that sytem.img took 30 minutes to write has something to do with all those '0' folders [IMG]
- I tried flashing multiple recovery's to my device but they only show up if I open them via ADB. Ohterwise CWMR shows up again because that one is actually installed in the 'correct' (read:incorrect) folder.
- With Skipsoft roolkit I actually received an error while writing userdata.img. It said: remote: write fail. I thought this was due the multiple installation folders and the toolkit not knowing where to place/flash the rom.
Thanks in advance!