Develop Bugs

Koodo Note 2 compatibility?

Hi everyone. So I Just got a note 2 the other day after having been using a nexus 4 for the past six months. I never use stock Roms and haven't since I got my s3 a year or so ago (I seemingly change phones often...). That being said I was looking into how to root this device and which Roms were compatible etc.
It seems all Canadian note 2 devices are the same? Rogers, Bell, koodo/telus etc? Am I correct in assuming this, and if so that any of the Roms found in this forums sub forums for aosp as well as other Roms like PA etc are compatible? (if it's compatible with the att note 2 my koodo note 2 is good to go?)
Also, it seems this devices forums are outdated and dying sadly, so can anyone recommend a recently active Rom, be it aosp or not, that is highly themeable and configurable, and preferably has good s-pen support?
Much appreciated!
Oh, and a link to the correct post for rooting this device and flashing new recovery (twrp or cwm) in its latest compatible version would be awesome too.
Thanks everyone!

There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.

Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
For a nice belt and suspenders approach: make backups of your EFS partitions with all known methods: EFS Professional text format, QPST qcn, "Synergy ROM" method recovery script. (I adapted the latter for the T889V and it should work as is for your device.)
Assuming your device already has the stock 4.3 ROM, you will burn the KNOX fuse by flashing anything custom or generally trying to root.
(There may be more steps involved for KNOX, you're on your own for that part: the only thing stock 4.3 I've flashed is the modem.)
To root, get the latest t0lte Odin-flashable TWRP image, apply SuperSU or superuser zip from there as desired.
There's still a fair amount of activity out here, I've been running Omni nightlies for a while now.
It's normal for things to slow down: Bugs get squashed, ROMs on a manual release schedule slow down because they've implemented what they wanted, automatically built ROMs get smaller incremental updates from upstream. There's been an uptick with the stock TouchWiz 4.4 releases in the pipeline (the N7105 Nordic Countries CSC has been pushed, others are incoming) and kernel sources also trigger some action. Another factor for slow down is that early adopter devices are going on two-years and people upgrade.
I hardly use the S-Pen so I can't help you that much with it. There's a couple open source apps that support it and that can be added to your choice of AOSP ROM to enable things like gestures or hand-drawn notes.
Click to expand...
Click to collapse
Great Question and great response.
I recently got the Koodo note 2. I finally switched coming from my well aged HTC HD2. Anyway I have a quick question. If i'm using a TW or a AOSP rom I can't connect to my Mac adhoc network. The old roms I used on My HTC had something baked into them that allowed that. Note sure if there's a special file I have to change. Any help would be appreciated.
Thanks

Darkshado said:
There are two Canadian Note 2 models: the I317M (yours) and the T889V (mine).
So long as you don't try flashing a non I317M modem on your device, you can pretty much flash any t0lte/t0lteatt/t0ltetmo a.k.a N7105, I317(M) or T889(V) ROM out there. Along the same lines, do not flash anything meant for the N7100.
Click to expand...
Click to collapse
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.

Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!

Catalyst2012 said:
Thank you Darkshado for all your helpful posts!
1) I'm also considering one if these from Koodo, currently advertised to contain the dreaded 4.3 update. May I restate what your saying is t0lte for N7105, t0lteatt for I317M, and t0ltetmo for t0ltetmo. When I looked previously on the TWRP site I saw the 't' choices but no clear cross reference to device model number.
2) I've read for many many hours about the downgrade path to 4.1.1 to unlock and how this would blow the KNOX fuse. Considering I'd be buying the device new from Koodo, I'm not happy about the prospect of losing an entire 12 month warranty-assuming a broken KNOX.
Click to expand...
Click to collapse
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.

DelphinusMinor said:
This is a Note 3 rom for our Note 2's. I have the same phone as you are asking about. That rom will work for the I317M/I317 variants also.
http://forum.xda-developers.com/showthread.php?t=2504016
Comes with most of the N3 features including Air Command(very handy), and you can use the S5 GUI and some of the S5 apps also.
It's been very stable for me so far. I love it and it's my current daily driver.
Good luck!
Click to expand...
Click to collapse
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?

