Where to find stock recovery images for the Nexus 5? - Nexus 5 Q&A, Help & Troubleshooting

Hi xda community.
Maybe I'm blind, but I can't find stock recovery images for the LG Google Nexus 5. I run all my devices rooted, with unlocked bootloader, TWRP and Cyanogenmod 13. However, due to security concerns I would like to flash a stock recovery again and lock the bootloader.
However, I can not really find first-hand stock recovery images. Searching yields only unsigned third party downloads like this one. No way I'm going to flash this.
The official Google developer factory images only contain a bootloader image and a radio (?) image and the hammerhead stock ROM zip archive. But what I'm looking for is the recovery image!
Any idea where to get them first hand and singed or at least check-summed? Thanks!

Ok for some reasons, the factory image contains all images in the zip, including a recovery zip.
However, flashing that renders recovery unusable - little android with a red sign. I don't really worry (yet), but what would be the cause for that?
Is there any issue to run Cyanogenmod with a stock recovery? Should I prefer the CM recovery instead? Is the CM recovery as secure as the stock recovery?

The Android logo with a red exclamation is the stock recovery (recovery.img in the factory images) with its basic features.
You should be able to run CM13 with a stock recovery but locking the bootloader seems enough IMO. Actually I keep it unlocked because it could be my last chance to recover my device without loosing all my data.

Hi, not sure if you still need this but if you check page 1 of this XDA thread under "Nexus 5 Specials", you can find all of the stock bootloaders, radios, recovery, stock/ custom ROMs and stuff like that.
I've flashed a lot from this guys thread and I know the stuff there is legit and reliable. You're right though, only flash what you trust from a Official source.
You should be able to find what you need on that thread, good luck whatever route you choose.
Link to thread: (Page 1: Nexus 5 Specials.)
http://forum.xda-developers.com/goo...gle-nexus-5-roms-kernels-mods-t2475401/page50

Primokorn said:
The Android logo with a red exclamation is the stock recovery (recovery.img in the factory images) with its basic features.
You should be able to run CM13 with a stock recovery but locking the bootloader seems enough IMO. Actually I keep it unlocked because it could be my last chance to recover my device without loosing all my data.
Click to expand...
Click to collapse
Ah, okay. It shows only the logo, no menu or something. Does that sound correct?
The issue with keeping it unlocked is basicly that anyone can recover my device. I use backup synchronization from within android and when the devices fails, I can simply whipe it and start fresh because I have all data synched to my computer (using syncthing).
Rooted Droid said:
Hi, not sure if you still need this but if you check page 1 of this XDA thread under "Nexus 5 Specials", you can find all of the stock bootloaders, radios, recovery, stock/ custom ROMs and stuff like that.
I've flashed a lot from this guys thread and I know the stuff there is legit and reliable. You're right though, only flash what you trust from a Official source.
You should be able to find what you need on that thread, good luck whatever route you choose.
Link to thread: (Page 1: Nexus 5 Specials.)
http://forum.xda-developers.com/goo...gle-nexus-5-roms-kernels-mods-t2475401/page50
Click to expand...
Click to collapse
Thanks, will look into that one.

5chdn said:
Ah, okay. It shows only the logo, no menu or something. Does that sound correct?
The issue with keeping it unlocked is basicly that anyone can recover my device. I use backup synchronization from within android and when the devices fails, I can simply whipe it and start fresh because I have all data synched to my computer (using syncthing).
Click to expand...
Click to collapse
Stock recovery offers basic features: reboot, wipe cache, factory reset...
This is the bootloader.
You have a rooted phone so anyone can install BootUnlocker app to unlock the bootloader without wiping anything.

Primokorn said:
Stock recovery offers basic features: reboot, wipe cache, factory reset.
Click to expand...
Click to collapse
Yeah, I don't have that, it looks like this issue: https://www.youtube.com/watch?v=yoJ_vRTRX7g However, the CM recovery works. Edit, after watching the video, I understand it's a non-issue
Primokorn said:
You have a rooted phone so anyone can install BootUnlocker app to unlock the bootloader without wiping anything.
Click to expand...
Click to collapse
Mind elaborating how _anyone_ can install an app on my phone? No custom recovery, no debugging enabled, bootloader locked, phone encrypted, pin set up. How to access my phone to install a bootunlocker?

