Database Develop

[Q] Install a new ROM without loosing data

Hi,
I want to install a new ROM without loosing any data and settings. I have made a Titanium backup.
As I now have only one SDCard, will ti be OK to copy the titanium directory to the PC, do the clean install, and copy ONLY the TB directory back to the SD, and do a restore?
Thanks for answers,

velizet said:
Hi,
I want to install a new ROM without loosing any data and settings. I have made a Titanium backup.
As I now have only one SDCard, will ti be OK to copy the titanium directory to the PC, do the clean install, and copy ONLY the TB directory back to the SD, and do a restore?
Thanks for answers,
Click to expand...
Click to collapse
If the current ROM is any of the ff:
CM7 Stable (7.0, 7.1)
CM7 Nightly
Phiremod
CM7 MiRaGe KANG
AND the new ROM any of the above as well, you can just do the ff:
Put the new ROM's zip as well as any associated Kernel zips to the root of your microSD card (or anywhere really, doesn't matter. It's just so you can easily see and navigate to it)
Reboot to ClockWorkMod Recovery menu. Advisable if you have the latest CWM installed, which would be 3.2.0.1. (You can get the latest CWM through ROM Manager, which can be downloaded off the Market.)
Once you're there, go to Mounts & Storage.
Format System
Format Cache
Afterwards, go ahead and install your new ROM.
Once it boots up, you will still have all your apps even if you don't use TitaniumBackup since you did not format the "Data" partition.
All of the instructions above is if your install is in your NookColor's eMMC as opposed to running it off a microSD card.
Hope this helps.

les02jen17 said:
If the current ROM is any of the ff:
CM7 Stable (7.0, 7.1)
CM7 Nightly
Phiremod
CM7 MiRaGe KANG
AND the new ROM any of the above as well, you can just do the ff:
Put the new ROM's zip as well as any associated Kernel zips to the root of your microSD card (or anywhere really, doesn't matter. It's just so you can easily see and navigate to it)
Reboot to ClockWorkMod Recovery menu. Advisable if you have the latest CWM installed, which would be 3.2.0.1. (You can get the latest CWM through ROM Manager, which can be downloaded off the Market.)
Once you're there, go to Mounts & Storage.
Format System
Format Cache
Afterwards, go ahead and install your new ROM.
Once it boots up, you will still have all your apps even if you don't use TitaniumBackup since you did not format the "Data" partition.
All of the instructions above is if your install is in your NookColor's eMMC as opposed to running it off a microSD card.
Hope this helps.
Click to expand...
Click to collapse
Did all that,
Booted to CM7.2, lost gmail, lost market. Now trying to roll back.

velizet said:
Did all that,
Booted to CM7.2, lost gmail, lost market. Now trying to roll back.
Click to expand...
Click to collapse
You may need to reinstall gapps.

velizet said:
Did all that,
Booted to CM7.2, lost gmail, lost market. Now trying to roll back.
Click to expand...
Click to collapse
Installing gapps again is part of installing a new ROM, which I forgot to mention. My bad. Just download gapps from ROM Manager, then flash it via recovery or via ROM Manager too.
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz

les02jen17 said:
Installing gapps again is part of installing a new ROM, which I forgot to mention. My bad. Just download gapps from ROM Manager, then flash it via recovery or via ROM Manager too.
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz
Click to expand...
Click to collapse
Hi,
Now I am back to the latest 7.1 Nightly with everything working, had to install market.apk, than gmail.
The reason I do not want to loose data is, as I am not in US, because of some stupid Google policy, I had to sideload some apks like G+, currents, earth, maps, etc. and I do not want to fetch them again.
So my 2 questions are:
1- If I install gapps again, will I be able to keep these sideloaded apps?
2- Is it worth to move to 7.2 at all? (BTW 7.2 RC0 is around 70 MB, whereas the latest nightlies are all around 100 MB)

Why don't you move those .apk files to another folder, say, the eMMC.

votinh said:
Why don't you move those .apk files to another folder, say, the eMMC.
Click to expand...
Click to collapse
Because I don't know what will happen if I move those to another place, say, emmc.

velizet said:
... I had to sideload some apks like G+, currents, earth, maps, etc. and I do not want to fetch them again.
Click to expand...
Click to collapse
Why would you have to? O-M-G! you aren't one of those, DELETERS are you?

