[Q] i9000m + Froyo + Internal SD Card failure ? - Galaxy S I9000 Q&A, Help & Troubleshooting

Ok so there's alot of info. regarding Internal SD card failure and Froyo.
My question is will this occur with a natural Froyo update instead of a flash ?
I have a stock i9000m - never even rooted, no lag fix, nothing.
I heard Froyo will be coming soon (im guessing via Kies?)
Will the Froyo update mess up my Internal SD as appears to be happening with Froyo Flashs ?
Also, will I lose my apps when I update via Kies to Froyo ?
thanks guys.

From what I've seen on here there is no direct link to sd failure from flashing. I think just as many have failed that were not flashed. Always possible though that a botched flash could spell doom.
An official update should not damage your phone. If it does, you should return it to bell for repair or replacement.
Many on here recommend a factory reset after update, I'm planning to do that myself. Reinstalling apps is no big deal. Takes only minutes and because they are linked to your google account you don't have to buy paid apps again.
Sent from my GT-I9000M using XDA App

However, the linking to the Market account does not restore unpaid apps. These you will have to install again, and of course, you have to remember which ones these are. This could be time consuming.
In my case it took about 2 hours. I had many apps, and in some I could not remember the names: A fair amount of time was lost searching for the names.
Any easy solution to this is to back up this directory on your phone afore you reset:-
Directory: /data/app
It contains all the .apk of your apps.
use the ADB to get a shell on your phone - There are a few guides around on how to set this up. Once set-up, please use this command to get a shell:
adb shell, and then su to root:
adb shell
su
* How to backup.
Change into the directory
cd /data/app
Archive the files to a file on your SD card. In this case the archive tar file is called /sdcard/apps.tar. You can put it anywhere you want with any filename you like.
tar cvf /sdcard/apps.tar .
* Perform a factory reset.
* Restore the files.
Here you should extract the archive into a tempory directory and use a file manager like Astro to click on and then install the apk files:
Create a temp directory for the files:
mkdir /sdcard/apkrestore
Change to the directory:
cd /sdcard/apkrestore
Extract the files from the archive:
tar xvf /sdcard/apps.tar
List the file files in the dir - you will see many files with .apk extensions.
ls /sdcard/apkrestore
Install the apks
Start ASTRO file manager and navigate to /sdcard/apkrestore
Click on the apk you wish to install.
Its funny how people seem to omit this information: as if they think people only ever buy apps and never use the free ones ;P

forgetmyname said:
However, the linking to the Market account does not restore unpaid apps. These you will have to install again, and of course, you
Its funny how people seem to omit this information: as if they think people only ever buy apps and never use the free ones ;P
Click to expand...
Click to collapse
Awesome info. I guess I will try this.
Questions. I obviously have to have a root to use these ADB commands ? I haven't rooted phone yet.
Other question, is there an easier way to back up all apps? Like what if I root ? I can get Titanium Backup Pro -- will this work? would this back up apps to my sdcard ? I have a 32gb external card too -- can I back up apps to this or no ?
Final question,
has anyone in Canada been able to do a normal, official update via kies to froyo 2.2 ?? is it avail. yet ?

Related

[Q] ClockPackage on di11igaf's

