WARNING: This guide is tested on Nokia 6 TA-1000 only!
ALWAYS DO BACKUP BEFORE PERFORM ANYTHING!
Use Titanium Backup, Internal Backup Tool or...whatever.
中文版教程：http://bbs.dospy.com/viewthread.php?tid=17830185&bbsid=1021&page=1
Click to expand...
Click to collapse
You can download the required firmware I mentioned there:
https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
PART 1: Preparation
1. Install OST LA 6.0.4 and patch it. DO NOT INSTALL OST LA 6.1.2 I MENTIONED BEFORE.
2. DO FULL BACKUP, DO FULL BACKUP, DO FULL BACKUP!
PART 2: Downgrade bootloader
If you're running Android O that comes from OTA Update, that means the bootloader must be downgraded before downgrade your phone to Nougat.
If you've already have old bootloader, skip this part.
Click to expand...
Click to collapse
To downgrade the bootloader, you need to download this OTA package:
https://ota-filesite.c2dms.com/SWUpdate/500000748
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
Power off your phone, then connect your phone to a charger.
When you see the charging logo, press and hold Volume Up and Power key.
If you see "No command" displayed, release both keys, then press Volume Up while holding Power key. This will pop up a menu.
Click to expand...
Click to collapse
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
PART 3: Install homebrew "Stock" firmware
Download the firmware from the link above.
D1C-331G-0-00CN-B01.7z - Nougat 7.1.1 with December 2017 Update
D1C-332A-0-00WW-A01.7z - (Hong Kong/Taiwan Variant, Full Google Play Service included) Nougat 7.1.1 with July 2017 Update
D1C-5210-0-00CN-B03.7z - Oreo 8.0.0 with January 2018 Update and old bootloader
D1C-5550-0-00CN-B02.7z - Oreo 8.1.0 with March 2018 Update and old bootloader (made from leaked OTA)
Extract the firmware archive into a new directory, for example, I extracted it to D:\D1C-331G-0-00CN-B01.
Open OST LA from INSTALLATION DIRECTORY DIRECTLY. Load the mlf file in extracted directory.
If your phone get stuck at recovery, pick "Reboot to bootloader", then connect your phone to PC.
If your phone is already powered off, just connect it to PC directly.
Click "Next" if it's usable. Otherwise, click "Edit Phone Information", after "Boot FTM Mode Fail" prompts, you can click "Next" now.
This will flash the firmware to your phone. If the procedure unexpected interrupted because of your phone doesn't cooperate properly (e.g. Your phone suddenly reboots to OS), close the OST LA, then press and hold both Volume keys and power key to force power off your phone, then flash it again.
When the progress bar is going to complete and your phone is booting (NOKIA logo is displayed on the screen), the flash procedure is already completed.
In most cases, if your phone prompts md5 checksum fail after flashing, this is also expected. You can close OST LA, unplug the phone, then reboot the phone with [Volume Up] and [Power] key.
PART 4: Full userdata erase
If your phone can boot into OS normally, skip this part.
Click to expand...
Click to collapse
Because the encrypt algorithm is different between Nougat and Oreo, you must do full userdata erase or the phone will get stuck at NOKIA logo.
Enter Download(Fastboot) mode again with the method you're familiar with.
Open OST LA, load the firmware, then click "Edit Phone Information".
If you've already know how to obtain the service permission, you can just type this command instead:
Code:
fastboot oem dm-verity (md5 checksum of your phone's serial number)
Then type this command:
Code:
fastboot format userdata
You also need to flash TWRP to do another format procedure, which the procedure I've given in this topic:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-flash-custom-recovery-root-t3702354
After you enter the recovery, tap "Wipe" (清除), "Format data partition" (格式化 Data 分区), then type "yes" to proceed.
NOTE: Root package included in recovery isn't compatible with Android Oreo.
Click to expand...
Click to collapse
You can reboot your phone to the OS now. If the phone get stuck at Powered by Android logo, just do PART 3 again.
I successfully sucessfully fw (Oreo) through OST 6.0.4 and have installed TWRP on Oreo.
But the Root package does not work.
I'm testing with the zip install package via TWRP as the MODs for example (Emoji package, Font, ...) Hope it works.
I can't flash your firmware "Nougat 7.1.1 with December 2017 Update"
stuck on writing md5, what's wrong ?
hawwin88 said:
I can't flash your firmware "Nougat 7.1.1 with December 2017 Update"
stuck on writing md5, what's wrong ?
Click to expand...
Click to collapse
You can use a text editor (do not use notepad) to edit the md5.dat, and modify the checksum to expected checksum displayed on the phone, then flash again.
I'll reupload the correct package soon.
anyone tested on t 1021
Can we get root access and xposed on oreo or is it still unavailable?.
Please I am begging the senior members please, someone should help me..my phone has been bricked for 2 months now..my Nokia 6 ta-1003.. it's stuck on QLD 900E... PLEASE HOW DO I resolve this myself...I have been without a phone since... someone should help me out of this nightmare..it doesn't come on,just only shows the notification lights and QLD 900E on device manager... awaiting a positive response..thanks
TA-1021 Downgrade help
is this method useful for nokia 6 TA-1021??????
hikari_calyx said:
You can download the required firmware I mentioned there:
https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
PART 1: Preparation
1. Install OST LA 6.0.4 and patch it. DO NOT INSTALL OST LA 6.1.2 I MENTIONED BEFORE.
2. DO FULL BACKUP, DO FULL BACKUP, DO FULL BACKUP!
PART 2: Downgrade bootloader
To downgrade the bootloader, you need to download this OTA package:
https://ota-filesite.c2dms.com/SWUpdate/500000748
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
PART 3: Install homebrew "Stock" firmware
Download the firmware from the link above.
D1C-331G-0-00CN-B01.7z - Nougat 7.1.1 with December 2017 Update
D1C-332A-0-00WW-A01.7z - (Hong Kong/Taiwan Variant, Full Google Play Service included) Nougat 7.1.1 with July 2017 Update
D1C-5210-0-00CN-B03.7z - Oreo 8.0.0 with January 2018 Update and old bootloader
D1C-5550-0-00CN-B02.7z - Oreo 8.1.0 with March 2018 Update and old bootloader (made from leaked OTA)
Extract the firmware archive into a new directory, for example, I extracted it to D:\D1C-331G-0-00CN-B01.
Open OST LA from INSTALLATION DIRECTORY DIRECTLY. Load the mlf file in extracted directory.
If your phone get stuck at recovery, pick "Reboot to bootloader", then connect your phone to PC.
If your phone is already powered off, just connect it to PC directly.
Click "Next" if it's usable. Otherwise, click "Edit Phone Information", after "Boot FTM Mode Fail" prompts, you can click "Next" now.
This will flash the firmware to your phone. If the procedure unexpected interrupted because of your phone doesn't cooperate properly (e.g. Your phone suddenly reboots to OS), close the OST LA, then press and hold both Volume keys and power key to force power off your phone, then flash it again.
When the progress bar is going to complete and your phone is booting (NOKIA logo is displayed on the screen), the flash procedure is already completed.
In most cases, if your phone prompts md5 checksum fail after flashing, this is also expected. You can close OST LA, unplug the phone, then reboot the phone with [Volume Up] and [Power] key.
PART 4: Full userdata erase
Because the encrypt algorithm is different between Nougat and Oreo, you must do full userdata erase or the phone will get stuck at NOKIA logo.
Enter Download(Fastboot) mode again with the method you're familiar with.
Open OST LA, load the firmware, then click "Edit Phone Information".
If you've already know how to obtain the service permission, you can just type this command instead:
Code:
fastboot oem dm-verity (md5 checksum of your phone's serial number)
Then type this command:
Code:
fastboot format userdata
You also need to flash TWRP to do another format procedure, which the procedure I've given in this topic:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-flash-custom-recovery-root-t3702354
After you enter the recovery, tap "Wipe" (清除), "Format data partition" (格式化 Data 分区), then type "yes" to proceed.
You can reboot your phone to the OS now. If the phone get stuck at Powered by Android logo, just do PART 3 again.
Click to expand...
Click to collapse
Hi, i have Oreo 8.1 install in my ta 1003, initially it was a ta 1000 but i did flash the ta 1003 rom after down grading the bootloader with help of another thread. I want try out this Home brew rom and am not sure how to go about. The ta 1003 has issues with the network, like the VoLTE option is not working.
I cant get to stock recovery manually, I tried holding power and up volume but still not working. I'm using TA 1039 with Android 8.1.
What should i do?
hikari_calyx said:
PART 2: Downgrade bootloader
To downgrade the bootloader, you need to download this OTA package:
To prevent from FIH removed this OTA package, I mirrored this OTA package.
You need to enter stock recovery manually.
In some cases, you may get stuck at stock recovery.
Pick "Install update from ADB", then use adb sideload command to push this OTA package to your phone.
Code:
adb sideload D1C-331G-0-00CN-B01-331F-0-00CN-B01-update.zip
After this update installed, your phone will reboot once, then get stuck at recovery. Your bootloader has been downgraded now.
Click to expand...
Click to collapse
Sorry, just one question.
If the TWRP already has those partitions decrypted, can the userdata partition be safely restored after updating from Nougat to Oreo?
does anyone have the OTA package backed up? https://ota-filesite.c2dms.com/SWUpdate/500000748 doesn't work anymore
Dantheman221 said:
does anyone have the OTA package backed up? https://ota-filesite.c2dms.com/SWUpdate/500000748 doesn't work anymore
Click to expand...
Click to collapse
Change c2dms into oss-cn-hangzhou.aliyuncs :
https://ota-filesite.oss-cn-hangzhou.aliyuncs.com/SWUpdate/500000748
Hello
After updating to Android 9, I lost dm-verity command and TWRP. Fastboot says it's an invalid command now. Help?
Edit: Okay, flashed old bootloader and got dm-verity back. Unlocked bootloader, now am stuck on recovery, won't boot to 7.1.1 OS. Help?
Hello,
I have a Mi Mix 3, MIUI global 10.2 stable, 10.2.2.0 PEEMIXM.
I managed to root, install TWRP and gcam after a few days of trying.
* Two days ago I updated from phone settings (About phone, Check updates ...)
* I lost both root and TWRP.
* I tried exactly the previous methods to root and phone stuck at booting (three dots flicking on the screen) - via PC / adb / fastboot.
* After that, I reset phone to factory settings and try again - boot in fastboot, try to flash TWRP and I get this error message: error cannot load TWRP.img file (not available or missing).
I also mention:
1. Phone was already rooted by the same procedure
2. Phone is unlocked
3. Dev options / USB debugging check
4. I renamed TWRP.img with recovery.img
5. I even try "TWRP" without extension ".IMG" (last week before the update I succeeded this way - no .img in the name of the file)
Please help
I need something so that I can root phone again AND won't delete TWRP and root after next update.
Thx very very much.
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
PWn3R said:
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
Click to expand...
Click to collapse
Thank you very much for your time and information. I must add that I was able to flash TWRP according to the procedure explained above, but I couldn't enter/access TWRP recovery. Then, I tried to re-flash TWRP and I always get the message: "error cannot load 'twrp.img' no such file or directory"
And I've tried several methods, several TWRP, different USB cables - almost everything you can imagine. Still, I cannot load the TWRP.img - it's not found. I must say I follow exactly the procedure explained in every posts.
What options do I have?
If you are using adb to load twrp, try putting it in the c/ of your pc, and putting twrp image in the adb folder, and if that didnt work, try renaming the img file to pocorecovery
Hi guys
I just successfully flashed my K8+(2018) to oreo from nougat and kept my working fastboot. Im gonna tell you how but first........
I Duhjoker am in no way responsible for anything that may befall your device by trying any technique or by following this guide. Do this at your own risk.
What you will need::::::::
Lg K8+(2018) LM-X210ULM
K8+Oreo-rooted-boot.img =====second post
K8+Oreo-twrp-recovery.img====second post
LGUP dual mode
Lg firmware extractor ??? This is for those portting a recovery and boot.img for a different cv1 device
Oreo firmware for your K8+(2018) X210ULM
and/or
Nougat firmware for your K8+(2018) X210ULM
Magisk manager
Patience
Ok so go to settings and tap general then about phone then software and tap the build number 7 times and to make yourself a developer. Exit about phone and open your newly opened developers settings turn off auto updates and enable oem unlocking and debugging.
Now this guide assumes your cv1 device is on nougat. If you are already on oreo and have no ARB number and want to upgrade your oreo rom to include a working fastboot mode then you will need to first downgrade your cv1 device to the earliest version of nougat firmware you can find and repeat the steps above.
To unlock the bootloader go to your adb folder open up a command line and type
adb reboot bootloader
When it boots to a mostly black screen with a tiny lil paragraph describing fastboot and giving some instruction type
fastboot flashing unlock
Or
fastboot oem unlocck
From there your done for now with fastboot. Lets go ahead and type fastboot reboot.
A developer here who was trying to unbrick his lg phone ended up hacking the program LGUP and found out a way to download to different partitions of the phones memory. The option called partition dl will allow us to flash a rom to the phone with out flashing the aboot partition which holds our working fastboot mode. You could even change your phone from a aristo 2 to a fortune 2 or k8 or any number of combinations as long as you do not ever flash aboot.
Warning! Warning! Warning! Warning! Warning!
Just a reminder. If you flash the aboot of anothet cv1 device to your phone it will immediately go dead and will be bricked under Qualcomm HSUSB 9008 mode which at this point in time there is no fix for.
Now you will need LGUP dual mode and since we are using a cv1 device go over to tecknights Aristo 2 page grab LGUP dual mode from there and thank him for all his hard work.
While your there if you want root you will need to go ahead and grab his twrp 4 cv1 devices with oreo kernel from his tutorial on flashing a prerooted oreo rom and port it over to the K8+ or not or i may have it posted here. Either way you will need it soon.
Now download the LG firmware extractor and pull the boot.bin from the oreo rom you are using to upgrade your device to and rename it to boot.img then put it in a dedicated folder in external storage.
Download the latest version of magisk manager put it on your external storage sd card with your oreo boot image.
Now lets flash our K8+(2018) X210ULM to Android 8.1 OREO.
Plug your phone into your windows pc and start LGUP dual mode Dev. When it loads your device hit select and the fladhing screen will appear with several more options than the LGUP your probably used to working with. Click the circle next to
Partition DL
Now go and choose the rom you want to flash and check every partition except aboot. Then hit ok. When it gets done it will reboot into Oreo and you will still have your boitloader is unlocked screen warning upon boot.
If not you did something wrong. Reflash nougat read the directions again and reflash the oreo rom with every partition except aboot. Remember do not flash aboot. If you do you will lose your working fastboot.
You now have a cv1 device that not only has fastboot mode but it can also flash.
Now for root go to settings and set up your developers options and this time you will notice that the oem unlock switch is greyed out in the unlock position.
Now install magisk manager and choose the install by picking a file and patching it. When it gets done you will find it in internal storage Download folder. Now hook plug your phone back into the pc and place your TWRP 4 CV1 DEVICES w OREO KERNEL and magisk patched image into the adb folder and rename them recovery.img and boot.img and open up a commandline there.
Now type
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Upon booting go to magisk and let it setup up the enviroment and reboot then before rebooting to twrp go ahead and go to settings and Downloads in magisk and install TWRP helper. Then go do not reboot but go up to modules and hit the reboot to recovery option. It should now reboot to twrp where you can now mount your partitions then make a back up then check those mounts again and reboot to system.
Thats it. Your done.
Extra:::
This can be done with any cv1 device that does not have an ARB value on before you start flashing. You upgrade an Aristo 2 to Oreo as well as a Fortune 2. The only stipulation is that you choose firmware with an ARB value of 0 and start with a device with a firmware that has an ARB value of 0.
Ive heard that one could possibly change an Aristo 2 to a Fortune 2 and a Fortune 2 to a K8+ or vice versa but im not brave enough to try.
Please be sure to thank Tecknight for his work with the CV1 and you dont have thank me but it would nice if some one did.
Maybe i said i would post my recovery and rooted boot images. Maybe i didnt. Well i did i say i might. So any way these are my images. One magisk rooted-boot.image for the Lg LM-210ULM ONLY. This image is only to be used with K8+ running oreo. Do not use with nougat.
IF YOU TRY TO USE THIS IMAGE WITH ANOTHER CV1 IT WILL BOOTLOOP.
We also have a TWRP image for K8+ Lg LM-X210ULM android 8.1 Oreo. while this image should work for any android 8.1 cv1 device, its for android 8.1 only and could cause a bootloop if used for a 7.1.2 nougat device.
The recovery i ported over myself from teknights oreo version for cv1 devices. Why did i not just use his since most cv1 devices can use the same recovery? Well when i first started rooting this device i did but had some issues with my device feeezing at the K8+ screen. Also i had to set the system.img to ext4 or no mounting and i had to set firmware to vfat as well. Data was changed to ext4 since every time twrp was started i would have to wipe a reformat it.
Never had a problem where i had to change any thing in the recovery.fstab before but once those changes were made i had no more boot loops, mounting or formatting issues and it works without fail now.
Im including the no verity opt encrypt flash zip too. Dont forget to flash the first time you boot twrp or you might have a bad day.
Edit:::: since i pulled these images using flashify after flashing the no verity zip and also flashing the twrp storage helper you may not need to use flash zip or module yourself but i dont think it would hurt.
Good find!
Do not try to flash another device to your cv1. I have tried this as an experiment and netted a device in hsusb 9008 mode. Only flash rom images for your device or buhbye felicia.
I followed this guide here on unlocking the bootloader, installing TWRP and rooting the phone only I forgot to install the magisk.apk beforehand. I installed TWRP custom recovery but doing so has removed any and all normal functionality from my device. I did not make a backup as it was a new device and therefore had no data that I thought was worth keeping.
The device now says it is in orange state when booting and that it will open in 5 seconds. The timer then does not count down and it is stuck there on the booting screen indefinitely unless I reboot the device straight into either fastboot mode or TWRP recovery mode.
Apparently I may have deleted the stock ROM in installing TWRP, why this would be the case, I do not know, but I cannot access my system's normal functionality anymore.
Attempting to reboot into the system simply takes me back to the neverending orange state screen and all guides online that talk of reflashing the stock ROM say I have to use something called SP flash or OST instead of ADB without saying why? I cannot run OST or SP flash as I am running a linux computer and the above are only available on windows 10.
In addition, I have tried using the fastboot update command to update from the stock ROM I can find for nokia 3, but it always states that there is no android-info.txt found.
What can I do to actually be able to use my phone?
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Juuuul said:
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Click to expand...
Click to collapse
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
hammered58 said:
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
Click to expand...
Click to collapse
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Juuuul said:
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Click to expand...
Click to collapse
You actually boot into TWRP it does not have to be installed,, you install it once you boot into it plus you would probably need a otg because you do not have a OS . Here's a link to the Msm tools
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/
There are several great write ups on how to use and install msm tool right here in the op7p forum I will see what I can find and post later
[OP7PRO][LATEST OOS 11.0.5.1 GM21AA/GM21BA] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com