Related
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...
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
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.
I downloaded the Android 10 zip file from Oxygen Updater app. Went to settings app, selected local upgrade and installed the update. Since I already had root, and wanted to still have root, I went over to Magisk app, installed magisk (the way to do after installing an OTA) and I also flashed twrp and again installed magisk. After this is where everything went downhill. I rebooted the phone and I had Android 10 installed fine, but I didnt have root access. I wasnt able to use magisk, so to get back root access, I booted to twrp and there I had the problem where my internal memory was 0mb. So I followed a guide online and was able to fix it, but I lost all internal data, so I booted my phone and downloaded the magisk zip and went back to twrp, where again my internal memory was 0mb so I again followed the same steps and this time, I flashed the magisk zip using an otg pendrive. After all the android setup process, I couldnt find the magisk app anywhere. I assumed that my phone isnt rooted and since I was almost fed up at this moment, I thought, I'll manage a few days without root. After a while when I opened netflix it says that it isnt compatible with my device and on checking online, it seems that this problem occurs when the phone is rooted. I again tried to boot to the recovery to flash magisk but now the stock oneplus recovery comes. How do I get out of this situation? I want my phone either properly rooted or even if its totally unrooted its okay. I might have messed up on many things along the way, please help me fix it.
prathk said:
I downloaded the Android 10 zip file from Oxygen Updater app. Went to settings app, selected local upgrade and installed the update. Since I already had root, and wanted to still have root, I went over to Magisk app, installed magisk (the way to do after installing an OTA) and I also flashed twrp and again installed magisk. After this is where everything went downhill. I rebooted the phone and I had Android 10 installed fine, but I didnt have root access. I wasnt able to use magisk, so to get back root access, I booted to twrp and there I had the problem where my internal memory was 0mb. So I followed a guide online and was able to fix it, but I lost all internal data, so I booted my phone and downloaded the magisk zip and went back to twrp, where again my internal memory was 0mb so I again followed the same steps and this time, I flashed the magisk zip using an otg pendrive. After all the android setup process, I couldnt find the magisk app anywhere. I assumed that my phone isnt rooted and since I was almost fed up at this moment, I thought, I'll manage a few days without root. After a while when I opened netflix it says that it isnt compatible with my device and on checking online, it seems that this problem occurs when the phone is rooted. I again tried to boot to the recovery to flash magisk but now the stock oneplus recovery comes. How do I get out of this situation? I want my phone either properly rooted or even if its totally unrooted its okay. I might have messed up on many things along the way, please help me fix it.
Click to expand...
Click to collapse
Looks messy. I don't know the workarounds to get you through. If I was in your place, I would use MSM to reset it to factory settings, update to Android 10 as needed and then use a patched boot image to install magisk. I went that route this time as I really don't need twrp. Search xda for the exact steps to do this. Fairly easy.
life2018.jjn said:
Looks messy. I don't know the workarounds to get you through. If I was in your place, I would use MSM to reset it to factory settings, update to Android 10 as needed and then use a patched boot image to install magisk. I went that route this time as I really don't need twrp. Search xda for the exact steps to do this. Fairly easy.
Click to expand...
Click to collapse
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate? Meanwhile, I'll try to get things ready to try MSM tool once again.
prathk said:
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate?
Click to expand...
Click to collapse
You can try one of the fastboot stock ROMs: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Options for the fastboot ROMs, as I see it:
- Flash Android 9 fastboot stock ROM, root, and try to update and keep root (like you did before).
- Flash Android 10 fastboot stock ROM, and try to root by flashing patched boot image.
- Flash Android 10 fastboot stock ROM, and leave it unrooted.
prathk said:
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate? Meanwhile, I'll try to get things ready to try MSM tool once again.
Click to expand...
Click to collapse
I had similar issues and decided to fastboot oem lock my bootloader after upgrading to Android 10. This reset everything to stock on Android 10 and avoids the issue with Netflix for now. I may re-root at some point but the downsides of being rooted are a bit more glaring now with Android 10 (losing enterprise email for my work, worse version of Netflix, etc).
My assumption is you ran into the same encryption issue I had where the only way out was reformatting and wiping data in the process. Next time I do anything with TWRP/Root/OTA updates I'll be disabling my pin and fingerprints to see if that avoids the issue. I've had it happen 2-3 times now where internal storage is showing 0 and is encrypted with no way to enter my pin.
Just do it all over again, boot to OS install through local upgrade and open magisk, flash twrp first then install magisk OTA and reboot, that way it will go to the other partition.
I made this zip courtesy of SuperR's kitchen free version. I look forward to playing with the donate version.
This is a %100 stock ROM which also will flash the stock recovery. I had some difficulty on first setup. It is highly recommended you flash a custom kernel over this ROM. If you use the stock kernel you may get the secure startup screen. In order to get past this you have to flash stock recovery and let the phone reset.
ALSO REMEMBER WHEN YOU ENTER THE WRONG PASSWORD ON THE SECURE STARTUP SCREEN IT MAY WIPE YOUR SD CARD AS WELL!!! I always end up corrupting my SD somehow when messing with my daily driver
Edit:. It looks like flashing a custom kernel gets rid of all of the above problems. I wanted to try a completely stock experience.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If anyone is still using my old ROM YOU MUST STOP USING IT! I have identified multiple problems with it including boot failures excesive heat and other glitches most likely due to the partitions being different. I took the time to verify that most of the partitions from NotYetADev's ROM are different from mine. Unfortunately I'm not smart enough yet to be able to build my own update binary at this time. However I have developed a hacky work around. I've essentially just repacked NotYetADev's zip with my own ROM images I dumped from my 100% Stock VS995 running 20d. I haven't tried dailey driving the ROM from the repacked zip file alone. It might run just fine. However I noticed the build.prop was showing VS99520c still. So just to be safe I built the boot and system image Zip in superR's kitchen to flash over NotYetADev's.
Required Files:
VS99520d OREO Prerequisites.zip
vs9520dRAW2.zip
no-verity-opt-encrypt-6.0.zip By abdyasar
Magisk 24.3 By topjohnwu
VS995_1.0-ezV2020.zip By ezzony
Recomended Files:
alpha-modedui_overlay_dark.zip By I95swervin
Alpha-moddedui-IOSsignal-RoundedRecent.zip By I95swervin
Safetynet-fix-v2.3.1.zip By kdrag0n
Auto_Debloat_Lgv20_msm8996_Oreo_v8.8s_flashable.zip AKA Leamon Drop By Darnrain1
Troubleshooting files:
Unmodified Stock LG Recovery Image
If you aren't running Verizon firmware you MUST do a factory reset. You might be able to get away with dirty flashing over VS99520c if you are running NotYetADev's ROM. If you are running Leamon Drop I think you are going to have to factory reset also. I always wipe cache and Dalvik when presented the opertunity.
First tap install VS99520d OREO Prerequisites.zip then Add more Zips.
Next select Magisk 24.3.zip then Swipe to confirm Flash.
Boot System. If you see static boot that's good. When you get to the setup screen shutdown. I swaped out NotYetADev's stock recovery image with a VS995 TWRP recovery image. But you may want to boot into fastboot and flash a TWRP recovery image just to be sure.
Once back in TWRP Format Data
reboot recovery
Wipe everything but SD card and USB OTG BE CAREFUL!
install VS99520dRAW2.zip
add no-verity-opt-encrypt-6.0.zip
add Magisk 24.3
When done reboot system and see if it boots. If it doesn't boot or there are services crashing you may need to flash stock recovery image via fastboot and run it. You could also try the entire flashing process again. Whenever I run stock recovery I always remove the SD card before booting just in case.
If the system Boots I would install EZ V2020 kernel next. Also the easiest way to install the corect Magisk app is to rename the magisk.zip to magisk.apk and install it from your file browser. I would ask you hold off on running the Lemon Drop debloat script to help me test this ROM. I know I shouldn't have mentioned it but it's so awsome!
I thought I figured out a way to get around the limitations of the free version of SuperR's Kitchen. However after testing the files I've uploaded I notice the build number is showing SuperR instead of "OPR1.170623.032". It's probably harmless but considering I donated I feel I shouldn't have it in my ROM. The problem is that the newer donate version of the kitchen doesn't produce a ROM that boots. You can either edit your build.prop yourself for now. Perhaps later I'll fix it and upload a stock build.prop.
Thanks for posting this, will give it a try and see how it compares against Alpha O rom which is on 20c.
This installed fine and was able to reboot back into TWRP, wipe data, and re-install the ezV2020 kernel. It booted into standard setup, not the secure startup that you mentioned. Going to apply the following and then check performance: https://forum.xda-developers.com/t/...hones-volte-and-wifi-calling-working.4432865/
@Whosondephone or @nickb2b hoping one of you can help me out here as I can't figure out what went wrong or how to progress on this.
I have a VS995 that was running 7.0 with Magisk root and using the MK2000 kernel and TWRP. I loaded this zip and after boot I got the decryption error mentioned in the OP so I went ahead and wiped data.
Upon reboot into the OS I had a total static screen, which IIRC is due to no longer having a custom ROM. Luckily, I was still able to adb shell in and reboot to recovery but TWRP was no longer working. It would boot to TWRP splash screen but then would just continue on and I could never get into TWRP.
After finally getting the device to be detected by my Win 10 as an ADB device (the standard driver packages didn't work by themselves and I manually needed to set the device as an ADB device in device manager), I was able to fastboot flash the latest TWRP.
Then I was able to flash a custom kernel (tried both the ev2020 kernel linked above and the latest oreo MK2000). The static was gone and I got the Verizon Hello start screen.
After 30 seconds or so on the Verizon screen it brings me to screen that says
"Decryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone you need to perform a factory reset....."
Then there is a "reset phone" button that when I click on will bring me to TWRP.
I have tried to wipe data, factory reset, reset data using the stock recovery, etc all multiple times.
I keep getting this upon boot.
I tried to revert to the official latest KDZ using uppercut but constantly get "spc code does not match" at 4% of load.
Please let me know if you can assist.
EDIT: I've been able to reload the 7 KDZ and am working on re-unlock with dirtysanta. Once that is done I'd like to try this again. Any advice on how to get it to work?
Oh God. I'm currently working tirelessly on getting the definitive version of this ROM going.
After you re-dirty Santa and get rid of secure startup "decryption unsuccessful" I recommend flashing a full Oreo ROM Like alpha Omega rom. Google "where are the alpha omega rom threads" to find it. It has been brought to my attention that developers flash additional partitions on the vs995 variant. I have made a zip with the required partitions but I'm not ready to release it. When you install Alpha Omega I would recommend selecting no kernel. Then flash EZv2020 kernel separately after. You could use mk2000 also however many users including myself think it has problems. Flashing a custom kernel should get rid of the secure boot issue and static boot.
Reboot and setup.
Then dirty flash my ROM over the alpha Omega install. Flash custom kernel again. I flash magic just for good measure. I'll come back with the version number later. I have problems with newer versions of magisk.
As a side note if you see the static boot on a v20 you know you're in good shape. That is a side effect of the dirty Santa root method on the stock kernel. It can easily be removed by covering the proximity sensor, after the phone has booted, making sure the screen turns black, second screen too. When you release your thumb on the proximity sensor the screen will be normal.
if you're still getting the secure startup screen, it's hacky. I tried so many troubleshooting steps I don't remember exactly which one worked. I believe I got past it by flashing the stock recovery from a backup. All the stock recovery does is once it loads is immediately factory reset the phone, probably some other proprietary nonsense too. When you run the stock recovery all you see is multiple rings white red blue green on top of each other. You have no options for anything.
I REPEAT!!! POWER DOWN YOUR PHONE AND REMOVE THE SD CARD BEFORE RESETTING. THE SECURE STARTUP RESET THINGY ERASES THE SD CARD TOO.
I have a backup of it from a dump I did. I'm not sure if the dirty Santa root method makes a backup of your stock recovery, I don't think so.
Once the stock recovery completes reboot the phone and set it up. Shut down the phone. You can then run fastboot by holding volume down and plugging in USB cable. On the computer open a command prompt in your fast food directory type
fastboot flash recovery "enter TWRP image name here."
I'm not sure if this is important or not. However I cross flash all my V20'S with US996 stock firmware and perform dirty Santa. Whether the phone is a VS995 or US996 Varrient.
And I'm quite sure I've had success flashing this ROM over stock Dirty Santa US996 Nougat. Success as in boot up anyways.
My daily driver is set up given the previous instructions.
Whosondephone said:
Oh God. I'm currently working tirelessly on getting the definitive version of this ROM going.
After you re-dirty Santa and get rid of secure startup "decryption unsuccessful" I recommend flashing a full Oreo ROM Like alpha Omega rom. Google "where are the alpha omega rom threads" to find it. It has been brought to my attention that developers flash additional partitions on the vs995 variant. I have made a zip with the required partitions but I'm not ready to release it. When you install Alpha Omega I would recommend selecting no kernel. Then flash EZv2020 kernel separately after. You could use mk2000 also however many users including myself think it has problems. Flashing a custom kernel should get rid of the secure boot issue and static boot.
Reboot and setup.
Then dirty flash my ROM over the alpha Omega install. Flash custom kernel again. I flash magic just for good measure. I'll come back with the version number later. I have problems with newer versions of magisk.
As a side note if you see the static boot on a v20 you know you're in good shape. That is a side effect of the dirty Santa root method on the stock kernel. It can easily be removed by covering the proximity sensor, after the phone has booted, making sure the screen turns black, second screen too. When you release your thumb on the proximity sensor the screen will be normal.
Click to expand...
Click to collapse
Thanks. I'm downloading the Alpha Omega Oreo variant A-O_VS995_20C_1.3.1.zip right now.
Android File Host shows it is going to be 8 hours to get (not a problem on my end...Fiber).
In the meantime I just finally got the VS995 Nougat dirty santa's again with SuperSU installed according to the original instructions.
I am trying to flash your ROM again right now on top since I won't be able to try the AO method until tomorrow.
P.S. I only use this phone for my kids as a "tablet" so I don't need to be on any network. I'm simply looking for a ROM that is at least 8.0+ that I can root. If you have other suggestions on a good one that might be easier to load, I'm all ears.
TraderJack said:
Thanks. I'm downloading the Alpha Omega Oreo variant A-O_VS995_20C_1.3.1.zip right now.
Android File Host shows it is going to be 8 hours to get (not a problem on my end...Fiber).
In the meantime I just finally got the VS995 Nougat dirty santa's again with SuperSU installed according to the original instructions.
I am trying to flash your ROM again right now on top since I won't be able to try the AO method until tomorrow.
P.S. I only use this phone for my kids as a "tablet" so I don't need to be on any network. I'm simply looking for a ROM that is at least 8.0+ that I can root. If you have other suggestions on a good one that might be easier to load, I'm all ears.
Click to expand...
Click to collapse
You should be more than fine with alpha Omega rom then. Nobody knows what the 20d update actually did. It has the same 2018 security patch as 20c.
The only reason I'm making this ROM is to because you cannot set up Wi-Fi calling using alpha Omega ROM.
You could also try flashing the AOUS996 Universal version. You get some interesting extras such as being able to pin recent apps, keep and from being closed. Along with more LG themes if you're into that kind of thing.
I also recommend i95swervin's dark themed UI mod and rounded recents.
You could try lineageos. The last version I tried was pie. They supposedly fixed the headphone out. And they supposedly made it easier to install. Historically you had to flash lineageos over nugget firmware. You lose always on display. The second screen is treated as a notch. I would probably still use it if it's supported VoLTE. I think they're up to Android 11 now.
TraderJack said:
Thanks. I'm downloading the Alpha Omega Oreo variant A-O_VS995_20C_1.3.1.zip right now.
Android File Host shows it is going to be 8 hours to get (not a problem on my end...Fiber).
In the meantime I just finally got the VS995 Nougat dirty santa's again with SuperSU installed according to the original instructions.
I am trying to flash your ROM again right now on top since I won't be able to try the AO method until tomorrow.
P.S. I only use this phone for my kids as a "tablet" so I don't need to be on any network. I'm simply looking for a ROM that is at least 8.0+ that I can root. If you have other suggestions on a good one that might be easier to load, I'm all ears.
Click to expand...
Click to collapse
Well I was able to get the Dirty Santa exploit with SuperSU and TWRP back on the device as it was before. I tried one more time to flash your ROM but it simply hung (on the static screen) with the Verizon logo. I let it sit for 30 minutes, tried to clear data again and then let it sit for another 30 minutes and it never booted.
I then reloaded the Nougat kdz again and went through DirtySanta a second time. However I can't get it to properly complete. I get through all the way until I have to "fastboot flash boot bootbackup.img" and then setup the device again. The final step is supposed to be rebooting to recovery and then flashing SuperSU again but this is impossible because of the static screen. You are unable to turn the screen off in TWRP so assuming it is actually booting to TWRP I can't do anything because I can't see anything. I tried to install a custom kernel at TWRP, but that is apparently overwritten on the bootbackup.img flash so again, I don't see how this is possible as it all appears to be a catch-22.
Then, I tried after reapplying the kdz again - when I was able to reboot into recovery the first time - I tried to apply the Alpha Omega Oreo Rom which finished downloading. I'm not sure if it is completing correctly or not, it looks mostlyOK, but at the end says creating some symlinks fails and exists with an error 7. But within twrp screen there are no errors. So I reboot and then it just gets stuck at the LG screen after boot.
I have no idea how it worked the first time since I have followed the guide to a T both times. I've actually re-tried about 5 times now. So I'm left with a phone that I can get 7 back on, but I can't get it properly rooted so it becomes basically useless to me.
I'm going to load back on stock KDZ again and hopefully find a solution to move forward.
I failed to mention. Don't use super SU. The goal of Dirty Santa is to unlock your bootloader. Aka give you fastboot. With fastboot you can then flash a custom recovery. That's it. Stop.
To preface we are using US996 KDZ and TWRP image regardless of which phone model you have.
Here are the steps I recommend for flashing on a VS995 or US996:
1. Using patched LG Up flash US99610f firmware KDZ
2.Download TWRP 3.7.0_9 for US996
3.Place the TWRP image in your fastboot folder. Open the step three file in notepad and replace all TWRP images with the download one. Example:
Fastboot flash recovery TWRP3.7.0_9.img
4.Save and run step 3. Or just enter it manually.
5.in TWRP you format data.
6.reboot recovery
7.install my zip
8.install ezv2020 VS995 kernel if using my ROM.
Whosondephone said:
I failed to mention. Don't use super SU. The goal of Dirty Santa is to unlock your bootloader. Aka give you fastboot. With fastboot you can then flash a custom recovery. That's it. Stop.
Here are the steps I recommend for flashing on a VS995 or US996:
1. Using patched LG Up flash US99610f firmware KDZ
2.Download TWRP 3.7.0_9 for US996
3.Place the TWRP image in your fastboot folder. Open the step three file in notepad and replace all TWRP images with the download one. Example:
Fastboot flash recovery TWRP3.7.0_9.img
4.Save and run step 3. Or just enter it manually.
5.in TWRP you format data.
6.reboot recovery
7.install my zip
8.install ezv2020 VS995 kernel if using my ROM.
Click to expand...
Click to collapse
Thanks. I actually found an archive I put together over 4 years ago on the process that worked best for me.
Using it I was able to use dirtysanta and then put the latest Magisk (well v.23), the latest BTTF for 7.0 and TWRP 3.7.
I'm confident that with this procedure I can recover to this point again without a problem.
Tomorrow I will try the procedure you listed above, however since I am already on the 13A 7.0 VS995 version, is there a way I should try it from here? After all, if it fails I can just reload the kdz from 996 and go from there.
One other question that has me kind of scratching my head. I have written in my archive - and the dirtysanta instructions say that after step 2:
"Verizon Users Vibrator will be constantly going off, until the whole process is complete (Past Android Setup Wizard)."
And I seem to recall that this in fact did happen years ago when I did this process, but when I go through it all again I never have the vibration issue. I'm reading something that makes is sound like maybe 13A doesn't have that problem, but the archive I wrote has me loading 13A *and* mentions the vibration - meaning I think I did get it previously on 13A.
Any ideas why I don't seem to have any issue with vibration anymore when doing this process from the start of KDZ load?
Honestly I wish I knew. Someone has mentioned to me that there are a set of instructions out there to fix the vibration issue. As I'm sure you can relate, I've always just been happy enough when the thing works. For whatever reason I did those instructions on my new US996 and the Vibration issue was gone. Only thing I can say is the US996 firmware doesn't vibrate at all on power up or power off. However the VS995 does.
I'll also add that I flashed the partitions zip I recently added to the first post to my new US996. I think before flashing the system. Probably doesn't matter which order though.
In the past when switching from a US996 firmware to a VS995 firmware the vibration comes back. I was shocked when it did not this time.
Edit: to clarify it does vibrate on startup like normal. Short vibration. In other words it gets the signal to shut off!
I've also noticed there are at least two boot corruption screens. The older one from Nougat with less words and a better rhyming scheme. Then I think AO ROM flashes a newer one with Oreo that has more words and no rhyming. I also throw out there that I swear at some point early on in my rooting learning phase there was a third one that mentioned press the power button to skip this message. I might be hallucinating however I remember being so thankful for it. And I had no idea what caused it. This was at a time when I had no idea what I was doing.
Whosondephone said:
I failed to mention. Don't use super SU. The goal of Dirty Santa is to unlock your bootloader. Aka give you fastboot. With fastboot you can then flash a custom recovery. That's it. Stop.
To preface we are using US996 KDZ and TWRP image regardless of which phone model you have.
Here are the steps I recommend for flashing on a VS995 or US996:
1. Using patched LG Up flash US99610f firmware KDZ
2.Download TWRP 3.7.0_9 for US996
3.Place the TWRP image in your fastboot folder. Open the step three file in notepad and replace all TWRP images with the download one. Example:
Fastboot flash recovery TWRP3.7.0_9.img
4.Save and run step 3. Or just enter it manually.
5.in TWRP you format data.
6.reboot recovery
7.install my zip
8.install ezv2020 VS995 kernel if using my ROM.
Click to expand...
Click to collapse
I can't get this process to work, not even the first step.
I downloaded the US99610f kdz but when I try to use UPPERCUT to flash it tells me it can't because it is a 996 and I'm on 995 (in slightly different terms). I tried both the refresh and upgrade options.
I notice you said using "patched LG Up" which is what I believed Uppercut was doing, but just to make sure I searched and also found this thread:
LGUP 1.16.3 Patched Setup installer - w/ LGMobile drivers and Common_DLL
Hey guys, i always had issues with getting LGUP to work correctly, so therefore i just made an installer that installs everything in one package. LGUP_Common.dll should work for devices above the LG G6. For any problems with it, don't hesitate to...
forum.xda-developers.com
It used a newer version of LG Up which had some more options, but basic error messages were the same.
So I'm not sure how you are flashing 996 onto this device if it doesn't already have a 996 ROM.
EDIT: Update, I searched around and found this thread:
[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix)
[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) Team After a flash gone very bad, I got myself a brick with a locked bootloader & wrong viariant in LGUP [US996-->H990ds]. In my attempt to recover I tried...
forum.xda-developers.com
I assume it is the patched LGUP you were talking about? I installed it and it successfully detects my device, but I continue to get this same error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm going to try to flash the Alpha Omega Rom again and see if I can get that working.
I can't believe this phone was old 4 years ago and still today we don't have a clear cut way to install a rooted Oreo :/
If you have any more ideas I'm open to them as I doubt this AO install will work.
EDIT: Going through some more threads it seems I need to use the Partition DL option to cross-flash. I am trying that selecting all partitions. Hope I don't make my phone unrecoverable...I'll report back if I get through your procedure.
Well this just continues to be a sh** show. I was able to successfully flash the US996 kdz using the partition DL option.
After the first boot my ABH screen was gone and the boot logo was different but it booted up right into a "Secure start-up" error and I had to enter my password in incorrectly 30 times (with delays) to proceed. So that was 15+ minutes just there.
Actually, it was pretty weird because at about attempt 15 I started writing some of this response and I was kind of absent mindedly just typing in a password every 30 seconds when it would let me. At attempt 4 or 5 when I typed in a couple of random characters, instead of telling me it was invalid, it actually rebooted into the setup. That seems kind of amazing that I could have randomly guessed an encryption password by typing in a couple of characters?
Anyway, I had no other option other than going through almost 30 times because the key presses to try to get into recovery didn't work (not even stock recovery) and the bootloader is relocked so I could not just go and run step 3 again to re-flash twrp as you instructed.
I'm not sure what I am missing in your instructions, but it doesn't seem possible to do them without running a full exploit again after going to US996. And, I don't know which exploit that would be. It seems there is a dirtyelf exploit for the US996 model (?), but I'm not about to try that on my actual 995 without knowing for sure what to do.
I've confirmed I can get back into download mode, so I *hope* I can recover back to my 995 KDZ and move on if need be.
In the meantime I'm going to keep it on what is currently the US996 kdz you told me to flash which appears currently to be in a completely locked state.
If you can provide some precise instructions on how to move on from here it would be appreciated.
You can run the dirty Santa exploit on us996 firmware. Just like you would on VS995 firmware. Just once you get into TWRP your done. You don't need to follow any more steps for the dirty Santa procedure if you're going to flash a ROM.
Yes there are many different types of LG up. The one I'm using has the dump option. I am pretty sure I was able to select upgrade on mine and it doesn't give me any issues with the wrong type of phone.
Whenever you flash a kdz you return to stock/locked. At least as much as possible. I thought you'd have to deal with that secure boot. Somehow.
The best guide I follow to this day is "High On Android V20 root". It's not 100% accurate, and is slightly outdated but it it the best.
I realize I failed to mention to dirty Santa before the step 3. If you need extremely detailed instructions I can't give them until the weekend when I'm around my PC. I can give thorough instructions perhaps sometime today.
Whosondephone said:
You can run the dirty Santa exploit on us996 firmware. Just like you would on VS995 firmware. Just once you get into TWRP your done. You don't need to follow any more steps for the dirty Santa procedure if you're going to flash a ROM.
Yes there are many different types of LG up. The one I'm using has the dump option. I am pretty sure I was able to select upgrade on mine and it doesn't give me any issues with the wrong type of phone.
Whenever you flash a kdz you return to stock/locked. At least as much as possible. I thought you'd have to deal with that secure boot. Somehow.
The best guide I follow to this day is "High On Android V20 root". It's not 100% accurate, and is slightly outdated but it it the best.
I realize I failed to mention to dirty Santa before the step 3. If you need extremely detailed instructions I can't give them until the weekend when I'm around my PC. I can give thorough instructions perhaps sometime today.
Click to expand...
Click to collapse
Yes, I found this thread on reddit which is the only indication I have found anywhere that stated dirtysanta was ok to run on the us996 firmware. So I did that and continued on with the process until step 3 and booted into TWRP.
Then I canceled out of the password prompt, wiped data and flashed your ROM. BTW it seemed to take almost 2x longer than it has in the past (maybe like 12-14 minutes instead of like 6-8). It seemed to go ok until the end when I got this:
Code:
*********************
Magisk 24.3 Installer
*********************
cannot mount /system
-unmounting partitions
mount: failed to mount /dev/block/platform/soc/624000.ufshc/by-name/system at /system: Invalid argument
VS99520d 3 Installed
script succeeded: result was [VS99520d 3 Installed]
Updating partition details...
Failed to moun '/system' (Invalid Argument)
...done
I tried to flash the us995 ev kernel but it said that my phone was a 996. Then at the bottom it said something like "You are on and this is for Oreo." Those multiple spaces are there because it was actually blank, as if it couldn't read the variable.
I tried to reboot to system anyway and it just rebooted to the bootloader.
I have now rebooted into TWRP, cleared data again for good measure, wiped my SD card, am recopying your ZIP and will try to install one more time just because.
I don't see it working though, so I don't think this procedure is a success.
If you are using an LGUP procedure that allows you to do an "upgrade" instead of a Partition DL maybe something is different with your setup. You haven't been really descriptive in most of your steps and in the OP this seemed more or less like a drop in on stock and flash, which it clearly has turned out not to be. I do appreciate the help so if you have a more specific set of instructions that has definitely worked for you I'll give it another go.
P.S. "High On Android V20 root" doesn't have a single hit on Google.
P.P.S: This might be what you were referring to?
How to Root LG V20! [AT&T/Sprint/Verizon/Korean] | HighOnAndroid.com
highonandroid.com
Not to sound ungrateful - because I really do appreciate the help and if it gets me there in the end it should be worth it (assuming I can get there within the next day because I've already spend close to 10 hours on this), but you really need to be a bit more descriptive in your instructions. Especially As someone releasing files for other's uses without appropriate background and caveats can lead to headaches, wasted time, and possibly bricked devices. I know everything here is use at your own risk, but I assume you would actually want people to use your stuff if you are bothering sharing in the first place.
Anytime you have to format data in TWRP. You need to reboot recovery. Otherwise the partitions are not visible to TWRP.
Whosondephone said:
Anytime you have to format data in TWRP. You need to reboot recovery. Otherwise the partitions are not visible to TWRP.
Click to expand...
Click to collapse
I definitely did do a reboot recovery in TWRP after clearing the data the first go. I didn't know it was required, but I followed your instructions to do it anyway. I am still re-copying your zip, but once that is done I will clear data and reboot recovery once more before I try the re-flash.