Catalyst2012 said:
Looks fascinating! A brief read indicates its for the N7100 - thanks for clarifying that it works for the i1317M. Does Call Recording work for you?
Click to expand...
Click to collapse
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.

Darkshado said:
1) Nope, t0lte is just as fine for the I317M. (If anything I'm even surprised the TWRP team still builds three separate recoveries. I'd have to look at the code for any meaningful differences, but I'm short on time to do that. Maybe ask on IRC?)
2) It's unfortunate, but then again there are other options, you could get a code from Koodo or elsewhere online; if you're adamant about keeping KNOX untouched. My understanding is that in Europe, the onus is on companies to prove that the user's root and ROM related activities caused problems with a given device. I'm thinking that the same would hold in many Canadian provinces if someone put up a fight in small claims court.
Click to expand...
Click to collapse
Thanks.
1) No need to check the TWRP code as your response was clear and helpful.
2) A local unlocker business told me: they have a new way that no longer requires downgrading to 4.1.1. With his codes, I could unlock the device without any additional software or PC for C$40. I explicitly asked about KNOX - he wasn't 100% clear but said he did not think it would affect it. He said they buy lists of unlock codes based on IMEI and resell them for a small profit. Koodo requires 90 days on Koodo + the same unlock $ fee. I wasn't planning on staying on Koodo that long. In perhaps the 8 hours by now I've spent reading about this on XDA, its still not certain a device with 4.3 can be customized without blowing the Knox efuse. Towelroot 'might' give me root without tripping it but the risk of losing a full 12 month warranty is not welcome. A used device might be OK if it was still on 4.1.x. If it had been downgraded from 4.3, though unlikely, I probably wouldn't know until after I got home. Otherwise I could root+custom right way and never mess with samsung roms.
Any suggestions are welcome!

DelphinusMinor said:
I haven't tried. I can't test it at the moment either because I need to top my minutes up. D'oh! I should be doing that tomorrow sometime.
It's a great rom. Been using it for several days and no issues.
Click to expand...
Click to collapse
You should be able to test it without using any of your minutes. Just call Koodo customer service from your handset (*611 I think) it should be a free call. When the voice menu begins, start recording. Ask a few questions like "Do you support custom ROMs?" or "Do you know the winning lottery numbers", or whatever, this is just a 2-way voice recording test. I use this trick all the time when testing. Enjoy.

Help a novice please - have ROOTED Samsung Galaxy Tab Pro 8.4 (SM-T320) - Update?

I just received a used Samsung Galaxy Tab Pro 8.4 (SM-T320) - and discovered (not known to me before purchase) it is Rooted.
When I went to do an Update via standard Settings>about Device - it refused returning tablet modified.
also it had the App SuperSU (free) installed) which asked about permission on a couple of Apps I used.
I have absolutely no experience of Rooted tablets,
and currently have no idea how the tablet was rooted, and what with.
So I am seeking your patience and some advice about this, please.
Is there a way to return to the Stock installation?
If so, how to I check that this is possible?
Or should I keep the Root?
If so, how do I update the tablet?
eg: how do I check what, or if any, custom ROM has been installed?
or
which custom ROM do people advise I install?
Thanks for any advice.
Vincent

Just back up your valuable data and storage contents and flash stock via Odin. And I believe at this time point the updates are not of much importance, so if you're on KitKat you might as well ignore that if you can't spare time for backups.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

AndyYan said:
Just back up your valuable data and storage contents and flash stock via Odin. And I believe at this time point the updates are not of much importance, so if you're on KitKat you might as well ignore that if you can't spare time for backups.
Thanks for the reply.
Funny that was starting to be my take too.
Either leave it rooted as is - since it really is just KitKat 4.4.2 - but with more ability.
Or later when the spirit moves perhaps upgrade via a custom rom.
Thank you.
Vincent
Click to expand...
Click to collapse
Click to expand...
Click to collapse

@vincent. I have the same tablet as you and I prefer to run the latest OS which is Marshmallow. As you state you are already rooted so you might as well try out a custom ROM. I recommend Resurrection Remix ROM by Vasumit and the XDA thread can be found here. Latest update to ROM is here. You will also need to install gapps. I recommend Banks Dynamic Gapps 6.X.X found here. Give it a try, I'm sure you will like it. ROM is buttery smooth and Vasumit updates it often. :good::good:

