Trouble installing stock ROM due to multiple '0' folders !HELP! - Samsung Galaxy Nexus

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!

Related

No files found after factory reset

I had a problem copying files from GN to PC. I though I could fix them formatting the sdcard.
So I've done a factory reset.
When it finished, at reboot the system (AOKP JB 3) was restored but the sd files were still there.
If I go to recovery to install some zip, it doesn find some folders and every file (I can see them mounting GN after boot).
CWR says "no flies found" when I try to open each folder.
What do you suggest?
Update: I tried updating to last CWM and .. same problem.
It looks like every folder is empty (but they aren't).

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.

[Q] ANY method to clean up the "0" directories?

Hi,
I know that for some ROMs that when you flash them, you will get a "0" directory (I forgot the exact reason, but something to do with multiuser?)
I have been playing around with various ROMs lately, and they have been creating "0" directories inside my currently existing "0" directories (eg. sdcard0/0/0)
This was not a big issue for me back when I had just one 0 directory, but now that I have a couple inside each other, titanium backup restores app data to directories that is not visible to some of my apps like S Note. (Plus it is eating up my internal sd card memory) Temporarily, I currently just cut and pasted my .snb files for my S Note to the working directory so I can view them on my phone for now.
Does anyone know of ANY method (I mean ANY method. I don't mind having to do factory reset/wipe, flashing the ROM again, etc) to clean up my internal sd card?
I've already tried flashing stock ROM and unrooting, then rooting and flashing a new ROM again, but that did not work.
Thanks!
A full reflash with odin will do it otherwise I think theres a cleanup zip somewhere in one of the cm 10.1 threads
mrevankyle said:
A full reflash with odin will do it otherwise I think theres a cleanup zip somewhere in one of the cm 10.1 threads
Click to expand...
Click to collapse
I tried flashing the stock ROM with Odin, and rooting it again with Odin, but it still left the 0 files there.
Can you tell me a little bit more about the cleanup zip for CM10.1?
Wipe Data with TWRP. Backup everything you need and remove your external SD card first.
jmapark91 said:
Hi,
I know that for some ROMs that when you flash them, you will get a "0" directory (I forgot the exact reason, but something to do with multiuser?)
I have been playing around with various ROMs lately, and they have been creating "0" directories inside my currently existing "0" directories (eg. sdcard0/0/0)
This was not a big issue for me back when I had just one 0 directory, but now that I have a couple inside each other, titanium backup restores app data to directories that is not visible to some of my apps like S Note. (Plus it is eating up my internal sd card memory) Temporarily, I currently just cut and pasted my .snb files for my S Note to the working directory so I can view them on my phone for now.
Does anyone know of ANY method (I mean ANY method. I don't mind having to do factory reset/wipe, flashing the ROM again, etc) to clean up my internal sd card?
I've already tried flashing stock ROM and unrooting, then rooting and flashing a new ROM again, but that did not work.
Thanks!
Click to expand...
Click to collapse
First of all take a nandroid backup. Save it on sdcard and on your pc/laptop. Than copy all in folder 0 to root of int sdcard amd then delere folder 0. Restart your phone and all is now ok. Tips++ instal Omega rom 43.1 the mostly stabile rom ever.
Not forget to allways read OP before flash something.. have a nice evening..
Sent from my GT-I9300 using xda premium
I had luck changing the permissions of the 0 folder in TWRP to 755, rebooting, and deleting the 0 folder in Root Explorer. Everything defaulted back to /sdcard after that. Make sure to copy anything you don't want to lose out of the 0 folder before deleting it.

[Q] gt18160- adb pull sdcard file permission problem!

Hello lovely android people,
I am a newbie, so im guessing this probably isnt the right place to post this type of question. Please feel free to guide me to the right place.
So the question...
I rooted my galaxy ace2 (gt18160) and install Pimp My Rom app from the market. Did some changes with it and now the phone wont start up, stuck in the bootloop where the logo appears and it does not go anywhere from there.
Ive been researching for solution since yesterday, and found out that I could re-flash the firmware using o2 stock using odin.(although im not quite sure this is a correct solution)
Since there's a possibility of all the data getting deleted, I want to get some files out of the device using ADB pull.
I used adb shell to look for the files I need. At first I could see the sdcard in the root directory / but could not access it without su. After doing su command I can go inside the sdcard directory (where my files are), but it appears to be empty.
ls -l /mnt lists the sdcard with unusual d--------- permission.
Im stuck and dont know how I can grab my files from the sdcard folder.
any suggestion will help.:cyclops:
Thanks
mnt/sdcard is only a symlink to storage/sdcard0 (mount for the internal sdcard) so it does make sense that adb can't cope with that path.
Still, it is impossibibble to delete stuff from either of your sdcards via odin or recovery. Flashing via odin doesn't wipe the data partition either, so as ong as u select the right firmware for our phones, nothing can go wrong really
Thanks for your reply Carpe-Dimi.
after checking /prop.partiitons, it seems that sdcard hasnt been mounted.
The problem now is that there are 18 partitions and I dont know which is the sdcard?
I tried mounting the first mmcblk0. Give me the 'device or resource busy' error.
Excuse my arrogance but I would have liked to find out why I cant access the sdcard or why I cant mount the partitions.
...and thanks again for letting me know that flashing does not wipe the data. :good:
SOLVED!
As Dimi said, flashing does not wipe data partition. But I was able to recover my files in recovery mode as it automatically mounted the mmcblk0p8 partition.
Then installed stock firmware.... tried new jelly bean, then went back to stock as its slow and laggy.
Cheers

[Q] TWRP folder with backups with large question mark (invisible)

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.

Categories

Resources