Database Users

Question regarding flashing Cataclysm mod on Feb update when it's out

Hey all... Just a simple question... I have the Cataclysm mod .zip from jan5 measuring around 35mb.... Would like to know if I flash the same over the Feb update when the same comes out... Would the same work and I'll get all the features on that or not.....
Would be trying nonetheless but wanted to know....

likely no.

I had the same question... if no is no - great... just want to rephrase it...
My understanding of the Cata MOD - is that it installs on top of stock. If that is the case, when the FEB security update is released why not install it as originally planned for the Cataclysm updates? (where the vendor.img was NOT included)...
In theory this may work? IF not - why?

Ok - I'm going to grab the February release and take the approach of only flashing the CATA MOD file ontop of the system/vendor images... I'll report back here if it works... as stated I believe in theory it should work just fine.
Would be a great way to continue to enjoy CATACLYSM ROM... best ROM out there...

luigidk said:
Ok - I'm going to grab the February release and take the approach of only flashing the CATA MOD file ontop of the system/vendor images... I'll report back here if it works... as stated I believe in theory it should work just fine.
Would be a great way to continue to enjoy CATACLYSM ROM... best ROM out there...
Click to expand...
Click to collapse
Please make sure to report back, I'm curious about this too. I'm fairly sure it isn't the best idea, though

redsmith said:
Please make sure to report back, I'm curious about this too. I'm fairly sure it isn't the best idea, though
Click to expand...
Click to collapse
I'll do a nandroid backup first.
Then - will flash the new system.img, the CATA MOD, then the new Vendor.img... based on my previous notes on how to install just the MOD file - this SHOULD work. I suppose one gotcha may be if the kernel needs to change - in that case I'd just immediatly flash a custom kernel over the stock cata kernel that comes with the MOD flash. I use GOD's Kernel - http://forum.xda-developers.com/nexus-6p/orig-development/kernel-t3276585
I note that the boot image and radio images have not changed in this release - so we're talking pretty straightforward testing here!
My understanding was that Atl4ntis developed the MOD file just for this reason - and also decoupled the CATA MOD work from the main stock rom. The end result was a unique ROM whereas it truly 'sat on top' of stock...
This is one reason I liked the rom so much - it was for all purposes a stock ROM - with the bells and whistles that CATA had - sitting on top as extras... at least that is how I looked at it.
IF this doesn't work - I'm likely just going to go back to stock ROM anyway as I don't trust anyother ROM's stability - based on past experience - CATA is the ONLY ROM that was stock-stable.
Still frustrated that people on this site killed Cataclysm for us.... Whatever political crap that was going on was BS - here was a GREAT developer who just plain delivered and delivered and delivered... and made things better for many of us. To be slammed in any way or manner is beyond petty.

luigidk said:
I'll do a nandroid backup first.
Then - will flash the new system.img, the CATA MOD, then the new Vendor.img... based on my previous notes on how to install just the MOD file - this SHOULD work. I suppose one gotcha may be if the kernel needs to change - in that case I'd just immediatly flash a custom kernel over the stock cata kernel that comes with the MOD flash. I use GOD's Kernel - http://forum.xda-developers.com/nexus-6p/orig-development/kernel-t3276585
I note that the boot image and radio images have not changed in this release - so we're talking pretty straightforward testing here!
My understanding was that Atl4ntis developed the MOD file just for this reason - and also decoupled the CATA MOD work from the main stock rom. The end result was a unique ROM whereas it truly 'sat on top' of stock...
This is one reason I liked the rom so much - it was for all purposes a stock ROM - with the bells and whistles that CATA had - sitting on top as extras... at least that is how I looked at it.
IF this doesn't work - I'm likely just going to go back to stock ROM anyway as I don't trust anyother ROM's stability - based on past experience - CATA is the ONLY ROM that was stock-stable.
Still frustrated that people on this site killed Cataclysm for us.... Whatever political crap that was going on was BS - here was a GREAT developer who just plain delivered and delivered and delivered... and made things better for many of us. To be slammed in any way or manner is beyond petty.
Click to expand...
Click to collapse
didnt work... started from scratch and flashed the stock system image with having the userdata formatted as wel... then proceeded to flash the cata mod (JAN5) update almost around 35mb.... also had checked previously that it had it's own boot.img so after flashing cataMOD.. went to bootloader and flashed the stock boot.img...
came up and got stuck at android bootlogo.... waited 15mins and went to stock again.... but there is some light at the end of the tunnel... i was using slimROM devloper's @Yank555 rom(YAOSP) is freaking awesome and the most stable.... also has my beloved feature "SLIMDIM" which dim's the nagiation bar...
here is the link:-
https://twitter.com/yank555lu >>> for following development...
and the Android-fileHost link:-
https://www.androidfilehost.com/?w=files&flid=45668