5chdn said:
Mind elaborating how _anyone_ can install an app on my phone? No custom recovery, no debugging enabled, bootloader locked, phone encrypted, pin set up. How to access my phone to install a bootunlocker?
Click to expand...
Click to collapse
"Anyone" is excessive for an encypted phone of course
Using a long password was enough to hack Android phones having Lollipop; hacking a 4 digits password can get cracked in minutes with a computer; thanks to the software FROST, security researchers extracted photos, web history and contact lists from locked & encrypted Android phones,...
Anyways, Android is not a secure OS and I never trust those security tools. I don't store precious information on my device and I'm safe from day one lol

Related

[I9020A] Nexus S, Master Clear?

Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do
Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)
Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that

Going to root, am I doing it right?

I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.

[Q] So I got the OnePlus One. What next?

I was using an iphones for 3 years and learnt all about jailbreaking and unlocking and then I made a switch to android in 2013. I got myself a nexus 4 and stock android was good enough for me and I used my nexus 4 till it gave up very recently. With the nexus 4 I never really cared about rooting the phone for whatever reasons and now with the Oneplus I am very interested to start customizing it. The only problem is my knowledge on rooting phones, flashing, custom roms and kernels are 0. I don't even know what people mean by those things. Yes, a complete noob but I can learn pretty quickly and follow instructions well. So where do I start now?
Any help is appreciated.
First thing to do is unlock your bootloader, then install TWRP recovery, then make a backup of your stock ROM. From there you can root your stock ROM or you can flash a custom ROM, or you can just leave it as is. But the most important thing is to unlock your bootloader now, before you really start using the device because it wipes all user data during the unlock process. I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
I was like you a couple of months back. I'll tell you this, before you start anything make sure you do a back up. That's the most important thing. From there on you can do whatever your heart desires. As my friend above has stated unlock the boot loader, install a custom recovery and you're ready to go.unlocking the boot loader will allow you to install a custom recovery. You need the custom recovery to flash zip files such as ROMs and kernels etc. I hope this helped !
Sent from my iPad using Tapatalk
Thank you guys! That helped.
timmaaa said:
First thing to do is unlock your bootloader, then install TWRP recovery, then make a backup of your stock ROM. From there you can root your stock ROM or you can flash a custom ROM, or you can just leave it as is. But the most important thing is to unlock your bootloader now, before you really start using the device because it wipes all user data during the unlock process. I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
So I did as it said on the video by xda developers. I did everything and the phone seems to be working fine except for the fact that it isn't rooted properly. I download ROM Toolbox and it gave me a warning message saying no root access found. Then I downloaded Root Checker from playstore and verified my root and it says my phone hasn't been rooted properly.
I manually rooted my phone by using TWRP custom recovery + SuperSU.
Edit: Did a clean up within SuperSU & installed it again using google play and now it works properly. The only thing that was different this time I was prompted to install the binries which I wasn't asked to when I used TWRP to install SuperSu.
[Q] So I got the OnePlus One. What next?
Click to expand...
Click to collapse
Enjoy it It's a great phone, take it easy read, read and read again BEFORE doing anything. Make sure you have the right files for the right phone. Always do a backup before doing any changes.

Difference between the two??

Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.
Vikings09876 said:
Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.
Click to expand...
Click to collapse
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?
Vikings09876 said:
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?
Click to expand...
Click to collapse
You'll have to flash a copy of your stock recovery or your stock firmware, if you can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You'll have to flash a copy of your stock recovery or your stock firmware, if up can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm just gonna leave it as is rn because the phone works tbh, I just don't have a working recovery. The stock ROM doesn't seem to be available atm as the phone was just recently released. I'm sure it will be released at some point, and I'm not too worried about it. If anything, I can just pay it off and upgrade to a different phone.
Use crom apk by Samsung to unlock your bootloader.....till the files come out that's as far as me or ne of us r getting
Update twrps have been tried to compile with no success till Ashyx (our luck to have his services) recieves the kernel source
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
There is a rooted boot.img that ill be testing since i havbe access to exclusive stock firmware and have recourse should ne th ing be wrong....ie a brick.
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
Kindly redirect to this thread

LineageOS 14.1 on Nokia 3?

