Related
Hello,
I couldn't unlock the bootloader as the OEM unlocking's disabled and i can't access system! Everything's erased!
Any help????
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
junglism93 said:
A bit more info might be helpful mate.
What did you do to arrive at the situation you are in?
Can your pc see your device via ADB and if so what are you using: latest platform tools or toolkit?
Can you boot to stock recovery or bootloader?
Without any of the above info its going to be extremely difficult for anyone to give any kind of answer.
Click to expand...
Click to collapse
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
eldeen said:
The device isn't recognized via ADB.
I can boot to Bootloader
The phone was working fine with the latest google stock android 10, i decided to lock the bootloader cuz the phone was getting overheated so i thought it'd be a good idea to lock the bootloader. Prior to do that, it asked me to erase everything! I erased everything and when i tried to reinstall the stock image it asked me to unlock the bootloader!!
The problem is that USB debugging isn't enabled and the phone is empty with no system!
Click to expand...
Click to collapse
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
junglism93 said:
Ouch! That's a right old situation you have there mate, with no OS installed a locked bootloader and no ADB function I'd have to say your phone is non recoverable!
Sorry mate but I can't see anyway out of that lot.
Maybe someone else a bit more knowledgeable might chip in but I'm deffo out of ideas.
Click to expand...
Click to collapse
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
eldeen said:
Thanks for help anyway,
But there must a solution to this! I mean my phone isn't under warranty and I'm willing to go for paid services to unlock the bootloader!
Click to expand...
Click to collapse
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
AndroidNazi said:
Try switching slots, assuming the pixel is an A/B device. Maybe you still have a bootable system in your other slot and I don't think you need an unlocked bootloader to switch slots
Click to expand...
Click to collapse
Thanks for help, but could you please show me how to do that?
eldeen said:
Thanks for help, but could you please show me how to do that?
Click to expand...
Click to collapse
Make sure you have the latest fastboot. On the bootloader your phone will either say "slot a" or "slot b" and you should type "fastboot --set-active=b" if you are on slot a or "fastboot --set-active=a" if you are on slot b
still didn't fix the problem... any probable solutions please?
Hi guys I have a OP 7 pro bricked (boot loop), I try everything to un bricked, that is why I ask for any help. I use msm tool and install several zips but when the tool finish it still have the same problem, I can access to the fastboot mode but my bootloader is locked, so I cannot try the fastboot method cause my pc won't recognize when I connect my phone in this mode (I think that's because I need to have enable usb debugging).
I've got bad news, if your bootloader is locked and MSM tool fails you will most likely have to send it in as it will no longer be easily fixable, I unfortunately had this same issue on my OnePlus 8 and learnt the hard way.
You said that you "cannot try the fastboot method" because your PC won't recognize your phone... did you install Oneplus fastboot drivers correctly? You should be able to access your phone in fastboot, even with bootloader locked.
Try with another PC too. Just my 2 cents, sorry if this doesn't help you...
lauchiebeans said:
I've got bad news, if your bootloader is locked and MSM tool fails you will most likely have to send it in as it will no longer be easily fixable, I unfortunately had this same issue on my OnePlus 8 and learnt the hard way.
Click to expand...
Click to collapse
Launchiebeans thanks for take your time to answer, where did you send it, did you repair yours
jonsat said:
You said that you "cannot try the fastboot method" because your PC won't recognize your phone... did you install Oneplus fastboot drivers correctly? You should be able to access your phone in fastboot, even with bootloader locked.
Try with another PC too. Just my 2 cents, sorry if this doesn't help you...
Click to expand...
Click to collapse
First thank you for your time.
I though that too, but i didn't do it , maybe is because I read that in order to use this method (fastboot), oem unlock and usb debugging have to be enable on my OP 7 PRO
Ps: today I'll try again whit another pc, maybe it works, I think the Qualcomm drivers, adb drivers and OP drivers are a nightmare, who knows how many I've been downloaded those in order to make everything right
Sorry for my English I'm from Costa Rica
Sounds like he is stuck o. The older firmware that don't recognize oem unlock command. Not doing the developer preview upgrade then Ota out to regular firmware. Kinda sounds like what I started out on this t mobile one
TheMadScientist said:
Sounds like he is stuck o. The older firmware that don't recognize oem unlock command. Not doing the developer preview upgrade then Ota out to regular firmware. Kinda sounds like what I started out on this t mobile one
Click to expand...
Click to collapse
Hi MadScientist do you hav the same prob? Didi you solved?. Like I said I think the fastboot method to unbrick doesn't work for me because we need to have oem unlock and usb debugging enable on the OP. I will use another pc to discard
Ps: don't know what you mean with "older firmware"
Since I don't remember what version of firmware I have I try the older 9.5.3 to 10... On oxigen. Even i read that someone resolve his problem installing the Chinese version (hidrogenOs) I don't remember the exact name
cirmendoza said:
Hi MadScientist do you hav the same prob? Didi you solved?. Like I said I think the fastboot method to unbrick doesn't work for me because we need to have oem unlock and usb debugging enable on the OP. I will use another pc to discard
Ps: don't know what you mean with "older firmware"
Since I don't remember what version of firmware I have I try the older 9.5.3 to 10... On oxigen. Even i read that someone resolve his problem installing the Chinese version (hidrogenOs) I don't remember the exact name
Click to expand...
Click to collapse
Nm I read your post wrong. I thought you just couldn't get oem unlock enabled
cirmendoza said:
Launchiebeans thanks for take your time to answer, where did you send it, did you repair yours
Click to expand...
Click to collapse
I Ended up sending it to OnePlus and the repair was free as it was a software issue.
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true
so, i was following the guide for the bootloader unlocking process and succeeded. rooting process is what bricked my phone, unfortunately.
i loaded the patched magisk image in to boot_a like it said, and hoping that everything would have went well, it did not.
now phone will not boot. recovery modeis broken. adb does not recognize my device, and i have no clue how to get to edl mode from there.
as far as im aware, there is no kdz for the lg v50 sprint variant. (v450) unfortunately.
can anyone help me?
i feel like im SOL
It's not my main phone, but I really like the cameras on it. Was just looking to rid it of lgs software.
Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel
@Vortex said:
Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel
Click to expand...
Click to collapse
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong
I didn't use the file for the g8.
Beefybeardedbear said:
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong
Click to expand...
Click to collapse
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb
@Vortex said:
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb
Click to expand...
Click to collapse
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.
Beefybeardedbear said:
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.
Click to expand...
Click to collapse
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm
@Vortex said:
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm
Click to expand...
Click to collapse
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?
Beefybeardedbear said:
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?
Click to expand...
Click to collapse
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting
@Vortex said:
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting
Click to expand...
Click to collapse
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now
Beefybeardedbear said:
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now
Click to expand...
Click to collapse
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.
@Vortex said:
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.
Click to expand...
Click to collapse
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.
Beefybeardedbear said:
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.
Click to expand...
Click to collapse
i also have oneplus 8. but bootloader is locked unless i get my phone sim unlocked. but thats after i pay off the phone
You just need to find a V50 Sprint device from another user or your friend, then backup all partitions, back them up, then flash to your device.
Note: ignore imei partitions
How would I flash it? Through fastboot and adb? I've already found one.
hello?
You flash them through fastboot by giving the following command:
fasboot [file name i.e abl_a] [file location]
Alternatively if you can go back to EDL/QFIL/9008 mode, you can load through the software
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Unfortunately, I haven't even tried. And I've given up. Going to chinese brands now. They are way easier to root and rom. Like oneplus and xiaomi. You could try the method above that a member mentioned.
geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Get KDZ Tools
unzip the kdz
look for abl_a.img abl_b.img laf_a.img laf_b.img xbl_a.img xbl_b.img xbl_config_a.img xbl_config_b.img
flash it on fastboot. If you have follow the guide to unlock, you should have backed up all these files.
hope this helps.
Hello,
I am trying to convert Tmobile OP9 to Global version and I am stuck at a basic step of getting the oem unlock code when trying to unlock the bootloader.
Details:
1. got my network unlocked from mobbdeep couple of weeks back.
2. Under Settings > "Network Unlock" status shows as unlocked
3. Installed the latest SDK as I am following the guide here to get the bootloader unlocked. When I boot in fastmode and run the oem command it stays at "waiting for device" and returns nothing.
Code:
fastboot oem get_unlock_code
When I run this, device list shows empty
Code:
adb devices
- Enabled USB debugging and stay awake options is checked from what I read on few posts
- When I restart the phone normally and then run "adb devices" it shows my phone listed
- Working on windows machine
What am I doing wrong here ?
TIA !!
PS: attached image shows the device state as Locked
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Superguy said:
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
Click to expand...
Click to collapse
Thanks for your response.
I tried that earlier assuming the same but it asked me to first flash the unlock token for which I am following the steps
I was however able to get the device listed after manually uninstalling/installing adb drivers
avid_droid said:
Check in device manager. If you have the yellow triangle on your phone in device manager just download android composite driver and update it through device manager/browse computer/ select unzipped folder and click OK.
Might be the issue
Click to expand...
Click to collapse
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
This thread was helpful as well. Thanks !
cass89 said:
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Click to expand...
Click to collapse
This thread was helpful as well. Thanks !
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
FRNK8 said:
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
Click to expand...
Click to collapse
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Hey thanks for the heads up. I will
Would infact first go through the conversion steps to go back to Tmo just incase things go south.
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Following the guide here, I just performed the bootloader unlock successfully. Per your suggestion, I want to backup the modem files before I proceed any further.
I cant seem to recollect how do I backup the modem files when I did the same conversion for OP6T. Can you please guide me here before I proceed with the next steps.
I tried installing the partitions backup but it wont allow me without root. I vaguely remember that I hadn't rooted my device the last time while backing up these files or is root needed ?
TIA !
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
craznazn said:
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
Click to expand...
Click to collapse
Can you help me with the steps to root ? Just want to be careful while doing so.
I saw some posts but that was related to the Tmobile OP9Pro(in my case its its Tmo Op9). The boot images were different so I didnt try to play around.
Thanks !
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
craznazn said:
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
Click to expand...
Click to collapse
Okay did this step.
Downloaded an copied stock image and the boot_patched image provided on the link and copied to my phones internal storage
Also as next step said, rebooted the phone
- went to Magisk app > install > selected boot_patched.img from internal storage
- phone restarted
- When I open the partitions backup app it still shows "device is not rooted" warning
What step did I miss ?
FRNK8 said:
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
Click to expand...
Click to collapse
do you have a link for the driver I'm having the same problem