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 modified before it was cool.
Hi everyone, similar to my threads for OP3, OP3T, OP5, OP5T and OP6 as unbrick tools allow to (obviously) unbrick your phone but also to rollback to specific versions of Oxygen OS I decided to search for more and succeeded in that.
I linked to 9.0.11 , 9.0.6 and 9.0.5 packages shared by @iaTa in his thread and by @SpasilliumNexus in his AFH here, rest has been found and shared by me.
As the instructions and Qualcomm drivers are already available here , I don't feel a need to rewrite them.
You can ask questions here on how to use and issues, however I might not be able to answer immediately.
Here are the files uploaded on AndroidFileHost ordered by Android version:
ANDROID 9:
OOS 9.0.4
OOS 9.0.5
OOS 9.0.6
OOS 9.0.11
OOS 9.0.12
OOS 9.0.13
OOS 9.0.15
OOS 9.0.16
ANDROID 10:
OOS 10.3.0
OOS 10.3.2
OOS 10.3.5
OOS 10.3.7
OOS 10.3.8
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
Notes for T-Mobile version owners:
It is possible to use Pie EDL packages with patched tool made by @AnonymousTipster available at https://drive.google.com/open?id=1dYuVxnf_J97KPrRt6KEBOjau1BRvtnJQ (download link come from his thread ).
According to @fullofhell , the commands "fastboot erase modemst1" and "fastboot erase modemst2" will turn off SIM lock definitely and allow OEM unlock option to stop being greyed out in developer options (behaviour introduced in OOS versions superior to 9.0.11). That will allow to unlock bootloader and then root/flash custom roms.
Credits:
@Titokhan for giving advice on how to present thread
@headsh0t95 for suggesting me to request an access to upload files on AndroidFileHost
@AndroidFileHost for the hosting
OnePlus for the device and OS
Some_Random_Username said:
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 modified before it was cool.
Hi everyone, similar to my threads for OP3, OP3T, OP5, OP5T and OP6 as unbrick tools allow to (obviously) unbrick your phone but also to rollback to specific versions of Oxygen OS I decided to search for more and succeeded in that.
I managed to find out 9.0.12 one (which is as of writing the latest available) but also the first one released for OOS 9.0.4 and linked to 9.0.11 , 9.0.6 and 9.0.5 packages shared by @iaTa in his thread and by @SpasilliumNexus in his AFH here
You can find instructions and Qualcomm drivers here.
This is not a support thread: if you have questions on how to use tool or issues please ask in the relevant thread.
Here are the files uploaded on AndroidFileHost ordered by Android version:
ANDROID 9:
DECRYPTED OOS 9.0.12
DECRYPTED OOS 9.0.11
DECRYPTED OOS 9.0.6
DECRYPTED OOS 9.0.5
DECRYPTED OOS 9.0.4
Click to expand...
Click to collapse
Decrypted. Wot?
ZeroKool76 said:
Decrypted. Wot?
Click to expand...
Click to collapse
Decrypted meaning no longer protected by passwords sorry for the confusion but if you take a look at the previous threads I made you might notice that some of the files are still password protected as OnePlus support don't give you these files already decrypted when they remote to your computer to help you to unbrick your phone -which is quite understandable as they allow to bypass Google Factory Reset Protection-.
Some_Random_Username said:
Decrypted meaning no longer protected by passwords sorry for the confusion but if you take a look at the previous threads I made you might notice that some of the files are still password protected as OnePlus support don't give you these files already decrypted when they remote to your computer to help you to unbrick your phone -which is quite understandable as they allow to bypass Google Factory Reset Protection-.
Click to expand...
Click to collapse
Awesome. Thank you for the clarification
Added 9.0.13 unbrick tool
Guys i am not that experienced on this stuff. I've bricked my 6t and dont have access to a windows computer. either mac or linux only. Anyway to run this on mac or linux?
Some_Random_Username said:
Added 9.0.13 unbrick tool
Click to expand...
Click to collapse
Where is it?!
gasroca said:
Guys i am not that experienced on this stuff. I've bricked my 6t and dont have access to a windows computer. either mac or linux only. Anyway to run this on mac or linux?
Click to expand...
Click to collapse
The tool is sadly Windows only but you could try to setup a virtual machine with USB passthrough
kermex said:
Where is it?!
Click to expand...
Click to collapse
In the first post perhaps?
Some_Random_Username said:
The tool is sadly Windows only but you could try to setup a virtual machine with USB passthrough
In the first post perhaps?
Click to expand...
Click to collapse
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Some_Random_Username said:
In the first post perhaps?
Click to expand...
Click to collapse
That DECRYPTED OOS 9.0.13 link?
Anyone ever come across an open beta msm? And FYI, if you copy Anon tipsters patched msm factory.exe to this tools working directory, it works.
Thanks man
gasroca said:
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Click to expand...
Click to collapse
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
kermex said:
That DECRYPTED OOS 9.0.13 link?
Click to expand...
Click to collapse
Yes
fullofhell said:
Anyone ever come across an open beta msm? And FYI, if you copy Anon tipsters patched msm factory.exe to this tools working directory, it works.
Click to expand...
Click to collapse
As far as I know OnePlus doesn't provide any open beta msm tool. Anon tipsters patched msm factory.exe will indeed work however as written here 9.0.11 version must be used if user wish to unlock bootloader as later versions of OOS closed the loophole that allowed T-Mobile owners to do so
Some_Random_Username said:
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
Click to expand...
Click to collapse
Yeah thanks. I've managed to fix it after almost 2 days of messing about with it its now back to normal ?
Some_Random_Username said:
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
Yes
As far as I know OnePlus doesn't provide any open beta msm tool. Anon tipsters patched msm factory.exe will indeed work however as written here 9.0.11 version must be used if user wish to unlock bootloader as later versions of OOS closed the loophole that allowed T-Mobile owners to do so
Click to expand...
Click to collapse
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
gasroca said:
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Click to expand...
Click to collapse
If u haven't fixed yet, your partitions are derped. Power off and run msm. Or just run a fastboot rom to fix. When that happens just msm, it's the quickest. And if u do as I explained above u can just use the newest msm and not have to upgrade..
fullofhell said:
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
If u haven't fixed yet, your partitions are derped. Power off and run msm. Or just run a fastboot rom to fix. When that happens just msm, it's the quickest. And if u do as I explained above u can just use the newest msm and not have to upgrade..
Click to expand...
Click to collapse
facts tho i prefer fastboot method, just remove the windows related **** from the bat and copy paste.
@fullofhell where is your repo
xstefen said:
facts tho i prefer fastboot method, just remove the windows related **** from the bat and copy paste.
@fullofhell where is your repo
Click to expand...
Click to collapse
Yeah that's what I do
---------- Post added at 09:09 PM ---------- Previous post was at 08:27 PM ----------
I made a bunch of scripts for Debian bases distros.. i use newest pop os...wonder if we could port msm over somehow...lol
fullofhell said:
Yeah that's what I do
---------- Post added at 09:09 PM ---------- Previous post was at 08:27 PM ----------
I made a bunch of scripts for Debian bases distros.. i use newest pop os...wonder if we could port msm over somehow...lol
Click to expand...
Click to collapse
I typically run Arch or a derivative but its all the same, I'd help with whatever I could.
fullofhell said:
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
Click to expand...
Click to collapse
Just to be sure, that engineer mode can be accessed from *#808# and SIM lock section is when swiping to the right, in "Others column"? It is like that on my 5T (see screenshot) but I don't know if it's same on a converted 6T
Related
This thread is strictly for info regarding Root/Twrp/Roms
If you have any ideas or have tried anything please post here
I AM IN NO WAY A DEV ,i am using google and common sense
Here is the link to the sprint boot.img (https://drive.google.com/file/d/0B9Vkl8ldvnNdOGlyLW4wOXNDRUk/view?usp=drivesd)-Thanks to @XirXes
Heres what i have tried
-So far i have tried signing the sprint boot.img to magisk with no luck,it gives me files are read only errors.I was able to get past the the first two steps of this post for systemless root via adb (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
-Flashing the stock sprint boot.img to confirm compatibility hint hint its compatible
ROOT HAS BEEN ACHEIVED!!
UPDATE- As of 9/13/17 we now have root in the form of a patched boot.img thanks to @themustached for patching the boot.img so gracefully for us
To install the boot img you need to reboot to fastboot and run the command "fastboot flash boot (name of boot.img).img
https://drive.google.com/file/d/0B8kodjBRTHoZR2Zob1VLX0xOVkU/view?usp=sharing
Just a update as I have been away from this phone for a bit
We have kernel source now (like 2 months ago) and there are 3 AOSP ROMs that I know about being worked on so far I don't know any details or anything but what I do know is that they completed the build process they are working on getting it running on our phone
joemossjr made the the ncp Rom and got TWRP for us so big thanks to him!
Substratum works on legacy with root and newest version of TWRP just in case anyone was wondering.
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
joemossjr said:
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
Click to expand...
Click to collapse
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
altimax98 said:
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
Click to expand...
Click to collapse
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
I have insurance and I'm willing to risk my device worst case,it's not a problem,I've noticed if you boot it,it doesn't like to set correctly
joemossjr said:
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
Click to expand...
Click to collapse
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Downloaded them all found no recovery
Verified ATT & Sprint boot.img works om Tmobile
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
bart bart said:
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
Click to expand...
Click to collapse
We are all in this situation. It is likely going to be quite some time before we get root due to the dual partition system.
Based on the Pixel info, we need TWRP first
Sent from my Moto Z (2) using Tapatalk
The recovery is in the boot.img of 7.1 and up devices
Dumper US Cellular Boot.img
altimax98 said:
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Here is dumped boot.img of US Cellular Boot.img. There is a recovery under sbin folder. Hopefully you can make a bootable TWRP from it?
https://www.dropbox.com/s/hjfr8wj2da...ootus.zip?dl=0
If anyone wants to join our efforts the let us know and we can add you in
I want to join your efforts.
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
joemossjr said:
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
Click to expand...
Click to collapse
Thank you
Sent from my SM-N930F using XDA-Developers Legacy app
Deleted
Any progress? Anything I can do to help? I have T Mobile variant with unlocked bootloader.
We brought in another guy from the pixel forum who made their twrp recovery he's going to take a look and see what can be done
Question before I delve further.
fastboot -i 0x2b4c flash:raw boot <kernel> [ <ramdisk> ] rather than just flash <partition> [ <filename> ] perhaps for the twrp? Just a spit ball idea as I wrap my head around. Been a few years since I bothered with phones rather than.. other systems. I'm sure this round probably already been tried but curious of the turn before I fry the new toy xD.
joemossjr said:
If anyone wants to join our efforts the let us know and we can add you in
Click to expand...
Click to collapse
I can test stuff when the time comes.
I am not responsible if you break your phone in any way, these are here for your aid. I will help as much as i can, but it is on YOU, the user to read the OP and understand exactly what it is you are doing at ALL times.
READ THIS: http://mata.readthedocs.io/en/latest/ LEARN FROM IT, DONT EVEN CONTINUE UNLESS YOU HAVE READ THIS
These can be used to return to 100% stock as long as you can get into fastboot mode on the device, and have unlocked the bootloader and critical partitions. All images contained in the zips are directly from the essential Fastboot zips and OTA's, and dumps for the rest
Prerequisites:
1. Working fastboot environment in bootloader: (test using the command fastboot devices should return your s/n) Windows drivers are at the bottom of the OP.
Essentials windows drivers contain working ADB/Fastboot and places an environment variable to link to these binaries, i would HIGHLY recommend ditching any and all adb/fastboots you may have (minimal, HTC, etc) and use what is supplied by essential, they just work (Not gonna help you either if your hellbent on using your adb/fastboot).
The zips contain all the firmware (19 Images), TWRP11.img (the latest version), and a stockboot.img (so you can conveniently place on your phone and flash in twrp) when rooting with magisk, and boot.fix.red.img (In case you kill verity).
2. Bootloader unlocked: run the command fastboot flashing unlock in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock will relock the bootloader. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
3. Critical partition unlocked: run the command fastboot flashing unlock_critical in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock_critical will relock the critical partition flashability. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
4. Common Sense: Use IT!!!!!
Downloads
Android 10 BTS Folder: https://sourceforge.net/projects/mata-bts/files/10
Q Beta BTS Folder: https://sourceforge.net/projects/mata-bts/files/Q-Beta/
Pie BTS & Novendor Folder: https://sourceforge.net/projects/mata-bts/files/Pie
P Beta BTS: https://sourceforge.net/projects/mata-bts/files/P-Beta/
Oreo BTS & NOVENDOR: https://sourceforge.net/projects/mata-bts/files/Oreo/
The Files below are OLD as dirt BTS
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
OPM1.170911.130 mega.nz (oreo 8.0 beta)
NMK32F AFH (latest nougat 7.1)
NMJ88C mega.nz (nougat 7.1)
NMJ51B AFH (nougat 7.1)
NMJ32F AFH (nougat 7.1)
NMJ20D mega.nz (nougat 7.1)
NMI81C AFH (nougat 7.1)
Drive Folder of Patched Essential Boot images Credit Goes to @dazeone
Some OLD AS DIRT Novendor zips aswell... if anyone still cares
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
Windows Drivers
drivers
Unzip this and check out the flash-all.[bat,sh] scripts for win/lin (they're identical but provided for easier flashability).
They're set up to flash to both slots. Most people will want to do this on a back to stock mission, but they can be adjusted if your goal is something else.
If coming from some other rom, you're also going to want to wipe your data, or you're not going to boot. This can be accomplished by the command in the bootloader: fastboot -w keep in mind there are multiple scripts to wipe for you in the zips.
These can also be used to make custom roms/rooted boot images/etc too, so have fun with it!
Thanks:
@invisiblek - aer0zer0 stole his thread, he put most of it together
@aer0zer0 - i stole the thread from aer0, his 2yr old son makes more use of the PH-1 than he does.
@bmg1001 - Root thread, found here root
@dazeone - Provides independent patched boot images and has an awesome YouTube Channel of Guides! DazeOne Youtube Channel
Enjoy
Heck ya
Yesssss
Ill be giving this a shot in a few days hoping to return my phone back to complete stock.
Hot diggity... been fun reading/watching you all work on this through Discord, think I'll go ahead and unlock it while I still have my S8 in case I trash things
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
vekenti said:
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
Click to expand...
Click to collapse
Lineage okay for you lol?
You've got one of the top devs on Lineage working on this so I think you're good.
Thank you! I'll be rooting now that we have a safety net!
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
invisiblek said:
So as we're still waiting for Essential to release official factory images, I thought it'd be helpful to link the dumps that we've produced. These can be used to return to 100% stock as long as you can get into fastboot mode on the device.
Click to expand...
Click to collapse
Thanks for this. My fingerprint sensor was not working for some reason after rooting and I thought i would go completely stock. This thread helped me to go completely stock and get the fingerprint back to working.
Thought I haven't locked the bootloader yet. Will try it later.
---------- Post added at 05:55 AM ---------- Previous post was at 05:48 AM ----------
sarcoptic said:
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
Click to expand...
Click to collapse
For flashing to critical partition you need to unlock them. The command is similar to unlock boot-loader.
Code:
fastboot flashing unlock_critical
And to lock it again
Code:
fastboot flashing lock_critical
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
sarcoptic said:
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
Click to expand...
Click to collapse
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Freaking rockstar thanks!
invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Thanks mate.
Thanks for the dump! Just yesterday I was trying to figure out how to do the adb backup command but I gave up cause I couldn't get a good reliable connection to my phone (driver issues, then to failed to connect to device, then to using the adb shell and a mouse on recovery, fun times.)
Great
please can someone guide on how to root it
chambar said:
please can someone guide on how to root it
Click to expand...
Click to collapse
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
charlie.s said:
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
Click to expand...
Click to collapse
Much appreciated, indeed dunno how i missed it.
free XDA points for @invisiblek .......Thanks for putting it all together, hopefully you can get a teiko sports watch when you turn all the points in, LOL
Seriously, thanks for putting it all together
Hello Huawei Honor Note 10 owners,
I've been asked by a member of the xda community to create a short and brief tutorial how to get the ROOT installed on this magnificent device. As many of you know, Huawei are not exactly very friendly releasing the unlock method for a bootloader since earlier this year, so we must be looking for other ways how to get it done ourselves.
So here we go:
1) UNLOCK THE BOOTLOADER
The only official way how to get the bootloader unlocked right now, is to pay for this type of service. I had my unlock code delivered fairly fast from the following website:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
There are 2 options there, a slow one for $20 and a fast one for $23. Naturally I voted for the faster one to have my device unlocked as soon as possible. Main thing is: it works! Here are the steps how to get the bootloader unlocked for Huawei honor note 10:
a) Go to Settings -> About Phone or Settings -> System -> About Phone and tap on build number 7-8 times. You will see a message “You are now a developer”. At this point head back to Settings and you will see an option called Developer Options. Enable USB debugging on your device now.
b) download and install 15 seconds adb installer on your laptop/PC (ideally running Windows), get the file from here:
https://androidmtk.com/download-15-seconds-adb-installer
c) to ensure you have the correct drivers running for your smarthpone, you might want to install Huawei's HiSuite software found here:
https://consumer.huawei.com/minisite/HiSuite_en/
d) download the following zip package platform-tools_r28.0.1-windows from the source here:
http://mirrors.zzu.edu.cn/android/repository/?C=M;O=D
e) boot your phone into fastboot/bootloader mode.
Make sure the phone is turned on and connect it to computer using usb cable.
Open command prompt/power shell pressing SHIFT+right click (touchpad or mouse) on Windows. It will be a dark blue command screen. You must execute this step inside the platform-tools folder from step d)
Type in the following line: adb reboot bootloader. Your phone reboots to fastboot mode in a few seconds.
Now type in another line: fastboot device. Your phone will be listed as a combination of letter and numbers.
Last line to type: fastboot oem unlock **********. The stars represent your unique unlock code that was given to you from the website above.
You will see a warning message about Unlock Bootloader, use Volume buttons to navigate to Yes (highlighted in red) and Power button to select Yes.
Your device will now reboot, wipe all data and then boot back into Android. Your Note 10's bootloader has been just unlocked, congratulations!
2) FLASH TWRP recovery to HUAWEI HONOR NOTE 10
a) first you need to download the following apk as listed by bark1234: https://1drv.ms/u/s!AizwhfImY2xzgadtepfbKJ1BQqxMvg
You can open it up using winrar and just extract the twrp.img file from it. Keep this file as it is the actual TWRP. It is important that you move the twrp.img file in the platform-tools folder, don't skip this step!
b) Turn off your phone. Press and hold Power + Volume Down until you see a fastboot screen.
Or you can also boot into fastboot mode while device is on. Just connect the phone to laptop/PC using usb cable. Open command prompt/power shell from within the platform-tools folder and execute the following lines:
type the familiar line: adb reboot bootloader
next line to type: fastboot flash recovery_ramdisk twrp.img. You will see that command executed successfully in matter of second.
last line to type: fastboot reboot. As soon as you execute this last command line, remove the USB cable and keep pressing Volume UP, so the device will boot to TWRP. If you don't do it quickly enough, your phone just reboots back to system. But no worries, TWRP is already there!
3) ROOT HUAWEI HONOR NOTE 10
a) download the latest stable Magisk zip file from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
Have it ready there, make sure to keep it on your phone's internal memory under one of the folders (I kept it under Downloads folder).
b) Switch off your phone and reboot it by holding volume up + power button. You will boot into TWRP recovery. Be patient there, you might want to hold both buttons for a good while until you see the TWRP screen.
NOTE: In my case the TWRP was encrypted, because I had my lock screen password active (under security settings in system). To bypass this, I just switched lock screen feature completely off. This way TWRP stopped asking for the password and I could proceed with flashing procedure without a problem.
c) Once you're inside TWRP, just locate the Magisk zip file and flash it. Just like that. Then you can reboot back to system.
d) download the Magisk file manager from the same source where you download the Magisk zip file: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now you're rooted:good:
IMPORTANT NOTE: I will not be held responsible if anyone bricks their HUAWEI HONOR NOTE 10 following this tutorial. It works for me, hopefully it will work for you, too.
Anyone has already tried that?
The site does not look very serious to me.
In addition, I would wait until there is an official firmware if something goes wrong.
I have ordered from https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below and got the code in 3-4 hours. though i ordered 1-20 mins one, buts thats okay.
Finally i can confirm the mentioned website works for bootloader unlock code.
letschky said:
Anyone has already tried that?
The site does not look very serious to me.
In addition, I would wait until there is an official firmware if something goes wrong.
Click to expand...
Click to collapse
I was able to achieve all of the above. I understand your concerns about that website's appearance. But... the unlock code works. You can pay per PayPal in case things go south.
You can download official firmware online. The latest one I was able to locate and download was the 125 build version. Although admittedly I haven't tested that version...
For now my phone is rooted, running on the latest 132 build?.
P. S. I can only imagine there will be "more trustworthy" bootloader unlocking service available in some time. And hopefully cheaper, too. Right now this is the next best thing and for those ones who are impatient to wait (like myself) can benefit from it.
Hope this helps?.
bark1234 said:
I have ordered from https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below and got the code in 3-4 hours. though i ordered 1-20 mins one, buts thats okay.
Finally i can confirm the mentioned website works for bootloader unlock code.
Click to expand...
Click to collapse
Thanks for the confirmation. Feel free to root the beast now?
Now successfully Rooted. Thanks a lot guys. all because of xda camaraderie.
And i was able to get full rom 125 package. Yes i downloaded it from http://androidhost.ru/41z, so be careful while flashing, i haven't tried it yet.
Here : https://1drv.ms/u/s!AizwhfImY2xzgag8-DCUTfaIvpWcCw
7gismo said:
I was able to achieve all of the above. I understand your concerns about that website's appearance. But... the unlock code works. You can pay per PayPal in case things go south.
You can download official firmware online. The latest one I was able to locate and download was the 125 build version. Although admittedly I haven't tested that version...
For now my phone is rooted, running on the latest 132 build.
P. S. I can only imagine there will be "more trustworthy" bootloader unlocking service available in some time. And hopefully cheaper, too. Right now this is the next best thing and for those ones who are impatient to wait (like myself) can benefit from it.
Hope this helps?.
Click to expand...
Click to collapse
ok thanks
i know ,i come from the Honor Note 8 and Unlock with DC Unlocker.
23 USD it´s ok ,you can always use the code.
Where did you find the B125 firmware?
---------- Post added at 02:53 PM ---------- Previous post was at 02:41 PM ----------
bark1234 said:
Now successfully Rooted. Thanks a lot guys. all because of xda camaraderie.
And i was able to get full rom 125 package. Will share onedrive link in few hours.
Click to expand...
Click to collapse
One Question,after unlock Bootloader delete that all Data (Factory Reset)?
letschky said:
ok thanks
i know ,i come from the Honor Note 8 and Unlock with DC Unlocker.
23 USD it´s ok ,you can always use the code.
Where did you find the B125 firmware?
Click to expand...
Click to collapse
I'd be careful flashing it (haven't tried it myself), but here's the source:
http://androidhost.ru/41z
Androidhost.ru offers 3 firmware versions for Note 10, with an exception of the latest one. But I believe there's the 132 build floating somewhere around Chinese forums, but that's beyond my powers, as it requires creating accounts and point systems and so on...
And yes, bootloader unlock wipes your data, so you'll be back to a fresh system. Just make a backup from the system settings beforehand and you'll be good. Worked for me?.
7gismo said:
I'd be careful flashing it (haven't tried it myself), but here's the source:
http://androidhost.ru/41z
Androidhost.ru offers 3 firmware versions for Note 10, with an exception of the latest one. But I believe there's the 132 build floating somewhere around Chinese forums, but that's beyond my powers, as it requires creating accounts and point systems and so on...
Click to expand...
Click to collapse
Thank you Downloading..
letschky said:
Thank you Downloading..
Click to expand...
Click to collapse
No problem at all. Please keep us posted in case you decide to play with that firmware...
Cheers ?
7gismo said:
No problem at all. Please keep us posted in case you decide to play with that firmware...
Cheers ?
Click to expand...
Click to collapse
I just need them as security if something happens, but I'll do it tomorrow
---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------
ok now I have bought the unlock code, 1-20min for 23usd
letschky said:
I just need them as security if something happens, but I'll do it tomorrow
---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------
ok now I have bought the unlock code, 1-20min for 23usd
Click to expand...
Click to collapse
Good stuff. Keep us updated whether it works for you or not, when you get a chance. Thanks?.
SmartPhonesFan said:
So guyz who is rooted what can you do now ? what can be done better? can you change build.prop? from china to EU ?
Click to expand...
Click to collapse
To be honest, I'm not sure if i want to go that far as I'm OK with the way I have things setup right now... perhaps the others who rooted their Notes can be of more help?
bark1234 said:
Now successfully Rooted. Thanks a lot guys. all because of xda camaraderie.
And i was able to get full rom 125 package. Yes i downloaded it from http://androidhost.ru/41z, so be careful while flashing, i haven't tried it yet.
Here : https://1drv.ms/u/s!AizwhfImY2xzgag8-DCUTfaIvpWcCw
Click to expand...
Click to collapse
Thanx for the faster Download!
---------- Post added at 10:01 AM ---------- Previous post was at 09:50 AM ----------
7gismo said:
Good stuff. Keep us updated whether it works for you or not, when you get a chance. Thanks.
Click to expand...
Click to collapse
Ok,i test it in 2-3 Hours and give the Feedback.
Ok,what i test.
Unlock Bootloader works.
Twrp works
Downgrade failed from 132 to 125 at 99% bit it shows in Settings-Phone Info 125
Update to 132 works
Update via Hi Suite from 125 to 132 works
Back to Stock with eRecovery to 132 works.
Root not testing but later
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
Update:Bootloader is locked if you downgrade from 132 to 125!Unlock again.Phone Locked,not Relocked.So original condition that's good
Uploading the Full 132 Rom maybe you can do something with it,it is from Hi Suite Update
letschky said:
Ok,what i test.
Unlock Bootloader works.
Twrp works
Downgrade failed from 132 to 125 at 99% bit it shows in Settings-Phone Info 125
Update to 132 works
Update via Hi Suite from 125 to 132 works
Back to Stock with eRecovery to 132 works.
Root not testing but later
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
Update:Bootloader is locked if you downgrade from 132 to 125!Unlock again.Phone Locked,not Relocked.So original condition that's good
Uploading the Full 132 Rom maybe you can do something with it,it is from Hi Suite Update
Click to expand...
Click to collapse
Thanks a lot for all the input, much appreciated!. When you say your bootloader got locked again, can you actually reuse the unlock code over and over again if you want to have the bootloader unlocked again, is that correct? I just wonder if we have to unlock the bootloader again in case there's a future update released from Huawei to a newer build (higher than 132).
ProCam said:
Could you provide some screenshots from Root Checker and Magisk as proof?
Click to expand...
Click to collapse
See 4 screenshots attached
7gismo said:
Thanks a lot for all the input, much appreciated!. When you say your bootloader got locked again, can you actually reuse the unlock code over and over again if you want to have the bootloader unlocked again, is that correct? I just wonder if we have to unlock the bootloader again in case there's a future update released from Huawei to a newer build (higher than 132).
Click to expand...
Click to collapse
yes the bootloader code can be used again and again
ProCam said:
Nice thx ill be the receiving the phone in a few days and was kinda bumbed out when i found out it couldn't be unlocked/rooted. its gonna cost me a little but i will be worth it for use with adaway, viper4android and luckypatcher etc.
Click to expand...
Click to collapse
Just for your information, viper4android will not run on any Huawei device from EMUI 8 and above due to 64bit audio drivers only, viper4android runs on 32bits. Just tested all versions myself listed under Magisk modules and all of them fail on driver needs to be reinstalled message
Now that we can unlock we need a port of the AOSP from openkirin.net.
Unfortunately, beyond my pay grade. An alternate OS is what this device needs outside of china.
Edit before publishing: I started writing this for all variants other than sprint, but I'll now make a separate thread for variants that have kdzs and those that don't, otherwise this will be a mess.
Firstly, keep in mind that no one is responsible if you end up bricking your device! There is currently no way to recover from a hard brick other than sending your phone in for repair, so make sure you follow every single step carefully if you wish to proceed!
Additionally, flashing an xbl through DD may not pass randomly even if it appears that it has worked, so be aware of the risks. Only at&t users will need to flash the xbls anyway since that is the only variant other than sprint which does not have kdzs available.
Users with the AT&T variant who are stuck on pie: temp root only works on android 10, as such you will unfortunately not be able to bootloader unlock your device. The firehose may leak at some point in a few months, and you will be able to unlock (and update manually) if it does.
The process for unlocking bootloaders on models other than the sprint one (specifically At&t for this guide) is practically identical; however, it uses different xbl_config.img and xbl.img files, which need to be specific for your device from the pie firmware.
The version naming may not be the exact same for other models, but you just have to ensure that you are on the March patch or below. If you are on April, you can find the guide to switch slots and do so in order to revert to March. To STOP UPDATES, fully uninstall or disable the update center packages either with ADB or package disabler pro for LG, which you can easily find online.
So I repeat, you're going to follow the sprint g8 bootloader unlocking guide, but you have to use the xbl and xbl_config for your device rather than the ones provided in the sprint guide. The engineering abl is the same, but I'll include it here anyway so that you don't have to mess around with any of the files provided in the sprint g8 guide.
Now, steps that are to be ignored and steps that may differ slightly:
Keep in mind that I'm only mentioning what you should be aware of and what may be different, but you still have to follow the guide written by BrandonB1218 in general.
1a: Of course, you still need a vulnerable firmware, and sadly AT&T does not provide kdzs, so you cannot bootloader unlock if you are on the May patch.
You can Ignore this: I found that another method that most likely stops updates is following this guide on youtube. It's supposed to bypass frp lock, but it also gets by all the LG agreements you have to accept, so it will ask you to agree to these if you ever open up the software update option in settings and will probably not update if you don't.
2: Some people had issues with different versions of the mroot script, so try all of them before you come asking for help please. I also suggest that you just temp root without running the temp root magisk setup as you may end up bricking if you accidentally flash a module or make magisk flash a patched boot img (DO NOT FLASH ANYTHING OTHER THAN WHAT'S INCLUDED IN THE GUIDE).
I suggest running the backup script and the commands to make sure you're completely safe, but make sure you keep them separate because a lot of the partitions included in the commands that @BrandonB1218 mentioned are device specific and include your IMEI. The backup script should only backup the partitions that aren't device specific such as system, and this is probably the one you'll need if at all because you shouldn't be touching other partitions. STILL DO BOTH THOUGH
3a: Yes, you have to run the command to find out which slot you're on, but you will not flash anything from the pie or 20d sprint backup that's listed there, or else you will likely brick.
3b and 3c: This should all be the same: If your active slot is A, follow 3b, and if your active slot is B, follow 3c. The commands should also be the same, just with different files.
If your active slot is A, but the files included for your device are also named xbl_a.img, for example, you can just rename them to fit with the command.
Otherwise, you can just change this, for example,
dd if=/storage/emulated/0/Download/xbl_b.img of=/dev/block/bootdevice/by-name/xbl_b
to this:
dd if=/storage/emulated/0/Download/xbl_a.img of=/dev/block/bootdevice/by-name/xbl_b
You also need to flash the engineering laf, so either rename the file or change the command so it works. The link is embedded
Overall, its just important that you take the right file in the first part of the command and flash it to the correct partition of the correct slot in the second part.
If I remember correctly, the method to boot into fastboot is hold vol- and power until the screen goes black (while the phone is plugged into the computer) and then to let go of power as soon as that happens.
4a and 4b: You do not want to do either of these as the boot img and other partitions vary per variant. I unfortunately do not have the magisk patched At&t boot img, but you can patch it yourself from the backup you made and flash it. It might be good to do this beforehand, but you could also just temp root again and dd flash it.
Alternatively, you can flash the metaphysics 1.7 kernel with twrp and magisk included, but you still have to follow the rest of the twrp installation in the sprint g8 bl unlocking guide. TWRP is the same for all US variants.
Congrats! You should now be bootloader unlocked and ready to go at this point. If you ever find yourself unable to boot on the slot which DOES NOT have the engineering abl, you can always switch to the slot with the engineering abl, go to fastboot, and fastboot flash your backed up partitions.
Credits:
Obviously to BrandonB1218, for writing the sprint g8 bootloader unlocking guide
vl48 for basically answering all my questions and providing the needed files
j4nn for writing the temp root
Mr. Zhu for twrp
KamioRinn for metaphysics
Anyone else who contributed in telegram to get this to work!
Amazing! Can't wait to do this. I'll report back when I get this phone unlocked.
Thanks for taking the time.
Files can't be downloaded dead link
blumix said:
Files can't be downloaded dead link
Click to expand...
Click to collapse
No issues here
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Pietrobell86 said:
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Click to expand...
Click to collapse
No sorry. Not sure exactly what your problem is, but it might be solvable with root
Shtiff1 said:
No issues here
Click to expand...
Click to collapse
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
Click to expand...
Click to collapse
I am talking about the AT&T_G8.zip
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
@antintin zip not downloading, FYI
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
I can't find it, sorry. I'm on Verizon
Hey, thanks for the guide. I'm rather worried about trying this as LG's newer models are so darn easy to brick. AT&T variant has no LG Bridge support which is incredibly stupid. At least we have kind people like you helping us free our phones
My LG G8 is a secondary phone right now, and as such, I'm very interested in trying this out. Unfortunately, the download link for AT&T_G8.zip give me a 404.
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Espen115 said:
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Click to expand...
Click to collapse
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
antintin said:
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
Click to expand...
Click to collapse
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
lightningdude said:
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
Click to expand...
Click to collapse
Why would it have to be removed?... I'll just upload it when I get home and have time
antintin said:
Why would it have to be removed?... I'll just upload it when I get home and have time
Click to expand...
Click to collapse
Just out of consideration for space in your account, in case you were low on free space. I also didn't notice that it was a < 3MB file.
so is someone going to reupload the file or what? cant even download it from the op attachment.
does this even work with 20m or are those of us out of luck?
File Broken
Anyone has the copy of AT&t_G8.zip? Its 404 now.
MaemoToWindows said:
Anyone has the copy of AT&t_G8.zip? Its 404 now.
Click to expand...
Click to collapse
Always has been.
I have it but it won't let me add it
Can u email it to me? [email protected]
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
If flashing/rooting errors out, and you end up in Qualcomm Crash Dump Mode, please perform the following:
Restart into Fastboot Mode by holding Volume Down + Power buttons until the device vibrates, then release only the power button
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Follow the steps on this site to Flash the stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
If you have trouble rebooting to FastbootD (Recovery)
Try swapping Active slots from the application (typically slot A worked for me)
Choose reboot to FastbootD
Sorry if this is a stupid question, but is this to be used when the OP 10 Pro is ALREADY on OS 13, or is this to be used when the unit is on OS 12 (not yet rooted) and you want to take it to OS 13?
Thanks for your help.
Either or would be fine.
It's an upgrade using a full OTA update.
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Not yet, but once I find one I'll upload it ASAP for the community.
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
thanks. It would be nice. good work.
Hi there, do you have for C.22?
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
There is...check this out
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
linhdanstore said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Literally look above.
Savio Dantes said:
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
Click to expand...
Click to collapse
Can you use ADB tools to restore stock rom if the device was soft bricked?
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them in the first place becomes both forgotten and obsolete, that's when I typically stop supporting them.
Savio Dantes said:
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them becomes forgotten, an obsolete, after which I typically stop supporting them.
Click to expand...
Click to collapse
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
SKNIZZY said:
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
Click to expand...
Click to collapse
Yes it does.
Fastboot enhance works fine, you need to remove the cow files first and have a valid payload.bin but that's it