Develop Bugs

Note 2 - Dual BOOT Roms

Anybody got this working? saw on the google play store there are a lot of apps that don't support samsung unfortunately because of the way things are partitioned.

What apps don't support Samsung?
Sent from my GT-N7105 using xda app-developers app

If by dual boot you mean booting two roms its not working on the note II yet AFAIK. Here is the progress thread http://forum.xda-developers.com/showthread.php?t=2153211&highlight=dual

mrevankyle said:
If by dual boot you mean booting two roms its not working on the note II yet AFAIK. Here is the progress thread http://forum.xda-developers.com/showthread.php?t=2153211&highlight=dual
Click to expand...
Click to collapse
That is correct, having 2 roms in memory and being able to switch between the two, with ease.
I saw that someone already had it working via Aroma on the Original Galaxy note.

BigBison420 said:
That is correct, having 2 roms in memory and being able to switch between the two, with ease.
I saw that someone already had it working via Aroma on the Original Galaxy note.
Click to expand...
Click to collapse
Ya k that's what i thought. You cant do that yet on the Note II but it is being worked on

mrevankyle said:
Ya k that's what i thought. You cant do that yet on the Note II but it is being worked on
Click to expand...
Click to collapse
Just figured I would give a "bump" to this Q&A since this dual-booting Samsung & AOSP is working well at this point. There are a few caveats and I am compiling a FAQ on just this topic. DerTeufel's thread is here and the OP references my FAQ > http://forum.xda-developers.com/showthread.php?t=2239453

Nand secondary?
RichMD said:
Just figured I would give a "bump" to this Q&A since this dual-booting Samsung & AOSP is working well at this point. There are a few caveats and I am compiling a FAQ on just this topic. DerTeufel's thread is here and the OP references my FAQ > http://forum.xda-developers.com/showthread.php?t=2239453
Click to expand...
Click to collapse
That would be nice, because I can't figure out how this DB recovery works. I have 2 ROMs on my phone right now. I appear to be able to do anything I want to my primary ROM, but I cannot figure out how to back-up my secondary.
The DB recovery is a useful idea. I have a custom 4.2.2 as primary and a sammy 4.1.2 as secondary. Both ROMs work was expected. Primary does not have to have devil kernel, but I believe secondary needs it in order to survive.
I am still new at this DB recovery thing. Has anyone figured out how to nand the secondary ROM? I have noticed that I can flash TWRP and I don't lose either ROM, as long as I DO NOT factory reset. I just have to flash DB Recovery again to access the other ROM. I have also noticed that some data is shared between the two ROMs. Robo TD shares the same back-up file on sdcard0, which is delightful
Today I am going to try a dirtly ROM flash on primary. Wish me luck.

floykoe said:
That would be nice, because I can't figure out how this DB recovery works. I have 2 ROMs on my phone right now. I appear to be able to do anything I want to my primary ROM, but I cannot figure out how to back-up my secondary.
The DB recovery is a useful idea. I have a custom 4.2.2 as primary and a sammy 4.1.2 as secondary. Both ROMs work was expected. Primary does not have to have devil kernel, but I believe secondary needs it in order to survive.
I am still new at this DB recovery thing. Has anyone figured out how to nand the secondary ROM? I have noticed that I can flash TWRP and I don't lose either ROM, as long as I DO NOT factory reset. I just have to flash DB Recovery again to access the other ROM. I have also noticed that some data is shared between the two ROMs. Robo TD shares the same back-up file on sdcard0, which is delightful
Today I am going to try a dirtly ROM flash on primary. Wish me luck.
Click to expand...
Click to collapse
The kernel is "shared" between them. If you flash another ROM to primary, it replaces the dual boot kernel. You are correct that the other ROM is not affected but other kernels can not boot the secondary ROM which is stored in a custom location. Creating a nandroid of (or restoring to) the secondary partition only requires you to go into the dual-boot selection and choose "enable secondary". Then all commands such as factory reset, bacup, restore, wipe cache, etc pertain to the secondary ROM until you reboot or reload recovery. You could choose backup and when it completes you coul go into dual-boot again and select "enable primary". Then all the commands would pertain to the primary ROM - again until you reboot or reload recovery.
Sent from my BNTV600 using Tapatalk 2

