Related
...[from elsewhere] ...I didn't see any mention of this in the how-to threads so I didn't back up my EFS files from the stock rom. Anyone here have had any issues with this after going back to stock?
Click to expand...
Click to collapse
That is an example of things that are scattered in many threads...specifically, what are the things you should DO or SAVE before flashing a new ROM?
Above seems to be one (except is "EFS" a folder or what?). Would folks please offer your suggestions of the "protective" steps to be done/preserved in case of future difficulties.
Actually, in addition to the one quoted, doing a Titanium Backup is in almost all of the how-to discussions, so I guess that is already covered.
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
mcord11758 said:
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
Click to expand...
Click to collapse
Recapping this...
EFS is a file. Can save it using Root Explorer or Android Mate.
I have copied down all the data under the battery. Is there more than that in this file?
I am confused about second paragraph. You mention download
Android ID Changer
Busy Box
Which one is it that captures the Android ID? And obviously it saves it, but where?
Yes, odin is mentioned in the how-to's, but it IS part of the flashing process. I am looking for things that should be done BEFORE starting that.
Yes, I know the build (1006). It is part of the data under the battery. And flashing wouldn't destroy or modify that.
Yes the efs had your csc or product code. If you flash a rom that is a port from another device this may be changed. Not an issue if you do not use kies.
Busybox is an app that installs commands onto your phone that certain programs need to operate correctly. Titanium backup and android id changer need this to function correctly. Android id changer saves your id in a file on your internal sd. The file is called update.id when you flash a rom you open the app again click load id, then change id. Phone reboots, id us back to your original id
Odin is a utility that flashes you back to stock 2.1. It is used by many as a safe way to go from rom to rom with a clean install. It is also used to recover from software bricks.
If you have more questions that pop up pm me, this way we are not clogging up the q&a
I think the exchange helps many people who I assume, like me, are trying to sort all this out.
MAIN purpose of the thread is to identify things to do/save before beginning the 'change to another ROM' process--which to me would include the Odin flash back to stock if you aren't there already.
But these side question resolutions are pertinent.
Your Busybox comment threw me a curve. It sounds like you are saying it installs stuff TiBU and Android ID Changer need in order to work. You mean TiBU as downloaded from the market does not work as a standalone app?
tibu needs busy box. If you download tibu and open the app there is a button on the bottom that says problems. If you click it it will also look to install busy box commands.
You are right about the usefulness of threads like this, no disrespect but it looks like you joined xda 4 days ago. These types of discussions are constant and rehashed on nearly a daily basis. For some odd mental quirk I read then all and help when I can. There are a thousand questions you can have, the offer to pm was to keep it easy
I have been reading for two weeks--I mean reading A LOT, not just 4 days ago; that was when I registered on the site. This is a =wonderful= resource, but it is a plain fact that what you need to know is scattered all over the place, both video and written how-to's. I have not found a single one that includes everything you need to know. I mean, for example, they will tell you to do something, which seems trivial to them, but which really involves other knowledge. And that sounds like a non-isue, but in fact it is a complete showstopper for "us" types. Yes, you can go off hunting to clarify the incompleteness, but that is exactly what I am talking about--hunting all over the place.
By the time someone gets to the point they can create something with completeness, the problem is...they are already to the point they can create such a thing. That contradiction arises from it being almost impossible to remember what you didn't know "back then."
I had been studying HARD trying to get "it," everything you need to do to flash a different ROM. Then, a day or so ago, in all that hunting around I speak of, someone mentioned "be sure you ... before you flash." It dawned on me that, when you think you are ready to flash, you aren't. There are things that should be done BEFORE. I started the "hunt" again as alluded to here. Then I said, dang, all us newbies would be well served if all the preliminary do's and save's were in one thread (preferably, ultimately in one LIST). Thus the reason for this thread.
If I am wrong, and other newbies really don't need to know these things, then yes, it can be done in PM. Others will never see it, and still be stuck in the hunting-all-over mode. Thus, I think it is desirable and helpful to others to put it in public, in one thread.
Once again no disrespect. Your point is taken.
Tibu to back up all your user apps, no system information. unless you want to learn how to use odin in the case of issues
Android id changer to back up your android id
Rom manager to back up your current setup, and flasg clockwork recovery. Never restore a backup of one rom on top of another rom
Contacts to external sd, sim, or sync with google
Efs using root explorer to copy folder and save in pc
Odin to flash stock and or recover from software brick. Builds 1010 and above do not use one click odin
No offense taken, and that's a great input. Thanks.
If others see anything else, please contribute.
Ok, I am also new at this, I have flashed 3 Roms. This is what I have done when changing ROMs.
Download Titanium Backup and rom manager. Back up your apps with Titanium Backup.
Download the ROM you want to flash.
Download Odin.
Turn on usb debugging.
Plug phone into the computer, pull down the notification window and click on usb to mount the sd card.
Open this up to look at files.
You should have an update.zip file you can copy to your desktop. You also should have a folder named Titanium Backup that you can save as well.
Once you have this, you can begin.
Take your phone to stock using odin. There are several tutorials available. I used this one,http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 because I have a 1010 phone.
Once this is done, I push the voume up and down along with the power button. You will get a menu giving you a choice to reinstall packages. You need to click this, go to yes, and it will pull up to the same menu again. Hit reinstall packages again which will get you to clockwork recovery.
Now, I chose to wipe/factory reset to make sure my phone was "clean".
Then, I chose to apply the update.zip.
Then, I chose to install a zip file from the sd card, scrolled down to the rom file, and chose it.
Then it will install the Rom. You will choose go back, then reboot the system. Then your Rom should be installed.
I think I remembered everything. I used a few tutorials:
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
and this one:http://forum.xda-developers.com/showpost.php?p=10183875&postcount=4
Hope this helps!
OOPS. Thanks, but this thread is for things to do or save BEFORE starting the ROM change.
So... let's say that you didn't save your android id before you flashed... will that cause problems?
beryxil said:
So... let's say that you didn't save your android id before you flashed... will that cause problems?
Click to expand...
Click to collapse
You tell me. Did you? Are you experiencing problems?
it depends on the rom you are using. You may experience issues downloading from market and certain games may give you issues.
If you did not save it and you are not having problems then no big deal. You can go back to stock and save it, then flash again.
Let me apologize first of all as I come from 5 years of using Windows Mobile knwoing what I am doing (cooking ROMs included) and now just got my Galaxy /Android a couple weeks ago and am blank at all of it.
After messing up with some system files and (useless) stock applications (like I removed stk.apk and other stuff) I decided to do a full hardware reset as the phone started getting random crashes.
But after the full reset things only got dramatically worse. I quickly realized all the missing system apps are still missing (I thought they'd be "restored") and basically nothing works, just crashes one after the next, cant use anything.
So, a hardware system reset on the galaxy, doesnt really reset anything except user installed apps and settings... amazing
Can someone please tell me (the idiot here, I know) how to do a real full restore where all system files, all missing files and positively everything gets back in the Tab as it was originally?
What a flippin' nightmare... Thanks in advance very much!
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
if you don't have a backup of this apk, download a rom (like Modaco or Overcome),
open with winzip and extract the Stk.zpk from system/app and push it to /system/app on your Tab using adb (remember set the permissions to 644 after push).
A hardreset NO restores deletions on /system
Note: Other files that are not deleteable in /system/app are: Browser.apk, Email.apk, TouchWiz30Launcher.apk and TwWallpaperChooser.apk
Note (2): For your convenience, i attach the Stk.apk file from Overcome-1.1.3. Try it
Note (3): In order to restore ALL system data and apps, you need to restore a full rom.
Click to expand...
Click to collapse
OK, first of all a big thanks for both file and info. Aside from the Stk.apk, the biggest thing that made me run into problems was trying to update my Contacts.apk:
http://forum.xda-developers.com/showthread.php?t=907399
things didnt work out for me and even after restoring the original files (Contacts.apk and Contacts.odex) nothing really worked again, reason for wich I tried a system reset.
Now, do I need to re-root the Tab or its still rooted, and can I perform the operations easily with Root Explorer like I did before? You mentioned to use adb and set permissions to 644 after push but, sorry again for the ignorance, I have no clue what adb is nor what/how to set permissions. Pathetic to be ignorant huh?
My last 2 questions are, where could I find the original Contacts.apk and Contacts.odex and if needed a full ROM to do a total restore?... hopefully I wont need to get to that point?...
Thanks a million again.
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
bartito said:
hi,
try to download overcome-1.1.3, and extract all the deleted apk's from system/app directory. push into the /system/app in your tab.
the apk's of overcome are deodexed (you don't need the .odex files). after that, wipe your data/cache and reboot.
if this don't works, try with roto rom
Click to expand...
Click to collapse
Hmmmm thanks again but I think Im beyond all this. I dont have a file manager on my system, just realized I deleted the useless stock one and had repalced it with Root Explorer and ES File Explorer. I have them on my External SD Card to install them again but withou a file manager or an app installer cant get to them. And I tried download an app installer from the Market and get Framework errors non-stop and downloads do not initialize... I think Im beyond a quick fix... how do I get my hands on a stock full ROM to restore everything... and how? What a nightmare... gotta tell you, I love Windows Mobile... I love it... never ran into anything like this in the past 5 years of using it... never...
Thanks again!
use "adb" in order to access to your tab from your desktop pc.
bartito said:
use "adb" in order to access to your tab from your desktop pc.
Click to expand...
Click to collapse
Cant. Dont even know if I need Kies installed or not (I did have it installed) but adb just asks me to connect the phone and thats it... its connected aready... this is desperating...
OK I did manage to connect with adb but, how to I install applications? I can navigate to my SD card where I have ES File Explorer and Root Explorer but dont seem to be able to install them... Also if i try to copy Stk.apk I get immediately an failute message... this is crazy...
OK so I managed to install ES File Explorer and Root Explorer with adb... crazy process. It seems my phone is still rooted after the reset. From the phone I copied Stk.apk back to /system/apps where it was before deleted.
But needless to say nothing got fixed... not sure if Stk.apk is now "actually" installed or just there in the folder. But still nothing works and crashes every 10 seconds... logs provider, dialer, phone, framework, contacts... its all a firework of crashes...
Given that you've hard reset your device already, you are pretty much wasting your time trying to "fix" what you broke by messing with /system, and you should really just flash another ROM.
My suggestion would be to follow the advice on this thread.
Regards,
Dave
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
VeEuzUKY said:
Yeap, that what i did and it was succesfull. My only issue is that Id like to convert my Tab's file system to ext4 to improve speed and performance and then update to the 1.4Ghz OC Kernel. I have no idea how to do those 2 things... actually Im not sure I understand the difference between a ROM and a Kernel... I assume a Kernel is part of the engine of the ROM itself but I have no idea how to perform the update. I read countless threads and its all scattered info without finding one straight to the point guide on how to do it...
Thanks again
Click to expand...
Click to collapse
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
foxmeister said:
Part of your problem is that you are trying to run before you can walk! Your experience with WinMo is of pretty much no use to you in the Linux/Android world, and until you get a better handle of how everything hands together you are always going to feel a little lost.
Personally, since your device is now up and running again, I'd suggest that you hold off doing anything else for while, until you get a chance to catch up with some of the basics. Once you are a little more familiar, you can then start with something simple like flashing the MoDaCo kernel (instructions here) to support EXT4, and to give you access to ClockworkMod recovery.
IMO, whilst EXT4 and O/C kernels will give you a performance boost, they are not as noticeable as jumping from a shipping ROM to one of the JMx development builds that Samsung has put out. If you are running JMI, you should already be feeling that the device has got much snappier.
Regards,
Dave
Click to expand...
Click to collapse
Yes Dave you are right, right and right again!!! Thank you for the wisdom and advice!!!
The main thing I have understood with today's messy experience was that the actual ROM files are never deleted or damaged as long as you dont access them via a rooted tool and start deleting them. Now I understand that Titanium Backup, Sprint Backup (my favorite), My Backup Pro and others, only back-up and restore what the user installs on top of the ROM itself. So a full "reset" wipes all that data but leaves the ROM files as they always were. If they got damaged in the process, they'll still be damaged till a a full ROM restores all system data, now I get it.
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Till I find an app or way to do a simple one-click "backup everything" and then "restore evertything" I always feel vulnerable to changes I make to the Tab that may get it unstable or corrupt and then not being able to be restored properly without a full ROM Flash and then re-installing all from scratch.
With WinMo, I could do all sorts of crazy experiments and tweaking and after that, a registry restore or back-up restore would bring me back my phone to exactly like it was with all my stuff and configuration in a matter of seconds or minutes. Thats what I need to find out with this Tab/Android and then Im ready to be able to explore messing up with this knowing I can always easily go back within minutes to the state I had before with all my apps and settings.
This is what I need to learn next how to do! Trampoline without a safety net is not a good idea. Ive alwways loved WinMo for the ease of backing up and restoring whatever I was doing on my handsets withjout ever worrying to put myself at risk to loose it all. I need to learn this on Android and its definitely more intricate!
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
instechgainza said:
just put sdcard into your samsung tab and flash modaco kernel amd it will automatically covert to ext4, after that you can flash the 1.4ghz kernel you wanted.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
VeEuzUKY said:
Sorry, I cant follow you. I put an SD card in and flash modaco kernel? What files do I put on the sd card for this effect?...
Click to expand...
Click to collapse
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
instechgainza said:
no...you need a kernel to flash via odin, you need sdcard mounted so that it will backup all files automatically while converting to ext4..head over to modaco kernel section amd follow the instruction.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Where is the modaco kernel section you refer to? I can search for hours and find zilch... these blogs are endless...
VeEuzUKY said:
What I still dont get is the issue of bakcing up and restoring. In Windows Mobile, a toll like SPB Backup has a simple option called FULL BACKUP and that backs-up everything on top of the ROM and then restores everything after a full reset on top of the ROM again like it was before. The problem I have with apps like Titanium Backup, Sprint Backup, My Backup Pro, etc... is that there is not a "BACKUP ALL" option... one has to backup "data", "settings", "apps" and I always feel stuff will be left behind and then not restored.
Click to expand...
Click to collapse
What you want is a Nandroid backup, which you can only make from a recovery image like Clockworkmod recovery.
Essentially, this does exactly what you want, but you need to flash a new kernel (e.g. the MoDaCo kernel) which supports Clockwordmod.
Regards,
Dave
bartito said:
deletion of Stk.apk causes FC's in phone and acore.
Click to expand...
Click to collapse
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
b0ricuaguerrero said:
i beg to differ about stk.apk fc's your phone. that's the first thing i delete when removing system apps with no fc's
refer to this link about having a bare bones system. stk.apk is for management of multiple sim cards
http://wiki.cyanogenmod.com/index.php?title=Barebones
Click to expand...
Click to collapse
When I delete stk.apk (for me useless useless useless) the first thing that happens immediately is that when I hang-up on a call made or received, the Tab vibrates then freezes for about 5 seconds then tells me the phone application has crashed. I tried this with 2 ROMs now as a test and its guaranteed. More even, if you use a program like SYSTEM APP REMOVER you can emulate the removal of an app by disabling it... it only takes me to disable STK and a reboot for the phone not to work. cant get rid of it, that simple
Can one of the devs, share with us what happens when Android loads what does it do to the efs directory, what is the purpose of each of the files in this directory. There are not so many.
efs
.....nv.log
.....nv_data.bin
.....nv_data.bin.md5
imei
......nvmac.info
.....bt.txt
.....mps_code.dat
I searched on google and did not find anything definitive.
StarLog said:
Can one of the devs, share with us what happens when Android loads what does it do to the efs directory, what is the purpose of each of the files in this directory. There are not so many.
efs
.....nv.log
.....nv_data.bin
.....nv_data.bin.md5
imei
......nvmac.info
.....bt.txt
.....mps_code.dat
I searched on google and did not find anything definitive.
Click to expand...
Click to collapse
Your Google-Fu is weak: http://www.galaxyroot.com/how-to-efs-folder-backup-restore-nv_data-bin/
General gist: Don't mess with it.
knightnz said:
Your Google-Fu is weak: http://www.galaxyroot.com/how-to-efs-folder-backup-restore-nv_data-bin/
General gist: Don't mess with it.
Click to expand...
Click to collapse
Hey thanks, but I did find that, I already know how to backup and restore it.
My question was implied to be a lot more technical, like what byte structure in each file, has what representation.
What part of the bootup process touches or creates the files.
But thanks for sharing.
The file format of files in /efs has not been disclosed. People have tried reverse engineering it with various degree of success.
It does contain IMEI, carrier lock information and other radio related stuff. See unlocking threads here and in Galaxy S forums.
There is also daemon (efsd) which monitors, backups and checksums files in efs.
The radio firmware must have some way of accessing files in efs, but not directly, probably via RIL, since Galaxy S CyanogenMod folks can move it to different file system.
There is probably a lot of useful and interesting stuff stored in these files but messing with them is also dangerous, so backup first.
Thats what I needed to hear, so I must dig more. thanks for the headsup on galaxy s forum
Update 2:
So now I can see most of the files with ES, but OI file manager isn't seeing them. What the heck is going on? Ghost files?
Alright, so I'm in a bit of a pickle.
I was having problems with Rdio and wanted to wipe all traces of it from my phone to install an older version. Using ES File Explorer, I searched for all the files related to the app in "/" and once I found them, I foolishly used select all and delete. Problem is, it seems "select all" actually selected all the folders in / and not only those found using the search function.
The odd part is I can see all the folders in / when I use OI file manager (though some are empty, namely /data and /datadata), but not when I use ES.
Does anybody have an idea as to what I can do? Odd thing is the phone is working fine and not all files on it have been deleted (the files inside EFS seem to have been though, but I still have signal). I'm afraid to reboot it since I figure it might become bricked. I've got a recent Nandroid backup which wasn't deleted, so I'll be fine if I can get to recovery, but is there any chance of that not happening?
Anyways, I'm feeling really dumb and stressed out.
Thanks for looking and/or helping!
Cheers!
Update
Making a call seems to have restored the files (.bak and others) in the efs folder and some other files seem to be reappearing. Maybe if I just wait it out all the files will come back from the dead? Files that weren't showing 10 minutes ago are back and are dated earlier than today.
Again, I'm mainly looking to know if I can reboot into recovery (or normally?) without many problems.
Thanks!
Sorry I know from researching this that people get annoyed when a thread about this comes up but I've been looking for a solution for a few days on and off and read a lot of threads on it and can't find the answer. So I now know that flashing a 4.2.x based ROM using an outdated TWRP caused the problem, and using the latest version of TWRP will prevent the directory structure from getting more layers deep (and it has), but how do I fix the damage that is already done? I'm new to this stuff so maybe the answer is obvious and I'm just not seeing it. Should I move the files a few layers down manually and delete the redundant layers? I've read that 4.2.x uses the /0 structure to support multiple users so do I move the files down to that layer? I've also seen people talking about formatting the drive and starting fresh, but like most threads about this they just die before a successful solution is confirmed. Will flashing a new ROM rebuild the directory structure on a formatted drive or would there be an extra step involved?
I plan on flashing back to a stock ROM as soon as I get this sorted out and there is nothing on the device that I care to save except a couple Titanium backups that I copied over to a PC.
Thanks for any help.
Ryan_Mc said:
Sorry I know from researching this that people get annoyed when a thread about this comes up but I've been looking for a solution for a few days on and off and read a lot of threads on it and can't find the answer. So I now know that flashing a 4.2.x based ROM using an outdated TWRP caused the problem, and using the latest version of TWRP will prevent the directory structure from getting more layers deep (and it has), but how do I fix the damage that is already done? I'm new to this stuff so maybe the answer is obvious and I'm just not seeing it. Should I move the files a few layers down manually and delete the redundant layers? I've read that 4.2.x uses the /0 structure to support multiple users so do I move the files down to that layer? I've also seen people talking about formatting the drive and starting fresh, but like most threads about this they just die before a successful solution is confirmed. Will flashing a new ROM rebuild the directory structure on a formatted drive or would there be an extra step involved?
I plan on flashing back to a stock ROM as soon as I get this sorted out and there is nothing on the device that I care to save except a couple Titanium backups that I copied over to a PC.
Thanks for any help.
Click to expand...
Click to collapse
Yes,Moving the files to the /0 Layer will Work.OR you could also also move it to the Root of the Memory.even that will Work.
manasgirdhar said:
Yes,Moving the files to the /0 Layer will Work.OR you could also also move it to the Root of the Memory.even that will Work.
Click to expand...
Click to collapse
Thanks! Moved manually and deleted the junk and all is well!