velizet said:
Because I don't know what will happen if I move those to another place, say, emmc.
Click to expand...
Click to collapse
The .apk file is more like the package, let's say, like a .zip file (in Windows), you can make 1001 one copies if you want. You can move it from drive C: to drive D if you want. You can move it to the external hdd if you want. You can store it on the cloud if you want.
Basically, you do whatever you want with it.
You might not understand what I meant, I guess.
Just store it (them) to another storage so you can access it (them) and reinstall later if you need.

MISRy said:
Why would you have to? O-M-G! you aren't one of those, DELETERS are you?
Click to expand...
Click to collapse
If you read my op, you will see the answer.

votinh said:
The .apk file is more like the package, let's say, like a .zip file (in Windows), you can make 1001 one copies if you want. You can move it from drive C: to drive D if you want. You can move it to the external hdd if you want. You can store it on the cloud if you want.
Basically, you do whatever you want with it.
You might not understand what I meant, I guess.
Just store it (them) to another storage so you can access it (them) and reinstall later if you need.
Click to expand...
Click to collapse
I know what you mean, but if you look at the context I'm using, that piece of info is not helpful.
What I don't know is the Android system, where it keeps the applications, what happens when I install the system, how are apks affected etc.
For example in windows, you cannot just upgrade the system and expect every installed application to work.
The main point of the original post was trying to understand these.

Unless you want to become an OS developer, in this case an Android OS guru, then you need to learn and understand clearly the structure of it. If you are just a normal user or power user, why make your life harder digging into what and/or how the system and its associated files work???
Just like in Windows, all you need is the installation package (file), install it, it will install to the default directory, all you have to do next is run the executable file and let it run.
Next time, if you want to re-install, all you need is that "installation package". Why do you need to care what happen w/i those default installed folders such win/system32/xxxx or C:\Program Files\xxx?
Yes, sure, you can dig into it to understand more about, but why would you do that if you are just an user?
Back to your question, if I understand correctly, you want to REINSTALL those apps (if they are not coming back after install new ROM) and that's what I tell you.
Another note: unless you are intending installing the completely new custom ROM, /data need to be formatted, otherwise, no need to bother it.

votinh said:
Unless you want to become an OS developer, in this case an Android OS guru, then you need to learn and understand clearly the structure of it. If you are just a normal user or power user, why make your life harder digging into what and/or how the system and its associated files work???
Just like in Windows, all you need is the installation package (file), install it, it will install to the default directory, all you have to do next is run the executable file and let it run.
Next time, if you want to re-install, all you need is that "installation package". Why do you need to care what happen w/i those default installed folders such win/system32/xxxx or C:\Program Files\xxx?
Yes, sure, you can dig into it to understand more about, but why would you do that if you are just an user?
Back to your question, if I understand correctly, you want to REINSTALL those apps (if they are not coming back after install new ROM) and that's what I tell you.
Another note: unless you are intending installing the completely new custom ROM, /data need to be formatted, otherwise, no need to bother it.
Click to expand...
Click to collapse
First of all, according to my philosophy of life, knowledge does not make life harder in the long run.
Secondly, I really doubt copying an .apk file to a medium as you say makes it install automatically.
Thirdly, I want to know when an application is installed, is it contained in its own directory, or does it write something to somewhere like a registry or what, and also where do the former preferences stay, etc.
Hope I can make myself clear.

velizet said:
First of all, according to my philosophy of life, knowledge does not make life harder in the long run.
Click to expand...
Click to collapse
Absolutely true, no argument with this.
Secondly, I really doubt copying an .apk file to a medium as you say makes it install automatically.
Click to expand...
Click to collapse
There is nowhere that I said it will AUTOMATICALLY install. You INSTALL it when you need it.
Thirdly, I want to know when an application is installed, is it contained in its own directory, or does it write something to somewhere like a registry or what, and also where do the former preferences stay, etc.
Click to expand...
Click to collapse
I leave this question to other Android gurus to help you.

[Q] Can we change the font?

I have played Android devices for several years and rooted them for several years. The first thing after rooting is to change the font under /system. But I heared that this may coz OS reset!
Did anybody try this? what if we use a softLink for the font file to avoid the checksum comparing?