Issue 1: I'm trying to install ClockPackage.apk, Gallery3D.apk, MyFiles.apk in order to have the stock clock. I keep getting the error "Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]" when i try to use the command adb install (any of the 3).apk. I have also tried "adb push" which doesn't seem like a valid command. I tried moving the 3 apk files to my sd card on the phone and using "installer" and "eoeAppinstaller" from the market and these fail as well. Any more suggestions? I really like this di11igaf's ROM, but I cannot stand the new alarm ( i like the gradual volume increase of the stock). I have tried a couple of market clocks, but they just didn't work for me. Thank you very much in advance.
Issue 2: If I use CWM and choose Reboot into Recovery i get the following:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter OK Key, Select : Vol UP / Vol Down
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
format internal sd card
update media, please wait
update media finished
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
-- Applying Multi-CSC...
Installing Multi-CSC
(in red)
Installation aborted
At this point I can use the volume buttons to scroll up and down, but the power button will not select anything. The only thing I can do is remove the battery and boot the phone back up, which then takes me into CWM recovery v2.5.1.0. I was able to install the di11i add on, but I don't think that I'm supposed to be pulling the battery to get to this point.
Thanks again and sorry about the long post.
Im no expert on this type of stuff but I use di11i roms and I just transfer apk's to the root of the phone through the regular mass storage mode and use root explorer for the rest.Havent had any problems yet.
As for issue 2 is the package a .zip file? If not that may or may not be the problem.
From my own personal experience the 3dapp isn't sign so I can't install it too
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
diablo009 said:
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
Click to expand...
Click to collapse
+1 you can simply use root explorer to copy the apk files into \system\app folder. quick and easy.
booty hater said:
As for issue 2 is the package a .zip file? If not that may or may not be the problem.
Click to expand...
Click to collapse
It is a zip file and it installed. What concerned me was the process. Should it have frozen up like that and forced a battery pull? Nothing I've read leads me to believe that was proper behavior of the CWM.
diablo009 said:
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
Click to expand...
Click to collapse
I don't have that directory. Are you creating it on the phone and then putting the files into it? I may have not been clear on what I am trying to do. I am trying to do what was posted in this forum http://forum.xda-developers.com/showthread.php?p=11207089&highlight=clockpackage#post11207089 posts #2515
I just looked into exactly what you were talking about and I got it figured out.It wasnt installing for me either but this is what I did and it works now.
Through mass storage mode I copied the 3 files to the root of the card.
Then I moved the files to the app folder which is inside the system folder.
I use root explorer for the moving.
When you move them into the app folder its gonna ask to overwrite say yes.
After you get everything moved it will work if you go to the app in the drawer.I never actually installed anything but did an overwrite.
booty hater said:
I never actually installed anything but did an overwrite.
Click to expand...
Click to collapse
Right. Apps in the system/app folder are auto-picked up
supervg3 said:
I don't have that directory. Are you creating it on the phone and then putting the files into it? I may have not been clear on what I am trying to do. I am trying to do what was posted in this forum http://forum.xda-developers.com/showthread.php?p=11207089&highlight=clockpackage#post11207089 posts #2515
Click to expand...
Click to collapse
u cannot see it in my files. u need to have root access, and something like root explorer.
So it looks like I could have just copied and pasted the files from the sdcard/Clock folder I placed them in to the /system/app folder using Super Manager. I swear I tried that and it failed before I went through all the crappy steps below. Oh well.
Ok this is going to sound pretty cheap, but I didn't want to pay the ~$4.02 for an ap that I was going to use three times. I did find another way. I used Super Manager and http://forum.xda-developers.com/showthread.php?t=877316&highlight=installing+apk post #3.
So for any other cheapskates out there.
1. Install Super Manager on phone
2. Install ADB on pc
3. Connect phone to pc and copy the three files ClockPackage.apk, Gallery3D.apk, and MyFiles.apk to the sd card. (I just drag and dropped in windows explorer)
4. Use Super Manager to move to /system/app/ and rename the existing file Gallery3D.apk (I renamed it to Gallery3D.old)
5. Use adb to copy the 3 files from the directory in which you originally placed them on the phone to /system/app/
in adb type:
adb shell
su
(accept the prompt on your screen)
cd /sdcard/whereveryoustuckfile
cp blahblahblah.apk /system/app/ (the red from Pirateghost).
6. Reboot
The clock and alarm work fine, but I cannot get Daily briefing option in alarm to work. I get a FC. I did install the "apk add on pack for 5.6" post 3 of http://forum.xda-developers.com/showthread.php?t=897416 , but I dont think Daily Briefing was included in that. Any suggestions? And one last thing - what is the di11iBrowserfix.zip from post 3 of the thread above for? Thanks again to all who contributed.
I got the daily briefing working. Everything is almost perfect, but I would like two things still.
1. Is there anyway to change the tune that is played when you have smart alarm selected? I have a different tone selected, but I think once you select smart alarm it defaults to that new age tone.
2. My alarm goes off, I stop it, but then I have to unlock it before I see the daily briefing. Can anyone think of a way to have the phone unlock when I turn off the alarm. I know it is so insignificant, but it used to do that when it was stock and it was pretty cool.
Come one guys and gals - don't make me figure this one out by myself j/k but seriously I have surprised myself already by getting this far and I really don't have skill or knowledge for the last two things. I'm learning though....slowly.
Thread etiquette
Did I do something wrong here? I got some really quick responses to my questions before, but nothing on my latest. I ask this next question with all seriousness - should I have started a new thread since it's kind of a new topic? No worries either way, I just want to post in the the most effective way. Thanks. BTW, my phone is working great. I'm getting ready to install 6.0 GPS is a little screwy - often has me west of my location by about 30 meters by I attribute that to the phones hardware. Other than that I have no complaints (except for the lame smart alarm tune)
diablo009 said:
Right. Apps in the system/app folder are auto-picked up
Click to expand...
Click to collapse
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
ddoubt said:
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
Click to expand...
Click to collapse
you should start a topic instead append to other's topic.
you can flash any kernel/modem using CWM, just make sure it is i9000's.
ddoubt said:
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
Click to expand...
Click to collapse
Nope. Get the CWM flashable zip, and copy to ur sdcard. Then go to CWM recovery console, and install this zip. Reboot.
But, please take a nandroid backup, and try to avoid OC kernels if u r unsure ur phone can handle it. Phones freeze when tried to oc beyond their capability.
diablo009 said:
Nope. Get the CWM flashable zip, and copy to ur sdcard. Then go to CWM recovery console, and install this zip. Reboot.
But, please take a nandroid backup, and try to avoid OC kernels if u r unsure ur phone can handle it. Phones freeze when tried to oc beyond their capability.
Click to expand...
Click to collapse
Thanks for the info and sorry for appending to this topic!