rohit25 said:
didnt work... started from scratch and flashed the stock system image with having the userdata formatted as wel... then proceeded to flash the cata mod (JAN5) update almost around 35mb.... also had checked previously that it had it's own boot.img so after flashing cataMOD.. went to bootloader and flashed the stock boot.img...
came up and got stuck at android bootlogo.... waited 15mins and went to stock again.... but there is some light at the end of the tunnel... i was using slimROM devloper's @Yank555 rom(YAOSP) is freaking awesome and the most stable.... also has my beloved feature "SLIMDIM" which dim's the nagiation bar...
here is the link:-
https://twitter.com/yank555lu >>> for following development...
and the Android-fileHost link:-
https://www.androidfilehost.com/?w=files&flid=45668
Click to expand...
Click to collapse
Did you also flash the vendor.img after flashing the CATAMOD?

luigidk said:
Did you also flash the vendor.img after flashing the CATAMOD?
Click to expand...
Click to collapse
nope

Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat

myuzi said:
Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat
Click to expand...
Click to collapse
can confirm that everything works... i guess flashing the vendor did the trick...

myuzi said:
Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat
Click to expand...
Click to collapse
Great news!
- with the bootloader being the same, as well as the radio - is there a need to flash anything other than system.img, CATA MOD, and vendor.img.
- also - why did you manually flash, rather than flash the images with TWRP? (note, when flashing images with TWRP I see an option to install to either boot or recovery - and I'm still trying to determine which to use... in the meantime I'm installing the drivers on my PC so I can manually flash also.
- for manually flashing - can you flash in order: system.img, catamod, vendor.img? without rebooting between steps? (I figure I can flash a kernel later in TWRP)

myuzi said:
Hi, worked for me.
I manually flashed the latest factory images. (bootloader, radio, recovery, boot, system, cache, vendor, userdata)
Then I flashed twrp.
Booted into twrp and installed latest Cat-Mod, SuperSU 2.52, franco-r9.
Rebooted into bootloader and flashed vendor again and formatted userdata.
Hope this helps,
Pat
Click to expand...
Click to collapse
a question though.. i somehow have decrypted my phone... is any adversity of the same.. should i encrypt it back again.. and if yes.. how...

luigidk said:
Great news!
- with the bootloader being the same, as well as the radio - is there a need to flash anything other than system.img, CATA MOD, and vendor.img.
- also - why did you manually flash, rather than flash the images with TWRP? (note, when flashing images with TWRP I see an option to install to either boot or recovery - and I'm still trying to determine which to use... in the meantime I'm installing the drivers on my PC so I can manually flash also.
- for manually flashing - can you flash in order: system.img, catamod, vendor.img? without rebooting between steps? (I figure I can flash a kernel later in TWRP)
Click to expand...
Click to collapse
hey.. the catamod would be flashed from twrp.. would suggest taking the steps that work.. should be simpler..

rohit25 said:
hey.. the catamod would be flashed from twrp.. would suggest taking the steps that work.. should be simpler..
Click to expand...
Click to collapse
agreed - and more consistent - don't have to check whether all images need flashing!
Did you flash CATAMOD last - or before Vendor (I can't remember if it matters!)

luigidk said:
agreed - and more consistent - don't have to check whether all images need flashing!
Did you flash CATAMOD last - or before Vendor (I can't remember if it matters!)
Click to expand...
Click to collapse
catmod first.. i had the jan6 variant so that had the vendor in it... then had to boot to bootloader and then flash vendor again.....

rohit25 said:
a question though.. i somehow have decrypted my phone... is any adversity of the same.. should i encrypt it back again.. and if yes.. how...
Click to expand...
Click to collapse
Sorry, I should have been more clear. I always format userdata before booting into android, so the phone will be decrypted. The choice is yours if you want to encrypt or not. There really isn't much benefit to decrypt on the 6P since it's plenty fast as is. I'm just a creature of habit.

I've successfully upgraded to MMB29Q - and have stayed on CATACLYSM ROM - using the last CATA MOD.
For me this is a big deal as it is the first time I've done a manual update using fastboot commands. but thanks to everyone in XDA - went very well (Note: I've always used some type of toolkit in the past, or everything was already baked into a FULL ROM install...)
Also - first time I'm going 100% no root - so I can keep running AP
I flashed these images from the MMB29Q image - in order:
- bootloader.img
- radio.img
- boot.img
- system.img
- booted into recovery:
- used TWRP to flash CATA MOD
- booted back to bootloader:
- flashed vendor.img
- used TWRP to flash a permissive kernel (God's Kernel)
- used TWRP to copy/chmod the latest HOSTS file from ADAWAY (no longer using Adaway directly as I'm not running root)
- used TWRP to flash latest V4A install (atmos/sony version)
- used TWRP to flash sony music player install
- rebooted
everything is 100% - no root - AP working and CATA enhancements in place

luigidk said:
I've successfully upgraded to MMB29Q - and have stayed on CATACLYSM ROM - using the last CATA MOD.
For me this is a big deal as it is the first time I've done a manual update using fastboot commands. but thanks to everyone in XDA - went very well (Note: I've always used some type of toolkit in the past, or everything was already baked into a FULL ROM install...)
Also - first time I'm going 100% no root - so I can keep running AP
I flashed these images from the MMB29Q image - in order:
- bootloader.img
- radio.img
- boot.img
- system.img
- booted into recovery:
- used TWRP to flash CATA MOD
- booted back to bootloader:
- flashed vendor.img
- used TWRP to flash a permissive kernel (God's Kernel)
- used TWRP to copy/chmod the latest HOSTS file from ADAWAY (no longer using Adaway directly as I'm not running root)
- used TWRP to flash latest V4A install (atmos/sony version)
- used TWRP to flash sony music player install
- rebooted
everything is 100% - no root - AP working and CATA enhancements in place
Click to expand...
Click to collapse
looks good... and not using toolkits is big WIN... manual is much better..

[Guide][How to]Update Bootloader/Firmware to OOS3/H2OS2 w/o installing OOS/H2OS

Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you

matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt

Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.

Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?

jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.

Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?

jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.

I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?

jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.

I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.

Duplicate post.Deleted

ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader

matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!

ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful

Is this enough to install CM14 or do i have to install the whole room and them flash CM14?

Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP

I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm

slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate

1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)

walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app

Won't boot into system or fastboot

Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?

CiT42 said:
Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
Click to expand...
Click to collapse
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm

Choose an username... said:
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Click to expand...
Click to collapse
I flashed DrakenFX's B29 stock rom. Didn't thought it would work with recovery but anyway ! Thank you.
Do you recommend some ROMs, kernels, etc ?

CiT42 said:
Do you recommend some ROMs, kernels, etc ?
Click to expand...
Click to collapse
Nah, they are all mostly bad. The best of the bunch seems to be NucleaRom, it has an okay kernel (Radioactive, not too good battery-wise but I've never seen so little UI lag, like, ever) and okay features (like 1/3 of what ResurrectionRemix has), an awesome maintainer (OrdenKrieger) and boots in like 15 seconds
But the stock ROM is currently the best of them all, not battery wise (you can get some obscenely high SOT numbers on LineageOS with Substratum black themes) but it's fluid and stuff runs well on it. The status bar is hideous though, and MiFavor is white themed, on an AMOLED screen, what the crap ZTE?
Don't try PureNexus, permanent hard brick from the looks of it.
LineageOS works okay but it has some compatibility problems with some apps I use, dunno
I think you could try the dual-boot patcher, that way you can test the roms and keep a working stock rom to use it as your daily driver without losing data. i never used the dual boot patcher though, so good luck if you will use it

I've bad experiences with Dual boot on my old 1+.

ZTE Axon 7 Rom help

hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!

gelie68 said:
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
Click to expand...
Click to collapse
I am currently using DarkRom...great battery life and have not encountered any bugs as yet.

gelie68 said:
hello guys,
this is my first thread here on Xda forum.
it's my very first time i want to install a custom Rom on my smartphone. could someone please let me know which Rom is the most stable, less battery draining Rom to install?
thanks a lot!
Click to expand...
Click to collapse
LOS is pretty good on both fronts, Pure Fusion seems to be based on AOSP, good battery life; Nuclea was pretty good too.
Read EVERYTHING or you may DFU brick your phone (disassembly required) or even wipe your IMEIs. Remember that your phone model is the one on the back of the phone, NOT NECESSARILY the one that the system says!
For custom ROMs you'll need the UNIVERSAL BOOTLOADER, your corresponding MODEM FILE, an image of TWRP 3.1.1-0, and MAGISK on your phone. Reboot only after flashing everything, and after flashing the Universal Bootloader, select Install Image and select the TWRP image, then flash it to the recovery partition

Choose an username... said:
LOS is pretty good on both fronts, Pure Fusion seems to be based on AOSP, good battery life; Nuclea was pretty good too.
Read EVERYTHING or you may DFU brick your phone (disassembly required) or even wipe your IMEIs. Remember that your phone model is the one on the back of the phone, NOT NECESSARILY the one that the system says!
For custom ROMs you'll need the UNIVERSAL BOOTLOADER, your corresponding MODEM FILE, an image of TWRP 3.1.1-0, and MAGISK on your phone. Reboot only after flashing everything, and after flashing the Universal Bootloader, select Install Image and select the TWRP image, then flash it to the recovery partition
Click to expand...
Click to collapse
i have installed the TWRP 3.1.1.0 and rooted the phone. everything is ok till now!
i don't understand what you mean with the need for the universal bootloader, corresponding modem file.
thanks for your hellp!

gelie68 said:
i have installed the TWRP 3.1.1.0 and rooted the phone. everything is ok till now!
i don't understand what you mean with the need for the universal bootloader, corresponding modem file.
thanks for your hellp!
Click to expand...
Click to collapse
To install any custom ROM you first need to flash the A2017X_Universal_Bootloader.zip, then flash TWRP 3.1.1-0 (the universal bootloader installs an old version of TWRP which will appear after a reboot, you simply overwrite it by flashing the TWRP.img) then the modem file for your own model (for example A2017G_Modem.zip), then the ROM, then Magisk_14.3.zip.
The A2017X_Universal_Bootloader.zip and the modem files are in the LOS thread.

Choose an username... said:
To install any custom ROM you first need to flash the A2017X_Universal_Bootloader.zip, then flash TWRP 3.1.1-0 (the universal bootloader installs an old version of TWRP which will appear after a reboot, you simply overwrite it by flashing the TWRP.img) then the modem file for your own model (for example A2017G_Modem.zip), then the ROM, then Magisk_14.3.zip.
The A2017X_Universal_Bootloader.zip and the modem files are in the LOS thread.
Click to expand...
Click to collapse
i used the Axon7toolkit to flash recovery and root. it says i can use it to flash Roms...
anyway it's a new world to me and i feel lost here.
do you advise i read any beginner guide about Flashing roms and modding?
thanks a lot.

gelie68 said:
i used the Axon7toolkit to flash recovery and root. it says i can use it to flash Roms...
anyway it's a new world to me and i feel lost here.
do you advise i read any beginner guide about Flashing roms and modding?
thanks a lot.
Click to expand...
Click to collapse
Don't know about any guides, but basically read the posts entirely before actually trying to do anything. The axon7toolkit is nice and all but you just shouldn't use it for flashing stuff. If you have TWRP, you can simply forget about the toolkit for pretty much everything.
To install a ROM you have to use the Install button on TWRP. If you have an error 7 it probably means that your TWRP version is old, check that and install the latest TWRP image if that happens.
If the ROM asks for a pin on startup, go to Wipe then Advanced then Format data

stuck in unlock phone screen

succesfully unlock the bootloader,flashed the twrp but when i flashed the supersu then it get stuck in the unlock warning screen..and after fewsecond it relaaunched the twrp recovery...guyz anyone plss help..i get worried about my phone..thanks in advance

ahadabdul said:
succesfully unlock the bootloader,flashed the twrp but when i flashed the supersu then it get stuck in the unlock warning screen..and after fewsecond it relaaunched the twrp recovery...guyz anyone plss help..i get worried about my phone..thanks in advance
Click to expand...
Click to collapse
You need to flash ElementalX kernel prior to flash SuperSu or magisk if you want to root stock nougat or marshmallow rom.
Instructions are here if you need details: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918

strongst said:
You need to flash ElementalX kernel prior to flash SuperSu or magisk if you want to root stock nougat or marshmallow rom.
Instructions are here if you need details: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Click to expand...
Click to collapse
i am in soak test when i unlock bootloader and rooted it..when i wiped data it shows os not installed....what does it mean?

ahadabdul said:
i am in soak test when i unlock bootloader and rotted it..when i wiped data it shows os not installed....what does it means?
Click to expand...
Click to collapse
Even in soak test it you need to install exkernel as mentioned.
Maybe you wiped the system partition too?! Then you can here's no os at all... Can you remember what partitions you exactly wiped?
I would recommend to clean flash the last available stock nougat rom in terms of security https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 if you don't want to install the soak test again and you're willing to upgrade

strongst said:
Even in soak test it you need to install exkernel as mentioned.
Maybe you wiped the system partition too?! Then you can here's no os at all... Can you remember what partitions you exactly wiped?
I would recommend to clean flash the last available stock nougat rom in terms of security https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 if you don't want to install the soak test again and you're willing to upgrade
Click to expand...
Click to collapse
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?

ahadabdul said:
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?
Click to expand...
Click to collapse
Welcome here and have a great time on this great device :laugh:
You don't want to root? Why you have flashed supersu mentioned in your first post? I'm a little bit confused now
please take some time to hold on and think about what you want and what's your intention with your device. I don't know what you want and can't recommend anything unless I know what you want.
You should tell
After that we will see what suits you best:good:

ahadabdul said:
now please tell me what should i do...did i flash a rr rom or do what..please advice me..i am new to this community and know very less about it...plss help me brother..i dont want to root but to fflash a rom..should i do it?
Click to expand...
Click to collapse
As strongst has mentioned, please clarify what you're trying to accomplish with your device - what you want may elicit a different set of suggestions from us.
However, if you're trying to flash a custom ROM, you do not require root at all for our device. You simply require TWRP on your device, then you flash the custom ROM through TWRP. Be aware that many of the latest custom ROM builds are 64 bit in nature and as such require a 64 bit TWRP flashed. The instructions in the relevant custom ROM thread should have the link.
Also, you may wish to clarify what state your device is in at the moment: as far as I can see, it's still in the stock ROM, with TWRP, no system loaded and failing to boot from flashing SuperSU onto the stock ROM kernel, is that correct?

strongst said:
Welcome here and have a great time on this great device :laugh:
You don't want to root? Why you have flashed supersu mentioned in your first post? I'm a little bit confused now
please take some time to hold on and think about what you want and what's your intention with your device. I don't know what you want and can't recommend anything unless I know what you want.
You should tell
After that we will see what suits you best:good:
Click to expand...
Click to collapse
what i actually want is to need a new custom rom to atleast run my device ...which is my primaary device ..please tell me should i flash a rr rom ...i flash twrp 3.2.0.0....please tell me?...first i want a rooted phone with new custom rom but now i have to run this phone which is dead now..anyhow...please tell me the way i can..

echo92 said:
As strongst has mentioned, please clarify what you're trying to accomplish with your device - what you want may elicit a different set of suggestions from us.
However, if you're trying to flash a custom ROM, you do not require root at all for our device. You simply require TWRP on your device, then you flash the custom ROM through TWRP. Be aware that many of the latest custom ROM builds are 64 bit in nature and as such require a 64 bit TWRP flashed. The instructions in the relevant custom ROM thread should have the link.
Also, you may wish to clarify what state your device is in at the moment: as far as I can see, it's still in the stock ROM, with TWRP, no system loaded and failing to boot from flashing SuperSU onto the stock ROM kernel, is that correct?
Click to expand...
Click to collapse
i was in the soak test version.i unlocked bootloader,flash recovery and flash supersu..but phone does not on..it stuck in the unlock screen..and ..and i think i accidentally did thw wipe data ...what should i do

ahadabdul said:
what i actually want is to need a new custom rom to atleast run my device ...which is my primaary device ..please tell me should i flash a rr rom ...i flash twrp 3.2.0.0....please tell me?...first i want a rooted phone with new custom rom but now i have to run this phone which is dead now..anyhow...please tell me the way i can..
Click to expand...
Click to collapse
1)Again, you do not need root to install custom ROMs, only TWRP is required.
1a)Which TWRP have you flashed, is this the 32 bit or 64 bit version? If this is the official TWRP 3.2, I think that may be the 32 bit version. In which case, you'll want Resurrection Remix 5.8.5 https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275
As you cannot boot properly, the easiest way to flash would be to boot your device to TWRP recovery, then connect your device to your computer. Your device's internal storage should be visible then, you may wish to back up your files at this point. Copy the RR custom ROM zip and the GApps package of your choice to your device and flash in TWRP as per the instructions. As usual with flashing custom ROMs, you will have to wipe /system, /data, cache and Dalvik in TWRP before flashing. Up to you if you choose to wipe internal storage as well (but usually a good idea switching between stock and custom ROMs).
Once you've booted into RR, you should have root as it already comes with magisk.
If you want to flash the RR 6.0 custom ROM, you must have the 64 bit TWRP recovery flashed before you attempt to flash the 6.0 custom ROM or any Oreo custom ROMs at the time of writing.
2)Alternatively, as strongst has suggested, if you simply want your device to be working again, you'll have to flash the latest stock ROM again, since you've likely tripped the anti-rooting measures in the stock kernel.
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
ahadabdul said:
i was in the soak test version.i unlocked bootloader,flash recovery and flash supersu..but phone does not on..it stuck in the unlock screen..and ..and i think i accidentally did thw wipe data ...what should i do
Click to expand...
Click to collapse
Which soak test, NPJ25.75-2? If so, that's a really old soak test, and as such I would recommend you flash the latest stock ROM available for your device, else you may run into issues with the newest custom ROMs, particularly if you have a G4 Plus. Can you mention what device and what region you're in, so we can guide you to the correct stock ROM to flash?
Yeah, that phone not turning on is because of SuperSU flashed onto the stock Nougat kernel, which you cannot do for our device - you need a custom kernel. The main ways to get around it are as I described above - flash a custom ROM or re-flash the correct stock ROM for your device.