I've been doing this crap so long I seem to be forgetting the basics. I am on a stock based ROM currently, and I'm going to another stock based ROM that actually gets updates. I don't want to have to back up all my apps and data and everything because it takes so long. Can I do it? Dirty flash? I feel like the last time I did a dirty flash it still removed a bunch of stuff I need.
Sent from my LGLS990 using Tapatalk
Decepticaons said:
I've been doing this crap so long I seem to be forgetting the basics. I am on a stock based ROM currently, and I'm going to another stock based ROM that actually gets updates. I don't want to have to back up all my apps and data and everything because it takes so long. Can I do it? Dirty flash? I feel like the last time I did a dirty flash it still removed a bunch of stuff I need.
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
You can dirty flash a stock based rom over a stock based rom. Just flash it and it should work, but I can't tell you of it is fully functional because you did a dirty flash
Decepticaons said:
I've been doing this crap so long I seem to be forgetting the basics. I am on a stock based ROM currently, and I'm going to another stock based ROM that actually gets updates. I don't want to have to back up all my apps and data and everything because it takes so long. Can I do it? Dirty flash? I feel like the last time I did a dirty flash it still removed a bunch of stuff I need.
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Backup is still the best way to go, dirty flash creat bug, and can even make your device bootloop.
You can dirty flash but any apps installed on system will be over writen such as exposed or any thing u manually installed on sys partition
You can backup your applications and data using LG backup tool in settings.
You can do a clean install and then restore your data.
This is the easiest and safest way between stock Roms.
Regards
Sent from my LG-D855 using Tapatalk
Related
So now that we have a source release with a safe recovery built-in is a full wipe still needed when flashing ICS to ICS?
This is probably a dumb question but I've been wondering about it.
This question is about going from tw to tw base Rom.
Sent from my SPH-D710 using Tapatalk 2
epic4gfaded said:
So now that we have a source release with a safe recovery built-in is a full wipe still needed when flashing ICS to ICS?
This is probably a dumb question but I've been wondering about it.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I have done several ICS to ICS flashes using AGAT's recovery with no issues.
In general it's a good idea to not let data linger around, especially if you're flashing a new ROM. It rules out that any problems you experience are due to corrupted data from the flash process.
Fortunately with Agat's repack you can safely restore backups for TW roms.... meaning the setup should only be a one time deal for each new ROM flash.
I'm just wondering if you have an older base like 4.0.4 and you want to flash an 4.1.1 rom is that possible or should i upgrade to 4.1.1 then flash?
It's totally possible.
However, this is a good time for a clean install. ie data wipe.
I hardly ever recommend one. But, this is one of the times.
I didn't, however. Last time was ice cream to jelly bean
Sent from my SGH-T999 using xda premium
Thank you
also do you know if flashing back to stock and then upgrading thourgh the kies to 4.1.1 and then flashing a custom rom be safer?
Fewer steps = better.
qwerty123z said:
Thank you
also do you know if flashing back to stock and then upgrading thourgh the kies to 4.1.1 and then flashing a custom rom be safer?
Click to expand...
Click to collapse
You sound like my brother in law. He does that every time he flashes a new ROM, makes no sense to me. When I flash a new ROM, I wipe data/cache and /system, then flash the ROM and restore my Titanium Backup.
Thetenthdr said:
You sound like my brother in law. He does that every time he flashes a new ROM, makes no sense to me. When I flash a new ROM, I wipe data/cache and /system, then flash the ROM and restore my Titanium Backup.
Click to expand...
Click to collapse
Same here... I never did an official update from ICS to Jellybean and so far so good. I know that it's best to install the latest drivers/partitions, but I was too lazy. Lol
Sent from my SGH-T999 using xda premium
My apologies if this has been asked before. But from my understanding the Google edition still has all the touch wiz framework. I was Wondering if you had to Odin back to stock in order to flash a modified stock Rom? I had to do this on my s3 because it always gave me problems. This is an issue for me now because my hard drive on my laptop is fried and have no access to Odin besides mobile Odin.
Sent from my SGH-M919 using Tapatalk 4 Beta
A modified stock ROM will be packaged to flash in recovery. Just be sure to properly wipe since you will be going back to TW.
So all I have to do is do a super wipe, system and all. And I should be good to go? Can I nandroid back to my current set up if I don't like the Google edition Rom? Or will that cause complicatIons that will require me to Odin back to stock?
I know it's a dumb question. But I want to Bork my Device
Sent from my SGH-M919 using Tapatalk 4 Beta
MacTheRipperr said:
So all I have to do is do a super wipe, system and all. And I should be good to go? Can I nandroid back to my current set up if I don't like the Google edition Rom? Or will that cause complicatIons that will require me to Odin back to stock?
I know it's a dumb question. But I want to Bork my Device
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nandroid is fine, and doesn't need any wiping, it does it before the restore, but I wipe anyways.
If you just want to flash a different ROM, for going from ROM to different ROM, it's best to:
Factory Reset
Wipe both Caches
Format /system
Flash ROM or ROM and gapps if it's AOSP
To upgrade a current ROM to an updated version, if the base version of Android hasn't changed, you can dirty flash, which is the exact steps, minus the factory reset.
Okay thanks, I was just curious. Because I can't currently restore from Odin because I don't have a pc.
Sent from my SGH-M919 using Tapatalk 4 Beta
Tried IRC, so I'm going to try here also.
Anytime I use a ZVB or ZVC based ROM, the kernel crashes within 10-15 seconds of being flashed. No matter which of those based ROMs I use, I get the kernel crash in the same time period. I've tried different kernels as well, but none have worked. I've use Awesome's Kernel Cleaner each time before flashing the kernels, but get the same result.
Here's the kicker though, if I use any of the AOSP ROMs it will run fine. My only problem is there was no EFS backup, so I get no service, which pretty much makes using the 4.3.x+ ROMs useless. Basically, I'm trying to get back to stock ROMs so I can get service and save the EFS to use on the later ROMs. If I can even just get the ZVC ROM working that would be great too.
I'm not sure if there is a AOSP kernel stuck in there or something, and it's not clearing it out, or what is going on. I'm doing a complete wipe with data everytime I flash.
I appreciate any help, and thank you for taking the time to read!
Jxt. said:
Did you flash a radio ?
Click to expand...
Click to collapse
When flashing the ZV ROMs? I did the ZVB radio when I did the stock ROM. I might have done it after instead of before though.
Jxt. said:
you only flash a radio once, have you been doing it everytime you flash a rom?
Click to expand...
Click to collapse
Only when I went from ZVB to ZVC just to be sure. Would the radio cause the kernel crashing?
Jxt. said:
yes could be, can you give me the that you got the radio from
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40169203
HyphyCus said:
Tried IRC, so I'm going to try here also.
Anytime I use a ZVB or ZVC based ROM, the kernel crashes within 10-15 seconds of being flashed. No matter which of those based ROMs I use, I get the kernel crash in the same time period. I've tried different kernels as well, but none have worked. I've use Awesome's Kernel Cleaner each time before flashing the kernels, but get the same result.
Here's the kicker though, if I use any of the AOSP ROMs it will run fine. My only problem is there was no EFS backup, so I get no service, which pretty much makes using the 4.3.x+ ROMs useless. Basically, I'm trying to get back to stock ROMs so I can get service and save the EFS to use on the later ROMs. If I can even just get the ZVC ROM working that would be great too.
I'm not sure if there is a AOSP kernel stuck in there or something, and it's not clearing it out, or what is going on. I'm doing a complete wipe with data everytime I flash.
I appreciate any help, and thank you for taking the time to read!
Click to expand...
Click to collapse
Are you wiping /system too? If in TWRP 2.5.0.0, wipe>advanced click all 4. If 2.6.x.x all BUT internal data
He told me in irc that this originally happened after the screen broke and he replaced it. After that anything stock gives a kernel crash but aosp doesnt.... if that helps anyone trying to help him.
engine95 said:
Are you wiping /system too? If in TWRP 2.5.0.0, wipe>advanced click all 4. If 2.6.x.x all BUT internal data
Click to expand...
Click to collapse
Using 2.6.3.0, and wiping everything but SD card. Wiping 3x before installing ROM, gapps and kernel. Tried multiple stock based kernels. Can install CM or Slimbean and it will boot no problem, and work fine. It's just the stock ROMs, and tried Lifeless as well.
Guess this has everyone stumped huh?
HyphyCus said:
Guess this has everyone stumped huh?
Click to expand...
Click to collapse
There's always LGNPST. Only other option to see if it'll fix it.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
There's always LGNPST. Only other option to see if it'll fix it.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried that with the stock ZV9, ZVB and ZVC. Even used LG flash.
Here's an idea that came in my head. Maybe it's crashing when it tries to connect to the Sprint network. Since the AOSP ROMs never attempt to connect to it, they don't crash. But the stock ROMs do, so they crash when attempting.
If I'm not rooted, I get just a reboot. If I run SuperSU from TWRP before rebooting, then I get the Kernel Crash screen when it reboots.
Good day everyone.
I have successfully rooted my S3 1747.
I have done a backup after installing Rom manager. I also have a nandroid and titanium backup completed.
I would like to install cyanogen mod but its very important that I am able to get my contacts back.
I plan to install through the so called easy method in rom manager.
Am I able to get my stuff back after the install?
Thanks in advance
Most system app data will not be compatible. I don't know about CM, but in TW there's an option to export contacts to SD. It'll save them in a .CSV file. Maybe you can import them to CM contacts like this. Might want to confirm that first though.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Thanks for the reply. I'm going to do this later. Does cyanogen live up to the hype?
Everyone has their own preference. I personally like touchwiz better. There are plenty who would agree and disagree.
If you've got a nandroid backup of your current set up, its pretty easy to flash a bunch of different ones to see what you like, and then go back if none keep your interest.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Thanks again for the response and sorry for my late thanks. I was busy at work and overlooked the post.
Sent from my SGH-I747M using Tapatalk
You can use google to back up all contacts and restore them on any android with your google account on it....as for the install I believe our s3 is compatible with the cm installer
crazymonkey05 said:
You can use google to back up all contacts and restore them on any android with your google account on it....as for the install I believe our s3 is compatible with the cm installer
Click to expand...
Click to collapse
When you say cm installer. I assumes you are talking about the app and pc program that does everything automatically. It says my phone is compatible however wouldn't work originally. I had to root and use twrp. Can I use that to update from now on or should I continue to use twrp?
Sent from my SGH-I747M using Tapatalk
Edit - double post
Well for me cwm is the easiest to use as you just wipe and flash.....its purely up to you, if your gunna use twrp just download the zip boot recovery wipe system, cache, dalvik cache, data (factory reset), and hit install zip and bam you got cyanogen
I wouldn't wipe /system before a flash. If the rom fails to flash youll have no OS to boot into, and it can be a huge pain to get it back. If the rom does flash, its first step will be to format /system, so it gets done anyway.
I think this may be one of those things people used to have to do on some older devices, and was carried on to newer ones. I just think its an unneeded extra step, and more than a few times ended up taking a day or two to help people get their device working right again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
I wouldn't wipe /system before a flash. If the rom fails to flash youll have no OS to boot into, and it can be a huge pain to get it back. If the rom does flash, its first step will be to format /system, so it gets done anyway.
I think this may be one of those things people used to have to do on some older devices, and was carried on to newer ones. I just think its an unneeded extra step, and more than a few times ended up taking a day or two to help people get their device working right again.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
That's good advice that would have helped me a lot. All the instructions I followed online said to wipe/format everytime.
Sent from my SGH-I747M using Tapatalk
Yeah, its extremely common advice. I see it all the time. There are rare times when it is necessary to format system, but I dont feel a rom flash is one of them.
Its still possible to end up with no OS after a failed flash, but the chances are greatly decreased by eliminating that one step!
Sent from my SAMSUNG-SGH-I747 using Tapatalk