Database Users

LG aristo 2 (K8 2018)

Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well

I just got this phone. Let me know how what happens please.

tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.

I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool

attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.

tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?

Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2

Hmm and you flashed the twrp that was for the aristo right?

Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?

you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?

The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.

I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.

Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.

We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.

The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?

@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App

brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.

brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?

Bricked my Chinese OP6t (A6010) and not sure what to do. Help??

I was trying to help a friend out by installing the international OS on his new OP6T (A6010) because I know a friend who did it a year or two ago and it worked perfectly. We thought it would work out but I couldn't get the firmware to install using the normal system update--it said that the firmware was lower than the currently installed firmware and therefore couldn't be installed.
So, I tried downgrading using the msm tool (I didn't realize the Chinese version was different...) and now it is stuck in a boot loop saying "build version and HW version is not match!"
What options do I have here? I didn't install TWRP (I was going to but tried the MSM tool because people were recommending it on many other sites...but were only talking about Tmobile and Global variants so I didn't realize Chinese was an entirely separate one).
Is there any way to fix this?

You can get it into fastboot right? I'd push the latest official fastboot ROM into it via ADB.

snatale1 said:
You can get it into fastboot right? I'd push the latest official fastboot ROM into it via ADB.
Click to expand...
Click to collapse
No, when I hold any combination of buttons, it gives me the error message. I can't do anything with it at the moment.
I got it to flash "fastboot mode" for a moment, but then the error message went up again and black screen.

That's weird, fastboot should be coming up before it tries to load the OS, you're going to be left with reflashing (in your case) HydrogenOS via download mode and MSM.

snatale1 said:
That's weird, fastboot should be coming up before it tries to load the OS, you're going to be left with reflashing (in your case) HydrogenOS via download mode and MSM.
Click to expand...
Click to collapse
Thank you for the information here with this. Are all msm things specific to certain firmwares or is it possible to throw a firmware into an msm thing? I'm not sure about this one yet.

I have a A6010 I have used this to go back to Android 9 with out issue.
https://androidfilehost.com/?fid=1395089523397966003

mchlbenner said:
I have a A6010 I have used this to go back to Android 9 with out issue.
https://androidfilehost.com/?fid=1395089523397966003
Click to expand...
Click to collapse
Thank you for your help here.
Unfortunately I keep getting the same message again and again in all of the msm tools I've tried: images do not match with the phone.
I'm not sure how I've done it but I've messed it up badly and now not sure how to fix it.

nightcow said:
Thank you for your help here.
Unfortunately I keep getting the same message again and again in all of the msm tools I've tried: images do not match with the phone.
I'm not sure how I've done it but I've messed it up badly and now not sure how to fix it.
Click to expand...
Click to collapse
You're going into download mode correctly right? Holding BOTH Vol buttons while then plugging into the USB cable thats already in your comp?

snatale1 said:
You're going into download mode correctly right? Holding BOTH Vol buttons while then plugging into the USB cable thats already in your comp?
Click to expand...
Click to collapse
Yeah, I was able to get it recognized by the computer and the msm software. It was just not accepting it.
I actually finally got it to work, though, but using the patched version of the msm tool that Tmobile users were using to install the international firmware, because it ignores the check for hardware/firmware matching and just forces the firmware on there.
It took two different msm tools/firmwares but finally it worked out. It was an incredibly relieving sight to see it boot up and not immediately go into the same bootloop again.

Glad to see you got it going.

Good day, please I got into the same issue of hardbrick on my oneplus 6t chinese variant. Please would you be kind enough to give a break down on how you got it to work. And were you able to finally install Oxygen OS?