DowntownRDB said:
@vincent. I have the same tablet as you and I prefer to run the latest OS which is Marshmallow. As you state you are already rooted so you might as well try out a custom ROM. I recommend Resurrection Remix ROM by Vasumit and the XDA thread can be found here. Latest update to ROM is here. You will also need to install gapps. I recommend Banks Dynamic Gapps 6.X.X found here. Give it a try, I'm sure you will like it. ROM is buttery smooth and Vasumit updates it often. :good::good:
Click to expand...
Click to collapse
DowntownRDB
Thank you so much for your encouragement and suggestion.
Even though I have used Android on tablets and phones for years -
I am still a n00b when it comes to Root and Custom ROMs
I have heard of the more famous ROMs like CyanogenMod etc -
what makes Resurrection Remix ROM by Vasumit better than CyanogenMod
in terms of features and/or support please?
How easy (or not) are custom ROMs to undo?
Many thanks,

UnknownVT said:
I have heard of the more famous ROMs like CyanogenMod etc -
what makes Resurrection Remix ROM by Vasumit better than CyanogenMod
in terms of features and/or support please?
Click to expand...
Click to collapse
Personal opinion below: most AOSP-based ROMs have equal or slightly better support than CM because the team behind them is much smaller, but they might die out one day because of the same reason. CM maintains a huge number of devices and is the basis of many, so it's not likely to disappear soon. Also, CM is usually among the quickest to get to a new Android version while others usually sync from CM and start from there.
As of features, others are guaranteed to have more than CM. CM doesn't like adding features these days.
How easy (or not) are custom ROMs to undo?
Click to expand...
Click to collapse
Do: Flash TWRP, make a full backup of your stock ROM, full wipe and flash the new one.
Undo: Full wipe and restore the old backup, or if you decide you don't want your data, use Odin.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

AndyYan said:
Personal opinion below: most AOSP-based ROMs have equal or slightly better support than CM because the team behind them is much smaller, but they might die out one day because of the same reason. CM maintains a huge number of devices and is the basis of many, so it's not likely to disappear soon. Also, CM is usually among the quickest to get to a new Android version while others usually sync from CM and start from there.
As of features, others are guaranteed to have more than CM. CM doesn't like adding features these days.
Do: Flash TWRP, make a full backup of your stock ROM, full wipe and flash the new one.
Undo: Full wipe and restore the old backup, or if you decide you don't want your data, use Odin.
Click to expand...
Click to collapse
Thank you very much for the very helpful reply -
this was about as good as I was hoping for -
really appreciate all the help I am getting here, thank you.
It will take a bit of time for me to get my head around the information - as it is all new to me -
and I want to proceed with care/caution so I don't end up bricking my tablet.
Gratefully and thanks,

UnknownVT said:
Thank you very much for the very helpful reply -
this was about as good as I was hoping for -
really appreciate all the help I am getting here, thank you.
It will take a bit of time for me to get my head around the information - as it is all new to me -
and I want to proceed with care/caution so I don't end up bricking my tablet.
Gratefully and thanks,
Click to expand...
Click to collapse
Hey!
you could look at it this way, most of the people here have a hard time just ulocking the device and rooting it, not that yours is already done, might as well right. along with the proper research, your device could be one hundred times better, the stock OS of the tablet isn't that good (lets face it.) and with the current technology, it will have a hard time keeping up because the OS for this device is not that efficient (personal opinion). Anyways, it's still up to you to do it or not. Cyanogenmod has released the nightly version of Marshmallow 6.0 for this device. maybe you could check it out!! ^_^