RichMD said:
The kernel is "shared" between them. If you flash another ROM to primary, it replaces the dual boot kernel. You are correct that the other ROM is not affected but other kernels can not boot the secondary ROM which is stored in a custom location. Creating a nandroid of (or restoring to) the secondary partition only requires you to go into the dual-boot selection and choose "enable secondary". Then all commands such as factory reset, bacup, restore, wipe cache, etc pertain to the secondary ROM until you reboot or reload recovery. You could choose backup and when it completes you coul go into dual-boot again and select "enable primary". Then all the commands would pertain to the primary ROM - again until you reboot or reload recovery.
Sent from my BNTV600 using Tapatalk 2
Click to expand...
Click to collapse
This is all very interesting and essential information to those of us trying to figure out this DB Recovery system. I suspect this is yet the tip of the iceberg.
So, with a DB set-up, both ROMs need to be installed with the Devil Kernel. For instance, Primary is installed first with Devil in place, then the same for secondary (or vice-verse), because you can't install a ROM with no kernel; but it turns into one kernel in the end. Is this correct? Only one kernel can exist with DB system. If secondary has devil and primary has trinity, secondary is (&cked. In other words, you still only have a single boot system with a secondary ROM installed that has no recovery capabilities.
OK, assuming that all that is correct (or at least parts of it), you get a big fat thank you.
Now earn another. Do both ROMs (sharing the same kernel) have to also share the same governor, I/O, clock, and voltage settings? Custom can handle more than sammy and different ROMs like different settings.

floykoe said:
This is all very interesting and essential information to those of us trying to figure out this DB Recovery system. I suspect this is yet the tip of the iceberg.
So, with a DB set-up, both ROMs need to be installed with the Devil Kernel. For instance, Primary is installed first with Devil in place, then the same for secondary (or vice-verse), because you can't install a ROM with no kernel; but it turns into one kernel in the end. Is this correct? Only one kernel can exist with DB system. If secondary has devil and primary has trinity, secondary is (&cked. In other words, you still only have a single boot system with a secondary ROM installed that has no recovery capabilities.
OK, assuming that all that is correct (or at least parts of it), you get a big fat thank you.
Now earn another. Do both ROMs (sharing the same kernel) have to also share the same governor, I/O, clock, and voltage settings? Custom can handle more than sammy and different ROMs like different settings.
Click to expand...
Click to collapse
I can post a more detailed answer later on today. However, the phone will always only have one kernel. When your phone boots up the kernel is loaded first. At that point, if you have the dual boot kernel, it has the capability to boot one or the other ROM. The secondary ROM is stored in a separate location on the internal SD card. If you flash a new ROM to either the primary or secondary partition, it will replace the kernel. At that point, both ROMs are still okay, but whatever the new kernel is, it can only boot the primary rom. Additionally, if you flashed directly to the secondary rom and the new kernel is not compatible ( AOSP vs. TW) with the pre-existing primary rom, you must flash the dual boot kernel again or the primary rom will not boot up properly. If you flashed to the primary rom, you don't technically need to reflash the dual boot kernel until you want to be able to boot up the secondary ROM again.
Sent from my GT-N7105 using Tapatalk 4 Beta

What if you were to delete the second rom off the internal or is there a way that it can be corrupted causing the phone not to boot after the primary kernel? can an ODIN restore to stock fix this (since it will repartition for only one boot)

Unable to upgrade Galaxy 3

When the update file downloads then it verifies but when it goes to install, it errors out and stops [see attached image]. There is also mention of Gmail.apk but when I go and look for it, it's not there. I have deleted the file and downloaded several time but wind up with the same result. I have put a copy in the ext sd card and tried from there but it will not install. Any ideas on how to do the upgrade?
Thanks, Dave

Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app

topherk said:
Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.

JOB Dave said:
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
Thanks for reading all of it. Most people would just look at the first page and the last page and say "Oh, it's not there!" That being said, I hope you have a better understanding of what's going on when you get an OTA notification.
Now that's been said, I had written a post on another thread that covers the steps A-Z. I've linked it and quoted it below.
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, it should have 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

JOB Dave said:
The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
I don't think there's a way to be "just a little rooted"
:silly:
Follow topherk's directions to a tee, and you'll be fine.
As a noob, I was scared to death knowing that I was rooted and I was going to get an OTA!
xda-developers has everything you need. The files, the guides, the support from senior members.
Relax and have fun...
---------- Post added at 06:11 PM ---------- Previous post was at 05:54 PM ----------
BTW, I flashed freeza's md4 odexd rom (cause a stock sg is odex), the md4 firmware, and the optimized kernel. Flashed (installed) them in that order. Just download them from the site onto your phone, and boot into recovery to flash each. Probably too paranoid, but i rebooted after each flash *just* to be sure). Cleared dalvik cache after installing the rom. Ummm, and ran checksum on my files before I installed them (I use md5 checker app).

Thanks, that got me started. now I have to figure out which rom and kernal I want to install.

