Database Info

Apply Monthly System Update to Systemless Root ... REALITY CHECK!

Hi everyone
More than a question, I wanted to share some steps I plan to follow to apply the monthly system update and check I am on the right track. I had a Google Pixel 2 for a few months and I am learning more about the model every day.
Previously, I tried to follow different procedures found here on XDA such as applying OTA with boot images temporarily restored but I ended up with a bootloop not event TWRP could fix since all data was encrypted.
Objective:
Update the system to the latest Pixel 2 update (in this case Feb 2018) avoiding bootloops or bricks
Current Status:
Pixel 2 Walleye with Jan 2018 update
Rooted systemlessly with Magisk
No Magisk modules installed
/system modified since I have AdAway and other apps
No BusyBox installed
No Custom Recovery installed
Proposed steps:
Uninstall Magisk completely
Remove root apps from Device Admin (such as Greenify, Tasker, etc.)
Download latest factory image from Google
Extract the following from the image zip:
bootloader.img
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img​
Restart phone into booloader
Fastboot bootloader.img
Reboot the bootloader
Fastboot the following commands in this order:
radio.img
boot.img
dbto.img
cache.img
system.img
recovery.img​
Reboot phone
Install Magisk by patching boot
Re-run root apps (AdAway, etc.)
Renable root apps as Device Admin (Tasker, Greenify, etc.)
Is the above safe enough to avoid bootloop and also not lose apps and data installed?
I am aware any modifications to /system will be lost.
Have a look, let me know if on track, and if you want, give me your blessing.

Yesterday I used Dueces bootloop recovery script to update without losing anything.
I had magisk + TWRP installed
Download full update not OTA, extract to program tools directory or where you keep your goodies. Pull all factory update in folder with deuces recovery script.
From stk rooted ROM reboot bootloader,
Run dueces script from bootloader
After finished script No to format data
Reboot system when done.
From there you should be good to go, you will need to repatch but image in magisk and all that but i lost no data and had no issues
So I was on 1.171019.019 installed 1.172019.21 from fastboot with script and wiped nothing and lost nothing..
** My directions are probably incomplete so follow his instructions in his OP.

This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.

nolimit78 said:
adb sideload kernel.zip
Click to expand...
Click to collapse
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)

Rukbat said:
kernel.zip from where? The OTA? One you saved with TWRP on it?
I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)
Click to expand...
Click to collapse
The kernel.zip is whatever kernel you'd like to use (flash or elemental) but it's not required. I just rename for shorter commands for ADB Yes, you've hit the nail on the head. If you're going to be stock/rooted, you'll have to do this every month to stay current.

And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)

Rukbat said:
And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)
Click to expand...
Click to collapse
In my process outline, you don't have to remove fingerprints.

To boot to TWRP to handle files that you already copied to the phone? TWRP doesn't decrypt the names any more, does it? So all you see is garbage (encrypted hash, I guess). If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints. Or are you saying to restore the PIN and the fingerprints are still active?

Rukbat said:
To boot to TWRP to handle files that you already copied to the phone?
Click to expand...
Click to collapse
No, this is only to apply the update and flash a custom kernel and magisk
Rukbat said:
TWRP doesn't decrypt the names any more, does it?
Click to expand...
Click to collapse
No, it sure doesn't. This was caused by the Feb Update
Rukbat said:
If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints.
Click to expand...
Click to collapse
Yeah, to do anything in TWRP (outside of ADB Sideloading) you'll need to remove the PIN.

And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Created filesystem with 11/7389184 inodes and 511894/29553659 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
Click to expand...
Click to collapse
Then it wrote the system, but
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
Click to expand...
Click to collapse
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?

Rukbat said:
And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.
---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------
As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:
Then it wrote the system, but
It never reboots. If I reboot at that point, I get the recovery screen.
If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.
What next? Is there a fix, or does this one have to be replaced also?
Click to expand...
Click to collapse
Oh my gosh. Stop sending your phone back.
Update your platform-tools. Change cables. Change ports. Use the search function.
Sent from my Pixel 2 using Tapatalk