[FIXED] [Q] XT860 - Broke my /system/app folder...

EDIT: Fixed! Procedure I used was to download Danifunker's system dump, move it to /sdcard/ via adb push, then run the following:
Code:
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
This completely refreshed my /system folder. Original post below:
--------------------------------------------------------------
Hello XDA forumgoers, longtime reader first time poster here. I'm currently posting because I made a few mistakes. Several mistakes, actually.
1. In my quest to de-bloat my XT860, I accidentally removed one file too many, which caused my phone to mysteriously not have a cell signal. (com.motorola.service.main kept crashing.) So I hit the forum and grabbed a system dump from this thread (thanks Willis111):
http://forum.xda-developers.com/showthread.php?p=17501981
I had bought the phone with some version of Cyanogenmod Recovery installed by the previous owner, so I was able to use that and ADB to stick the .apks and .odex files in the /system/app folder, chmod 644 them, and even factory reset for good measure.
2. As I soon found out, I had somehow made things worse. The phone, when boot into, shows the "press android to begin" page, but com.motorola.service.main and some other apps keep FCing on me, and I can't progress past that screen. In my haste, I didn't backup any of my system folders at all, though, I still backed up my apps with Titanium.
Tl;dr:
presumably none of the /system/app apks boot, most notably com.motorola.service.main. How do I fix this? Can I?
Try to flash
http://forum.xda-developers.com/showthread.php?t=1288823
You also need to chown 0:0 both the apk and the odex
Have you tried using my original system dump? It was taken with dd, so things like symlinks and the other sort should be functional. The only caveat is that a number of apps were frozen at the time, so you may need to unfreeze them with titaniumbackup.
http://www.multiupload.com/SORQERFAYT
DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?
jonsicoli said:
DoubleYouPee: Is this that chinese rom I've heard of? I heard that if I flash this, I can't root my phone. So I think I'll save this one as a last resort.
eww245: chown'd, no result.
daniflunker: how do I open this?
Click to expand...
Click to collapse
What about rootkeeper?
DoubleYouPee said:
What about rootkeeper?
Click to expand...
Click to collapse
I can't get past the "click android" screen, so I probably can't install or run it. Any way to do it via adb or Cyanogenmod Recovery?
I really appreciate the help.
jonsicoli, if you want to restore your *entire* /system folder (not just apps) you would run a similar command-set as this.
1. Copy the file to the internal memory
adb push c:\path.to.folder\mmcblk1p21.img /sdcard
the file will be located in the root of the sdcard (or you could drag and drop the file in USB storage mode)
2. Do a full restore on system memory *I have not checked to ensure this is working... but a command similar to this should work
adb shell
su dd if=/sdcard/mmcblk1p21.img of=/dev/block/mmcblk1p21
- wait -
(it would have to write about 500mb and replace all of the contents of /system )
reboot
_______________________________________________________
Okay, if you just want to look at the files, you could use a linux machine to mount the filesystem (it is a standard ext3 FS) or you could do what I have done on my windows system:
Install EXT2FsD from http://sourceforge.net/projects/ext2fsd/files/latest/download?source=files
Then install OSFMount from http://www.osforensics.com/tools.html
Point the OSFMount program to the img file that you downloaded and assign it a drive then voilla!
I am pretty sure this is a bit of overkill, but this should completely restore your system close to factory (minus the APKs that were upgraded/disabled, plus the fact root was done)
Thanks Danifunker! I reset my entire /system folder, and restoring my user app backup. I'm just relieved to have my phone back. Now to mark this thread as solved.
Awesome!!!!!! Glad to hear my system dump works! Thanks for testing
My command lines were written correctly also I guess?
Sent from my XT860 using XDA App
searched for like 8 hours until i found this thread. Just what i needed, i had system image for 2.3.6 from your other post but no command.