ROMs come with kernels already, so if you're unsure ATM, just flash a ROM and then later you can check out kernel switching. Just make sure that the kernel you are flashing is for your ROM version (4.1.2, 4.2.2, etc) and for your type (AOSP, Touchwiz).
Since you are just starting out, I would suggest TPR (The Peoples ROM) or MOAR (Mother of All ROMs). Both in Android Dev section (as opposed to Original Android Dev).
TPR also has AROMA installer, so it lets you pick what apps, kernel, and other goodies you want to flash and basically on-the-spot customization.

Downloaded the file MD4_update_FULL_Odex.zip and followed the instructions above and got zip signature failure, see photo. I am wondering if it worth doing the upgrade.
~Dave

In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app

topherk said:
In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?

JOB Dave said:
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?
Click to expand...
Click to collapse
Baseband has to do with what modem/radio you are on. This is independent of your ROM, so the two can be different version numbers.
The modem impacts your mobile data coverage and speeds. What you wanna do (if you wanna find the best modem for your area) is to switch modems and run each one for a week. Then switch. After you've gone through a couple modems, single out the ones that qork best and test those out till hou find the best and/or fastest one for your area and the places you frequent.

Am I the only one with these bugs?

Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?

AMKhatri said:
Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?
Click to expand...
Click to collapse
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
How do I get “root”?
If you are booted into a custom recovery (recoveries will be covered later), root is enabled by default. If you want root while booted into Android, you will need to place two files on your system partition: an “su” binary which grants root access, and a superuser app that manages that access. The two that are available are ChainsDD’s Superuser and Chainfire’s SuperSU. Usually these files are packaged up in a zip file that is flashable using a custom recovery, but they can be flashed manually using ADB. Both of these methods will be described below.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.

beekay201 said:
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.
Click to expand...
Click to collapse
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...

AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PSo you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872

AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
Mr., please, read the LINK i gave you! THIS ONE ->>>> http://forum.xda-developers.com/showthread.php?t=1812959
If you read it, you'll stop thinking you need to be doing anything at this point in FASTBOOT interface! Like mrgnex says, you need to be on a custom recovery to format /system. (Have you read the link yet? By now you should know that the /system partition and the /sdcard/ (aka userdata) are 2 different things!)
mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). (...) roms are a personal choice so there is no 'best' ROM. Just try out.
Click to expand...
Click to collapse
+1
For your reference, you can't erase /system in stock recovery.
AMKhatri said:
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872
Click to expand...
Click to collapse
Stop! THERE'S NO NEED FOR FASTBOOT HERE!

Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?

AMKhatri said:
Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?
Click to expand...
Click to collapse
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Now it's definitely clear!
I'll download CM10.1.2 tomorrow and will decide to install it once Stock JB 4.2.2 starts acting up again.
In the meantime I'll read on about kernels, please keep don't close this thread...yet.

clerk usdEuro
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)

AMKhatri said:
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)
Click to expand...
Click to collapse
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks...
I'll flash CM in a week or two, as I'm on a tight schedule currently, and I also wanna note down the average battery time I get out of 4.2.2

So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?

AMKhatri said:
So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?
Click to expand...
Click to collapse
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus

Pirateghost said:
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
What was I thinking...
I apologize guys... I guess I wasn't thinking straight as its past midnight here...
So just to clarify stuff so that I don't end up doing something wrong:
-> Head into Recovery Mode (with usb debugging enabled... connect usb cable to phone and pc)
-> Wipe System
-> Wipe Cache
-> Install from SD card (select .zip file)
right?
Also, I performed a backup of the applications I have via Titanium Backup, They'll work on 4.3 when I restore them right? or do you recommend downloading them from the play store again?
Sorry for being such a noob, and Thanks for your responses!

backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.

Pirateghost said:
backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.
Click to expand...
Click to collapse
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!

AMKhatri said:
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!
Click to expand...
Click to collapse
Seriously, how hard can it be for you people to waste 5, 5!!! minutes to browse the forums.
http://forum.xda-developers.com/showthread.php?t=2377318

Thanks!
According to a friend's recommendation I used Wugfresh Nexus Root Toolkit to Root, and surprisingly didn't lose any of my data!
Once again, Thanks for all the help everyone... You've all been quite helpful.

[MultiBoot][unofficial]MultiROM V32 [DISCONTINUED]