I'm not exactly new at this. Different cable, every USB port (including a 2.0 port, new download of both Google's driver and adb/fastboot, a new download of the firmware (and the sha256 is correct).
The next thing I'm going to try, as soon as I finish eating, is another computer. If that fails, and I'm pretty sure it will, I'll call Google tech support. Since it happened twice during an OTA, on two different phones, I may be able to get someone who knows how to feed the firmware into a nearly dead phone. I'm just looking for ideas I haven't had, when I post here. I'm about out of ideas. Again.

Evidently some computer manufacturers don't exactly build what they claim to build. My desktop has 2 USB 3.0 ports (which I already knew wouldn't work) and - supposedly - a USB 2.0 port. Flashing the firmware on the "2.0" port didn't work. Evidently it's not 2.0.
So I resurrected an old Windows 8.0 laptop. I think it has 0 cores running at 0MHz - it's SLOW! But it finally flashed the February update. Tomorrow (it's going on midnight here, and the phone is still downloading the last Google backup) I'll update to March.
Madness - but at least I have a working phone, and know how to get it working again if I need to (and have a few lifetimes to do it). And I have another laptop in the closet that actually works. That one gets resurrected next.

So what you're experiencing isn't new or an issue with your phone that you'd need to RMA the device. It's a learning curve because the A/B partitions are a completely different beast compared to older/other Android devices. Use Duece's Bootloop Recovery script to fix your problems. It'll work and you'll be good to go. Just be sure not to wipe. During my testing, I had to figure out all this myself and was /REALLY/ close to RMA'ing my device. But I continued to research and plugging away and found that that script helps users in your situation, as I've been in that very same situation myself.

No, it's a learning curve because, even though the USB ports on the back of the case are labeled 2.0, and have black plastic, they act like 3.0 ports with a Pixel 2. Doing exactly what both I and Google tech support did with the supposed 2.0 ports, on the aging laptop with real 2.0 ports, solved the "problem" that both Google and I were having. The phone was fine, what we were doing was right, the Acer desktop has a documentation error, and that was the only problem. (Even Google didn't seem to be aware of the USB 3.0/Pixel2 incompatibility, which many of the people in the Pixel 2 forums at XDA are.)

Follow the guide in my signature, it works, and you don't have to muck around with removing PINs and fingerprints.

Thanks for paying attention, but what really bothers me is having to remove the fingerprints in order to do a backup or restore in TWRP. I'm used to just booting to it and flashing a backup if I need it for some reason. If only Google would leave the fingerprint file alone when we went to None for the lock screen, just putting the PIN back would bring the fingerprints back. There's really no reason to delete that file. Maybe delete individual prints at the user's discretion (like changing passwords every once in a while), but not delete the whole thing just because I want to back up my current configuration.

What I do is uninstall Magisk. Then do the normal update from the update page in settings. After this I copy Magisk zip file to a usb drive. I boot into twrp using ADB. It doesn't decrypt but that doesn't matter. Use the USB as storage and install Magisk zip file through TWRP. Reboot and you are done updating with Magisk installed.

That sounds like an easy way of doing it, but doesn't the update balk at the patched boot file? Mine balked at something yesterday, which is what started all the mess yesterday. (Or does Magisk have a "remove and replace the boot file" button?)

nolimit78 said:
This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:
Code:
Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot
This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.
It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.
Click to expand...
Click to collapse
Thank you for the feedback!
One question I had for a while: flashing the data.img wipes what? Doesn't it wipe the apps you have installed?

[GUIDE] Rooting Mi A1 without TWRP

