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.
Related
Somewhat new to this, but I successfully rooted my 6633 which has stock 4.4.4 (Which I re-installed the stock firmware fresh). Afterward I Installed TWRP and attempted to create a custom recovery (I could never boot into recovery and tried many times and many ways), and assume I must at least create a custom recovery. Anyway, in attempting to create the recovery I tried to flash the img file. However, I could not find an image for the 6633 and (stupidly) flashed the image for the z3c. But other than freezing the phone the first time I shut it down, everything on the phone works fine. But a recovery was never created. I then found an img for the 6633 and tried to flash it but simply got an error message saying that "Failed remote: image is not a boot image". Apparently either the original mistakenly loaded (z3c) image won't let me flash another over it (unlikely, since it may have never even loaded) or (more likely) the new correct image is bad or corrupted. It is called "bootZ3dualmonxtest01.img" and was downloaded from another site. Searching this site I did find a kernel for the Z3 6653 but there is not any kernel for the 6633.
Again the phone works fine and I can do some file management things in the root, but the whole reason for doing this rooting process is so I can flash a mod to fix the crappy ringtone volume, that I located in another thread on this forum. It's been a journey & I had a lot of fun learning, but I'm not even sure that, in the end, the mod will even fix the ringtone volume (although posters on that thread claim it works). But that's a whole other issue. (lol). Sorry for the wordiness. I read the forums a lot and tried to be thorough. I know there are a lot of really smart people helping newbies like me. Any help is appreciated.
First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.
G-FACE said:
First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.
Click to expand...
Click to collapse
Thanks so much for your reply. However, the Bootloader was unlocked the whole time. In fact, the process did seem to correctly flash the wrong kernel (xperia Z3c). The reason I was trying to create a custom recovery is that I am apparently unable to boot to TWRP. I had read in another forum that the Z3 Dual does not come with a stock recovery and that a custom one has to be installed.
In any case, I followed the instructions to boot to TWRP (which gave a couple of methods), and it continues to just either just boot normally, or it I get an error "Damaged SD Card" and I lose some minor functionality. In that case, the phone won't shut down and I have to hold the power button and up volume to kill it. But then if I power it on, everything is normal. This error sequence only occurs when I try to boot into recovery.
Is it possible that when I flashed the wrong kernel (using the Xperia Z3c kernel) that I created this issue? I assumed that the reason for the error was that there was no stock recovery and one could be created by flashing the kernel image.
There is no stock recovery on Z3.
Here is a custom kernel for D6633, but you need to be on stock 23.0.F.1.74 firmware: http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
You can ask the dev there to prepare for you a custom kernel for another firmware version if you want.
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...
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.
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.
Hi, last fall I unlocked my Global OnePlus 7 Pro. I installed Magisk to add some tweaks, but I do not install TWRP or CWM yet. I planned to do “factory wipe and reset” to clean out my phone before I gathered the elements to install a custom ROM... it did not go well. After about a minute or so, it flashed an error msg and rebooted into a bootloop.
I remember I found a simple ADB command that let me bypass the bootloader? to get to a working phone... but then I got really sick for about 6 weeks with a bad infection (non-COVID). After that, I had severe memory loss and I have no idea what the ADB command was, or where to find it again. So I’m stuck with a phone I cannot let reboot or run out of battery... thankfully, I’m better now and I’d like to try and fix this once and for all.
1. I hope I was making sense about the ADB command... does that ring a bell for anyone?
2. when the factory wipe failed, I must have corrupted the Bootloader? How can I restore it?
3. while I have found the Stock ROM perfectly fine, I wanted to try out an Android 12 ROM. Once I fix the bootloader, I assume I can re-unlock the (restored) bootloader, root the phone, and then install TWRP and a custom ROM?
Any suggestions for allowing my phone to reboot normally would be awesome. Here’s my phone details:
SIM: Tmobile USA
Android 11, Security update 2021-08-01
Build Oxygen OS 11.0.3.1.GM21AA
Broadband 1.1-0007-SM8150_GEN_PACK-2.387049.1.399262.2
Kernel 4.14.190-perf+
Thanks for reading, and I hope I’ve been clear enough!
motionmonk said:
Hi, last fall I unlocked my Global OnePlus 7 Pro. I installed Magisk to add some tweaks, but I do not install TWRP or CWM yet. I planned to do “factory wipe and reset” to clean out my phone before I gathered the elements to install a custom ROM... it did not go well. After about a minute or so, it flashed an error msg and rebooted into a bootloop.
I remember I found a simple ADB command that let me bypass the bootloader? to get to a working phone... but then I got really sick for about 6 weeks with a bad infection (non-COVID). After that, I had severe memory loss and I have no idea what the ADB command was, or where to find it again. So I’m stuck with a phone I cannot let reboot or run out of battery... thankfully, I’m better now and I’d like to try and fix this once and for all.
1. I hope I was making sense about the ADB command... does that ring a bell for anyone?
2. when the factory wipe failed, I must have corrupted the Bootloader? How can I restore it?
3. while I have found the Stock ROM perfectly fine, I wanted to try out an Android 12 ROM. Once I fix the bootloader, I assume I can re-unlock the (restored) bootloader, root the phone, and then install TWRP and a custom ROM?
Any suggestions for allowing my phone to reboot normally would be awesome. Here’s my phone details:
SIM: Tmobile USA
Android 11, Security update 2021-08-01
Build Oxygen OS 11.0.3.1.GM21AA
Broadband 1.1-0007-SM8150_GEN_PACK-2.387049.1.399262.2
Kernel 4.14.190-perf+
Thanks for reading, and I hope I’ve been clear enough!
Click to expand...
Click to collapse
Iam literally shooting from the hip on this one but u could try the cmd. Adb reboot edl. See what that does
hammered58 said:
Iam literally shooting from the hip on this one but u could try the cmd. Adb reboot edl. See what that does
Click to expand...
Click to collapse
Hi hammered58, thanks for the reply... I mean no disrespect, but I'm going to wait to try that command until I possibly get other replies. I just am fearing being stuck in a bootloop again and not having the right command to finish the boot process : /
Thank you for offering the suggestion though! I've got it written down now as a way to move forward : )
If you want to start with a completely fixed 100% stock phone, you can use "MsmDownloadTool" to restore the phone: https://forum.xda-developers.com/t/...a-gm21ba-collection-of-unbrick-tools.3956595/
After restore, fully update the phone to the latest OOS version (Over-The-Air updates work for this). Then follow bootloader unlock instructions: https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Then follow the instructions for your custom rom installation. Most custom rom threads include instructions on how to install Magisk if you also want root.
After installing a custom rom, if you relock the bootloader it will forcefully factory reset the phone and either remove the custom rom (and remove root if you used Magisk) or just make it unbootable UNLESS you "Re-lock the bootloader with a self-signed build" which is a very entailed process and only works with certain roms. >99% of us with custom roms leave our bootloaders unlocked.
(Optional: Advanced) For more info on "Re-locking the bootloader with a self-signed build on a custom rom", see this thread: https://forum.xda-developers.com/t/...with-a-self-signed-build-of-los-18-1.4259409/
ninjæon, thank you for this! I had started reading on MSM Tool, and now I have more confidence to understand what it can do.
Many thanks for reaching out!
(Optional) More info on whether or not it's worth going through the trouble of trying to relock your bootloader while on a custom rom:
https://www.reddit.com/r/LineageOS/comments/n7yo7u
I can see that these questions have come up over and over again... thanks for the link. I first want to get my phone back to stock bootable OS, and then consider a ROM like Pixel Experience. I have liked how the OnePlus Oxygen OS is pretty debloated, esp compared with Samsung.
I appreciate your info! I got a lot to read this week : )
fastboot boot [image]
image can be gotten from https://www.oneplus.com/support/softwareupgrade
edit: happy oktoberfest!