kurogane_tw said:
Hey!
you could look at it this way, most of the people here have a hard time just ulocking the device and rooting it, not that yours is already done, might as well right. along with the proper research, your device could be one hundred times better, the stock OS of the tablet isn't that good (lets face it.) and with the current technology, it will have a hard time keeping up because the OS for this device is not that efficient (personal opinion). Anyways, it's still up to you to do it or not. Cyanogenmod has released the nightly version of Marshmallow 6.0 for this device. maybe you could check it out!! ^_^
Click to expand...
Click to collapse
Yes, thanks for the encouragement.
Seems ironic that I had done lots of look-sees (not quite research, but close) about rooting devices - and I actually now have one
(it was just unexpected on this Samsung Galaxy Tab Pro 8.4 (SM-T320)).
As you see I've decided to keep it rooted and am actively looking at which ROM to flash -
currently I am leaning toward the more conservative approach of doing the CM (CyanogenMod)
and rather than deciding between the snapshot CM-12.1 or the nightly CM-13.0....
perhaps I should just wait for a snapshot CM-13.0
(" and we’ll have a quality approved SNAPSHOT for CM13 sometime Jan." of course it is now Feb - so maybe soon?)
Thanks,

UnknownVT said:
perhaps I should just wait for a snapshot CM-13.0
(" and we’ll have a quality approved SNAPSHOT for CM13 sometime Jan." of course it is now Feb - so maybe soon?)
Click to expand...
Click to collapse
Don't wait for snapshots - they are just forked from nightlies at a certain timepoint and aren't more stable than nightlies. Just backup and flash a nightly, and if anything you feel unstable, restore the backup and/or wait for that to get resolved. I personally don't see anything disturbing aside from wonky external SD support (which is a universal bug across all 6.0+ ROMs).
P.S. The "Thanks" button is there - use it
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

AndyYan said:
Don't wait for snapshots - they are just forked from nightlies at a certain timepoint and aren't more stable than nightlies. Just backup and flash a nightly, and if anything you feel unstable, restore the backup and/or wait for that to get resolved. I personally don't see anything disturbing aside from wonky external SD support (which is a universal bug across all 6.0+ ROMs).
Click to expand...
Click to collapse
Thanks again, and thanks for pointing out the ext SD card issue with 6.0+ ROMs
Does this work?
How to Use SD Card as Internal Storage on Marshmallow ...
Thanks.

UnknownVT said:
Thanks again, and thanks for pointing out the ext SD card issue with 6.0+ ROMs
Does this work?
How to Use SD Card as Internal Storage on Marshmallow ...
Thanks.
Click to expand...
Click to collapse
The issue is mainly with how to use SD card as external storage (as on older Android versions), not with the new "adoptable storage" feature. That we don't have a definitive solution yet.
You might want to read through the last pages of the CM13 discussion thread in Development subforum if you're determined to get it working.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

[q] [official howto] complete guide to root & unlock bootloader for verizon note 4

[q] [official howto] complete guide to root & unlock bootloader for verizon note 4
Gents,
As the title says: This is EXACTLY what I'm looking for. The thing is that after looking and searching throughout this XDA section, here's what I've found:
http://forum.xda-developers.com/note-4-verizon/general/noob-how-unroot-phone-t3418431
http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
I would normally have no problem diving in head first into any of these threads. The issue is that even as I begin to read them, in each of these threads there's a handful of individuals claiming something like: 'Oh, you left this step out' or 'You forgot to include' this, or 'This only applies to this, but not that' and so forth.
I'm not really knew to the world of modding, rooting, theming, unlocking and so forth...but it does scare me a bit when there's so much information that seems to contradict other information or at the very least appears to be incomplete.
If possible, can someone with a solid understanding of the Verizon Note 4 and all things Permanent Root/BootLoader Unlock/Custom Recovery/Custom ROM installation please shed some light and provide some guidance for me on this thread?
I'm sure it would benefit many.
Just trying to get this Note 4 permanently rooted, with a kick-ass recovery...a snappy kernal and an awesome custom rom for my daily driver...all without bricking the poor guy.
Not sure how much it matters, however Just FYI here is some specifics on my particular Verizon Note 4:
Model Number: SM-N910V
Android Version: 5.0.1
Hardware Version: N910V.06
Please advise if possible.
Thank you,
BJ

You got here late............................
You need a History lesson. but I don't have time to give it to you. This thing has evolved. All the threads you mentioned have contributed to the testing and understanding.
Some of the OP in some of the threads have changed and no longer list the ROM's that first came out for Newly rooted Verizon Note 4. ( I wish they would bring back the custom 5.1.1 ROM's but they have moved on to Marshmallow )
I can tell you this. The first time you permanently root your phone, it should be on stock 5.1.1.
I created a thread mostly for my own use here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527
My thread can get you to a rooted stock Note 4 on stock 5.1.1 but my thread was not created for a newbie. You need a basic understanding of what you are doing.

