TWRP and a few other questions - Google Pixel 2 Questions & Answers

Usually after unlocking this is my first step but having a read through the TWRP thread and G+ its left me a little confused.
If i flash TWRP it seems like i have to make sure the boot image, the system and the vendor image all match up for the phone to boot. And monthly updates may cause TWRP issues.
Since theres a distinct lack of ROMs it looks like i will have to stay stock. Now if i update monthly do i have to reconnect to a PC and update the new monthly update with TWRP? Once ROMs do start appearing will i have to flash vendor images separately like i did on the Nexus 6P? And a final question, if want to put a custom kernel on the phone will that have to match the boot, system and vendor images for it work?
Im currently pretty happy with stock but im getting an itchy trigger finger and wanna start trying some Magisk Modules but have no means to do a backup just in case other than TiBu but even then wouldnt be able to pull the files from a bootlooping device.
TIA

yatezy said:
Usually after unlocking this is my first step but having a read through the TWRP thread and G+ its left me a little confused.
If i flash TWRP it seems like i have to make sure the boot image, the system and the vendor image all match up for the phone to boot. And monthly updates may cause TWRP issues.
Since theres a distinct lack of ROMs it looks like i will have to stay stock. Now if i update monthly do i have to reconnect to a PC and update the new monthly update with TWRP? Once ROMs do start appearing will i have to flash vendor images separately like i did on the Nexus 6P? And a final question, if want to put a custom kernel on the phone will that have to match the boot, system and vendor images for it work?
Im currently pretty happy with stock but im getting an itchy trigger finger and wanna start trying some Magisk Modules but have no means to do a backup just in case other than TiBu but even then wouldnt be able to pull the files from a bootlooping device.
TIA
Click to expand...
Click to collapse
Any time you make an update to the rom, or flash a new rom, wipe data/cache, you'll have to flash TWRP, Kernel, and Magsik at the end.
If you are staying stock, as Google pushes factory images with security updates, the easiest way and the least room for error, is to update via ADK and platform-tools using a PC and remove the -w from the flash-all script to maintain all your data, ADK will update on top of the ROM (there are plenty of guides in the guide section on how to do this). However, doing so will remove TWRP, so using ADK, you'll have to temporarily fastboot to TWRP, and install the TWRP zip, Kernel zip(optional), and Magisk zip (again, plenty of guides on how to do this). To answer your questions, NO, you don't have to flash the images separately, ADK and the flash-all script do this for you. Also, NO, you don't have to ensure the kernel matches the images. See this guide:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
When you make a backup in TWRP, it stores the files in a location in phone storage, so if you lose TWRP, you can fastboot the TWRP img with ADK, and restore via that. As long as you don't accidently wipe storage.
Right now, you're right, there are not a lot of ROMs for our phone. Personally I daily the Aquarius OS and absolutely love it. So I'd say give that a whirl. The dev just announced that he is going to maintain support for the phone.
https://forum.xda-developers.com/pixel-2/development/rom-aquarios-8-1-0-walleye-volte-wfc-t3775295

djer34 said:
Any time you make an update to the rom, or flash a new rom, wipe data/cache, you'll have to flash TWRP, Kernel, and Magsik at the end.
If you are staying stock, as Google pushes factory images with security updates, the easiest way and the least room for error, is to update via ADK and platform-tools using a PC and remove the -w from the flash-all script to maintain all your data, ADK will update on top of the ROM (there are plenty of guides in the guide section on how to do this). However, doing so will remove TWRP, so using ADK, you'll have to temporarily fastboot to TWRP, and install the TWRP zip, Kernel zip(optional), and Magisk zip (again, plenty of guides on how to do this). To answer your questions, NO, you don't have to flash the images separately, ADK and the flash-all script do this for you. Also, NO, you don't have to ensure the kernel matches the images. See this guide:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
When you make a backup in TWRP, it stores the files in a location in phone storage, so if you lose TWRP, you can fastboot the TWRP img with ADK, and restore via that. As long as you don't accidently wipe storage.
Right now, you're right, there are not a lot of ROMs for our phone. Personally I daily the Aquarius OS and absolutely love it. So I'd say give that a whirl. The dev just announced that he is going to maintain support for the phone.
https://forum.xda-developers.com/pixel-2/development/rom-aquarios-8-1-0-walleye-volte-wfc-t3775295
Click to expand...
Click to collapse
Any particular reason? Can the XL roms be used on the Pixel?