Device will be wiped if your bootloader isn't already unlocked.
Obviously, before doing this, you should enable OEM unlocking and ADB debugging in Developer Options. Also you should have ADB and Fastboot on your system (meaning they work on any directory). I use this version, just accept the installation of both the ADB/Fastboot drivers and the Google Device Drivers and you should be good to go.
Below you can find the untouched boot.img for the version you are on (or you can extract them yourselves, guide at the bottom of the thread):
2018:
March (V9.5.9.0.ODHMIFA) (OTA)
April (V9.5.10.0.ODHMIFA) (OTA)
May (V9.5.11.0.ODHMIFA) (OTA)
June (V9.6.2.0.ODHMIFE) (OTA)
June (V9.6.3.0.ODHMIFE) (OTA)
July (V9.6.4.0.ODHMIFE) (OTA)
August (V9.6.5.0.ODHMIFE) (OTA)
September (V9.6.6.0.ODHMIFE) (OTA)
October (V9.6.7.0.ODHMIFE) (OTA)
November (V9.6.8.0.ODHMIFE) (OTA)
December (V10.0.3.0.ODHMIFE) (OTA)
2019:
January (V10.0.4.0.ODHMIFE) (OTA)
January (V10.0.4.0.PDHMIXM) (OTA)
February (V10.0.5.0.PDHMIXM) (OTA)
March (V10.0.7.0.PDHMIXM) (OTA)
April (V10.0.8.0.PDHMIXM) (OTA)
May (V10.0.9.0.PDHMIXM) (OTA)
June (V10.0.10.0.PDHMIXM) (OTA)
July (V10.0.11.0.PDHMIXM) (OTA)
August (V10.0.12.0.PDHMIXM) (OTA)
September (V10.0.13.0.PDHMIXM) (OTA)
October (V10.0.14.0.PDHMIXM) (OTA)
November (V10.0.15.0.PDHMIXM) (OTA)
December (V10.0.16.0.PDHMIXM) (OTA)
Here we go:
GENERATING THE PATCHED BOOT.IMG
0. Download a suitable UNTOUCHED boot.img from above or extract one yourself by using the OTA links and dumping the image using the guide on the bottom of this thread.
To check which one is suitable for you go to Settings -> System -> About phone and check your build number. (e.g September 2019 one should be PKQ1.180917.001.V10.0.13.0.PDHMIXM)
1. Install Magisk Manager
2. Open the app and press Install on the prompt (It should prompt you to install the latest version).
3. Tap on Install on the prompt and then "Patch Boot Image File".
4. Select the untouched boot.img through your File Explorer. Wait for it to do its thing.
The patched_boot.img was created and it should be located at /storage/emulated/0/Download/patched_boot.img.
UNLOCKING THE BOOTLOADER
1. Move the patched_boot.img to your PC
2. Connect the device to your computer and open a Command Prompt
3. Check that ADB works with:
Code:
adb devices
Should say:
Code:
XXXXXXXXXXXX device
where the X's are a unique ID.
4. Boot into fastboot mode with:
Code:
adb reboot bootloader
(Yes you can obviously boot into bootloader by using Volume Down+Power Button etc)
5. You should be in fastboot mode. Check that it works properly:
Code:
fastboot devices
Should say:
Code:
XXXXXXXXXXXX fastboot
The device will be wiped after the next step.
6. Now we are going to unlock the device's bootloader with:
Code:
fastboot oem unlock
7. At this point the device is unlocked. Now do:
Code:
fastboot reboot
And let the phone boot
8. After booting, go into fastboot mode again with:
Code:
adb reboot bootloader
BOOTING INTO THE PATCHED IMAGE AND INSTALLATION
You should now be in fastboot mode from the last section.
1. Boot into the patched_boot.img that you generated earlier with:
Code:
fastboot boot patched_boot.img
The phone should boot normally and shouldn't take too long. For me it was the same boot time as always.
2. Now open Magisk Manager and press Install
3. When prompted tap onto Install and then choose "Direct Install (Recommended)"
Let it do its thing and then choose Reboot.
You should now have a rooted phone with Magisk without using TWRP.
Do not relock your bootloader or your device probably won't boot because you are rooted.
PAYLOAD DUMPING
Requirements: python3, protobuf (do python -m pip install protobuf after having installed python3)
1. Download the desired OTA (full OTA needed, not incremental ones, should probably be 1GB+)
2. Download the zip of the python script on github
3. Extract the script (both .py's) and inside the folder extract the payload.bin from the OTA archive
4. Now run:
Code:
python payload_dumper.py payload.bin
Wait for it to be done and you should have all the images in the same directory. With those, you can either just use the boot.img or even create a fastboot flashable OTA with a script.
Cheers!

Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.

The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).

