Nexus 7 partition table messed up/ broken? - Nexus 7 Q&A, Help & Troubleshooting

Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP

That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/

Tasssadar said:
That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/
Click to expand...
Click to collapse
Thank you for your help but I'm using clockworkmod recovery. What do i need to change in that command to suit CWM?

Matty Matt said:
Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP
Click to expand...
Click to collapse
Haha, I thought I was the only one! I thought I had partitioned my card somehow. I basically did the same thing as you. I also am running CWM. Its making Rom flashing almost impossible for me, I can only select & flash files from the SD "O". All my nandroids are on the regular SD selection. Did you ever find you answer Matt.?
Sent from my Nexus 7 using Tapatalk 2

Related

[Q] Why can I not delete my /sdcard/clockworkmod folder?

So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.

cannot use backup restore mnt/shell/emulated

http://onlybestandroidapps.com/the-new-multi-user-management-in-android-4-2/
recovery is still looking for backups in mnt/sdcard. filesystem only recognizes mnt/shell/emulated. big issue!!!!!!!!
xkwwwx said:
http://onlybestandroidapps.com/the-new-multi-user-management-in-android-4-2/
recovery is still looking for backups in mnt/sdcard. filesystem only recognizes mnt/shell/emulated. big issue!!!!!!!!
Click to expand...
Click to collapse
Yes, please post this in every 4.2 thread.
They are moved on the drive, as are all files. Recovery's will have to update, it's not the end of the world.
If you need them RIGHT NOW, boot into recovery, adb shell into the device, and go to /data/media/0/TWRP to find your backups. You can copy them to /data/media/TWRP or whatever, that's the absolute path where TWRP is looking.
CWM will be similar, different filenames.
I have no idea what that blog said as it was written by either a robot, a 3rd grader or babelfish.. You decide.

[Q] Where are nandroid backups stored on Nexus 4??

I used ROM Manager to 'Backup Current ROM'. It seems like I saved a couple nandroid backups successfully but I can't find where they saved so I can transfer them to my computer. I checked internalstorage/clockworkmod/ but there is no "backup" folder present, only 3 small files called .nomedia, .salted_hash, and .settings.
When I go in ROM Manager and go to "Manager and Restore Backups" I can see three dated backups listed, where are those?
I just want to successfully perform a nandroid backup and move it to my computer. I have tinkered with this device twice and lost data both times because of unsuccessful backups to my computer (totally my fault). Still getting used to Android.
right under the "Backup Current ROM" option in ROM Manager you can see it says mnt/shell/clockwordmod/backup
It's where CWM stores backups, you cannot see the folder from computer. But you can pull it via adb or copy it to sdcard using a root explorer then move to computer
Sent from my Nexus 4 in a Faraday cage
KyraOfFire said:
right under the "Backup Current ROM" option in ROM Manager you can see it says mnt/shell/clockwordmod/backup
It's where CWM stores backups, you cannot see the folder from computer. But you can pull it via adb or copy it to sdcard using a root explorer then move to computer
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
How exactly do I pull via adb?
provided you know how to use adb
adb pull "mnt/shell/emulated/clockwordmod" "C:/CWMbackups"
if you're not familiar with adb, well... go to the general section then read
Sent from my Nexus 4 in a Faraday cage
I'm having the same problem but I'm using TWRP. Is it possible to make TWRP store my backups in /data/media/0/TWRP instead? This is quite a mess to go through just to be able to make a copy of the backup on my PC...
Like the other guy said, just use root Explorer and copy the back ups, then past them in the faux sd card. This is the simplest way to do it. ADB can be challenging for the novice.
[email protected] via Nexus4
Don't know why...but my nandroid backups are in /mnt/shell/emulated/clockworkmod/backup
GretaLewd said:
Don't know why...but my nandroid backups are in /mnt/shell/emulated/clockworkmod/backup
Click to expand...
Click to collapse
Out of interest does anyone know why my backups are put there, I backed up using TWRP and it puts the backups there, but in recovery it looks to the sdcard/twrp folder so doesnt find the backups
same here. i've already browsed everything using file explorer but still cant find my cwm nandroid backup
Hi, i done the adb pull..
Later on if i wish to copy back to phone, do i need
to use adb push ? Thanks.
KyraOfFire said:
right under the "Backup Current ROM" option in ROM Manager you can see it says mnt/shell/clockwordmod/backup
It's where CWM stores backups, you cannot see the folder from computer. But you can pull it via adb or copy it to sdcard using a root explorer then move to computer
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
thanks man
nsg86 said:
Hi, i done the adb pull..
Later on if i wish to copy back to phone, do i need
to use adb push ? Thanks.
Click to expand...
Click to collapse
You should be able to just drag and drop anywhere on the sdcard folder.
On another note why do I have to do an image verification every time I leave a comment?

Zte open c 2.1