Any changes to /system will cause the bootloop reset. However, if you pull a file from /system and symlink it to a file not located on system (/data for instance) then the symlink will not cause a bootloop. When fooling with systemui, you can quickly get yourself in trouble if there is a flaw in your files though, so be careful. I would make a nandoird before trying it.

dbh369 said:
Any changes to /system will cause the bootloop reset. However, if you pull a file from /system and symlink it to a file not located on system (/data for instance) then the symlink will not cause a bootloop. When fooling with systemui, you can quickly get yourself in trouble if there is a flaw in your files though, so be careful. I would make a nandoird before trying it.
Click to expand...
Click to collapse
I have instructions on how to do the symlinking in my HD/HD+ Tips thread linked in my signature. But like dbh369 said, be careful. I was able to make a Vietnamese font for a user doing this. Look in the Q&A section, I think.
Sent from my Nook HD+ running CM10 on Hybrid SD

Thanks above two. Are you sure that Stock will check every file under /system? I plan to replace the font file directly and see the result. I will report the result. By the way, if it's reset, I plan to use CM10.1.

songxiny said:
Thanks above two. Are you sure that Stock will check every file under /system? I plan to replace the font file directly and see the result. I will report the result. By the way, if it's reset, I plan to use CM10.1.
Click to expand...
Click to collapse
Yes I am positive, any new or changed file on /system will reset stock. It automatically checks each file it finds and checks to see if it is on its manifest list and if it does not match the manifest or the checksums there, it will reset. So don't even try unless you want to lose everything including your media files.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
Yes I am positive, any new or changed file on /system will reset stock. It automatically checks each file it finds and checks to see if it is on its manifest list and if it does not match the manifest or the checksums there, it will reset. So don't even try unless you want to lose everything including your media files.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
yes, you are right. I tried to modify the font file directly, stock reset. Even I delete the file, it reset. But, your sysLink tips work.
Thanks a lot.

Complete Stock? [Nook HD]

I am looking for a way to flash complete stock rom witch is no where to be found? I deleted system apps thinking that will do the 8 boot fail thing and actually it didn't work like it did before? I need a flashable stock rom if it's possible? Any ideas?
Edit:
I also did a factory reset in cwm and that did not work either.

If you'd like to restore your device to factory default, you're need to do the "8-boot-loop-fail". This is not an automatic process, and you must do it manually.
Turn off your device.
Turn on your device.
Once you see the text "Nook" on your screen (before your Nook boots up), hold the power button down until the screen goes blank (turns off).
Repeat from step 2, seven more times (totalling to 8 failed boot attempts).
Do this eight (8) times, and your Nook will restore to factory defaults on the ninth boot. On the ninth boot, do not turn it off, let it do it's thing. It will take a while, and will restore the device back to stock; erasing all data on Internal Storage.
When performing the 8 boot-loop, I'd note down somewhere the amount of times you've turned your Nook off, as you can easily lose count.

HiddenG said:
If you'd like to restore your device to factory default, you're need to do the "8-boot-loop-fail". This is not an automatic process, and you must do it manually.
Turn off your device.
Turn on your device.
Once you see the text "Nook" on your screen (before your Nook boots up), hold the power button down until the screen goes blank (turns off).
Repeat from step 2, seven more times (totalling to 8 failed boot attempts).
Do this eight (8) times, and your Nook will restore to factory defaults on the ninth boot. On the ninth boot, do not turn it off, let it do it's thing. It will take a while, and will restore the device back to stock; erasing all data on Internal Storage.
When performing the 8 boot-loop, I'd note down somewhere the amount of times you've turned your Nook off, as you can easily lose count.
Click to expand...
Click to collapse
I haven't messed around with the nook.. but before I was able to delete a system app and it restored itself after a reboot?
Anyways.. Your guide did work. Thank you!
So my question now is are we able to edit stock files without it rebooting?

anthony062991 said:
I am looking for a way to flash complete stock rom witch is no where to be found? I deleted system apps thinking that will do the 8 boot fail thing and actually it didn't work like it did before? I need a flashable stock rom if it's possible? Any ideas?
Edit:
I also did a factory reset in cwm and that did not work either.
Click to expand...
Click to collapse
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD

