Related
Hey Guys -
I purchased my AT&T A9 about a month ago and have been pleased with it. It has s-off via Sunshine and was rooted by using one of the first methods here which basically involved replacing the boot image, restoring to factory, flashing the recovery image (TWRP), then installing SuperSU. This method worked great except for one thing.
When trying to format an SD Card for "Internal" use, it shows a message towards the end saying that the card is slow then upon completion says it is corrupted. After trying 3 brand new cards plus a couple of posts, I found the issue was experienced by many and due to the root / SuperSU as users who used an alternate rooting method didn't experience the issue. After a few posts, I had a couple of things I was going to test - but - that was about 3 weeks ago. The testing would be to restore stock to phone, copy a key, rooted with SuperSU, then take an image from the phone and inject the keys, followed by reflashing the phone with it. Before doing this extensive test, I wanted to post and see if any solution has been posted since (that I haven't seen when initially looking through posts over the past few minutes.)
Given that my phone's currently rooted with s-off, what would be the ideal was to re-root currently which wouldn't have this issue so that I could use internal storage successfully?
Thanks & Happy Holidays!
The latest supersu patch the boot.img I think and you need to replace that one with a fresh stock boot.img. I would have installed stock rom and done it all over again, but this time you just have to flash the rom, install twrp and then install supersu from twrp, I think you must format data to not sure, it is all covered in a post so do a search for it.
Thanks. Where can I get a stock boot.img? I downloaded the restore exe (RUU) from HTC which I got rom.zip from but couldn't extract it. I guess I could restore phone to stock but prefer not to if I don't have to. Thanks
If you do a backup of data partition before you restore stock room, then you can use that after you are done.
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.
Ok so I haven't done any rooting, flashing, or otherwise phone modding a long time. I've just been using my Pixel 2 stock unrooted since it came out. A few days ago, I finally rooted systemlessly with Magisk, using fastboot boot for TWRP and ADB sideload for Magisk. All good. Easy peasy.
Today, I got hit with the December OTA. I wanted to take it. Uninstall all Substratum stuff, uninstall Magisk, no other mods to the system.. Bam. Should have been easy. What I didn't realize is I don't have (a copy of) my stock boot image. Which means, of course, that uninstalling Magisk just puts me in a soft brick that bootloops to the little dead android guy ("no command") over and over. I just went back to the TWRP boot and re-loaded Magisk to get working again while I try to figure this out. So I started looking up how to get my boot image so I could do this right. No luck. All the instructions I find are either outdated, meant for something else, or just plain don't work. I downloaded the November OTA zip. I was led to believe I could extract the stock boot image from that. But inside, all I find is a platform.bin file and I can't seem to do anything with it.
I don't know if I'm doing something wrong, looking in the wrong places, or if I'm just effin' stupid.
Can someone please help me with getting my boot image (from the November PQ1A.181105.017.A1 if it matters) and then maybe letting me know exactly what I need to do with it (instructions, if you will) to "unroot"/uninstall Magisk (presumably using the "Restore Images" option) so I can take this OTA and then re-root with Magisk again?
Any help would be greatly appreciated.
Signed,
A guy who used to feel like a pro at this stuff and now feels like a noob again
I would just download the December full image, remove the -w from the flash-all.bat (to save your data) and flash the image. Then install TWRP again and Magisk.
Might save a few headaches.
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 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.