Update: I have done it, I could not generate my own patched image, so I had to use the one in the provided post. I still opted to install magisk beta instead of the normal one and there was no problem, now I'm rooted. Thanks again.
---------- Post added at 05:22 AM ---------- Previous post was at 05:21 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
---------- Post added at 05:23 AM ---------- Previous post was at 05:22 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.

clau1996 said:
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
Click to expand...
Click to collapse
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.

sipollo said:
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.
Click to expand...
Click to collapse
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk

I guess I should have included that if you boot into any recovery after doing the "bypass" procedure, the device will get wiped, as mentioned by the rest of you guys.
This "guide" is only if you don't intend to ever use TWRP or something similar. Anyway, will add it to the OP, sorry if anyone got screwed up because I didn't mention it.
sgloki77 said:
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I guess if someone wants to start off with a new install it's better and faster to just boot into TWRP and flash Magisk as you just said.
Guide is mainly targetted to people who don't want to wipe for whatever reason (whether that is data or anything).

clau1996 said:
Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.
Click to expand...
Click to collapse
The resulting image should actually be a .img (or a .img.tar if you choose so in the settings) ?
Maybe you didn't look in the correct directory for the image (?)
Double check, because I did this procedure twice on my device and it worked that way.
Thanks for using the guide btw!
EDIT: whoops, should have merged with the other reply..

Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?

fernoct said:
Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?
Click to expand...
Click to collapse
I suppose it should be possible but I guess I will have to test it on the next OTA we get just to be sure.

hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks

lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.

michkost858 said:
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.
Click to expand...
Click to collapse
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader

lord bim said:
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader
Click to expand...
Click to collapse
Oh, yes it does. By the way, just to clarify; it's not a problem, it's a safety measure which Xiaomi implemented on the May Update and on. Otherwise your data would be at risk and easy to steal.

Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368

lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
Yes, nothing special about it

lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
After unlocking bootloader with vol- trick, if you want i uploaded last Fastboot Rom with a modified script.
You won't lose data and your bootloader will remain unlocked.
A Backup is strongly recommended (just in case).
Use Miflash.
https://1drv.ms/u/s!AnNVEh3KeCSVj94TW6xkP6Xj-CDeRg

lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
ProchyGaming said:
Yes, nothing special about it
Click to expand...
Click to collapse
I would recommend generating your own if possible.
Not sure if there's a difference tbh, however I think that, that one was patched for 16.0 and not 16.7 which makes it freeze up sometimes during boot.

thanks to all the valuable inputs the op and other have given here, so conclusion in you can install magisk without wiping data by this method, but your data will be erased the next time you boot into recovery. Also, one cannot be sure about otas as ota might trigger recovery for some stuff and then the data will be wiped. The only viable option is to just backup your data, either by titanium backup after installing magisk like mentioned in the op or just manually save necessary stuff somewhere, permanently unlock, flash twrp and then flash magisk.

One question though, why do we need to update Magisk into the beta version? Now that we have 17.0 is it necessary?

[SOLVED] Asking Experts for Solving Bootloop Nokia 8

So, I want to say that my Nokia 8 TA-1004 is having Bootloop. This happens very occasionally and randomly. It just attacks unexpected. I can't see what is the problem or what's the source of it. Thankfully, I have the logcat file. However, I do not understand what was the main cause. So please, I am asking the experts in here to help me identify the source of this error.
The Bootloop just boot like 4-5 times and then stopped Bootloop or sometimes just go straight to DOWNLOAD MODE and I had to restart manually. After that, i was able to gointo system like exploring like usual, and then it happens again. Sometimes not opening the app also happens. Repeat until you gets the nerve.
The phones status is rooted with magisk and unlocked bootloader but no twrp yet. Also, I am at 4.88B SP01 June,01 patch. If you are telling me that the root is the cause, then it is unlikely since it has been weeks since I had it rooted but the problem just came these recently.
Once again, I ask for the help of forumers here. I want to at least enjoy my phone that I love. I dont really want to sell the phone anymore.
Here's the link of logcat:
https://www16.zippyshare.com/v/2W0SVK8t/file.html
I promise. No viruses. Thank you

Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.