doctor-cool said:
I wish they would bring back the custom 5.1.1 ROM's but they have moved on to Marshmallow.
Click to expand...
Click to collapse
You said it all right there!
I have tried several Marshmallow ROMs and I always come back to 5.11. In my opinion it is just a better operating system!
All of my apps are able to write to the SD card with no issues and that is important to me.

doctor-cool said:
You need a History lesson. but I don't have time to give it to you. This thing has evolved. All the threads you mentioned have contributed to the testing and understanding.
Some of the OP in some of the threads have changed and no longer list the ROM's that first came out for Newly rooted Verizon Note 4. ( I wish they would bring back the custom 5.1.1 ROM's but they have moved on to Marshmallow )
I can tell you this. The first time you permanently root your phone, it should be on stock 5.1.1.
I created a thread mostly for my own use here http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527
My thread can get you to a rooted stock Note 4 on stock 5.1.1 but my thread was not created for a newbie. You need a basic understanding of what you are doing.
Click to expand...
Click to collapse
Is it possible to get permanent root on the Verizon Note 4 coming from Stock 6.0.1 ? If not, is there a downgrade procedure, coupled with a perm root guide?
Thx.
BJ.

Team,
So after some more searching...it looks like this may be what I'm looking for:
http://forum.xda-developers.com/note-4-verizon/general/guide-step-step-stock-n910v-6-0-1-to-t3426905
So, here's the last question (I know, I know)...but BESIDES CM13...are there any other recommended ROMS for Verizon Note 4 on Marshmallow?
Thx.
BJ

Has anyone done a stability/basic functionality comparison of ROMs ?

I have been hanging around XDA for past 1 week or so, and have spent numerous hours in understanding Android/rooting/ROMs etc. As a software engineer, i had the basic background, to catch up on Android platform, which is new to me. Having covered everything here from "Intro to XDA/beginners" to Phone specific details, here is some questions, as i tread carefully into Android tinkering.
I have held onto an aging Tmobile S4, trying to avoid buying a new phone. Still running stock m919uvsfqa1 baseband (OTA early 2017). This was ok, since I do not play games / stream video / run social media apps etc. After 4 years of running acceptably, this phone started misbehaving in 2017. No hardware or software changes other than the factory reset to wipe data/cache (in last few days). Restored all apps/data, using Samsung smartswitch (I will write a guide on this later, as a thank you & give back, to XDA community). Phone seems to be revived after this factor reset/restore. I have 3 questions :
If i am only interested in stability / integrity / functionality in phone, should i stick to stock kitkat 4.4.4 (OR) should i risk it and upgrade to Oreo based LineageOS 15.1 (which i found on xda as End-of-Life) ?? (OR) any other custom rom recommendations (like marshmallow SlimRom) ? In my limited knowledge in reading various threads on XDA, i find only these two roms mentioned for stability.
In any case, i am considering rooting with CF-Auto-root, to get SuperSU and remove bloat/ads...... Perhaps i can install antivirus apps, since i won't be running the latest security patches available in Oreo (if i run older versions of custom ROM). Would you advise this for a Software engineer, who is newbie to Android ? (OR) simply play it safe and stick to the bloatware/stock ? (Note: I have already gone through guides on "what apps to install after rooting".)
CF-auto-root will stick to stock recovery. Is there any benefit for me in installing TWRP ?

Any way to try out LOS without installing it on a phone ?

Hi
I have a Honor 5X (kiwi / KIW-L21) as my daily driver and as its nearing the end of it warranty (2 years) its starting to run slower (good job, Huawei). Given this and the fact that during these two years i never received ANY update apart from an update to android 6.0.1 from android 5, im considering switching to LOS 16.
The thing is im completely new to custom ROMs, recovery, phone rooting and that jazz and im a bit scared.
I wanted to know if there is a way I can try out LOS 16 (say for example on a VM) to be sure that i like it before installing.
If not, would I be able to restore my phone back to its current OS in case i dont like LOS and want to fall back to EMUI ?
PS : I wanted to try it out on an older phone I have and for which i dont care as much, but its not supported :'( Its an Asus Zenfone go ZB552KL
Thanks in advance !

