[Q] Updating OmniROM 4.4 daily on a device - General Questions and Answers

Hi Everyone -
First off, let me apologize in advance for asking this question as I imagine it has been asked dozens of times previously.
I recently installed a custom ROM (OmniROM 4.4 'KitKat') on my Galaxy Note 2. I backed everything up, rooted it, installed recovery, etc. and then installed the nightly build of the ROM at that time.
The ROM is currently undergoing heavy development/nightly builds and I'd like to update from time to time.
Here's my question: do I need to wipe the device completely every time to UPGRADE the same ROM to a newer build? installing the ROM is straightforward enough, it's reinstalling all the apps, reconnecting email, etc. that's a PITA if I were to do this several times per week.
Can someone let me know what the process is for upgrading? Or point me to a link!
Thanks a ton in advance!
B

Hi, I've updated ist daily in the last 5 days. I just checked for updates in the phone settings and the phone (GT.I9100G) does everything automatically. All my apps and data are still there after an update. Nothing was deleted.

Related

[Q] Verizon S3 locks up every reboot on rooted 4.1.2 > 4.3

I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.

[Q] Update from old Omni ROM

My WiFi Xoom is currently using Omni 4.4.2-20140427-1908+0200-wingray-HOMEMADE and kernel 2.6.39.4-ElementalX-Xoom-2.0+. I would like to update it to a more recent version of Omni ROM. When I first installed this ROM, everything worked very well. However, in the last few weeks the Xoom has frozen every few days. Launcher 3 also fails from time to time. This may or may not have anything to do with the ROM, but I might as well bring it up to date.
In Settings/About Tablet/System updates, I am being offered Omni-4.4.4-20140708-2252+0200-wingray-HOMEMADE.zip. Do I just "Flash now" from this update page, or are there other things that I should do, e.g. do I need to update gapps. If there are other things, what order should I do these in?
Most of the update information I have seen relates to updating a non-BigPart Xoom, but mine is already set up with BigPart.
Any help would be appreciated.
Thank you
Gordon1M

[Q] Random Force reboots

Hey guys, I'm a pretty heavy tinkerer and I know that comes with some risk. But before I completely wipe and reflash everything I wanted to see if someone could help diagnose my problem.
I have a Nexus 5 and have been running MultiRom for a while. I currently have Paranoid Android and Android L dual booting. I was on the newest version of PA (4.6 BETA 1) but I just flashed back to a past backup so now I am on PA 4.4 (I think). I have been having random reboots for about a day and now I can't even get my phone to stay on longer than a few minutes. I just installed Xposed and a few Modules so I assumed those were giving me the trouble, but I uninstalled Xposed when I started having problems and that didn't help. Even my backed up ROM and my Android L won't work without rebooting. This leads me to believe its something deeper down than my ROM.
Before I clean off and reflash, is there any way I can diagnose or fix this issue?
Thanks a ton.

[Q] Help Please.

So a couple of months ago, i rooted my phone (Gs3 Sgh-T999). And last month i finally decided to download a ROM. After doing so it was going great until my phone would reboot and get stuck on the reboot screen. So i would end up having to factory data reset and loosing all of my apps and stuff. After a while, i couldnt take it anymore. So with research i thought i just needed to update my firmware. So i did. And for about 2-3 weeks. Everything went fine. Then it started once agian. So i would boot into safe mode and delete the app i recently installed. One i started do that, I had no reboot issues. And i stopped downloading apps in general. And it worked... Until today. It rebooted and got stuck. I lost my cool and got furious. So i told myself, tommorow, im going to download a new rom. But i thought occured and i wondered what if it just does it on the other rom. So what i need to know, is, is it the rom or my phone and certain apps in general making it reboot? The rom im using is AOKP Jelly Bean Rom. 4.1.2 My firmware is T999UVDMD5. If there is any suggestions or help you can give me, please do so, idk how much more i can take. Thank you.
hi there
i think there might be a firmware glitch so I request you to restore the whole phone and try to use the cyanogen mod <I THINK IT MIGHT WORK ON YOUR PHONE>
< NEVER TAKE THE UNSTABLE OR NIGHTLY >
KIBS2173 said:
hi there
i think there might be a firmware glitch so I request you to restore the whole phone and try to use the cyanogen mod <I THINK IT MIGHT WORK ON YOUR PHONE>
< NEVER TAKE THE UNSTABLE OR NIGHTLY >
Click to expand...
Click to collapse
What do you mean by use cyanogen mod. I'm still learning but I am familiar with who they are. But what you want me to download, is it firmware or a ROM?