This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
my roms use stock kernel, comes from Open_C_upgrade_Tool: http://alturl.com/2bpns
vampirefo said:
This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
Click to expand...
Click to collapse
Thank you so much vampirefo, I am loving this build so far!
KUPOinyourWINDOW said:
Thank you so much vampirefo, I am loving this build so far!
Click to expand...
Click to collapse
This is the best build of Firefox OS I have ever used, omg. I don't know what it's like for you, but I can't find many bugs.
thanks man
overall i like it
the only negative is when unstick App Transition, opening/closing app/setting becomes very slow (in 1.4 i did unstick to make it faster/smooth)
2.1 works well, however 1.4 is more refined, closer to being released, Once 2.1 gets closer to being released it will be the preferred firefox version.
vampirefo said:
..in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
Click to expand...
Click to collapse
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?
Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system
YemSalat said:
Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system
Click to expand...
Click to collapse
You don't have to adb push the recovery to sdcard, use fastboot to boot recovery.
fastboot boot cw_recovery_50.img
or to install recovery
fastboot flash recovery cw_recovery_50.img
happyass**** said:
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?
Click to expand...
Click to collapse
do you have a micro sdcard installed? did you extract the backup in correct place?
vampirefo said:
do you have a micro sdcard installed? did you extract the backup in correct place?
Click to expand...
Click to collapse
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..
happyass**** said:
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..
Click to expand...
Click to collapse
Unless you have used recovery to make a backup, then you need to create all the folders, if you have used recovery to make a backup, folders would have been created except for new_2.1, which is made when you extract 2.1.
if you don't have /clockworkmod/backup folders on your sdcard you need to make them, then in /clockworkmod/backup extract 2.1
in recovery mount external_sd
then post output of
adb shell ls /external_sd/
adb shell ls /external_sd/clockworkmod/backup/
Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!
YemSalat said:
Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!
Click to expand...
Click to collapse
That usually means bad download, you may need to redownload 2.1.
vampirefo said:
That usually means bad download, you may need to redownload 2.1.
Click to expand...
Click to collapse
I re-downloaded it and it now falls with hash mismatch for system.ext4.tar.a
I tried formatting the sd card with .50 recovery but it still gives that error.
Is there any way to do the update via fastboot by any chance?
No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk
vampirefo said:
No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
I just did an adb push to the card:
adb push new_2.1 /sdcard/clockworkmod/backup/new_2.1/
But when I'm in .50 recovery - it does not see the new_2.1 folder. It only sees the one it created earlier when I did a backup.
Any idea what the heck could be wrong? xP
No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk
vampirefo said:
No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
Sorry about all the stupid questions, just the last one - can it be done via 'zip install' in recovery by any chance? Or does it have to be through restore?
The version I uploaded is restore only, you could make a zip install if you want, use Google to find info how to build cwm installation zip.
sent from my kingSing T1 via taptalk
Ok, thanks for the help!
I'll post the zip here if I succeed in making one.

[Q] Stock 5.1.1: sdcard vs. sdcard/0 problems

EDIT: Solved. See post #5.
___________________________
I had 4.4.4 stock ROM, and installed stock 5.1.1 ROM ([ROM][Manta][5.1.1] *03.05.2015* [Factory Images]) with PhilZ Touch recovery, and it's driving me nuts.
1) All data from my 4.4.4 /sdcard is moved to /sdcard/0.
But the system continues to use /sdcard.
Can I move all content from /sdcard/0 to /sdcard to have it all in one place?
2) I use Total Commander with the ADB file system plugin to copy files to my Android devices.
But now I cannot access /sdcard/clockworkmod anymore, since it doesn't show up.
I can only see it in /data/media/0/clockworkmod and it shows owner and group "0", whereas all other folders/files have "1023" as owner/group....?
Does anybody know why?
random_n00b said:
But now I cannot access the /sdcard/clockworkmod folder anymore, since it simply doesn't show up.
I can only see it in /data/media/0/clockworkmod and it shows owner and group "0", whereas all other folders/files have "1023" as owner/group....?
Does anybody know why?
Click to expand...
Click to collapse
User 0 is root, that is superuser. Any other number means normal underprivileged user.
I use twrp, and I never faced this problem.
[email protected] said:
User 0 is root, that is superuser. Any other number means normal underprivileged user.
I use twrp, and I never faced this problem.
Click to expand...
Click to collapse
OK. I'll give TWRP a try....
Edit:
TRWP does not move data to /sdcard/0/. That's good.
But now /TRWP/ has user/group "0", so it's similar to CWM and /clockworkmod/.
You may back up your data with adb pull or the twrp file explorer and then format back
Envoyé de mon Nexus 10 en utilisant Tapatalk
Finally I found a fix for my problems here.
That solved all access issues I had with the /clockworkmod an the /TWRP folders before.
:laugh::good:
___________EDIT________________
Made a few more tests.
When I switch back to Philz Touch (CWM), alle new backups are *again* not accessible. I need to run the "restorecon" command again to make the new backup folders accessible.
With TWRP no such problems. New backup folders are accessible right away.
--> Philz Touch caused all the problems I had. Will stick with TWRP from now on.
Not sure though if Philz Touch is the root cause, or the combination of ROM + Recovery...

Categories

Resources