Bootloop problem after freezing Homescreen Selector

Hi
First post here, I'm new to Android and rooting but I know my way around computer systems in general so hoping you guys can help me, haven't seen a thread about this exact problem so far.
I've semi-bricked (bootlooped) my Samsung Galaxy Ace running Gingerbread, having rooted it last month using the upd_1 package and enjoying a bloatware-free phone, happily installing apps onto my second partition on my SD card. I've not changed my ROM, just the stock is good enough for me for now. However I was getting continually prompted by Homescreen Selector nags at powering up for some reason and I thought I could disable it by applying Freeze using LInk2SD, but since doing that I continually get the Samsung logo, the orange "explosion" (I'm with Orange) then a vibration and the whole cycle repeats. My guess is the operating system can't find the selector.apk app since I froze it.
I thought the solution would be simple - use adb shell to rename back from selector.fro to selector.apk. However I'm unable to find any such file in my system/app folder. There are a load of other apk and odex files but not that one. When I type su I get "permission denied", though I definitely rooted my phone but I don't think I have my bootloader unlocked.
I don't have CWM installed or any backups unfortunately (yes, I know...), so even if I took one now prior to a factory reset, surely the same problem would come back if I were to restore from any backup I were to take now. I can get into Recovery and Download screens ok but don't want to restore the whole ROM unless I have to, since I know it's only one APK that is at fault.
So, please can anyone tell me how to locate the selector.fro file to turn it back to selector.apk? Or can't I do that without unlocking the bootloader first, or is there another solution?
Many thanks in advance,
Graham
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
QNBT said:
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
Click to expand...
Click to collapse
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
gkey2112 said:
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
Click to expand...
Click to collapse
You can extract it from the ROM's zip file, just locate it as you would on your phone.
But I don't have a ROM zip file. I'm not using a custom ROM, just stock. I may go down the custom ROM route one day, but for now I just want my phone to work again in the quickest way possible.
All I need is a copy of the original stock home selector APK. Can anyone help here please?
Found the file!
Never mind, got the apk from another thread. Flashing tonight...

Flashing an 4.2.2 rom and file structure issue.

I decided to start this thread as both assistance for some as well as a collaberation on workarounds when you a person flashes a 4.2.2 rom coming from a 4.1.2.
Just like some (maybe most) I flashed CM 10.1 and played around a bit with it and decided it was just not ready to be run as a daily. Being the flashalohic that I am, I made sure I backed up before flashing CM 10.1 so when I went into recovery and went to restore imagine my surprise when it was blank, yep nothing was there. Why did this happen? Well doing some research and reading/searching I found out that the update from Android 4.1.2 to 4.2.2 changes the file structure of the 'virtual' sdcard on our devices. Actually it changes it for every device. What has changed is that the ability to add user accounts, similar to any regular computer, has been implemented. However, if the proper steps are not taken before you flash a new 4.2.2 Rom, you will end up with a huge mess and run out of room on your device in a hurry.
The actual location when viewed with a root file manager has been here on 4.1.2:
/data/media
And though you will see the same files in /sdcard and /storage/sdcard0, those are just symlinks to the same info, just like a shortcut (on a windows box) or alias (on a mac box). Once you flash a 4.2.2 ROM, the actual location gets changed (and all the files moved) to here:
/data/media/0
And the symlinks get changed to /sdcard/0 and /storage/sdcard0/0. On the surface, no big deal, right? Wrong. The problems arise if the version of your custom recovery is not compatible with a 4.2.2 ROM. If it is not and you keep flashing 4.2.2 ROMs you might soon end up in trouble. If, while using the 'older' custom recovery, you continue flashing, your sdcard ends up somewhere around here:
/data/media/0/0/0/0/0/0 (etc.) with all your files copied to every '0' directory and your symlinks end up the same way, and your device quickly runs out of space (the dreaded "your device is low on storage" message).
This may also make it very difficult to restore your nandroid of a 4.1.2 ROM as well. If you are already in that situation, not to worry, the solution for that is later in this post.
So far I have only been able to to copy all the files found in the last /data/media/0/0/0/0 (?) folder to my computer. Then using a file manager that will show hidden files and folders, copy/move the files in the last '0' directory to:
/data/media/0
And then use file explorer to delete all the other '0' directories until I have just this one:
/data/media/0
leaving nothing else in the symlinks but /sdcard/0 and /storage/sdcard0/0. This techniques is if you end up with a huge file structure.
****BACK UP YOUR SD CARD FIRST!!!!! before deleting any 0 folders!!!****
NOTE: A reboot of your device is essential at this point.
If after flashing a 4.2.2 ROM you decide you don't like it and want to restore your nandroid to your saved 4.1.2 ROM, how does that work out?
1.) Get yourself a (good) root file browser.
2.) Brows to /data/media/0
note: this is where android (and almost everything else that uses a Linux kernel) mounts anything that is considered "external" storage.
3.) Do all of your file fixing from here. It will make changes universally.
4.) select all within /data/media/0 and then paste everything back into /data/media selecting merge and/or overwrite. Once done, just delete the /data/media/0 folder, reboot your phone and Profit.
This is a pain and I agree but at this point is the only way I know how to get around this. If anyone knows other ways please share.
* While writting this I came across this info from user elfaure. I havent tried this yet as I am at work and get crappy signal but please post results if you try and if it works, please thank him! *
elfaure: Ok folks for next guy who decides to upgrade to 4.2 but does NOT want the multi-user environment, give this a try.
1. Download the attached file
2. Remove the .txt extension
3. Copy it to your /data directory
4. Open Android Terminal Emulator (Free Market app if you don't already have it)
5. At the prompt type "cd /data"
6. Type "chmod 644 .layout_version" on the file in /data (/data/.layout_version)
Code:
cd /data
chmod 644 .layout_versionNow when you upgrade to 4.2 you should stay single user and have no /data/media/0 directory when you are done. If anyone tries this please let me know if it works and thank me if it does.
ps-its just a special file in a special location, the presence of which tells Android NOT to upgrade your system to a multi-user environment. If you later decide you want multi-users, delete the file and reflash (from recovery) the stock or custom firmware or ROM or recovery. If your custom ROM or recovery wipes the entire /data partition less /data/media including this file, obviously then this will not help, but with latest versions of ROMs and recoveries that should not happen any more.
http://forum.xda-developers.com/showthread.php?p=40911246#post40911246
It also looks as if he may be working on a script to help as well and I will keep track and update as needed.
So far this is what I have come up with and I hope it helps some and I hope others that are smarter than I can correct me if I am wrong on any of the above or other add information on other ways to correct this.
I think this is part of my issue but I don't have any 0 folder under data?
I too flashed the 4.2.2 ROM, and noticed that every everything on my sd card had somehow moved to my internal memory? When I went to reflash the ROM it failed. It I also tried to reflash the ROM I was originally running and it too failed. Luckily I was able to do a nandroid restore so the phone is "usable" but TWRP 2.5 still does not see my my external sd and that seems to be that make reason I can not do anything within in the recovery.
Any suggestions?
The op is telling you exactly how to fix it.
lizardking7112 said:
I think this is part of my issue but I don't have any 0 folder under data?
I too flashed the 4.2.2 ROM, and noticed that every everything on my sd card had somehow moved to my internal memory? When I went to reflash the ROM it failed. It I also tried to reflash the ROM I was originally running and it too failed. Luckily I was able to do a nandroid restore so the phone is "usable" but TWRP 2.5 still does not see my my external sd and that seems to be that make reason I can not do anything within in the recovery.
Any suggestions?
Click to expand...
Click to collapse
Let my clarify:
I have used two different file managers and even used to terminal emulator using ls -la to make sure i have no hidden files
sdcard0/data/ there is no media directory
Maybe this isn't my problem, since I don't see any file/dir with a 0, but all this mess started when I loaded up a 4.2.2 ROM?
Everyone should check this out to aid you in your flashing addiction.
Happy flashing!
http://forum.xda-developers.com/showthread.php?p=42237249
Sent from my HTCONE using Tapatalk 2
I flashing an aosp Rom and nothing in my sd card changed. Maybe I'm lucky?
Sent from my HTCONE using Tapatalk 4 Beta
Good information
so does this work? will i be able to nad back to sense and all my files are in the right place?
I couldn't get it to work, the attachment. However the new recovery I linked to looks to have promise but I haven't tested it yet cause I'm remote right now and need my phone at the moment. Will give it a go this weekend.
Sent from my HTCONE using Tapatalk 2
Seems @imneveral0ne has found a way to assist folks that like to go between 4.2.2 and 4.1.2
Check out his thread here.
http://forum.xda-developers.com/showthread.php?p=42512892
Sent from my HTCONE using Tapatalk 2
Weighing in, worked like a charm for the most part. TWRP recreated another TWRP folder inside its original TWRP folder (it has to be left at /data/media/0/TWRP for you to be able to reinstall a nandroid backup) [also forgoing obvious yo dawg joke here], but besides that my phone is back to being right as rain.
Nice write up on this issue. Thanks
sent via my tranquil⊙NE
I'm sure it wouldn't work for doing a nandroid restore, but on my Galaxy Nexus I would just make certain I had the latest version of TWRP, boot into recovery, format the SD card, and then push the rom files to /data/media/ and flash. That is my only complaint about this change, really...truly "clean" installations are inherently more risky or difficult, dependent on your knowledge level.
It won't let me delete folder 0 no matter what. Inside that folder is a ViperRom folder that won't delete as well no matter what I do!
Thanks for this info. I think I'm going to take the plunge this weekend so this will be very helpful info.
Sent from my HTC ONE using xda app-developers app
I think it moved my ROM data into the 0 folder, how do I get it out? Everything else from the 0 folder is deleted except for ViperROM's folder, and whenever I try to move or delete it, it just fails the operation. I already have a copy out of the 0 folder, but I still want it out, because otherwise I can't flash things, since it just shows the the almost* empty sdcard/0 folder. Help? Should I just put my mods in the 0 folder and deal with it?
Bseagull said:
I think it moved my ROM data into the 0 folder, how do I get it out? Everything else from the 0 folder is deleted except for ViperROM's folder, and whenever I try to move or delete it, it just fails the operation. I already have a copy out of the 0 folder, but I still want it out, because otherwise I can't flash things, since it just shows the the almost* empty sdcard/0 folder. Help? Should I just put my mods in the 0 folder and deal with it?
Click to expand...
Click to collapse
No. There is a script out there you can flash that will help. Check out post # 10.
Sent from my One using Tapatalk 4
So can we delete the legacy file now? I haven't done anything with my internal storage since coming from 4.1.2 for the first time. It looks like twrp 2.6.3 copied all my files correctly to the 0 file but all the files are still also in "legacy" folder. Is it duplicate that I can delete from legacy or are they just symlinked? I am never going back now that we have official 4.3 release.
ivwonka said:
So can we delete the legacy file now? I haven't done anything with my internal storage since coming from 4.1.2 for the first time. It looks like twrp 2.6.3 copied all my files correctly to the 0 file but all the files are still also in "legacy" folder. Is it duplicate that I can delete from legacy or are they just symlinked? I am never going back now that we have official 4.3 release.
Click to expand...
Click to collapse
I am not certain to be honest. It looks like the file structure didn’t change with the release of 4.3 so it’s possible that they are symlinked. If all your files are moved to the /0/ folder and you have nothing in the legacy folder it would make sense that you would be able to but I have yet to test this.
I suppose this weekend I could back up the phone and file tree and give it a shot
Thanks for the response. I haven't tested out yet either but will post back if I do.

Can't move TWRP folder off phone

I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work. Chmod 755 and 777 doesn't do anything. I was able to initially copy the TWRP folder into the downloads folder in the TWRP file manager, but now it just hangs there if I try to move it again.
How do I get access to my backup?
evanft said:
I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work.
How do I get access to my backup?
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
6Binford said:
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
Click to expand...
Click to collapse
Unfortunately, there aren't any solutions in that thread.
evanft said:
Unfortunately, there aren't any solutions in that thread.
Click to expand...
Click to collapse
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
josephpalozzi said:
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
Click to expand...
Click to collapse
I didn't even see GeoFX's post for some reason. That looks like it worked. Thanks!
TWRP and NAND Backups
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Florestan2 said:
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Click to expand...
Click to collapse
The way I understand it, and I might be wrong, is that before Android 4.0 (or maybe 5.0), the partition containing user data was called /sdcard and apps were stored in a separate partition. The partition where apps went was significantly smaller, which could result in people running out of space for apps while still having a ton of free user data. To remedy this, the newer version of android places apps and user data in the same partition (called media). The /sdcard that you see is a symlink (shortcut) to this new partition, and is included so that older apps that were designed to expect the /sdcard partition to be there will still work.

Categories

Resources