Hello all,
Coming from the Nexus 5 and OP6T (both rooted, TWRP and custom kernel), I will receive soon my OP7 Pro (after a replacement) so I am searching again for the most updated tutorial for rooting my phone.
So far, most of them applies to Android 9 (OOS 9) and it seems that the process is different for OOS 10.
I have some questions without answers yet:
1) Why flashing TWRP on an Android 10 device seems to be different that on Android 9?
For example, "fastboot flash twrp.img" doesn't work anymore (something like "invalid command").
2) What is the best, safest way to root OOS 10 on OP7Pro?
I have seen 2 methods: boot patch with magisk and modified twrp flash. Are there more methods working directly with Android 10?
3) Where can I find a working MSM Download Tool?
Is there one version per OP7 pro models (GM1910, GM1913, etc)?
Am I right that with this tool, it is impossible to really hard brick the phone?
Thank you for reading, don't hesitate to only provide me links with a little explanation
Related
Hey everyone,
Please pardon the nooby question. I am just confused about Android 10 and the new A/B partitions. I am currently running Android 9, fully rooted with TWRP. However, I am experiencing some slowdown and some app issues, I'd like to reset the phone and start over. I figured now would be a good time to upgrade to 10.
What is the status of root on Android 10? Is the procedure that same as previously? I just have a bit of information overload reading all the threads on here, I think it is confusing me further.
To clarify I would just like to run rooted stock Android 10.
Thanks a lot in advance, and pardon my ignorance!
To anyone who may be searching for the same information as me: My phone crashed last night so I flashed from 9 to 10, and rooted. No issues, no change in procedure.
Yes, the process is the same. Use LMSA to flash to the latest Android 10 version. Extract the boot.img of the stock ROM, and put it on the SD card of your device. Install magisk manager. Use the patch boot.img method to get a new, modified boot image. Use fastboot to flash the modified boot img, and you're in business.
More in depth instructions here.
I installed LineageOS 18.1 (Android 11) on my OP7P and want to boot (or flash) TWRP.
There is a lot of different information about the state of TWRP on Android 11.
I hope someone could clearify the following questions:
1. Does TWRP [3.5.2] support Android 11?
the release notes of 3.5.1 state that they "prepared a mini release before Android-11 support."
The release notes of 3.5.2 don't mention android 11 at all.
There are various people in the LOS18.1 thread that can boot twrp, so I assume there is some kind of (partial) support.
2. What if 'fastboot boot twrp.img' doesn't work?
For me I can't boot (or flash) TWRP (on LOS18.1).
So as the twrp/lineage os guide says I do:
fastboot boot twrp.img
Click to expand...
Click to collapse
It finished succesfull, but my phone stays in fastboot and doesn't reboot.
The TWRP guide says the following:
If fastboot boot command doesn't work you need to root your device and flash the TWRP installer (remember that flashing the TWRP installer you will lose the root).
Click to expand...
Click to collapse
I find this a very vague description; what do they mean with "doesn't work"?
(when I flash twrp it results in an unbootable phone, might be related to a/b partitions, but I have not enough knowledge of that)
3. Does TWRP work on encrypted phones?
I found various posts that suggest that TWRP doesn't work on encrypted phones.
I can't find any reliable source that supports that statement.
Twrp says this, but that doesn't clearify things at all.
I hope someone could give me some answers, or guide me to some reliable source so I can find it myself.
I find the documentation of LineageOS and TWRP lacking in that perspective.
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
lenigma1too said:
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
Click to expand...
Click to collapse
I also think there is no official TWRP for android 11, but twrp doesn't make this very clear in their docs.
Multiple people are claiming they are able to (at least) boot twrp on Android 11.
LineageOS 18.1 is Android 11 (but I will clearify the post).
Thank you for your reply
there is now a working TWRP version for Android 11.
Nebrassy version: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'
Hi,
After ignoring the notification to update to Android 11 for over a month, I finally gave in an tried the update today.
I normally run stock OOS ROM with TWRP and Magisk, and updates are always fairly simple, let the OS update, overwriting the recovery and losing root, plug in to the PC and just `fastboot boot` the TWRP image, and then flash TWRP and Magisk on the phone itself, and bobs your teapot.
Alas, Android 11 shat all over those plans. With all the news out about Android 12 being in Beta, I had forgotten that Android 11 was so new to OP7Pro. Correct me if I wrong, but TWRP doesn't seem to work, which was my first mistake, but now Magisk has moved to a "need to patch the boot.img" model, which I hadn't seen before?
Anyways, after attempting to patch my own boot.img, I can no longer boot anything; phone just gets past the bootloader unlocked warning, then reboots into recovery.
I panicked then and attempted to flash one of the flashable Android 10 images from Mauronofrio's thread, which I think made things worse; now it just reboots repeatedly.
Any help appreciated, thanks!
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
I managed to use the MSM Download Tool from the last time I bricked my phone, which got me back to a bootable Android 10. Not much worse in life than losing all my data but better than a brick.
mc_teo said:
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
(...)
Click to expand...
Click to collapse
You cannot
But we gladly do this for you (as I just did)! Remember that you can always report your own posts for any type of forum maintenance you may need.
At your service and stay safe!
Timmy
Forum Moderator
A fix for your failed patched boot.img is just flashing the stock boot.img.
For upgrading (official OTA) and keep root, after installation finishes don't reboot and go to magisk, select install to the inactive slot and reboot, after reboot your phone will have the lastest update without loosing root.
And the best way to restore your phone is using msmtool
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.