ZeroSkylineX said:
Any particular reason? Can the XL roms be used on the Pixel?
Click to expand...
Click to collapse
I believe it is due to the ROMs use of the kernel and how it translates to the different hardware. I know you may think that the only hardware difference of the pixel 2 xl is a bigger screen, but there are several hardware differences that make the pixel 2 xl different from the pixel 2. See this thread:
https://forum.xda-developers.com/pixel-2/help/flash-google-pixel-2-xl-rom-regular-t3758985

Related

why is there no interest in tge HTC A9?

Im just curious, what is the exact reason devs ignore these phones? Is there anything specific that makes them undesirable to work with? I dont think I have seen an HTC device be ignored this much since the HTC Snap?
Like i said... just curious
Cheers,
disco
It's just a phone that didn't really do well in the market, and no one wants to work on a phone that has little buyers...
What I'm wondering is why the Sprint version gets even less love than the out of date AT&T version which at least has a semi-working CM build.
Ok, thanks. Sucks that bad sales numbers can make a pretty decent phone so ignored.
Do you know if M9 or M8 are at all similar enough to A9 to maybe mod one of those roms for A9?
disco_y2k said:
Ok, thanks. Sucks that bad sales numbers can make a pretty decent phone so ignored.
Do you know if M9 or M8 are at all similar enough to A9 to maybe mod one of those roms for A9?
Click to expand...
Click to collapse
I'm not sure on that one, never worked with either, so it's kind of hard to tell, maybe put up a thread in the Q&A section with your question. And yes it does suck ????
This a copy/paste from somewhere in this forum, but I think its due to these reasons:
With the A9 (and the M9 prior to it), HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents."
Since the A9 has dm-verity enabled and forces encryption by default, root can only be achieved using the new "systemless" root methods. There are two currently working methods:
seSuperuser (this requires flashing only flashing a zip and installing an app from the Play Store)
SuperSU (automatically disables forced encryption & dm-verity, but requires a "Format Data" in TWRP)
There is also no way to take an OTA after you root. However, prior to rooting, you can take a fully untouched system image backup with TWRP, which can be used to restore a fully stock system to the device in order to take an OTA.
How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled on the A9's ABOOT, so TWRP must be fastboot flashed over stock recovery. The firmware zip included in the OTA will include a usable stock recovery image. That can be extracted and flashed after stock system is restored so that the OTA can be applied.
How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system).
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
My ota works fine. Im rooted and you can backup by formatting data partition in the beginning. Fastboot works fine, flashing wirks fine. Really have not had any issues described above.
Oh well

Update Build W/O a Computer