error748 said:
Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.
Click to expand...
Click to collapse
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?

godofknife said:
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?
Click to expand...
Click to collapse
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..

sumitinhome said:
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..
Click to expand...
Click to collapse
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.

godofknife said:
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.
Click to expand...
Click to collapse
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.

sumitinhome said:
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.
Click to expand...
Click to collapse
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.

godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
I have it. Wait sometime.. i will upload it on gdrive and share you link

sumitinhome said:
I have it. Wait sometime.. i will upload it on gdrive and share you link
Click to expand...
Click to collapse
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?

godofknife said:
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?
Click to expand...
Click to collapse
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk

sumitinhome said:
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk
Click to expand...
Click to collapse
Ah ha, thank you very much. I just need one more requirement. The driver. Honestly, there are so many drivers for Nokia 8 and none of them seems to work with my device detection. There's also type F, M driver..... Seriously confusing.

@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp

godofknife said:
@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp
Click to expand...
Click to collapse
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.

sumitinhome said:
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.
Click to expand...
Click to collapse
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?

@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.

godofknife said:
@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.
Click to expand...
Click to collapse
well done

sumitinhome said:
well done
Click to expand...
Click to collapse
Thank you.
godofknife said:
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?
Click to expand...
Click to collapse
@sumitinhome, how about this? I still have the issue. NO OS is running.

godofknife said:
Thank you.
@sumitinhome, how about this? I still have the issue. NO OS is running.
Click to expand...
Click to collapse
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button

sumitinhome said:
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button
Click to expand...
Click to collapse
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?

godofknife said:
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?
Click to expand...
Click to collapse
no it doesn't need any key

TWRP Root Decrypt December update for Blackshark 1st Gen

Tools and information
mauronofrio's recovery twrp
usb drivers
platform tools
magisk
munchy_cool's disableecrypt tool
get your files ready, the twrp img, twrp zip, and disableecryption zip
you may rename the img file into twrp.img
unlock your blackshark bootloader, i assume you have known how.
backup everything, whatsapp chats, use sms and backup restore app to backup your sms, call logs, and wifi logins
first.
check your update in which slot. is your phone now in last update ota december ? lets see in which slot it is.
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
if the answer is B, reboot your phone, and check the system is before ota or not. boot back to fastboot, and do this :
Code:
fastboot set_active other
then reboot. check if its in latest ota update or not. just make sure, which slot has been updated to latest ota, and which slot is before update.
i assume the ota update is in slot A.
format this slot by going to recovery, this should be stock recovery, then turn off your phone.
now get to slot B, turn it on, directly to fastboot, volume down and power
Code:
fastboot set_active other
it must be in _b now. make sure its _b.
Code:
fastboot boot twrp.img
do not do anything here. do not install anything first. because we are doing a backup here. so you are now in slot B, and the twrp is in slot B.
now lets backup the slot A which has been updated to the last ota / december 5th.
backup boot image from slot A using twrp.
Code:
adb pull /dev/block/sde11 boot_a.img
Code:
adb pull /dev/block/sda8 vendor_a.img
Code:
adb pull //dev/block/sda6 system_a.img
Code:
adb pull /dev/block/sde19 custom_a.img
*remember, we cannot backup userdata image here, i dont know yet how. these files you can save just in case things are messy.
still in slot B. still in twrp
go to Wipe
Advance wipe, choose data, repair or change file system, change file system, pick ext4
back to menu, choose mount, disable and enable until you have your internal storage pop up in your pc
then put the disableforceecrypt zip, flash, then reboot.
*you will see the message pop up in your phone saying there's an internal problem with your device. its normal. this happened if you decrypt the slot.
skip skip skip, check your wifi works or not, mine works. check also your device if its ecrypted or decrypted, mine is decrypted.
in this part, we have our slot B is decrypted. reboot back to fastboot to boot twrp.img
Code:
fasboot boot twrp.img
then put twrp zip, and flash.
get back to recovery, check if its normal and your internal storage automatically pop up at your pc. it should be normal..
from twrp, get back to fastboot
Code:
fastboot set_active other
and then reboot recovery
you are now in slot A, and you are about to flash disableforceecrypt zip and the magisk zip into slot A
put the zip files to your internal storage. flash disable first, then magisk.
and reboot to system.
you will see the message pop up in your phone saying there's an internal problem with your device. its normal. this happened if you decrypt the slot.
done.
you now have slot A and slot B decypted and rooted
*Rebellion is here.
credits to
@mauronofrio for the hardworking
@puppet13th for your input
*** I AM NOT RESPONSIBLE FOR ANY POSSIBLE DAMAGE DONE TO YOUR DEVICE AS A RESULT OF FLASHING AND I AM NOT RESPONSIBLE FOR ANY BRICKED PHONES OR LOST DATA... FLASH AT OWN RISK ***