Whats MultiROM
Multirom is a ROM manager created by Tasssadar with the ability to load multiple ROMs without the need to remove your older one, giving you the ability to test/run multiple ROMs at once, you can also restore TWRP backup as Secondary ROMs allowing you to look at your backup to choose the right one, or maybe just have 2,3,4,5,6 working OS on your phone... just because it's cool.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack.
I Nuked my SDCard twice in porting this tool over, I'm not entirely sure what caused it, but I reverted few changes which might have been the reason, so I hope it wont happen again.
Still, I'll highly recommend you make backups and keep them on your computer. Always.
I've been using this for 2 weeks now with no serious problems, but just as well, don't be blaming me if anything goes wrong.
keep the "i cant get this to work" messages out of my PM i wont bother replying to them,
as almost anyone on this thread can help you.
you have a problem, read the main OP and if you still cant get it to work... post your problem here...
and be specific... "this is not working" will get you nowhere and no answers.​
Special Thanks:​ @Tasssadar: For The MultiROM Source.​
Sources:​MultiROM
Modified TWRP​
Download is one post below.​

Requirements:
S-off/Unlocked Bootloader
Understand How KL Zeus Work*
By Flashing That Kernel, you'd need to flash a 2nd kernel to go along with it..
if you don't follow those instruction, the main ROM wont boot.​
To Install MultiROM:
Flash Zeus Boot.img
Flash Multirom-20141228-v30-UNOFFICIAL-endeavoru.zip normally trough recovery.
Flash Multirom-20150430-v32-UNOFFICIAL-endeavoru.zip normally trough recovery (New Layout ONLY).
Reboot
To Fix Write To SDCard issue(flash on secondary ROM only):Not Needed with New Layout
Flash UPDATE-SuperSU-v2.40.zip(possible only needed on Lollipop, if no, no harm in switching to SuperSU)
Flash SDFix.zip
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Add ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> Add ROM
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Change Kernels:
Boot TWRP --> Advance --> MultiROM --> List ROMs --> Flash Modules Zip*
List ROMs --> Remove boot.img
List ROMs --> Add boot.img
* The Modules must be flashed 1st, as the boot.img is replaced with each flash.​
Failed Install & losing memory
MultiROM -> TWRP
adb shell dosfsck -a /dev/block/mmcblk0p14
ToDo:
-- Nothing as it stands

and another one...

Amazing you did it..well done mate glad you are still with us on our dated hox.
Sent from my One X using XDA Premium 4 mobile app

Great!!! Eager to try but its very late night here
Also waiting for your Kernel
Sent from my One X using XDA Premium 4 mobile app

Wow your are just great ...... Will Test it if i have enough time.
Maybe you get tomorrow a pm
Gesendet von meinem HTC One X mit Tapatalk

Thant said:
OK one question maybe stupid but When I install MultiROM.zip from my recovery and then I will restart the phone it will directly start in TWRP and ask me which ROM I want ot boot or how I will go in TWRP recovery when it is not on the recovery partition and it will be posible to flash custom kernel on the others roms 2,3,4 and etc.?
Click to expand...
Click to collapse
It'll be better if i answer this here,
during boot, after flashing MultiROM, MultiROM starts and prompts you to choose what to boot,
Internal (Main ROM), TWRP or other ROMs you installed.
if you want to change kernel of a secondary ROM,
You boot TWRP -->Advance --> MultiROM --> Select ROM --> Remove boot.img
Select ROM --> Add boot.img, then you get to select the kernel you want.
To Flash the Zips/Modules
TWRP -->Advance --> MultiROM --> Select ROM --> Flash Zip
Ill update the OP with these now.

I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app

lalit387 said:
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main ROM will remain untouched..
but you'll need to know how KL Zeus works to boot it.

Great! I do not have important data in the internal storage, so I can test it.

@Thunder07 I want to test it too

The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.

Thunder07 said:
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Click to expand...
Click to collapse
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.

ljjehl said:
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
Click to expand...
Click to collapse
jeez... 1GB it is then :/

Thunder07 said:
jeez... 1GB it is then :/
Click to expand...
Click to collapse
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk

humzaahmed155 said:
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok

Thant said:
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Click to expand...
Click to collapse
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat

cappuccina said:
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
Click to expand...
Click to collapse
just now deleted CM11 to many bug for me I missed important notification. The phone beep but I don't see nothing on the screen. Now for this week I think to test SlimKat to see how it works I hope to be stable and don't miss any inportant notification. Whole day I thik on the question why today I have too many free hours and in the end of the day when start main rom I understand why

So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.

humzaahmed155 said:
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
Click to expand...
Click to collapse
When I add a secondary Rom I also go into the advanced/Multirom/ list and select the Rom I installed. I then remove boot.img, then go back and install boot.img (the boot.img I extracted from Rom), go to the directory I saved that to and it's done. Should boot after that.
@Thunder07,
My current issue seems to be a cache issue. I seem to have to fastboot cache a lot more than I like, otherwise I can't always get to TWRP. Reboot (or from poweroff) more often than not seems to get me only the internal Rom and not the MultiRom startup. I was hoping a wipe cache from device would be sufficient, but no luck.

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!