Related
Hi all,
This is probably a pretty basic question for you, so please bear with me, and if it is basic, hopefully there is a straightforward answer .
Having settled on the awesome CM-6.1.0-RC1, I haven't looked to change ROM.
However, with CM-7.0.0-RC1 being released, its time to upgrade .
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
I appreciate there is a lot of info in ali ba's dev thread [ [ROM] CyanogenMod experimental builds] however, there is approx 235 pages there, and the OP is a little lite.
Would it be possible to have guide here, as I presume many people will be wanting to follow the same upgrade path.
I am wondering how we can 'save' apps, [i.e. Angry Birds status, web browser installation, general settings/config,] during the upgrade... because I am guessing a full wipe is required and therefore a Nandroid backup won't really help...or will it?
Anyone that can help?
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
c_man said:
Can anyone please explain the steps needed to follow in order to go from CM-6.1.0-RC1 to CM-7.0.0-RC1 please?
Click to expand...
Click to collapse
First question should be:
Do we need to wipe when upgrading from CM6.1?
If we need wipe, I suggest you to:
- do a nandroid backup
- backup all apps with titanium backup
- wipe + flash 7.0 RC1
- download and install gapps
- restore apps with titanium backup
If no wipe required:
- do a nandroid backup
- flash 7.0 RC1
Question: does UOT kitchen (for circle mod battery) works with 7.0?
gilliu00_ said:
I'm also running CM6.1 rooted and I've tried upgrading by downloading Rom manager and then booting into recovery, doing a factory reset/wipe data/wipe cache/wipe dalvik cache - and then flashing the CM7 RC1 zip but I get a boot loop every time.
I've tried removing the SD card and Sim card but same error appears.
Actually it's weird because I've been getting a boot loop with every firmware I've tried to flash except for CM6.1.
Luckily I did a Nandroid backup...
Click to expand...
Click to collapse
http://forum.cyanogenmod.com/topic/15838-cyanogenmod-7-for-legend-v700-rc1-2152011/
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full ourput.
Please use Pastebin when possible
Skardy said:
First question should be:
Do we need to wipe when upgrading from CM6.1?
Click to expand...
Click to collapse
Yep, true.
Anyone?
Upgrading from earlier version of CyanogenMod 7?
* Perform a NANDroid backup of your current ROM.
* Flash CyanogenMod (your Google Apps will be backed up & restored automatically)
Click to expand...
Click to collapse
So no, you do not need to wipe before upgrading,
The backup is just for security reasons. You never know what could go wrong, so it's good to have a backup in place.
Just flash the new CM 7 and you should be good to go.
^ Mastacheata - thats if you're upgrading from earlier version of CyanogenMod 7
That question we are asking here is what if you're upgrading from CM6.1.
Oh I'm sorry, I misread that the whole time.
Gonna try it now and report back in a few minutes.
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
I'm thinking I may just do a full on Titanium backup, full wipe, then go for CM7.0RC1.
easyonthev said:
I've not gone 6.1 -> 7rc directly, but I did go from 6.1 to a 7 nightly build a couple weeks ago without wiping and I don't seem to have any problems (except GPS not working).
Click to expand...
Click to collapse
GPS not working in CM7.0 RC1 ??
Do we even have a list of things not working in CM7.0RC1? Again, the OP in the dev thread is a little lite with respect to 'known issue' and similar.
My test was unsuccessful.
I was neither able to install directly over 6.1 nor with prior wipe.
My phone would always end up in a boot loop.
Logcat did tell some Exceptions for unknown permissions.
Detailed explanation will follow in the developer thread.
i accidentally flashed cm7 build 0 over cm6.1 stable before. was able to boot but my phone was laggy & some features were broken, as far as i can remember. so i guess the best path is:
TI backup
complete wipe
flash cm7
TI restore
cliche by now, i know. but it never fails...
As we start the RC phase of CM7, many of you are now taking the leap from CM6 stable to the new RC's.
Some of you may be able to get away with doing this without a wipe; however, most of you will not be that lucky.
Differences in the rom, files system, and even Google Addons will likely throw most of you into boot loops.
Therefore, here is my recommended upgrade path:
1) Nandroid backup your current rom
2) Update your recovery to the latest available (CWR is my choice)
3) Format system via recovery
4) Wipe/Factory reset
5) Flash CM7 then Google addon 1/20
If any of you have data that you must absolutely save, then and only then should you use Titanium backup (or other backup apps) to restore your data. Please be sure not to restore any data to /system using these apps, as this will mostly likely corrupt your ROM and/or Market.
Click to expand...
Click to collapse
Here is what CM Team recommends
Skardy said:
Here is what CM Team recommends
Click to expand...
Click to collapse
Perfect, I shoud've found that myself .
Now its just a question as to whether to go to CM7.0RC2 - lots of people still reporting bugs...
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Go read the first post of the paranoid android rom under android original development. Don't flash things until you read the instructions. Cache is wiped by the rom, and you need gapps with a new install.
Sent from my Nexus 7 using xda app-developers app
delonicdevil said:
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Click to expand...
Click to collapse
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
mvmacd said:
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
Click to expand...
Click to collapse
and one more thing, flash a new kernel ONLY after the first reboot.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
thanks alot!
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
OH..I didn't knew it. Thanks!
I am not getting on how to do that
Hi,
Can any one post link to forum?
I am using paranoid android and in goomanager its showing new update available..!
after downloading zip what to do next?
If any one can put screenshot or list step it would be much helpful..
Thanks in advance...
Balaji_NEXUS said:
OH..I didn't knew it. Thanks!
Click to expand...
Click to collapse
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This actually makes no difference, aside from making the process more time consuming. The few and far between anecdotes that led to this practice are a cum hoc ergo propter hoc fallacy. Without a doubt, it does not hurt anything, but it also yields no real benefit over flashing in the same recovery session.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Wilks3y said:
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Click to expand...
Click to collapse
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Pirateghost said:
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Wilks3y said:
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Click to expand...
Click to collapse
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Pirateghost said:
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Wilks3y said:
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Click to expand...
Click to collapse
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Pirateghost said:
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok great.
Appreciate that
Can anyone help me please, I have posted this on the PA thread but have had no response
I am unable to install PA on my nexus.
I have rooted and unlocked my device via the nexus root kit, downloaded the latest TWRP and installed this on my device. Moved PA and GAPPS to my storage and flashed PA first and then GAPPS, wiped dalvik and reboot the device. All that happens is the ROM doesnt appear to want to flash on the device as it reset my nexus back to factory settings but never installed the ROM.
I have also attempted this with goomanager but get stuck in a bootloop after install
However, I have been able to download and install CWM and CM10 so I know there is no issue with the device.
Can anyone provide any insight as to why this may be happenening
Have you verified the md5 of your download?
Also, patience is a virtue. Believer or not, some questions aren't always answered in mere minutes, as most folks have lives outside of the forum. I know waiting can seem unreasonable at times, but the timespan between you asking in the PA thread and then starting this completely new thread asking the same question was less than twenty minutes.
Sent from my Nexus 7 using Tapatalk HD
You left out the most important step in switching from one ROM to another... As mentioned in several tutorials and posts:
WIPE DATA/FACTORY RESET before flashing ROM...
Sent from my Galaxy Nexus
Pirateghost said:
You left out the most important step in switching from one ROM to another... As mentioned in several tutorials and posts:
WIPE DATA/FACTORY RESET before flashing ROM...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It helps but for the last 3 different roms I've thrown onto my n7 I haven't done that, All I've had to do was wipe my caches.
Eagle1337 said:
It helps but for the last 3 different roms I've thrown onto my n7 I haven't done that, All I've had to do was wipe my caches.
Click to expand...
Click to collapse
Wiping caches is unnecessary. New cache is built upon first boot.
You might have gotten away without wiping data if the bases for your ROMs were similar. Paranoid requires a wipe coming from most other ROMs.
Also you run the risk of corrupting your settings and app databases when you don't wipe data between different ROMs
Sent from my Galaxy Nexus
Q&A for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
keith.valdez said:
If I'm flashing from an All F2Fs Ext4 rom, are there any special preparations I need to perform to ensure I don't brick? I would like to flash it but I want to ensure that there are few caveats first. Thanks.
Click to expand...
Click to collapse
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
NUMB401 said:
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
Click to expand...
Click to collapse
Exactly - if coming from All-F2FS in recovery put cache and data back to ext4 otherwise when you boot it will think your tablet is encrypted and ask for a password!
Thanks for the ROM. However a tilapia(3g) version would be greatly appreciated!
Click to expand...
Click to collapse
I have built Lolipop from source for it but 3G does not seem to be working with radio from KitKat (and I don't know where to get another radio.img)
failing Google+ apk
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Known incompatible for now. Rest assured it'll be fixed by the ota ?
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
gsmyth said:
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
Click to expand...
Click to collapse
Just F2FS
---------- Post added at 12:42 PM ---------- Previous post was at 12:42 PM ----------
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Latest GApps newly linked in OP has a working Google+
There is broken "Ok Google" hotword as well as voice search. It just won't listen to me
First off let me say this is awesome and really breathed new life into my old N7! Secondly I used the Tap & Go setup method from an GPE One M8 and it didn't really work all the way but whatever.
The issue is there is now an undismissable notification on my M8 saying setup completed. Any ideas how to get rid of this?
Oh and also has Face Unlock ever been present on the Nexus? Wanted to try it out but wasn't listed as an option. Thanks a ton!
TitBkp
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
I cannot log into play store since upgrading to lollipop. How can I fix this?
Sent from my AOSP on Grouper using XDA Free mobile app
Successfully installed via multirom, however play store crashes when opened.
am2012 said:
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
Click to expand...
Click to collapse
Try this beta one:
http://forum.xda-developers.com/showpost.php?p=56629869&postcount=196
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
S1L3nTShaDoWz said:
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
Click to expand...
Click to collapse
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
bshiznit said:
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
Click to expand...
Click to collapse
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
S1L3nTShaDoWz said:
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
Click to expand...
Click to collapse
Glad to hear it! Sometimes /system remains mounted so TWRP will incorrectly report missing OS
I guess the mic doesn't work, Shazam doesn't work?
Works great so far! Only issue appears to be the volume buttons (when used for notification volume) results in crashing.
Debranded, Debloated, Deodexed H901-10c ROM for T-Mobile LG V10 (LG-H901) - Clean & Stable
Thanks go to @Rydah805 for deodexing the stock ROM and being my guinea pig while I was fixing all the broken features.
Thanks also go to @KOLIOXDA for being my guinea pig while troubleshooting installation issues.
Features:
WiFi Calling works with Xposed (even in Airplane Mode)
Second screen works with Xposed (no more force-closes during calls)
No spyware (Adapt Client and Carrier IQ removed)
No T-Mobile apps
No Google apps (except Play Store, Search, Text-to-Speech, and Google Play Services)
Stock LG boot and shutdown animations
No boot sound (boots silently)
No Chrome customizations (Chrome homepage no longer forced to t-mobile.com)
Stock recovery restore disabled (does not overwrite TWRP on reboot)
External storage permissions fix (all apps can write to MicroSD card)
WiFi connectivity fix by @ZDeuce2
AOSP Emoji font
Over 100 additional alarm, ringtone, and notification sounds from Nexus and Samsung phones
Busybox 1.24.1
SuperSU v2.65 stable
Stock 10c kernel and boot image
Download (built Feb. 08, 2016): https://onedrive.live.com/redir?resid=FE4478E2ABDFD5FC!1082&authkey=!AMAKMBsK8gCEhH0&ithint=file,zip
Changes in this build: Updated SuperSU to 2.65 stable.
Before you install, read below:
Safe to install over stock ROM (odexed or deodexed), no need to factory-reset, unless you're compelled to do so by your inner demons.
Compatible with Xposed v79-sdk22-arm64 and later (sdk22-arm64 ONLY). Do NOT install any earlier versions or other variants of the Framework. You must use Xposed Installer 3.0 alpha 4.
Compatible with P_Toti's G4TweaksBox.
Compatible with the LG Apps Theme Engine.
The T-Mobile Device Unlock app does not work on this ROM and is not included. The Play Store version does not work, either. To SIM-unlock your phone, flash the stock ROM, unlock (SIM-unlock is forever and not ROM-dependent), then flash my ROM.
To get back Google and T-Mobile (except Device Unlock) apps, install them from the Play Store. They all work. They were removed because system apps are not Greenifiable, plus they were causing problems when deodexed.
If you use an ad blocker that modifies your hosts file (such as AdAway), you must reapply your ad-blocking filters as this ROM overwrites your customized hosts file with a stock hosts file.
Do NOT install the "Second Screen Fix" ZIP, second screen works fine in this ROM with and without Xposed. The "Second Screen Fix" is only for odexed ROMs and will break the second screen in this ROM.
This ROM removes any mods you have installed. If you want to reinstall them, they MUST be made for a deodexed stock ROM. Mods for odexed or non-stock ROMs may cause force-closes or a bootloop (flash them at your own risk).
If you're still seeing My T-Mobile, Lookout, or the other apps in your app drawer after installing my ROM, those are updates that have been installed from the Play Store - uninstall them manually like any other user app.
DO NOT USE "FIX PERMISSIONS" IN TWRP. TWRP has no idea what permissions are correct for your phone and will screw them up, resulting in random force-closes in various apps. If you did it, you will need to wipe the entire /data partition (not just factory reset) and reflash the ROM.
If Hangouts crashes when you receive a message or call, it's because it can't find one or more notification or ringtone audio files. Go into your phone's Sound settings and re-select your notification and ringtone sounds, then go into Hangouts settings and re-select the ringtone and notification sound for each type of notification (Hangouts call, Hangouts message, Google Voice call, Google Voice message, and so on).
DO NOT INSTALL PowerNap/WakeLockManager. You will get random reboots and corrupt internal storage, since WakeLockManager randomly hard-crashes the entire ART virtual machine.
To disable the OTA notification: http://forum.xda-developers.com/showpost.php?p=66304926&postcount=1002
Installation:
WARNING: Do NOT install over a custom ROM. You will get a bootloop/force-close loop.
Copy ZIP file to phone.
Boot into TWRP.
If clean-installing, factory-reset the phone. The installer wipes the system partition automatically.
Install the ZIP.
If you want Xposed, install it now (use only v79-sdk22-arm64 or later).
Reboot.
WARNING: Do NOT install mods for other ROMs on this ROM. You will get a bootloop/force-close loop.
Do not reuse this ROM without my permission - ask first and give credit where it's due!
Enjoy!
PS. I will begin work on the Marshmallow version of my ROM once we have an official way of flashing TWRP on the Marshmallow bootloader. I want the upgrade process to be "Flash the MM KDZ, install TWRP, flash my ROM." Until then, sit tight!
So we don't factory reset or wipe anything? What if we have mods flashed as well?
baySF said:
So we don't factory reset or wipe anything? What if we have mods flashed as well?
Click to expand...
Click to collapse
No Factory Reset OR Wipe,just flash over what you have ATM.
Make a backup of your present set-up before flashing though,just in case something else pops up.
EDIT:
Removed my previous statement regarding mods/add-ons,they'll need to be re-flashed & only de-odexed mods will work per siraltus (ROM OP)
baySF said:
So we don't factory reset or wipe anything? What if we have mods flashed as well?
Click to expand...
Click to collapse
If you have mods flashed, this will remove them, so you will have to reflash them - but only if they're made for a deodexed stock ROM. If they're made for an odexed or custom ROM, they will likely not work, so flash at your own risk.
KOLIOXDA said:
No Factory Reset OR Wipe,just flash over what you have ATM.
Make a backup of your present set-up before flashing though,just in case something else pops up.
EDIT:
A flash over a factory reset would probably work,I don't see why it wouldn't,but,it's probably not necessary.
I didn't reset or wipe anything & I'm doing just fine.
I don't have Xposed or any sound mods installed,but,my bet is you shouldn't have any problem flashing over a set-up with Xposed or any other mods.
Click to expand...
Click to collapse
The ZIP wipes the /system partition automatically so there is no need to wipe it manually.
In fact, if you wipe it manually, the ZIP will fail because TWRP will lock the /system partition for an unspecified amount of time and you will need to reboot TWRP before installing the ZIP.
If you want to clean-install this, then do a factory reset, reboot TWRP, then install this ZIP. I updated instructions in OP to reflect this.
Thanks!! I'll be checking this out shortly!! :highfive:
so we need to flash a stock rom first?
Just making sure, because I'm currently on black hole... Sorry, replied earlier, but son got sick again so I didn't see the other replies...
Sent from my LG-H901 using Tapatalk
ZDeuce2 said:
so we need to flash a stock rom first?
Just making sure, because I'm currently on black hole...
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
No, read the instructions under "To clean-flash".
siraltus said:
No, read the instructions under "To clean-flash".
Click to expand...
Click to collapse
Sorry, first read it right after you posted op... Then my son got sick again, so I didn't hit send for a while... Lol.
Sent from my LG-H901 using Tapatalk
ZDeuce2 said:
Sorry, first read it right after you posted op... Then my son got sick again, so I didn't hit send for a while... Lol.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Oh, sorry, yeah I rewrote most of OP in the past hour, LOL
Is it possible to change the DPI of the ROM without all the stock apps going crazy? I'm not sure of the status of xposed so I'm assuming thats outta the picture right now
_-..zKiLLA..-_ said:
Is it possible to change the DPI of the ROM without all the stock apps going crazy? I'm not sure of the status of xposed so I'm assuming thats outta the picture right now
Click to expand...
Click to collapse
The ROM is fully compatible with Xposed v79 SDK22 arm64.
No idea about changing the DPI. I don't recommend it as it seems to break things on this phone.
Dear Sir. Altus,
Thank you for the clean upload, and directions. Currently I am running Rydah805's deodexed rom that you were kind enough to work on fixing wifi calling, etc.
My question is: Is this rom different from Rydah805's V. 1.2.2 as stability and features goes? Would you recommend dirty flashing it over his rom?
Thank you all for your hard work and Happy Holidays
Best,
Bob
bobobobicsek said:
Dear Sir. Altus,
Thank you for the clean upload, and directions. Currently I am running Rydah805's deodexed rom that you were kind enough to work on fixing wifi calling, etc.
My question is: Is this rom different from Rydah805's V. 1.2.2 as stability and features goes? Would you recommend dirty flashing it over his rom?
Thank you all for your hard work and Happy Holidays
Best,
Bob
Click to expand...
Click to collapse
You're welcome. Yes, you should flash this over his ROM. I took his deodexed base and fixed everything that was broken in it (WiFi, Hotspot, power management, other stuff), and rather than cluttering the old thread, I started a new thread with a 100% tested build and clear instructions. I debloated and debranded it, added a few useful modifications, plus I made about 30ish corrections to broken permissions and SELinux contexts that were likely causing problems in his ROM that we had yet not discovered (the power management stuff was likely not functioning properly due to being denied proper privileges). Read the OP for a list of features and modifications.
siraltus said:
You're welcome. Yes, you should flash this over his ROM. I took his deodexed base and fixed everything that was broken in it (WiFi, Hotspot, power management, other stuff), and rather than cluttering the old thread, I and started a new thread with a 100% tested build and clear instructions. I debloated and debranded it, added a few useful modifications, plus I made about 30ish corrections to broken permissions and SELinux contexts that were likely causing problems in his ROM that we had yet not discovered (the power management stuff was likely not functioning properly due to being denied proper privileges). Read the OP for a list of features and modifications.
Click to expand...
Click to collapse
Thank you again! Dirty Flashing now
Xposed
Will this Rom have the second screen fix once I install Xposed?
Thanks for your hard work.
mkrunk12 said:
Will this Rom have the second screen fix once I install Xposed?
Thanks for your hard work.
Click to expand...
Click to collapse
You're welcome. There is no need for that, second screen works fine in this ROM with Xposed and without. The "second screen fix" is only required on odexed ROMs. Updated OP to reflect this.
I'm having this weird issue where the screen will become tinted, almost like there's a pop-up or the notification bar is pulled down. It'll usually go away after a second or if I tap somewhere on the screen, but it's kinda frustrating.
Sent from my LG-H901 using Tapatalk
TheJesus said:
I'm having this weird issue where the screen will become tinted, almost like there's a pop-up or the notification bar is pulled down. It'll usually go away after a second or if I tap somewhere on the screen, but it's kinda frustrating.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I think you posted in the wrong thread. You want to post in the Troubleshooting forum.
siraltus said:
I think you posted in the wrong thread. You want to post in the Troubleshooting forum.
Click to expand...
Click to collapse
No, I was the second one to install it over in the original thread and I didn't have the issue with the actual stock ROM.