Dear folks,
first of all let me thank you for all the good work in here.
I’m quiet used to ADB, fastboot, unlocked bootloaders, TWRP, Custom Roms etc since I've been routing my HTCs for couple years by now.
The other day a friend of mine, owner of a Nokia 3, asked me, if I could possibly “ungoogle” his phone. My idea was it to clean-install LineageOS, since it comes without GApps in first place.
That being said I found some instructions on the internet how to do it – not here at xda though.
I. What I did at first:
I unlocked the bootloader, getting the “orange state”-warning.
I flashed TWRP, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Then I thought I had to relock the bootloader, so that’s what I did and I got the “red state”-error. :angel:
So I ended up flashing original FW with OST. :good:
Ever since that, the bootloader had that “orange state”-warning, no matter what I tried. It is unlocked already. Even flashing the stock boot I found in here gave me that warning. Relocking bootloader fails. But I learned, that “orange state” is still OK. Is that true?
II. What I did next:
I considered if the bootloader is not the problem, maybe recovery is.
So from fastboot I booted TWRP.img, leaving the original recovery untouched, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
III. What I did next:
I considered that recovery CAN’T be the problem, since it was untouched. Is that true?
So it had to be the bootloader.
I booted original FW, installed Magisk Manager, created a patched boot.
The I booted into TWRP, removed encryption, installed LineageOS, flashed the patched boot.
Result: Nothing - device wouldn’t boot.
Now here it could be the point that my “stock boot” could have been broken in first place already, since it had the “orange state” ever since (see I.) Could this be the problem? If yes, how could I overcome this issue? Flashing the stock boot from xda didn’t help (see also I.) Since I didn’t really know what the problem was I ended up flashing original FW with OST.
IV. What I did next:
I flashed TWRP with SP Flash (Thanks for the wonderful guide @SkaboXD) to keep my locked/untouched/whatever bootloader (again: bootloader here isn’t locked anymore, no chance for me to relock it).
Then I booted into TWRP, removed encryption, installed LineageOS.
Result: Nothing - device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
Tu sum it up:
I am kind of proud to have reached one and the same goal over many different ways now
But I’ve spent hours of reading through the threads here and trying to find my way and nothing worked. I have never experienced problem like those with my HTCs and could need some serious help now, please.:fingers-crossed:
Q1: Is it even possible install LineageOS on a Nokia 3? That’s what I considered lately.
If yes: How? What am I doing wrong?
If no: What other options do I have to “ungoogle” the device? Root and manually remove all apps? I’m afraid, I won’t find all and that google is hidden somewhere else as well.
Thank you in advance!
wutzkman said:
Dear folks,
first of all let me thank you for all the good work in here.
I’m quiet used to ADB, fastboot, unlocked bootloaders, TWRP, Custom Roms etc since I've been routing my HTCs for couple years by now.
The other day a friend of mine, owner of a Nokia 3, asked me, if I could possibly “ungoogle” his phone. My idea was it to clean-install LineageOS, since it comes without GApps in first place.
That being said I found some instructions on the internet how to do it – not here at xda though.
I. What I did at first:
I unlocked the bootloader, getting the “orange state”-warning.
I flashed TWRP, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Then I thought I had to relock the bootloader, so that’s what I did and I got the “red state”-error. :angel:
So I ended up flashing original FW with OST. :good:
Ever since that, the bootloader had that “orange state”-warning, no matter what I tried. It is unlocked already. Even flashing the stock boot I found in here gave me that warning. Relocking bootloader fails. But I learned, that “orange state” is still OK. Is that true?
II. What I did next:
I considered if the bootloader is not the problem, maybe recovery is.
So from fastboot I booted TWRP.img, leaving the original recovery untouched, removed encryption and installed LineageOS.
Result: Nothing – device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
III. What I did next:
I considered that recovery CAN’T be the problem, since it was untouched. Is that true?
So it had to be the bootloader.
I booted original FW, installed Magisk Manager, created a patched boot.
The I booted into TWRP, removed encryption, installed LineageOS, flashed the patched boot.
Result: Nothing - device wouldn’t boot.
Now here it could be the point that my “stock boot” could have been broken in first place already, since it had the “orange state” ever since (see I.) Could this be the problem? If yes, how could I overcome this issue? Flashing the stock boot from xda didn’t help (see also I.) Since I didn’t really know what the problem was I ended up flashing original FW with OST.
IV. What I did next:
I flashed TWRP with SP Flash (Thanks for the wonderful guide @SkaboXD) to keep my locked/untouched/whatever bootloader (again: bootloader here isn’t locked anymore, no chance for me to relock it).
Then I booted into TWRP, removed encryption, installed LineageOS.
Result: Nothing - device wouldn’t boot.
Since I didn’t really know what the problem was I ended up flashing original FW with OST.
Tu sum it up:
I am kind of proud to have reached one and the same goal over many different ways now
But I’ve spent hours of reading through the threads here and trying to find my way and nothing worked. I have never experienced problem like those with my HTCs and could need some serious help now, please.:fingers-crossed:
Q1: Is it even possible install LineageOS on a Nokia 3? That’s what I considered lately.
If yes: How? What am I doing wrong?
If no: What other options do I have to “ungoogle” the device? Root and manually remove all apps? I’m afraid, I won’t find all and that google is hidden somewhere else as well.
Thank you in advance!
Click to expand...
Click to collapse
no it's not possible currently, that ROM doesn't work. The only way is to manually remove apps. You have my thread about manually removing apps here: https://forum.xda-developers.com/nokia-3/how-to/guide-how-apps-uninstall-t3804425
he can also remove google keyboard if he don't like it, but first install 2nd keyboard then remove Gboard. Location: /system/app/LatinIME
Google Play Store: /system/priv-app/Phonesky
Google Play Services: /system/priv-app/GmsCore
There are also more Google stuff that i am not sure is it good to remove.
If i find a way to remove Google apps completely i will tell you. When i get Nokia 3 again, I will maybe make stock based ROM with debloated apps, build.prop tweaks (that actually work), volume steps mode (without Xposed and build.prop), advanced reboot option (not sure on this one), Vanced YouTube, odexed and many more...
Stay tuned.
SkaboXD said:
no it's not possible currently, that ROM doesn't work. The only way is to manually remove apps. You have my thread about manually removing apps here: https://forum.xda-developers.com/nokia-3/how-to/guide-how-apps-uninstall-t3804425
he can also remove google keyboard if he don't like it, but first install 2nd keyboard then remove Gboard. Location: /system/app/LatinIME
Google Play Store: /system/priv-app/Phonesky
Google Play Services: /system/priv-app/GmsCore
There are also more Google stuff that i am not sure is it good to remove.
If i find a way to remove Google apps completely i will tell you. When i get Nokia 3 again, I will maybe make stock based ROM with debloated apps, build.prop tweaks (that actually work), volume steps mode (without Xposed and build.prop), advanced reboot option (not sure on this one), Vanced YouTube, odexed and many more...
Stay tuned.
Click to expand...
Click to collapse
Ok, then I wonder, why someone put instructions for the installation on the internet. What's wrong with people nowadays?
Anyways, thank you very much! At least I know, that I can stop my efforts at this point and it wasn't me being stupid :good:
I will stick to your guide. Does it matter, which version I use? 7.1.1? 8.0? 8.1? My plan now is to update to 8.1 since it comes with the highest security patches and then dig through the whole process of ungoogling the device.
Last one so far: Any idea how to get rid of that orange warning in the bootloader? It's not that big of a deal, but if there is a chance to get rid of it I'd be happy.
Your future plans for the Nokia 3 sound pretty awesome. Let me know when you're done - no pressure here.
wutzkman said:
Ok, then I wonder, why someone put instructions for the installation on the internet. What's wrong with people nowadays?
Anyways, thank you very much! At least I know, that I can stop my efforts at this point and it wasn't me being stupid :good:
I will stick to your guide. Does it matter, which version I use? 7.1.1? 8.0? 8.1? My plan now is to update to 8.1 since it comes with the highest security patches and then dig through the whole process of ungoogling the device.
Last one so far: Any idea how to get rid of that orange warning in the bootloader? It's not that big of a deal, but if there is a chance to get rid of it I'd be happy.
Your future plans for the Nokia 3 sound pretty awesome. Let me know when you're done - no pressure here.
Click to expand...
Click to collapse
Yeah, i encountered this too when there was no bootloader unlock guides on xda, all were fake, that's why i first check xda before doing anything.
No it doesn't matter, i used Android 7.1.1 December 2017 Security Patch before i gave it to my brother.
No idea, i think we need to modify some partition like aboot and include some changes but not sure currently.
Tnx for support, i will open a thread where we can discuss about changes you want to see in stock modified rom and advices what else i can do.
SkaboXD said:
no it's not possible currently, that ROM doesn't work. The only way is to manually remove apps. You have my thread about manually removing apps here: https://forum.xda-developers.com/nokia-3/how-to/guide-how-apps-uninstall-t3804425
he can also remove google keyboard if he don't like it, but first install 2nd keyboard then remove Gboard. Location: /system/app/LatinIME
Google Play Store: /system/priv-app/Phonesky
Google Play Services: /system/priv-app/GmsCore
There are also more Google stuff that i am not sure is it good to remove.
If i find a way to remove Google apps completely i will tell you. When i get Nokia 3 again, I will maybe make stock based ROM with debloated apps, build.prop tweaks (that actually work), volume steps mode (without Xposed and build.prop), advanced reboot option (not sure on this one), Vanced YouTube, odexed and many more...
Stay tuned.
Click to expand...
Click to collapse
better Build a rom based on oreo GO coz mt6737 is completely supported
tech2update said:
better Build a rom based on oreo GO coz mt6737 is completely supported
Click to expand...
Click to collapse
not sure if i can, low ram property patch doesn't work when i tested last time, but i will check it again.
SkaboXD said:
Yeah, i encountered this too when there was no bootloader unlock guides on xda, all were fake, that's why i first check xda before doing anything.
No it doesn't matter, i used Android 7.1.1 December 2017 Security Patch before i gave it to my brother.
No idea, i think we need to modify some partition like aboot and include some changes but not sure currently.
Tnx for support, i will open a thread where we can discuss about changes you want to see in stock modified rom and advices what else i can do.
Click to expand...
Click to collapse
Hi @SkaboXD,
to me it seems you have the most knowledge about rooting a Nokia 3 and always give solide answers, so I'd like to ask you directly.
After quite a while now I finally found the delight to spend more time with my friend's Nokia again. I flashed TWRP "successfully" but for whatever reason the phone won't load it. It also doesn't matter which TWRP-version I try. Not even booting directly into TWRP via fastboot boot xxx.img works. Every time I try it starts up stock 8.1. rom.
Any idea why this could be? What should I do? Reflashing the thing with OST again?
I tried that already^^ but when I started my OST-Tool it asked me for some weird login-data? It has never done that before.
Furthermore, once I get over that point, I plan to root it with SU, since I want to have a regular root, not a systemless one. Is there anything special to consider? Or will it be just the regular way
Install/Boot TWRP --> flash SU.zip --> boot device --> boom, you're done?
Sorry for the bother and thank you in advance!
wutzkman said:
Hi @SkaboXD,
to me it seems you have the most knowledge about rooting a Nokia 3 and always give solide answers, so I'd like to ask you directly.
After quite a while now I finally found the delight to spend more time with my friend's Nokia again. I flashed TWRP "successfully" but for whatever reason the phone won't load it. It also doesn't matter which TWRP-version I try. Not even booting directly into TWRP via fastboot boot xxx.img works. Every time I try it starts up stock 8.1. rom.
Any idea why this could be? What should I do? Reflashing the thing with OST again?
I tried that already^^ but when I started my OST-Tool it asked me for some weird login-data? It has never done that before.
Furthermore, once I get over that point, I plan to root it with SU, since I want to have a regular root, not a systemless one. Is there anything special to consider? Or will it be just the regular way
Install/Boot TWRP --> flash SU.zip --> boot device --> boom, you're done?
Sorry for the bother and thank you in advance!
Click to expand...
Click to collapse
hmm, i think that our twrp is not compatible with 8.1 yet, the only method that could work is flashing Magisk (SuperSU won't work, it's depreciated) with my guide but I'm not sure does it work on 8.1, i didn't tested. It would be easier if i have phone, in this moment i can't help much.
SkaboXD said:
hmm, i think that our twrp is not compatible with 8.1 yet, the only method that could work is flashing Magisk (SuperSU won't work, it's depreciated) with my guide but I'm not sure does it work on 8.1, i didn't tested. It would be easier if i have phone, in this moment i can't help much.
Click to expand...
Click to collapse
Ok just in general then: I don't give much about the version to be honest. After I fix my OST, I can reflash to 7.1, that's fine.
My thoughts now: Once I'm back to 7.1, I will boot into TWRP, do the whole magisk-magic with patched bootloader and so on...
I) I only know magisk as a systemless root, meaning I cannot delete unwanted apps for example. Is there any chance to get rid of them anyways?
II) I learned when keeping the original recovery, system OTAs are still possible. Will they destroy root?
If yes, I truly need to root at the latest system version possible. Will 8.0 work with root? Or just 7.1?
wutzkman said:
Ok just in general then: I don't give much about the version to be honest. After I fix my OST, I can reflash to 7.1, that's fine.
My thoughts now: Once I'm back to 7.1, I will boot into TWRP, do the whole magisk-magic with patched bootloader and so on...
I) I only know magisk as a systemless root, meaning I cannot delete unwanted apps for example. Is there any chance to get rid of them anyways?
II) I learned when keeping the original recovery, system OTAs are still possible. Will they destroy root?
If yes, I truly need to root at the latest system version possible. Will 8.0 work with root? Or just 7.1?
Click to expand...
Click to collapse
1.yes you can with systemless root, maybe you got misinformed. In fact i deleted system apps with Magisk.
2.true, 8.0 work with root. OTA will destroy root but you can just flash it again.
wutzkman said:
Hi @SkaboXD,
to me it seems you have the most knowledge about rooting a Nokia 3 and always give solide answers, so I'd like to ask you directly.
After quite a while now I finally found the delight to spend more time with my friend's Nokia again. I flashed TWRP "successfully" but for whatever reason the phone won't load it. It also doesn't matter which TWRP-version I try. Not even booting directly into TWRP via fastboot boot xxx.img works. Every time I try it starts up stock 8.1. rom.
Any idea why this could be? What should I do? Reflashing the thing with OST again?
I tried that already^^ but when I started my OST-Tool it asked me for some weird login-data? It has never done that before.
Furthermore, once I get over that point, I plan to root it with SU, since I want to have a regular root, not a systemless one. Is there anything special to consider? Or will it be just the regular way
Install/Boot TWRP --> flash SU.zip --> boot device --> boom, you're done?
Sorry for the bother and thank you in advance!
Click to expand...
Click to collapse
Yeah, last time I tried booting twrp I had that same problem, device wouldn't enter recovery
fastboot reboot recovery wouldn't work, eventually I flashed the recovery partition and on reboot held down the power and volume down buttons while the phone was plugged to my laptop before it finally entered recovery
redweaver said:
Yeah, last time I tried booting twrp I had that same problem, device wouldn't enter recovery
fastboot reboot recovery wouldn't work, eventually I flashed the recovery partition and on reboot held down the power and volume down buttons while the phone was plugged to my laptop before it finally entered recovery
Click to expand...
Click to collapse
Did you flash recovery with SPFlash? Because I tried to flash it with fastboot, even before I tried to boot into it. Neither one worked out for me.
Which Android version are you at?
wutzkman said:
Did you flash recovery with SPFlash? Because I tried to flash it with fastboot, even before I tried to boot into it. Neither one worked out for me.
Which Android version are you at?
Click to expand...
Click to collapse
No I used fastboot. Oreo 8.1. I think something happens during that orange state message that keeps fastboot from booting into recovery.
One other thing you can try - though it's a long route is:
1. first back up boot and recovery partitions with spflash - very important else your phone might not boot again
2. after backing up the partitions, flash the boot partition either with spflash or fastboot then reboot. You should boot into recovery.
3. The only problem is that you would need to manually patch the boot.img if you want to flash magisk (normally flashing magisk patches the boot partition from recovey) then flash the boot partition with the modified boot.img otherwise your phone won't boot anymore
redweaver said:
No I used fastboot. Oreo 8.1. I think something happens during that orange state message that keeps fastboot from booting into recovery.
One other thing you can try - though it's a long route is:
1. first back up boot and recovery partitions with spflash - very important else your phone might not boot again
2. after backing up the partitions, flash the boot partition either with spflash or fastboot then reboot. You should boot into recovery.
3. The only problem is that you would need to manually patch the boot.img if you want to flash magisk (normally flashing magisk patches the boot partition from recovey) then flash the boot partition with the modified boot.img otherwise your phone won't boot anymore
Click to expand...
Click to collapse
I've wasted quite some time trying root 8.1 with magisk, but no matter what I did, I always ended up with a softbrick. So you got me hooked up here.
Just to make sure. I flashed FW NE1-215H-0-00WW-B02 (I believe) via OST. (Strange sideeffect here: After flashing the whole new FW with OST, the phone already knew my WiFi and already had Magisk installed, both still from my older installations. I wonder why this is and I have not found a way around it yet )
After the flashed with OST I had two system updates via OTA, so right now I am on Oreo 8.1 stock with security updates from Jan05 '19, in other words: the latest FW possible. What next? According to you:
1. I back up boot and recovery. You mean stock boot and stock recovery, right? I believe my boot is not stock anymore, since it already has that orange state warning. Any way around it? Flashing stock 7.1.1 boot didn'T do any better. Anyways, any other chance to back it up without SPFlash? I have no clue how to back up boot and recovery with SPFlash.
2. I need to flash boot? Not recovery? What should I flash boot with? And then I will have to boot into recovery, like TWRP for example? Any suggestions which one to take? Currently I want to use TWRP 3.2.1-0 by SkaboXD (https://mega.nz/#!qIhFkKia!AkUMvQJ0P...hlCNaZfy2gE4vE) And that is the point, that is not working for me. I cannot boot directly into it, nor can I boot it after flashing. What am I doing wrong?
3. I have to patch boot.img manually. But how can I patch it without having Magisk installed?
Thank you for your time!
wutzkman said:
I've wasted quite some time trying root 8.1 with magisk, but no matter what I did, I always ended up with a softbrick. So you got me hooked up here.
Just to make sure. I flashed FW NE1-215H-0-00WW-B02 (I believe) via OST. (Strange sideeffect here: After flashing the whole new FW with OST, the phone already knew my WiFi and already had Magisk installed, both still from my older installations. I wonder why this is and I have not found a way around it yet )
After the flashed with OST I had two system updates via OTA, so right now I am on Oreo 8.1 stock with security updates from Jan05 '19, in other words: the latest FW possible. What next? According to you:
1. I back up boot and recovery. You mean stock boot and stock recovery, right? I believe my boot is not stock anymore, since it already has that orange state warning. Any way around it? Flashing stock 7.1.1 boot didn'T do any better. Anyways, any other chance to back it up without SPFlash? I have no clue how to back up boot and recovery with SPFlash.
2. I need to flash boot? Not recovery? What should I flash boot with? And then I will have to boot into recovery, like TWRP for example? Any suggestions which one to take? Currently I want to use TWRP 3.2.1-0 by SkaboXD (https://mega.nz/#!qIhFkKia!AkUMvQJ0P...hlCNaZfy2gE4vE) And that is the point, that is not working for me. I cannot boot directly into it, nor can I boot it after flashing. What am I doing wrong?
3. I have to patch boot.img manually. But how can I patch it without having Magisk installed?
Thank you for your time!
Click to expand...
Click to collapse
Sorry for the delay in getting back to you.
1. Your boot and recovery are stock since its the system update that installs them
Orange state just means your bootloader had been tampered with, it has nothing to do with whether your boot or recovery images are stock
2. You flash the twrp image. Ideally you should flash recovery partition, but in this case flashing recovery isn't working for you. Basically your phone is refusing to boot into recovery. What this method does is force the phone to boot the twrp image
3. If you're not using magisk or su, may I ask why you want to enter recovery for in the first place?
As an aside I just realised that you can flash boot.img from twrp, so instead of manually patching the boot.img, just flash stock boot and then flash your SU or magisk or whatever it is that you want to flash from recovery
redweaver said:
Sorry for the delay in getting back to you.
1. Your boot and recovery are stock since its the system update that installs them
Orange state just means your bootloader had been tampered with, it has nothing to do with whether your boot or recovery images are stock
2. You flash the twrp image. Ideally you should flash recovery partition, but in this case flashing recovery isn't working for you. Basically your phone is refusing to boot into recovery. What this method does is force the phone to boot the twrp image
3. If you're not using magisk or su, may I ask why you want to enter recovery for in the first place?
As an aside I just realised that you can flash boot.img from twrp, so instead of manually patching the boot.img, just flash stock boot and then flash your SU or magisk or whatever it is that you want to flash from recovery
Click to expand...
Click to collapse
Don't worry too much about it. We all have more important stuff than rooting a Nokia 3 to do.
1. Thank you! I've just learned something new :highfive:
2. I flash TWRP to boot partition? I did not think of that, but from what you say it definitely makes sense. And now I see, why I need a backup of my 8.1 stock boot and recovery. Perhaps, I should find out how to backup with SPFlash by now :fingers-crossed: . Too bad, there is no stable Oreo-FW out there. :angel:
3. I actually want to "ungoogle" the phone and therefore, I indeed want to use magisk. But I need TWRP in some way to install it.
Once I have TWRP at boot partition and loaded it, can I flash boot from there? In other words, can boot partition overwrite itself? I doubt it. How about:
a) I create a patched_boot.img right now manually with Magisk Manager, but without installing magisk zip.
b) I use fastboot to flash TWRP to boot and load into it
c) I install Magisk from there and reboot to fastboot again
c) I use fastboot to flash patched_boot.img and reboot the whole thing.
That could do the trick in theory, couldn't it?
wutzkman said:
Don't worry too much about it. We all have more important stuff than rooting a Nokia 3 to do.
1. Thank you! I've just learned something new :highfive:
2. I flash TWRP to boot partition? I did not think of that, but from what you say it definitely makes sense. And now I see, why I need a backup of my 8.1 stock boot and recovery. Perhaps, I should find out how to backup with SPFlash by now :fingers-crossed: . Too bad, there is no stable Oreo-FW out there. :angel:
3. I actually want to "ungoogle" the phone and therefore, I indeed want to use magisk. But I need TWRP in some way to install it.
Once I have TWRP at boot partition and loaded it, can I flash boot from there? In other words, can boot partition overwrite itself? I doubt it. How about:
a) I create a patched_boot.img right now manually with Magisk Manager, but without installing magisk zip.
b) I use fastboot to flash TWRP to boot and load into it
c) I install Magisk from there and reboot to fastboot again
c) I use fastboot to flash patched_boot.img and reboot the whole thing.
That could do the trick in theory, couldn't it?
Click to expand...
Click to collapse
I figured the flashing to boot partition one time when my phone kept booting into recovery after a failed ota update. I checked the install script and found out that at one point the boot partition is flashed with the recovery image
You definitely need to backup your boot image unless you want to risk not being able to boot your phone anymore
Flashing boot should be possible, after all even when you boot into twrp you can flash another recovery, in fact when you do a twrp restore especially one that has a recovery backup, you usually overwrite even the partition that twrp is installed on. Your method too would work, but I think it's easier to just let magisk do the job, i've had too many failed attempts at patching a boot image
redweaver said:
I figured the flashing to boot partition one time when my phone kept booting into recovery after a failed ota update. I checked the install script and found out that at one point the boot partition is flashed with the recovery image
You definitely need to backup your boot image unless you want to risk not being able to boot your phone anymore
Flashing boot should be possible, after all even when you boot into twrp you can flash another recovery, in fact when you do a twrp restore especially one that has a recovery backup, you usually overwrite even the partition that twrp is installed on. Your method too would work, but I think it's easier to just let magisk do the job, i've had too many failed attempts at patching a boot image
Click to expand...
Click to collapse
I MADE IT! :victory:
As it turned out I stumbled over quite some weird different problems:
a) As mentioned, I was not able to boot into TWRP recovery for whatever reason. So flashing TWRP to boot partition and therefore forcing the device to boot it did the trick. Thank you for this excellent advice!:good:
b) When Magisk tried to patch the boot image automatically, it always came up with a boot image of 0 kb in size. Of course, this could not work at all. So, manually creating a patched_boot.img and flashing it after the installation of magisk turned out to be the way to go.:laugh:
c) For whatever reason fastboot had quite some problems with my the device. It obviously kept producing strange, not reproducible errors. So I arranged myself with SPFlash and was good to go.
So now I have a full system backup for Oreo 8.1 stock and a full system backup for Oreo 8.1 with magisk root.:highfive:
I can work my way through ungoogling the device and whenever I screw up, I can simply recover with my backup
So Thank you @redweaver and also Thank you @SkaboXD for all the help!
So Yeah, The LineageOs Version Which is Based on Android Nougat is Very Near For Its Release! Compiled From Source With Nokia 3 Device Tree, Vendor & Also using Kernel Source!
Does anyone know if this build was ever released?
I am not experienced, so if I hit a wall would be stuck, but can follow directions and would like very much to install Lineage OS on my Nokia 3.

Categories

Resources