Thank you very much Brother! Excellent wrote a manual, and everything is quite clear !!!

Device Blackshark China ROM
SKR-A0
Need help my blackshark bootloop after I try to unlock bootloader
i make mistake that i write wrong code
adb reboot bootloader
Fastboot oem unlock
(its make my device factory reset) and then I try go to bootloader again but this device already unlocked.
But after that, I try to open recovery mode. and factory reset it. and its going like this *bootloop
please I need help, I can't do anything to this phone again because its can't go bootloader again even I press volume down+power T_T
What should I do ?
(Sorry my english so bad)

Ciao Mauro, ho appena preso il Black Shark 2 , riuscirai a farmelo rootare creando la Twrp Recovery adatta? Grazie mille... ho bisogno di poter installare Viper4 fx...

helppp
Hi, i need help whit this phone,I have the global version and I want to change to Chinese version, and I do not know what to do....

Ktcghost said:
Hi, i need help whit this phone,I have the global version and I want to change to Chinese version, and I do not know what to do....
Click to expand...
Click to collapse
Hey, you should unlock your bootloader first
Go, READ CAREFULLY the instructions below. Also if you unlock your bootloader, your PHONE data, EVERYTHING will be WIPE OUT!!!
BACKUP EVERYTHING FIRST BEFORE DOING UNLOCK OF BOOTLOADER
https://forum.xda-developers.com/android/development/unlock-black-shark-bootloader-t3859207

I'm a bit curious here. Doing the instructions will root the phone right? Is it possible to unroot or revert back to normal state?
I'd like to root my Blackshark global, and after installing China ROM JoyUi I'd like to unroot to see if it will receive updates.
Is it possible to unroot?

leipnacht said:
I'm a bit curious here. Doing the instructions will root the phone right? Is it possible to unroot or revert back to normal state?
I'd like to root my Blackshark global, and after installing China ROM JoyUi I'd like to unroot to see if it will receive updates.
Is it possible to unroot?
Click to expand...
Click to collapse
It is possible, but i don't think you will receive Chinese OTA.

gilbert32 said:
It is possible, but i don't think you will receive Chinese OTA.
Click to expand...
Click to collapse
I see. I guess I'll not bother to root this global anymore. And as you mentioned, since light settings doesn't work, and also the upside boot logo.
I guess its not worth it for now. Anyway thanks for the answer

My phone is just asking unlock password
Hi does anyone know how to get past the : To start Android enter your password screen? I did unlock and flash TWRP but for some reason id did restart the phone and since than i only see this screen and cannot log into bootloader or recovery.

korosfoy said:
Hi does anyone know how to get past the : To start Android enter your password screen? I did unlock and flash TWRP but for some reason id did restart the phone and since than i only see this screen and cannot log into bootloader or recovery.
Click to expand...
Click to collapse
The problem is you. You skipped half the op.

Now status is clean but cannot see twrp or boot from slot b
gilbert32 said:
The problem is you. You skipped half the op.
Click to expand...
Click to collapse
Now status is clean but cannot see twrp or boot from slot b i just want to revert to the original state from the backed up files from the process can i do ? @kanded