The oldphone approach is a good idea. Go to a recycling place and grab some old Motorola or Samsung phones. Broken screen is OK.

kurtn said:
The oldphone approach is a good idea. Go to a recycling place and grab some old Motorola or Samsung phones. Broken screen is OK.
Click to expand...
Click to collapse
My local trash collecting place isn't very open to people who want to take stuff (yes, what a nonesense) but i'll try that i guess. The thing is we have like 3 or 4 old phones but none of them are listed as compatible on the LOS website

IamGron. said:
My local trash collecting place isn't very open to people who want to take stuff (yes, what a nonesense) but i'll try that i guess. The thing is we have like 3 or 4 old phones but none of them are listed as compatible on the LOS website
Click to expand...
Click to collapse
You don't need official. Search XDA and you will find unofficial lineageOS for many old phones. https://twrp.me/Devices/ is a good place to find the phone's code name. With that you can check stats.lineageos.org for popular ROM versions.

Will give it a look, thanks.
If nothing usefull comes out of this investigation and I end up doing it on my 5X, is there a way for me to backup the whole phone (i mean not just data, like the whole OS) that way I can fall back to its current state if something goes wrong / i dont like LOS ?

IamGron. said:
Will give it a look, thanks..........
Click to expand...
Click to collapse
To be honest, there's various ways for backing up a whole device but, there's limited (possibly no) choices that all depends upon the device itself and the capabilities of said device. So there's no real way of answering this question without, also, taking under consideration that what works for one may/may not work for another.
With that stated...
I've always found that the only way to know if I like something as huge as updating the Custom Android version Firmware, is to "Hope for the Best and Prepare for the Worse".
I've been successful with Restoring TWRP Backups made but, have always had an (approximately) 50% +/- of a restoration working without any issues (a chance of requiring a fresh installation in the end).
In another words...
The only "recommended" way to upgrade/downgrade the LineageOS Android Versions is to make sure you have everything on hand for performing a fresh installation for both the upgrading and the downgrading of both Android Versions.
For anyone to guide you any other way should (ethically) be able to provide you with guidance in case something goes wrong in the process (of said guidance) with your specific device.
You should also ask for support and guidance within the LineageOS thread and, if needed, somewhere within the Device Dedicated Area of the forum that's specific to your device. This will help locate assistance from those who has your device as well.
For example...
[ROM][9.0.x] LineageOS 16.0 Official (kiwi) [NO VoLTE] by BadDaemon
[ROM] [9.x] LineageOS 16.0 Pie Unofficial for Honor 5x (kiwi) by coldhans
https://forum.xda-developers.com/honor-5x
I hope that I had explained this okay via text... :thumbup:
I wish you the best of luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.

Ibuprophen said:
To be honest, there's various ways for backing up a whole device but, there's limited (possibly no) choices that all depends upon the device itself and the capabilities of said device. So there's no real way of answering this question without, also, taking under consideration that what works for one may/may not work for another.
With that stated...
I've always found that the only way to know if I like something as huge as updating the Custom Android version Firmware, is to "Hope for the Best and Prepare for the Worse".
I've been successful with Restoring TWRP Backups made but, have always had an (approximately) 50% +/- of a restoration working without any issues (a chance of requiring a fresh installation in the end).
In another words...
The only "recommended" way to upgrade/downgrade the LineageOS Android Versions is to make sure you have everything on hand for performing a fresh installation for both the upgrading and the downgrading of both Android Versions.
For anyone to guide you any other way should (ethically) be able to provide you with guidance in case something goes wrong in the process (of said guidance) with your specific device.
You should also ask for support and guidance within the LineageOS thread and, if needed, somewhere within the Device Dedicated Area of the forum that's specific to your device. This will help locate assistance from those who has your device as well.
[...]
Click to expand...
Click to collapse
Hi there, thanks for the answer and sorry for the delayed reaction, I was busy
I will investigate on the linked threads and see what I want to do after that. My main concern being fingerprint sensor gestures (I know, stupid habits lol) asking on the kiwi forum is definitely a good idea. Same things for installing TWRP and the recovery, someone there would probably be able to help.
Thanks a lot for your time