Ok, let me start by saying that I'm fully capable of updating my phone with a computer, I'm just hoping there is a better way. So far every time I've downloaded a new firmware, update the flash-all.bat and run it, something will fail towards the end of the update and the only way I've been able to successfully update is by using one of those tool kits (forget which one, it's on my computer). I'm not that concerned about all of that with this thread. I'm wondering if there is a way to do it without a PC.
I'm on NMF26O (root, ElementalX, etc) and tried flashing Pure Nexus over the weekend. Since it's based on NMF26V, I kept receiving an error on boot about updating my vendor.img. So I downloaded that firmware, extracted it, and flashed the vendor.img in TWRP. That led to a plethora of other issues that I couldn't resolve by flashing the boot.img, reflashing the rom, ect. Several hours later I ended up flashing the boot.img and vendor.img for NMF26O, restoring my backup, re-installing Elemental, and rooting again.
Since these updates will be coming out every month, and roms will always be based on the latest update, I feel like I'll be pulling out the computer every month, downloading the updates, modifying the flash-all.bat, and running it through the tool, just to be able to update my rom. The first time I forget to update flash-all.bat, I'll lose the 60+ GB's I keep in internal storage. There has to be an easier way. TWRP is capable of flashing images. Has anyone been able to update without using a computer? I don't care if my radio is out dated, or something is mismatched as long as my phone works as intended.
Sent from my Pixel using Tapatalk
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
aholeinthewor1d said:
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
Click to expand...
Click to collapse
I'm on NMF26O. What's the difference between it and NMF26U and why would the vendor image from NMF26V work with NMF26U but not NMF26O?
Seems like all you would need is the /system from the rom, the vendor image, and maybe the boot image (or a custom kernel). I think I'm missing something here.
Sent from my Pixel using Tapatalk
If you install PN its based on NMF26V. So unless you are already on that then you would need to flash the ROM, reboot back to recovery, then flash the NMF26V vendor image.
I'll play devil's advocate here... Yeah there is an easier way, use your Pixel stock and take OTA's. Enjoy a phone that always works, with or without a laptop!
I understand my audience and realize this isn't a popular mantra here but I felt exactly like you did with my 6p and vendor images. I got to the point where I sacrifice root now just for my own sanity. My phone works for me, not the other way around.
What I do is side load the full OTA ( which you can get from the same place you get the factory images ). I only use the fastboot boot version of TWRP so that my stock recovery stays in place. Then all you have to do is boot into the stock recovery, adb side load the OTA file and re root. Then you're fully up to date without worries of your data being wiped :laugh:!
( Although if you look in the flash fire thread from Chainfire, he's working on a version that will let rooted pixels flash otas like normal ones :fingers-crossed: )
I think you guys are missing the point. I have no desire to ever be stock, which rules out the possibility for an OTA in any form.
What I'm trying to figure out is exactly what is necessary to make a custom rom (based on the latest OTA), work if flashed over an older build, without first somehow applying the full OTA. Or is it impossible?
On just about every other phone I've owned, we could piecemeal the files needed for minor updates, along with a custom rom. The only time we'd have to flash a full update is for major updates ( 4 to 5 to 6, etc).
Sent from my Pixel using Tapatalk
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Sent from my Pixel using Tapatalk
joshw0000 said:
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Click to expand...
Click to collapse
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
aholeinthewor1d said:
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
Click to expand...
Click to collapse
I've done it several times tonight. Went from O to U to V, flashed Pure Nexus, screwed up the rom, restored to O, then O flashed back to U and V.
Just flash it like a rom in TWRP RC1. Make sure you flash TWRP again before rebooting if you want to keep it.
Sent from my Pixel using Tapatalk

Bootloader Unlock and OTA

I'm thinking about unlocking my bootloader (well I will eventually, it just depends on how long I can last without root), but I've forgotten, is it still possible to take OTA's after you unlock your bootloader?
Thanks
Probably not.
Why shouldn't he be able to. Up until now the last four HTC devices M7, M8, M9, and 10 all received OTA updates even though the bootloader has been unlocked. There's just one new thing which startet with the change to Block-Based-OTA updates. An OTA won't install as soon as you change anything on the system partition (meaning that even mounting r/w in TWRP causes this!), due to a change in its md5 checksum.
5m4r7ph0n36uru said:
Why shouldn't he be able to. Up until now the last four HTC devices M7, M8, M9, and 10 all received OTA updates even though the bootloader has been unlocked. There's just one new thing which startet with the change to Block-Based-OTA updates. An OTA won't install as soon as you change anything on the system partition (meaning that even mounting r/w in TWRP causes this!), due to a change in its md5 checksum.
Click to expand...
Click to collapse
Wait, so if I flash magisk, I won't be able to take OTA?
Dang. If I just flash the stock recovery, will everything work, or will I have to restore to stock and take the OTA, then re-root?
When you unlock, then flash TWRP, first thing you do is Keep System Read Only. Then make a backup of System Image, boot image. When its time for OTA. restore system image, boot img and flash stock recovery. Reboot and then take OTA. You can now fastboot boot TWRP from download mode to make a backup of stock recovery(before flashing TWRP).
schmeggy929 said:
When you unlock, then flash TWRP, first thing you do is Keep System Read Only. Then make a backup of System Image, boot image. When its time for OTA. restore system image, boot img and flash stock recovery. Reboot and then take OTA. You can now fastboot boot TWRP from download mode to make a backup of stock recovery(before flashing TWRP).
Click to expand...
Click to collapse
Since TWRP can flash OTAs (firmware part of OTAs needs to be flashed separately via fastboot), restoring (and backing up) stock recovery is not mandatory.
Do you think Sunshine will come to U 11 or it's un-crackable?
schmeggy929 said:
When you unlock, then flash TWRP, first thing you do is Keep System Read Only. Then make a backup of System Image, boot image. When its time for OTA. restore system image, boot img and flash stock recovery. Reboot and then take OTA. You can now fastboot boot TWRP from download mode to make a backup of stock recovery(before flashing TWRP).
Click to expand...
Click to collapse
Thanks! For some reason though, when I tried to fastboot boot twrp, it would flash successfully but hang on the rebooting part. I have no idea what was going on. Pretty frustrating.
No laughing now- I'm on an old Galaxy s4 & U11 seems like my next device, VZW is too much & Sprint has a 1yr free program. I have rooted B4, & used Odin, but I got into other things & I don't recall how Fastbooting works… PLS help the once again Fastbooy noob & explain. Since the Sprint program requires you bring an already-paid-for 'bring your own phone' this is a BIG up front investment & I can't imagine going w/out Root/TitaniumBU/ or twrp to save images to pull my coals out of potential fires… TIA, oldwolf
IMHO, fastboot commands and such to get TWRP installed is waaaaaaay easier and faster than ODIN. I actually try every few phone generations to use a samsung device, but the pains of doing updates and such through odin isn't worth it to me. Pretty much you can unlock your phone through HTC.dev and then with the bootloader unlocked you can load your own recovery like TWRP. they walk you through all the steps and everything.
tacotoy, thanks for the reply; but what constitutes a FB command, & fm what program & in what status of android boot is it run? tia, oldwolf
Yeah, lost... New VZW OTA out today, but since I'm unlocked with TWRP, won't install. Trying to find the zip in the cache so that TWRP can install it, no joy so far, re-reading the TWRP thread.
Edit: Found path: /data/data/com.htc.updater/files/OTA_OCEAN_WHL_N71_SENSE90GP_NA_Gen_Unlock_1.11.617.4-1.11.617.3_R2_release_.zip
Fails, says system modified, even after restore to stock.
deafmetal1 said:
Yeah, lost... New VZW OTA out today, but since I'm unlocked with TWRP, won't install. Trying to find the zip in the cache so that TWRP can install it, no joy so far, re-reading the TWRP thread.
Edit: Found path: /data/data/com.htc.updater/files/OTA_OCEAN_WHL_N71_SENSE90GP_NA_Gen_Unlock_1.11.617.4-1.11.617.3_R2_release_.zip
Fails, says system modified, even after restore to stock.
Click to expand...
Click to collapse
Did you check to keep system read only before restoring the backup?
oldwolf613 said:
tacotoy, thanks for the reply; but what constitutes a FB command, & fm what program & in what status of android boot is it run? tia, oldwolf
Click to expand...
Click to collapse
just google Minimal ADB and Fastboot. Download the lastest and place all your zips and images in that folder. It is a standalone program easy and pain free.
Schmeggy929, thanks, that's easy enuf, but since this is gonna be (hopefully) my 'bring your phone'
to Sprint to get the free years worth of service- it's gotta be bought outright & while it's a good investment, I cannot afford to brick it & I'd rather look like a noob again than NOT ask…
I just used the latest RUU that OBJ posted in the Collection Post. This time I'll make sure to do the initial TWRP recovery in read-only... HTC noob...

Need help updating from rooted 5.1.1

I have a Shield Tablet (post battery fire exchange) and I would like to update it to the newest firmware/os... It is currently rooted, running BitO-Kernel, and stock nvidia rom. I did all the rooting and flashing on this tablet originally, but I never kept it up to date with newer updates. I heard on this forum awhile back that it's not just as simple as flashing a new rom, something about having to flash some other system stuff first or some partition or something. Basically I'm looking for a guide on how to update a Shield Tablet from rooted 5.1.1 to the newest OS version avalible. I tried sreaching the forum, but I couldn't find what I was looking for (maybe I'm not using the right search keyworks).
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20wifi&tx=$additional,shield
redpoint73 said:
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet wifi&tx=$additional,shield
Click to expand...
Click to collapse
Thanks I appreciate the help! Yes it's an original tablet (not the k1). It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root. I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
https://forum.xda-developers.com/shield-tablet/help/how-update-rooted-shield-tablet-to-t3355436
bluegizmo83 said:
It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root.
Click to expand...
Click to collapse
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
bluegizmo83 said:
I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
Click to expand...
Click to collapse
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
redpoint73 said:
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
Click to expand...
Click to collapse
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works. After that, I should be able to flash any current update (like 6.0) also, correct? And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
bluegizmo83 said:
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works.
Click to expand...
Click to collapse
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!
bluegizmo83 said:
After that, I should be able to flash any current update (like 6.0) also, correct?
Click to expand...
Click to collapse
Correct.
bluegizmo83 said:
And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
Click to expand...
Click to collapse
Not 100% sure. It's a full OTA zip, not an incremental update. So in those cases (full OTA) it may not need the preceding update installed. But again, I'm not sure.
redpoint73 said:
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!.
Click to expand...
Click to collapse
Ok thanks again, I appreciate all the help! One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
bluegizmo83 said:
One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
Click to expand...
Click to collapse
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
redpoint73 said:
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
Click to expand...
Click to collapse
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
bluegizmo83 said:
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
Click to expand...
Click to collapse
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
redpoint73 said:
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
Click to expand...
Click to collapse
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
bluegizmo83 said:
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
Click to expand...
Click to collapse
I'm not sure if it matters with the OTA. My feeling is, that it won't matter, and it will still install.
My guess is that in the worst case, the OTA fails, and you have to resort to flashing the recovery OS version.

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