korosfoy said:
Hi does anyone know how to get past the : To start Android enter your password screen? I did unlock and flash TWRP but for some reason id did restart the phone and since than i only see this screen and cannot log into bootloader or recovery.
Click to expand...
Click to collapse
I managed to do all the steps except one getting the TWRP working on slot A. So TWRP is not working on slot A and cannot load to recovery. Also I am not able to encrypt the phone. Then i have no root rights at all. And i done all the steps above mentioned. Can someone help me in this matter?
Best regards,
---------- Post added at 12:59 PM ---------- Previous post was at 12:37 PM ----------
korosfoy said:
I managed to do all the steps except one getting the TWRP working on slot A. So TWRP is not working on slot A and cannot load to recovery. Also I am not able to encrypt the phone. Then i have no root rights at all. And i done all the steps above mentioned. Can someone help me in this matter?
Best regards,
Click to expand...
Click to collapse
Things went from worst to even worst if it is possible ... now i am only seeing the BS logo and doesn't boot neither to recovery neither to bootloader .
I would really APPRECIATE THE HELP !!!

nice

...

When I try to boot into TWRP I got a black screen. How can I got into TWRP.
I can not flash it either

Accidentally formatted system partition in recovery

Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please

I think this
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system

Jaco2k said:
Just flash the latest build again from TWRP
- Download full OTA
- boot to TWRP
- plug phone to PC and move the downloaded OTA to phone internal storage
- In TWRP browse to OTA and flash it but DO NOT REBOOT
- flash TWRP installer
- reboot to TWRP and flash installer again just to be sure
- Reboot to system
Click to expand...
Click to collapse
I tried to do the same, but everytime I try to boot into recovery from fastboot, I get the same error
- FAILED (remote: Failed to load/authenticate boot image: Load Error)
Even tried different versions of twrp but same is happening

So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
In your first post you say "after installing TWRP"
If you have correctly installed TWRP you should be able to get to recovery by holding down power button and volume up button.

Jaco2k said:
So, wait a minute... You did not install TWRP to the recovery partition before starting to format stuff?
Click to expand...
Click to collapse
I did, installed TWRP quite a while ago before all this.
I was testing the latest dp on my mobile, but later I decided to revert back to stable. I flashed the pie version in local upgrade and wanted to start over.
So after booting once, I rebooted into TWRP and mistakenly selected system partition along with local storage in wipe option.
And now fastboot is the only thing I can boot in

I somehow don't think you are telling the story exactly as it went
I am assuming you flashed a full build and rebooted without flashing TWRP in-between.
Also, I am assuming you have flashed an older build that has the fastboot bug.
This means that you might be pretty screwed.
You can try to ADB push the full OTA via fastboot and flash it there using command line.
I guess at this point you are not caring anymore if you keep your data, right?
Also, there were some patched boot images laying around that might be worth flashing to see if fastboot is working on them.
As you have come across, there is a fastboot bug in some builds - I guess at some point it was fixed and then it reoccurred.
---------- Post added at 03:43 PM ---------- Previous post was at 03:39 PM ----------
BTW, I guess the link already posted in this thread might be your best bet, since you have removed TWRP when you flashed the updated build and you cannot fastboot recovery, as you have found out, due to a bug from OnePlus.

JerryDaBaaws said:
Hi, after installing TWRP, I was trying to do a fresh start on my op7 pro, but accidentally while formatting, I also happen to selected my system partition and formatted it.
Now I'm stuck on fastboot screen and can not install recovery or OS any how....
Can I recover without using msm tool from their support...
Help please
Click to expand...
Click to collapse
Just get the fastboot ROM for the same version you're on. For example 9.5.10 then you HAVE to use the one for 9.5.10.
https://androidfilehost.com/?w=files&flid=294300
Just download the Fastboot ROM (Make sure it's for your device as well). If on GM21aa then that's the one you use.
Put the phone in Fastboot mode and attach the phone to PC
Type Fastboot devices and make sure it comeback with your device serial number (like 6 or 8 digits, cant remember exactly)
Unzip the fastboot ROM and click on Flash-all.bat
Your phone will be like new as if shipped with 9.5.10 or whatever ROM you're on. There will be no root/TWRP/files (photos or music). You will have to do it all again but your phone will be working.