Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again
itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.
irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol
Has anyone updated to Android 12 and successfully rooted again with magisk? It seems from the Pixel 5 thread that there are problems with this..
I have removed root and restored stock boot + updated to Android 12. Have downloaded the factory image and am ready to patch + flash magisk patched boot, but I am reluctant to try after reading the Pixel 5 thread.
Sure, I've done it already.
Check here.
Worked for me too.
I'm starting to think that the 4a 5G and 5 (and presumably all newer models) have this restriction. Not sure why the 4a does not.
a1291762 said:
Worked for me too.
I'm starting to think that the 4a 5G and 5 (and presumably all newer models) have this restriction. Not sure why the 4a does not.
Click to expand...
Click to collapse
I have a Pixel 5 running official Android 12. I upgraded from a magisk rooted Android 11. When I flash the patched boot image in fastboot mode, restarting the device only takes me back to fastboot mode. The only way I can get past fastboot mode into Android 12 is to reflash the stock boot image.
Do I need to disable dmverity, etc.?
Skeetch79 said:
I have a Pixel 5 running official Android 12. I upgraded from a magisk rooted Android 11. When I flash the patched boot image in fastboot mode, restarting the device only takes me back to fastboot mode. The only way I can get past fastboot mode into Android 12 is to reflash the stock boot image.
Do I need to disable dmverity, etc.?
Click to expand...
Click to collapse
I haven't been flowing this thread since it doesn't apply to me but the last thing I saw seemed to suggest upgrading and then trying to figure it out didn't work. Check it out, maybe they got further.
[Closed] Android 12 Update and Root ***Obsolete***
Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
forum.xda-developers.com
Installed some Pixel launcher stuff and successfully soft-bricked my 8 Pro running OOS 12, Android can still boot but runs abnormally, can boot into fastboot(d) and adb under Android works, but now I can't do things with Google play related, can't install any apk, can't connect MTP to navigate internal storage, many more symptoms to name, which I think are because of some permissions are corrupted.
Anyway I plan to resotre the OS back to normal by reflashing the same version OOS 12 OTA file, which is IN2025 C.16, however since I can't install that apk Oneplus provides to use update utility, even if I get the OTA file (and payload.bin) I cannot flash it inside Android. I guess the best bet is to flash using fastboot, and I get payload.bin on my hand, now I have a question: which IMG files do I need to flash with fastboot(d) just to restore the OS? I don't want to lose any user data, at least I don't want to see internal storage formatted as I am unable to back up the files in it, and as I see in the forum, using something like flash-all.bat or Fastboot Enhance will erase everything so they are the last options.
So to re-flash the same OOS 12 at a minimum effort and loss, is it right that I just need to flash system.img and vendor.img and that's ok? boot.img is tempered with magisk, if not necessary I prefer not to re-flash it. For vbmeta IMGs I don't know if I need them flashed, in order to flash the same system as the one already running in the phone.
Read first:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Really read it first. Before you flash anything via fastboot.
IDK what you should do to retrive your device. But read the link above...
xtcislove said:
Read first:
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Really read it first. Before you flash anything via fastboot.
IDK what you should do to retrive your device. But read the link above...
Click to expand...
Click to collapse
Yeah I read this, and I see IMGs in the payload, that's some of the IMGs I plan not to flash until necessary
Hi, I did something stupid and need some help please.
I got the bootloader unlock code for my KB2007 - Unlock went well, no issues.
Then I proceeded to download and install the latest official TWRP - Also no issues, I was in the custom recovery, created some backups etc.
After that, I followed the instructions to install Lineage OS as posted here:
Install LineageOS on kebab | LineageOS Wiki
wiki.lineageos.org
I flashed the dtbo and vbmeta partitions as instructed and proceeded with adb sideloading the copy-partitions-20220613-signed.zip file - Somewhere around here is where things went south.
I was not able to access/read my data partition anymore, and attempted to flash the lineage-recovery. After a reboot, I'm now stuck in the bootloader (fastboot). When I select Recovery mode, the phone just goes black. I also can no longer "fastboot boot twrp.img" - Error: "Failed to load/authenticate boot image: Load Error".
After checking the guide one more time I noticed it says the device has to be on Android 12, which mine was not (it was still in factory condition - Android 11). So that was likely the problem.
So now the big question is can I recover from this state? If yes, what's the best way to do so?
Thanks so much!
FreeDee said:
Hi, I did something stupid and need some help please.
I got the bootloader unlock code for my KB2007 - Unlock went well, no issues.
Then I proceeded to download and install the latest official TWRP - Also no issues, I was in the custom recovery, created some backups etc.
After that, I followed the instructions to install Lineage OS as posted here:
Install LineageOS on kebab | LineageOS Wiki
wiki.lineageos.org
I flashed the dtbo and vbmeta partitions as instructed and proceeded with adb sideloading the copy-partitions-20220613-signed.zip file - Somewhere around here is where things went south.
I was not able to access/read my data partition anymore, and attempted to flash the lineage-recovery. After a reboot, I'm now stuck in the bootloader (fastboot). When I select Recovery mode, the phone just goes black. I also can no longer "fastboot boot twrp.img" - Error: "Failed to load/authenticate boot image: Load Error".
After checking the guide one more time I noticed it says the device has to be on Android 12, which mine was not (it was still in factory condition - Android 11). So that was likely the problem.
So now the big question is can I recover from this state? If yes, what's the best way to do so?
Thanks so much!
Click to expand...
Click to collapse
Restore to stock via MSM.
You must update to OxygenOS 12 before installing lineageos 19.1 or you will brick.
The lineagsos guide is wrong and I bricked my device by following it too.
For now, you can only unbrick it with msmtool.
[OP8T][OOS TMO KB09CB] Unbrick tool to restore your device to OxygenOS
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
Then OTA to OOS 12, then install LOS19.1.
Thanks guys! I was able to restore the device using the MSM tool
I intend to keep it on OOS 11 (and potentially flash LOS18.1), because KB2007 is the T-Mobile variant and based on what I read dual sim only works with OOS 11.
The problem is it is becoming increasingly difficult to find instructions (or even downloads) for anything but the very latest versions :/
FreeDee said:
Thanks guys! I was able to restore the device using the MSM tool
I intend to keep it on OOS 11 (and potentially flash LOS18.1), because KB2007 is the T-Mobile variant and based on what I read dual sim only works with OOS 11.
The problem is it is becoming increasingly difficult to find instructions (or even downloads) for anything but the very latest versions :/
Click to expand...
Click to collapse
You can also use KB2007 OOS 13 beta 1 which works with dual sims.
Rootk1t said:
You can also use KB2007 OOS 13 beta 1 which works with dual sims.
Click to expand...
Click to collapse
Thanks! Yeah, I also read about that, and it does indeed sound like a potential way to go.
Do you know if anyone has figured out yet what makes this "beta 1" special in that it allows dual sims? I think I also read it's no longer possible with beta 2.
FreeDee said:
Do you know if anyone has figured out yet what makes this "beta 1" special in that it allows dual sims? I think I also read it's no longer possible with beta 2.
Click to expand...
Click to collapse
As far as i know, it's still unknown what makes beta 1 work in dual-sim mode.