[Completed] Bootloop problem on Samsung Galaxy Tab 2 10.1 (P5100)

Hello!
I have the following problem and after countless searches over many forums I ended up finding no answer:
About 4-5 months ago my P5100 started to restart itself after 1 or 2 minutes of functioning properly (restarts even faster if i try to connect over Wi-Fi or install an app). I thought that if I leave it for a while everything will be ok, it wasn't the case so I started trying to fix it. Before I go on I mention that my P5100 was rooted , running CWM version 5.5 and CM10(10.1.3), i haven't messed with the rom, recovery, firmware etc. for more that one year and a half so it started all of a sudden. I tried everything starting from simply updating the CM version to ADB commands and finally flashing back to the stock firmware with Odin. The wipe data/factory reset didn't work neither in recovery nor commands, I even tried to delete everything via Internal Storage in my pc through USB. Every time it reverts itself to the point it was left before although everything seemed to work just fine no errors or so. It doesen't remember after reboot any setting I made or any app that i installed(if I manage to install one) it is like i didn't do anything at all to it. :crying:
Many thanks for taking your time to read my thread and maybe help me:laugh:
warriorsers said:
Hello!
I have the following problem and after countless searches over many forums I ended up finding no answer:
About 4-5 months ago my P5100 started to restart itself after 1 or 2 minutes of functioning properly (restarts even faster if i try to connect over Wi-Fi or install an app). I thought that if I leave it for a while everything will be ok, it wasn't the case so I started trying to fix it. Before I go on I mention that my P5100 was rooted , running CWM version 5.5 and CM10(10.1.3), i haven't messed with the rom, recovery, firmware etc. for more that one year and a half so it started all of a sudden. I tried everything starting from simply updating the CM version to ADB commands and finally flashing back to the stock firmware with Odin. The wipe data/factory reset didn't work neither in recovery nor commands, I even tried to delete everything via Internal Storage in my pc through USB. Every time it reverts itself to the point it was left before although everything seemed to work just fine no errors or so. It doesen't remember after reboot any setting I made or any app that i installed(if I manage to install one) it is like i didn't do anything at all to it. :crying:
Many thanks for taking your time to read my thread and maybe help me:laugh:
Click to expand...
Click to collapse
Hello and welcome to xda-assist,
your device has a quite good supported device specific forum
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
with even twrp 3.0.3 and pretty decent marshmallow builds, even official LineageOs nightly support started this week..
https://download.lineageos.org/espresso3g
Twrp 3.0.3
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
If want to sort out your present issue with your slightly outdated software instead you'll have to visit your device specific help thread
https://forum.xda-developers.com/galaxy-tab-2/help
or general help section
http://forum.xda-developers.com/android/help
Good luck
Sam Nakamura said:
Hello and welcome to xda-assist,
your device has a quite good supported device specific forum
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
with even twrp 3.0.3 and pretty decent marshmallow builds, even official LineageOs nightly support started this week..
https://download.lineageos.org/espresso3g
Twrp 3.0.3
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
If want to sort out your present issue with your slightly outdated software instead you'll have to visit your device specific help thread
https://forum.xda-developers.com/galaxy-tab-2/help
or general help section
http://forum.xda-developers.com/android/help
Good luck
Click to expand...
Click to collapse
Thank you very much i will proceed to those forums and seek further asistance :victory:

Categories

Resources