I wanted to enable full gpu rendering on my Samsung P6200... I am running 4.1.2, rooted. I downloaded the zip file, booted into recovery and installed the zip file, I rebooted, it shows the normal model number and that on the screen, and about the time when the boot animation starts it just goes blank, although it is still on, now, I rebooted back to recovery, I had made a backup moments before, I only had 770 MB of space left so it made a full backup except my /data partition, that failed, but I didn't want that backed up anyway. I thought well maybe I should restore, so I went to advanced restore and chose the boot partition to restore, restore was succesful, I restarted and did the same thing, now I try to restore the whole backup and it says md5 mismatch, I connect to adb and mount everything, and find my mnt folder is missing, now I don't know how to fix this, if I go to install zip from sdcard it shows all my files and folders there, but if I go to /sdcard/storage/sdcard0 in adb it only shows two folders, Download and Webzine. How to fix this, I don't want to restore my /data partition due to the fact that it only did like 5% of the backup of it and need a lot of that data, if I were to fix the md5 mismatch (don't know how) what partition would I restore to fix the boot error? And how do I fix the missing mnt folder issue?
Ok, sorry, found my files are stored in /sdcard/, although I could swear they were in sdcard0
Related
recently i have been having issues with my games and apps that are installed in my phone.........all of them say ether "application not installed" or the force close messege while the day before all was ok... so what can cause this issue
Have you made any changes to you phone recently, tweaked, anything...? Or did it just happen suddenly?
ivanrcks95 said:
recently i have been having issues with my games and apps that are installed in my phone.........all of them say ether "application not installed" or the force close messege while the day before all was ok... so what can cause this issue
Click to expand...
Click to collapse
Hi @ivanrcks95...
After reading your post I sat & scratched my head for a while...
1. do you have any apps etc moved-out to sd...? If so, are there many & what app did you use to move them...?
2. Are you running any ram tweaks or partition managment tweaks...?
The reason I ask these questions is because I have seen this behaviour often when an "Ace" is switching back from USB data transfer mode to Internal & SD memory...
The status of your ram at this point can cause a severe lag with the mounting of the necessary partitions often returning the error messages that you describe... on occasion you will also get "Problem loading widgets" etc. If a particularly bad lag occurs then the data & partitions can become corrupted...
An easy cure to get things running again would be a complete wipe & restore from Nandroid backup (assuming that you have done one...?)... A selective nandroid restore would let you just repair the system partition, which I feel would be adequate.
Have you tried re-installing 1 or 2 apps...? if they install successfully then that tells us that the partition is now functioning but some of the data contained has become corrupt. If the apps fail to install then I think we can safely assume that the partition is corrupt...
Again the simple solution would be a nandroid restore... If you do not have this option then I would suggest the following... :
1. backup all data from your sd card where possible & reformat & partition using CWM 4 or 5 (if ya runnin CM7.2 then you "MUST" use CWM5)...(sd card partitions may be cause of issue)
2. complete a full wipe (system, cache, Dalvik), Wipe battery stats (Always do when installing a new rom so battery can correctly callibrate to new power requirments)...
3. Re-flash rom, modded kernel etc. (always check if system, data partitions need to be mounted before flash from CWM to prevent boot errors & wrong permission assignment)...
4. Re-boot phone after flash to check all is well... Then copy back to sd the backup that you made at the beginning...
You should now have a fully working phone again... Downside is that you may have to re-install ya apps etc...
Nandroid backup recovery...
======================
1. Follow step 1 of my guide above...
2. If doing a "selective" nandroid restore then wipe just the Dalvik cache then just select the needed files and restore them... If doing a "Complete" nandroid restore then do a complete wipe before restore...
3. Re-boot phone after restore to check all is well... Then copy back to sd the backup that you made at the beginning...
You should now have a fully working phone again...
!!! IMPORTANT !!!
==============
If after formatting & partitioning the sd card, CWM has trouble locating the Nandroid backup after you place it in root of sd card then do the following :
1. Open into "Root" of sd card
2. Create a folder called "clockworkmod" all lowercase letters...
3.Create within the above folder another folder called "backup" again all lowercase...
4. now place within this folder your nandroid backup...
5. unmount usb (assuming your phone is connected to pc for folder creation)...
6. now complete the nandroid recovery...(should go without a hitch unless the backup has been altered in any way (MD5 hash file check will fail if file is altered after creation)...
Hope this info is of help to you given that you did;nt really provide many details of your problem...
Stay Breezy n Be Lucky...
Pe"ACE"...
ok i am running my own ROM that i havent published but its a mix with cyanogen and ice cream sunday put into one( so some bits from each rom to make my own) well when i re-install apps they work but ive noticed as soon as i reboot my phone they force close again i can try to reinstall my rom and do a full wipe to solve this but all my apps are in my sd card so it could be that my sd card is a bit mest up or maybe ive mest something up with my rom
My Nexus 7 device. Flashed PA 3.0 using TWRP. I used a backup to restore the previous rom. Made some Titanium backups. Reflashed PA 3.0 and Gapps.
THe data kept for user access under sdcard disappeared. Seems like it was erased and replaced with a fresh set of new folders and little bit of data that PA just made. Checked storage space and about the same amount of data/memory is still used up on sdcard. Checked around the directories below sdcard using file expert and couldnt find it. Used TWRP to look around the directories and found all my data in /data/media
Tried to move it to /sdcard but it fails.
Tried to move it in file expert but only a few files s moved. File expert doesnt seem to recognize any of the files in /data/media as having any data, ie there is 0 bytes on each file and all folders become a 0byte file and not a folder.
I can still see the old data i want but how do i retrieve it safely?
Hi guys,
I need your guys' help. Somehow I messed up my installation (Play store crashing, can't see SD card directory in the files browser etc.).
Goal:
All I want to do right now is to copy my SD card files from my N5 to my desktop (Mac) so I have all the settings and backups and then wipe the whole phone and start fresh, subsequently restoring app and settings.
I can see my SD card directory within the TWRP file manager, also my Nandroid backup, which I tried restoring (I don't know if you have to wipe anything before doing so), but after well over an hour turned the device off.
I read somewhere that there is a pull function to copy files from phone to desktop (see here: http://stackoverflow.com/questions/17629889/android-adb-pull-file-on-desktop). So I tried adb pull sdcard/ /Users/myusername/Desktop/android but it says "command not found"
Question:
What am I doing wrong and how do I copy the important stuff over?
Note: I have a N5 with TWRP custom recovery, unlocked bootloader.
Hey Guys,
I have a Android/WinCE Car Radio.
So I got Android on a SD Card and it booted well, but one day it stopped booting.
If I mount the SD from the internal Android on the device, there is a LOST.FOUND directory on the boot partition where boot.scr and so on is.
If I delete the directory and restart, the system boots from the SD again. But if I do a restart, the system won't boot again. I need to delete the LOST.FOUND directory every time...
I'll Attach the boot partition, maybe you can give me a solution to this.
Thanks
bump
If you run fsck, the filesystem check and repair command, it might find data fragments that are not referenced anywhere in the filesystem. In particular, fsck might find data that looks like a complete file but doesn't have a name on the system — an inode with no corresponding file name. This data is still using up space, but it isn't accessible by any normal means.
If you tell fsck to repair the filesystem, it will turn these almost-deleted files back into files. The thing is, the file had a name and location once, but that information is no longer available. So fsck deposits the file in a specific directory, called lost+found (after lost and found property).
Files that appear in lost+found are typically files that were already unlinked (i.e. their name had been erased) but still opened by some process (so the data wasn't erased yet) when the system halted suddenly (kernel panic or power failure). If that's all that happened, these files were slated for deletion anyway, you don't need to care about them.
Files can also appear in lost+found because the filesystem was in an inconsistent state due to a software or hardware bug. If that's the case, it's a way for you to find files that were lost but that the system repair managed to salvage. The files may or may not contain useful data, and even if they do they may be incomplete or out of date; it all depends how bad the filesystem damage was.
Click to expand...
Click to collapse
Make sure your boot files in the root of the partition are ok.
Make a backup of the files, copy the files in the lost.found directory over the existing files or use the original one (firmware download from device supplier?)
And make sure you unmount the SDcard safe.
Good luck..
THere are no files at the LOST.FOUND directory.
If I take a other SD and put the stock image on it, it's the same problem.
So, my phone bricked because of build.prop change, but before that, i downloaded a backup of my phone build.prop (S7 Edge) but in file manager of TWRP, it shows as if there was nothing, i can't check data in mount and internal storage is 0MB, there is no password (it didn't ask for one also) is there anyway i can retrieve my build.prop backup without erasing it?