I have a Galaxy s3 rooted So I was ble to flash the newest nightly cb 10.1 before the one that came out today. I want to try out the one that came out today however I am confused about something. I know i have to flash the rom and delete data and cache during recovery mode and what not. What step do i need to take so that when i do flash thi snew rom i dont have to manually re install all my apps and configure my phones layout again?/
You can try dirty flashing by just clearing cache and dalvike cache after you flash the new nightly. This method won't affect any of your apps or settings. If you get any weird bugs from dirty flashing, try clean flashing (which wipes pretty much everything) before reporting any bugs. If you have to clean flash then you can backup your apps with Titanium Backup.
OK, probably something silly I am not aware of so I hope it does not turn out to be.
Device HTC One X International.
CWM : v5.8.4.0
HBoot : 1.36.0000
So I have just changed my ROM from Cyanogen Mod 10.1.3 to SlimBean build 2.2 of Slim Bean 4.3.1. I have jumped from few ROMs over the past year without any issue apart from the know ones.
Anyway I did a backup of the Cyanogen 10.1.3 I was using, reset the data, wiped the cache and Dalvik and installed SlimBean.
The issue I am having is when I advanced restore the data from my previous Cyanogen ROM backup like I have done with each ROM change to keep apps and authenticators,etc; whenever I try to go into the security settings it basically crashes (Settings has stopped working message). I have wiped and used the stock SlimBean and it is working fine, the issue only comes up once I advanced restore the backup ROMs data.
I have reflashed the Slim boot.img, and got another copy of the SlimBean ROM just in case but that has not helped.
Everything else works fine just this one issue.
I know I am not using the latest CWM, could this be the problem?
Any help would be greatly appreciated.
I am currently running CM 11 nightlies but I miss the WIFI calling feature on the stock rom.
I would like to know how to go from 4.4.2 back to the official 4.3 while keeping my data.
Will Titanium backup help in this regard or will a nandroid backup be the way to go?
Titanium is the only way to go.
How do I go about removing CM11 and putting in the stock rom?
1. Stockmod and the related Modem.
2. Boot to Recovery and do Factory Reset.
3. Wipe Dalvik and Cache.
4. Flash Stockmod and the related Modem.
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Edit: I have now also tried
1. Restoring to original stock touchwiz 4.1.1
2. Wiping cache from original recovery
3.Rerooting
4.Restoring a backup of 4.3
5.Attempted to update to C-Rom, Carbonrom, Resurrection Remix -- No Luck Fails
Corvetrims77 said:
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Click to expand...
Click to collapse
I'd like to know myself. I'm stuck too. I can flash a 4.3 rom and everything works, but when I reboot, it gets stuck. All was fine until I flashed Wicked rom and flashed " MJ2 bootloader MJB" Now every time I reboot it gets stuck. Also If I try a reflash, the only way to get it to bootup is to format before flashing.
Try using Philz Touch as your recovery program.
audit13 said:
Try using Philz Touch as your recovery program.
Click to expand...
Click to collapse
I had cwm when I originally started out, switched to twrp to see if the recovery was the issue.
I assume you were running the latest version of cwm before you switched to twrp so it can't be the recovery.
Are you doing a full wipe of the system, cache, data, and Dalvik before installing the ROM?
Yea every time I wiped data, cache, dalvik , I even reformatted once. I have managed to boot up into tasl650AOKP which is a d2lte build but no other ROMs. I mean at this point it looks like I should just wait a bit to see if it is something with the ROMs interacting with my phone(as per all phones are made different)
Sent from my d2lte using Tapatalk
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
audit13 said:
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
Click to expand...
Click to collapse
Yeah I gave it a shot still no dice. I keep seeing other people having similar issues, so I am still leaning it has to do with the differences in d2lte builds vs dtatt builds
Sent from my d2lte using Tapatalk
d2att ROMs are okay? Just not any d2lte?
audit13 said:
d2att ROMs are okay? Just not any d2lte?
Click to expand...
Click to collapse
As I stated before I am able to boot int Task650AOKP(Which is a d2lte build), any of the others that I have tried have not worked. There are some updates out today, I am going to attempt again and post back results.
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
audit13 said:
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
Click to expand...
Click to collapse
Thanks for the help, I actually was just able to boot into C-Rom by following the same steps except I am using TWRP. No idea really what caused the Roms to get stuck on boot. Quite annoying.
I had TWRP on my phone but I was having problems installing ROMs when I first got the phone in January.As soon as I switched to CWM or Philz, no problems at all except for ROMs based on a stock 4.3 ROM.
was on software D with stock rom 4.4.2.. I am able to root.. and then able to get get TWRP for stock 4.4.2 install. So now I have custom recovery.
So I had the dimming issues and all fingers point to downgrading to stock 4.2.2 for ROM compatibility. So found the files to to downgrade to 4.2.2 with version of TWRP 2.7.0.1. So that seems to work. I don't get dimming issues with the LG boot screen comes up for example (my assumption that I have 4.2.2. installed now).
Now any ROM I throw at it, Slimkat, Mahdi, Pacman, CM11, it either freezes at boot and/or freezes in a few seconds once it's booted and I can swipe around in the OS. I tried wiping cache, dalvik, data, system, internal SD hoping that help install the rom cleanly, but still no go..
Any ideas? Am I missing something?
Thanks in advance.