anthony062991 said:
I haven't messed around with the nook.. but before I was able to delete a system app and it restored itself after a reboot?
Anyways.. Your guide did work. Thank you!
So my question now is are we able to edit stock files without it rebooting?
Click to expand...
Click to collapse
Glad to hear you've got it sorted.
I'm unsure which stock/system app would cause the reboot, as I haven't looked too deeply into it, sorry. Regarding editing stock files; yes, you can edit to your hearts content to what is visible. However once rooted, you can then edit additional files. You may get away with editing certain files, however, if you edit anything within the "/system/" directory, that will force a system reboot, and will erase all your content.
So in basic terms, you cannot edit within the "/system/" directory on the stock ROM. There maybe other files too which are outside this directory, but I haven't tested them either, sorry. But I can tell you that anything in system is a no-go.
All the best.

leapinlar said:
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Thank you! I will save the zip for backup. It will be much easier then rebooting 8 times.
HiddenG said:
Glad to hear you've got it sorted.
I'm unsure which stock/system app would cause the reboot, as I haven't looked too deeply into it, sorry. Regarding editing stock files; yes, you can edit to your hearts content to what is visible. However once rooted, you can then edit additional files. You may get away with editing certain files, however, if you edit anything within the "/system/" directory, that will force a system reboot, and will erase all your content.
So in basic terms, you cannot edit within the "/system/" directory on the stock ROM. There maybe other files too which are outside this directory, but I haven't tested them either, sorry. But I can tell you that anything in system is a no-go.
All the best.
Click to expand...
Click to collapse
That is what I was messing with. The "/system" files. I deleted some stock apps and it did not restored itself after a reboot? I am really shocked that it did not reboot itself back to its default. Last time i deleted an app from the /system it restored back to default. I used the latest Es File Explorer.

anthony062991 said:
Thank you! I will save the zip for backup. It will be much easier then rebooting 8 times.
That is what I was messing with. The "/system" files. I deleted some stock apps and it did not restored itself after a reboot? I am really shocked that it did not reboot itself back to its default. Last time i deleted an app from the /system it restored back to default. I used the latest Es File Explorer.
Click to expand...
Click to collapse
It could be that ES File Explorer did not really delete them. You have to set /system to r/w before deleting works.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
It could be that ES File Explorer did not really delete them. You have to set /system to r/w before deleting works.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I did R/W to the entire system. I deleted voice recording and then i forget the other apps, but it was all the system. I rebooted and it was completely out of the system. I am going to try to make google apps to work with stock rooted without it restoring itself after a reboot?
Edit:
I was on 2.0.6 Firmware if that means anything?
Edit:
You can edit /system/app but not anything else.
I install gapps and rebooted just fine and it kept all my stuff without it restoring itself..

Thanks
leapinlar said:
Look at my HD/HD+ CWM thread linked in my signature. I have a factory rom zip that can be flashed with my bootable CWM card. See item 9 and read the show content for the links and instructions.
The reason you are not back to where you were before you reset is because you were probably on a different version of stock ROM before it reset. The one stored on the device is usually older than what you had on it since it probably had updated itself a few times.
When you flash my plain stock (2.0.0) it will update itself to the latest version (currently 2.0.6) when you register.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Wow, it is useful for me !thanks

Recovery help needed

I did a wipe with Aroma installer and now my external storage won't show up in TWRP. It shows up if I boot all the way to Android, everything is still intact, but it won't show up in TWRP.
EDIT: I'm only having problems with TWRP, which is especially annoying since that's the one I used to make the backup. CWM seems to work fine.

Hi,
If you haven't got a folder called "0" on your Internal memory, create one and put all flashables and other such files into it.
That "0" folder is a 4.2.2 feature and even though our phone is only on 4.1.2, this version of TWRP was built using CM10.1

KidCarter93 said:
Hi,
If you haven't got a folder called "0" on your Internal memory, create one and put all flashables and other such files into it.
That "0" folder is a 4.2.2 feature and even though our phone is only on 4.1.2, this version of TWRP was built using CM10.1
Click to expand...
Click to collapse
I do have that folder, but it's nested within /data/media. Should I move it to root?

HopelesRomantc91 said:
I do have that folder, but it's nested within /data/media. Should I move it to root?
Click to expand...
Click to collapse
I'm not sure why it was there, but yeah move it to root and it should be fine.

Now I have a much more serious problem, as you can see here: my new problem

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.