[OP8T][OOS KB05AA/BA/DA] 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 modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, OP8Pro and OP Nord here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8T.
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
KB05AA tools (international firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.2
OOS 11.0.4.5
OOS 11.0.5.6
OOS 11.0.7.9
Mirror for first and last MSMs: https://onepluscommunityserver.com/
KB05BA tools (european firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.2
OOS 11.0.4.5
OOS 11.0.5.6
OOS 11.0.7.10
Mirror for first and last MSMs: https://onepluscommunityserver.com/
KB05DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.2
OOS 11.0.4.5
OOS 11.0.5.6
OOS 11.0.7.9
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Tips:
While crossflashing does not seem to break your /persist unlike on 8-series, it is advised that you back it up before attemting to do so as fingerprint reader may give an error related to enrollment issue. You can do so by using dd if=/mnt/vendor/persist of=/sdcard/persist.img (you must have root access, which is not something I'm going to explain here) and moving it to your computer/cloud.
Instructions:
Launch MsmDownloadTool V4.0.exe.
Windows 7 users may use MsmDownloadTool V4.0_Win7.exe instead, but it hasn't been tested.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using global tool or India while using indian tool or EU when using european tool.
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)
Power your device off.
Let it cool down for one minute.
Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
Wait some time (should not be longer than ~300 seconds).
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Credits:
@viperbjk for KB05AA and KB05BA OOS 11.0 files
@LLStarks for KB05AA OOS 11.0.1.2 file
@FullOfHell for testing 11.0 KB05AA tool and downgrade possibility
OnePlus for the device and OS

Will this work for the T-Mobile OnePlus 8T+ or only the unlocked version?
If it does work I guess I'll have to wait for my bootloader unlock code from OnePlus before doing this, or will this bypass it? (I'm already SIM unlocked but Everytime I try to request a Bootloader unlock code and press submit it tells me to enter a valid code, OP claims it's because it's not yet 45 days from when I purchased the device, which doesn't make sense)
#3 I don't see the link anywhere where I can download the MSM tool, it says download tool but does give a link
Thanks for your great work

SmileBigNow said:
Will this work for the T-Mobile OnePlus 8T+ or only the unlocked version?
If it does work I guess I'll have to wait for my bootloader unlock code from OnePlus before doing this, or will this bypass it? (I'm already SIM unlocked but Everytime I try to request a Bootloader unlock code and press submit it tells me to enter a valid code, OP claims it's because it's not yet 45 days from when I purchased the device, which doesn't make sense)
#3 I don't see the link anywhere where I can download the MSM tool, it says download tool but does give a link
Thanks for your great work
Click to expand...
Click to collapse
MSM tools don't care about bootloader lock status. So IF, and that's an IF until we hear otherwise, it works with our model, you won't need to be bootloader unlocked before running it.
I personally won't do anything until we also have the T-Mobile MSM tool as well.

NotATreoFan said:
MSM tools don't care about bootloader lock status. So IF, and that's an IF until we hear otherwise, it works with our model, you won't need to be bootloader unlocked before running it.
I personally won't do anything until we also have the T-Mobile MSM tool as well.
Click to expand...
Click to collapse
Assuming it works, will I be able to go with the version of the MSM tool from TMO to International OS or I'll need to wait for the TMO MSM tool and load the International OS into that MSM tool and get it done that way?

Great job getting hold of these, vouch!

SmileBigNow said:
Assuming it works, will I be able to go with the version of the MSM tool from TMO to International OS or I'll need to wait for the TMO MSM tool and load the International OS into that MSM tool and get it done that way?
Click to expand...
Click to collapse
Not sure. It wasn't possible with the 7T Pro because the device name was different (hotdog vs hotdogg). OP would be better able to answer this.

NotATreoFan said:
Not sure. It wasn't possible with the 7T Pro because the device name was different (hotdog vs hotdogg). OP would be better able to answer this.
Click to expand...
Click to collapse
I'd assume it's the same here as well, because recent years were always that the case and I'll be surprised if it's not the case here as well, so I guess I'll wait a bit longer for the T-Mobile MSM Tool

SmileBigNow said:
I'd assume it's the same here as well, because recent years were always that the case and I'll be surprised if it's not the case here as well, so I guess I'll wait a bit longer for the T-Mobile MSM Tool
Click to expand...
Click to collapse
We were able to convert the 7 Pro back and forth. Not sure about the 7T or 8.

NotATreoFan said:
MSM tools don't care about bootloader lock status. So IF, and that's an IF until we hear otherwise, it works with our model, you won't need to be bootloader unlocked before running it.
I personally won't do anything until we also have the T-Mobile MSM tool as well.
Click to expand...
Click to collapse
SmileBigNow said:
I'd assume it's the same here as well, because recent years were always that the case and I'll be surprised if it's not the case here as well, so I guess I'll wait a bit longer for the T-Mobile MSM Tool
Click to expand...
Click to collapse
@SmileBigNow you need to open the spoilers to see the download links
Additionally above files are strictly intended for unlocked units and cannot be used for conversion, however I got the file to unbrick T-Mobile variant as well, but I would prefer if someone could confirm it flash on their device before releasing it, feel free to DM me on here or Telegram (link on my profile). Note that I prefer latter.
If it works I will make a separate thread for it.
Edit 02:52 UTC: T-Mobile MSM tool is now live at https://forum.xda-developers.com/oneplus-8t/how-to/op8t-unbrick-tool-to-restore-device-to-t4180981/

Some_Random_Username said:
@SmileBigNow you need to open the spoilers to see the download links
Click to expand...
Click to collapse
The spoiler under MSM tool doesn't have a download link

droidgreg said:
The spoiler under MSM tool doesn't have a download link
Click to expand...
Click to collapse
You're looking at the wrong place, see https://i.imgur.com/c4rqhJy.png

Tested done 8T KB05BA . Thank sir

SmileBigNow said:
Will this work for the T-Mobile OnePlus 8T+ or only the unlocked version?
If it does work I guess I'll have to wait for my bootloader unlock code from OnePlus before doing this, or will this bypass it? (I'm already SIM unlocked but Everytime I try to request a Bootloader unlock code and press submit it tells me to enter a valid code, OP claims it's because it's not yet 45 days from when I purchased the device, which doesn't make sense)
#3 I don't see the link anywhere where I can download the MSM tool, it says download tool but does give a link
Thanks for your great work
Click to expand...
Click to collapse
I have the same issue. OnePlus reps couldn't wrap their head around that I'm already network unlocked... Kept saying I needed to wait the 45 days which is complete horse****. I had my 7t unlocked within a week and bootloader unlocked in 2. I get the same invalid unlock code error. Good God. They even tried to tell me "the unlock code TMO gave you is bad..." Like dude...I got the **** FROM THE PHONE ?*

zeusofyork said:
I have the same issue. OnePlus reps couldn't wrap their head around that I'm already network unlocked... Kept saying I needed to wait the 45 days which is complete horse****. I had my 7t unlocked within a week and bootloader unlocked in 2. I get the same invalid unlock code error. Good God. They even tried to tell me "the unlock code TMO gave you is bad..." Like dude...I got the **** FROM THE PHONE ?*
Click to expand...
Click to collapse
So did you attempt to use the MSM tool w/o unlocking the bootloader?

zeusofyork said:
I have the same issue. OnePlus reps couldn't wrap their head around that I'm already network unlocked... Kept saying I needed to wait the 45 days which is complete horse****. I had my 7t unlocked within a week and bootloader unlocked in 2. I get the same invalid unlock code error. Good God. They even tried to tell me "the unlock code TMO gave you is bad..." Like dude...I got the **** FROM THE PHONE ?*
Click to expand...
Click to collapse
Yeah, it doesn't even make any sense the 45 days wait, the 45 days is usually to get a SIM unlock from T-Mobile not a unlock code from OP, they are just coming up with stupid excuses

i keep getting "automatic detection of ddr failed"

jwarrior319 said:
i keep getting "automatic detection of ddr failed"
Click to expand...
Click to collapse
You have the T-Mobile exclusive variant as per your post in https://forum.xda-developers.com/on...ol-to-restore-device-to-t4180981/post83784625
You have to use the T-Mobile tool.

SmileBigNow said:
Yeah, it doesn't even make any sense the 45 days wait, the 45 days is usually to get a SIM unlock from T-Mobile not a unlock code from OP, they are just coming up with stupid excuses
Click to expand...
Click to collapse
Exactly... The OnePlus reps are getting especially ****ing retarded right now. You think they'd know the process well enough to know that if we are SIM unlocked we don't need to wait the 45

Some_Random_Username said:
You have the T-Mobile exclusive variant as per your post in https://forum.xda-developers.com/on...ol-to-restore-device-to-t4180981/post83784625
You have to use the T-Mobile tool.
Click to expand...
Click to collapse
Same thing with that one
Sent from my OnePlus KB2007 using XDA Labs

This tool just saved my butt. Thank you!

OnePlus 6T - Can't unlock bootloader nor get into Android

My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?

AOnePlus6TDestroyer said:
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
Click to expand...
Click to collapse

You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.

rogerrulez said:
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
Click to expand...
Click to collapse
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.

Only option now is to use msm tool again and hopefully get something working

Even with the bootloader locked you still should be able to boot the recocery image.

I have the 6T and 7T Pro. When I messed up my 6T my only hope was the msmdownloadtool. But make sure it's the right one.

When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.

Brettroth said:
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Click to expand...
Click to collapse
Are there more suitable tools for fixing a broken recovery mode? It did successfully do that.

rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
How?
rogerrulez said:
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Click to expand...
Click to collapse
Thank you! And yes, I tried that command but it is probably unset in the developer options (which I cannot reach, as Android isn't working anymore). I guess I'm using the incorrect version - how do you identify the correct one? I think I've used both the T-Mobile one and the other. I don't think the phone is T-Mobile, but I'm not sure how to identify whether it is or not.

It is very easy to convert a t-mobile variant to the international version. If you bought the phone used you would not know. One tell tale sign could be if you sim card holder supports either one or 2 sims. But that's not a sure way either because you can buy a replacement sim card holder. The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
As for the msm tool you would needd a modified version of that tool. You first use it to downgrade to Android 9. Then you have to upgrade that verion of android 9 to a slightly higher version before you are able to fully upgrade feely to 10 than 11 if you wanted.
If you have the international version pretty much and version of the msm tool would work but a modified version would be best.
However, the first step is to find out which variant you have.
When you used the msmdownload tool which version did you use, and did it finish the job ?

If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.

If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.

When I bricked mine I thought it was gone forever, I spent several days working on it but I was able to restore it. But I would never use the ubuntu rom on any phone that I care for.

When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.

rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
Wasn't sure about that. If that's the case, can you also flash from twrp then?

Brettroth said:
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Click to expand...
Click to collapse
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.

rogerrulez said:
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
Click to expand...
Click to collapse
That's what I meant. Flash a ROM from twrp. Ok so if that works this guy can fix everything from there. Gonna be a hassle tho. Instead of rebooting to recovery I think you would have to shut off phone and fastboot boot back into twrp to change slots right?

Somehow I feel like that won't work but I'm not locking my bootloader to test it

rogerrulez said:
The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
Click to expand...
Click to collapse
I'm afraid I can't' find it... It is dual-sim though.
rogerrulez said:
When you used the msmdownload tool which version did you use, and did it finish the job ?
Click to expand...
Click to collapse
I used a few - both T-Mobile and not. They all succeeded with (seemingly) no error, but didn't fix the bootloop.
rogerrulez said:
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
Click to expand...
Click to collapse
I see, but won't that need me to be in Android to be able to run the software?
rogerrulez said:
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
Click to expand...
Click to collapse
Yup, fastboot and recovery mode work fine. The bootloader is locked though, else installing TWRP, etc. would be easy.
rogerrulez said:
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
Click to expand...
Click to collapse
Yeah...
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
It doesn't do it automatically. Is there another way to boot it?
Brettroth said:
Somehow I feel like that won't work but I'm not locking my bootloader to test it
Click to expand...
Click to collapse
As far as I can tell there's no way to flash TWRP without unlocking the bootloader. And there doesn't seem to be any way to do that without getting into Android. And I can't get into Android...
Someone else suggested using this tool (https://github.com/bkerler/edl) as a last-ditch attempt. I'm going to give it a try and hope for the best!
Thank you both for your suggestions.

[HELP] Unlock bootloader.

Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.

Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..