Develop Bugs

newbie questions

Hi all,
I have 2 questions.
1..
difference between deodexed and odexed?
2..
If my evo is already root and nand unlocked. Do I need to follow toast part 2 every time when I want to install a new rom? Please advise.
Thanks
Jeff

1:
From Berzerker @ droidforums.net found via Google:
Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Click to expand...
Click to collapse
2: No, you don't need to reroot or re-nand-unlock. Once it's done it should be done, unless the ROM is a stock/RUU ROM and removed root, or you've updated over-the-air and the update removed root, or someone screwed up their ROM and made it remove root (people will generally find out and post about the latter ASAP and it will be removed.)

Great,
so what would be the best step? update.zip then apply new rom? or I'm off?

jefftse said:
Great,
so what would be the best step? update.zip then apply new rom? or I'm off?
Click to expand...
Click to collapse
No need to update.zip. If you've already rooted and have nand access, just copy the ROM file to your SD card in it's .zip format (leave it with it's default name so you know what one it is.)
Then turn off the phone, reboot while holding the volume button to get to the menu, then go to recovery.
I always perform a Nandroid backup, especially if you're at a "default" ROM right after root/nand. So Nandroid, then go to wipe and just move down the list wiping everything. Then go back to the first menu, select Flash Zip file from SD Card, select the ROM you want to flash, let it go, and reboot.
Edit: Oh yeah, make sure you remove that PC36IMG.zip file from the SD card before doing any of this.

Awesome!
One more questions,
What is OTA update? I think I'm supposed to update to 1.47.651.1?
and radio update for 2.05.00.06.10 WiMax update?

[Q] could someone explain systemui.apk?

So I've been cruisin' around the threads here and on rootzwiki looking to mod my newly rooted Gnex and I see most of the mods are using lingo I'm not familar with. Like systemui.apk dropping files here and there. I've used root explorer and I know how to mount r/w or whatever but I don't understand what to do and how to flash these mods. is there a tutorial somewhere?

First - an .apk file is just a compressed container that contains files just like a .zip file. In fact it is a zip file with certain Android specific folder structures, files, and "signatures".
Disclaimer - I don't mod or code on the Android platform and the following is based on my understanding of how Android works.
The SystemUI.apk is an Android system file that contains Android system ui code, layouts, and ui related content such as images and etc. What the modders have done is made changes to these code, layouts, and images to modify how the Andoid UI looks.
This SystemUI.apk file resides in a specific location on your phone. What most of the modders have done is made it easy for you and packaged this file into a zip file (which is usually what they give to you as a download) that you can flash via ClockworkMod recovery to automatically replace your stock SystemUI.apk copy with their modified copy.
If you are not familiar ClockworkMod recovery is the standard for flashing Mods, ROMs, and kernels onto your phone. Since you are rooted and want to tinker with your phone you should flash the CWM recovery to your phone if you haven't already. You can look up the many guides that show you how to do this.
To flash most of the mods you would download the .zip file to the internal storage on your phone. Then you would boot into CWM recovery (there are a couple of ways to do this - do a search) and choose the "Install zip from sdcard" and navigate to the file you downloaded. Flash the zip file and the mod should be installed for you.
Note: Many of the modders that make changes to the SystemUI.apk will have packaged this file into flashable zips. By flashing these zip files they overwrite the current SystemUI.apk on your phone. What this means is that if you flash a mod on top of another mod they will overwrite each other.

ok that clears some things up for me. I do have CWM flashed (currently sporting the touch version which is sweet by the way). So when a modder talks of the systemui.apk they are not asking for the user to do anything with the files, they are just explaing how the .zip file works? I guess I got confused because I thought that's what the modder was wanting me to do (change the Systemui.apk). I would simply flash the .zip then on reboot something crazy would happen like I'd lose my softkeys or the status bar would disappear. Thank God for Nandroid but after a while you get tired of trying to flash different mods because I have to go back and restore. I am currently running Android Revolution 2.1.2 but I don't know if that makes a difference or not.

automaddux said:
ok that clears some things up for me. I do have CWM flashed (currently sporting the touch version which is sweet by the way). So when a modder talks of the systemui.apk they are not asking for the user to do anything with the files, they are just explaing how the .zip file works? I guess I got confused because I thought that's what the modder was wanting me to do (change the Systemui.apk). I would simply flash the .zip then on reboot something crazy would happen like I'd lose my softkeys or the status bar would disappear. Thank God for Nandroid but after a while you get tired of trying to flash different mods because I have to go back and restore. I am currently running Android Revolution 2.1.2 but I don't know if that makes a difference or not.
Click to expand...
Click to collapse
They probably want you to change the systemui.apk and then push it to your phone. If this is not done correctly your system ui will disappear. Happened to me when I was trying to mod my softkeys.

automaddux said:
ok that clears some things up for me. I do have CWM flashed (currently sporting the touch version which is sweet by the way). So when a modder talks of the systemui.apk they are not asking for the user to do anything with the files, they are just explaing how the .zip file works? I guess I got confused because I thought that's what the modder was wanting me to do (change the Systemui.apk). I would simply flash the .zip then on reboot something crazy would happen like I'd lose my softkeys or the status bar would disappear. Thank God for Nandroid but after a while you get tired of trying to flash different mods because I have to go back and restore. I am currently running Android Revolution 2.1.2 but I don't know if that makes a difference or not.
Click to expand...
Click to collapse
Most modders will not ask you to modify the SystemUI.apk yourself. This requires knowledge of how to package and sign the apk so it will work with Android. Most likely if the modder gives you specific details about files in the SystemUI.apk package they are just distributing information about how the modification works.
The current rom you're on is 4.0.2. I suspect the mod you flash is only compatible with 4.0.3 (most people tinkering with their phones have flashed to 4.0.3 ROMs now) and that's what caused your issues.
You don't necessarily have to nandroid - although it is very good practice. Before you flash mods if you either know files are being flashed or use a zip utility (i highly recommend 7zip) to inspect the .zip file provided by the modder you can use Root Explorer or ADB to backup the files that will be replaced. This way it would be an easy restore if something screws up. Note that this isn't 100% bulletproof since it really depends on what the mod is and what it's changing in the Android system.

silow said:
Most modders will not ask you to modify the SystemUI.apk yourself. This requires knowledge of how to package and sign the apk so it will work with Android. Most likely if the modder gives you specific details about files in the SystemUI.apk package they are just distributing information about how the modification works.
The current rom you're on is 4.0.2. I suspect the mod you flash is only compatible with 4.0.3 (most people tinkering with their phones have flashed to 4.0.3 ROMs now) and that's what caused your issues.
You don't necessarily have to nandroid - although it is very good practice. Before you flash mods if you either know files are being flashed or use a zip utility (i highly recommend 7zip) to inspect the .zip file provided by the modder you can use Root Explorer or ADB to backup the files that will be replaced. This way it would be an easy restore if something screws up. Note that this isn't 100% bulletproof since it really depends on what the mod is and what it's changing in the Android system.
Click to expand...
Click to collapse
Well i guess im gonna hafta upgrade then wont I

Rooted 4.1.2 what's the best way to update to 4.2

What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!

Not sure if your talking about 4.2 which is to my knowledge only with cm 10 or liquidsmooth or aokp most likely or 4.1.2 md4 either case download the appropriate file of your choice and flash from recovery do make sure backup amyways hope that answers your question
Sent from my SPH-L710 using XDA Premium HD app

six3onei said:
What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!
Click to expand...
Click to collapse
I think you mean update to 4.1.2. Check your version in settings about device. If it's 4.1.1 go here :
http://forum.xda-developers.com/showthread.php?p=586
Sent from my SPH-L710

Cm10.1
Sent from my SPH-L710 using xda app-developers app

Deviant Xone (linked in my sig). Awesome 4.2.2 ROM.

If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.

Overstew said:
If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.
Click to expand...
Click to collapse
Apparently you can avoid this by updating your recovery....the emulated 0 folder, I mean
Sent from my SPH-L710

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!

six3onei said:
I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!
Click to expand...
Click to collapse
Hey six3onei,
I'm assuming you just got the notification for the OTA (Over-The-Air) update. The newest version of the Stock Rom is MD4 which is still 4.1.2. Android version 4.2.x probably won't come out for your phone for a couple of months (that's my guess with no data to back it up other than my own intuition).
As far as upadating, you actually don't have to apply the OTA to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
The rom you want to download off of Freeza's page is:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4 | Mirror
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse

Blacked out status bar

This is not my work. I did not create this. I only attempted to make it work on stock zvc odex.
Thanks to Scotty_Two for originally creating this for deodexed zvb roms.
http://forum.xda-developers.com/showthread.php?t=2198755
Adhvanlt helped me to get it to work on my locked but rooted lgog.
Since the release of the zvc update, it didn't work anymore. I loved the look, so I decided to sit down and redo what was done before. This time I was unlocked, but still needed to create an odex file for it. So following the steps I did before with adb I was able to make it work on my stock odex zvc phone.
The link to the zip file is below if you want to try it out on your phone. Again, this was done on a stock ROM.
Install at your own risk
I am NOT responsible for any damages or any bricks.
Make a nandroid backup before using.
Copy the stock LGSystemUI.apk and LGSystemUI.odex files from /system/app folder to your sdcard in case you want to revert back.
To use:
Download the zip file
Extract the files.
Copy the extracted files to: /system/app folder
Change permissions on both files to rw-r-r
Reboot
Enjoy
This is NOT flashable
https://db.tt/GOy768CI
Sent from my phone.

Here another screenshot
Sent from my phone.

Anyone try this? How bout a flashable link?
idk how i got here...

treezy26 said:
Anyone try this? How bout a flashable link?
idk how i got here...
Click to expand...
Click to collapse
I tried it on the stock rom unlocked and it works great. Well done. It only takes about two minutes to unzip and replace the original files in system/app. Btw, I would move the original files to your SD card to keep in case you want to go back to the stock look.

Sorry I don't have a flashable version as I don't have the knowledge to create it. If someone wants to either show me or do it, have at it. But a quick swap with a root explorer takes no time at all.
Sent from my phone.

I installed this onto the optimus ROM. I extracted the apk from the deodexed original Scotty_Two thread and pushed it into system just as it says in Scotty's thread and it worked on reboot. Just over write and when system starts failing just reboot FTW.
Sent from my LG-LS970 using Tapatalk

One of my first ROM flashes, could you please double check?

Wow, what a ride I had with this phone.
Starting with the fact that the model of the phone was SGH-I747 with AT&T branding I then tried to flash a custom ROM for this model, of course everything went bad, we'll not everything, but I couldn't make any calls, see IMEI nubmer and so on.
Thanks to a very helping member of SGH-I747 board, audit13, I found out that my phone is in fact T-Mobile's SHG-T999. I was lucky enough and was able to restore stock ROM of this model.
Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
And I just wanted to make sure that I don't miss anything important.
Phone Data
Model: SGH-T999
Bootloader version: T999UVUENC2
Android Version: 4.3
I've rooted the phone using this guide - http://forum.xda-developers.com/showthread.php?t=1771687 and using March 2014 - 4.3 JellyBean.
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works

You could follow this thread to backup your efs folder: http://forum.xda-developers.com/showthread.php?t=1804117
I suggest flashing CWM directly from Odin in download mode. I would not install it using an App from the play store. This is just my personal preference.
All of the other steps look fine.

viltnieks said:
....Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
....
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Click to expand...
Click to collapse
StockMOD Custom has much (if not all) of the carrier branding removed. It has added some customization tweaks to the ROM; mainly XPosed App and Wanam XPosed Module. It also has a few other custom apps and features from newer Galaxy devices replacing the stock apps. It is themed to look like a Galaxy S5 instead of an S3.
The StockMOD ROM has very little removed; KNOX, Syscope, CarrierIQ, and maybe something else. Other than that it will look almost identical to what you now have, including all of the T-Mobile stuff. This one would match the filename in the thread title. It was created first and the StockMOD Custom was added to the thread afterwards, is my guess.
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
Click to expand...
Click to collapse
I would also suggest this post for backing up imei and other nvdata. Specifically the reboot nvbackup instructions.
Since you are on NC2 bootloader and modem(baseband) do not mess with changing your modem to MJC (step 12). You can confirm that it will work on NC2 in the second line of the changelog of StockMOD Custom thread (post #2)
Another thing: I see StockMOD Custom has an Aroma Installer. I have not used a ROM with this option. Aroma Installer will give you choices during the ROM installation, I can only guess what they are without installing the ROM. The choices probably entail choosing between the stock apps and the later Galaxy device apps; Note 3, S4, and S5.

Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.

viltnieks said:
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
Click to expand...
Click to collapse
You're most welcome. I personally have used several of these methods, redundancy causes no harm.

dawgdoc said:
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
Click to expand...
Click to collapse
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.

viltnieks said:
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
Click to expand...
Click to collapse
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.

dawgdoc said:
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
Click to expand...
Click to collapse
Coould it be related to the fact that I have data_1, data_2, data_3 folder in my root?
Also when I enter /storage/ I have a lot of folders like:
emulate
extSdCard
sdcard0
UsbDruveA
UsbDruveB
UsbDruveC
UsbDruveD
UsbDruveE
UsbDruveF

I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.

viltnieks said:
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
Click to expand...
Click to collapse
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.

dawgdoc said:
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
Click to expand...
Click to collapse
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.

viltnieks said:
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
Click to expand...
Click to collapse
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.

dawgdoc said:
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
Click to expand...
Click to collapse
Thank you very much!