Database Info

Unlock bootloader and flash twrp with Spflashtool

Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ??

This methode work with So Flashtool ?

I'm going to make SPflashTool working. I have some issue

Riadh300 said:
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ?
Click to expand...
Click to collapse
Thanks for your enthusiasm but my method does not Unlock the bootloader so you should change your thread title.
As I told you I will open a thread when the method is fully tested by a few advanced user's who are testing it now and you will be given full credit for all your help.
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.

I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !

Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.

bigrammy said:
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
Click to expand...
Click to collapse
Thanks for this informations ! ?

Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
Actually, spflashtool bypasses the bootloader in this instance, so the bootloader is untouched and you still flash twrp
---------- Post added at 08:35 AM ---------- Previous post was at 08:02 AM ----------
bigrammy said:
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
Click to expand...
Click to collapse
Not to be pessimistic, but you do realise that even with all your precautions,people will still not read properly and will still brick their phones, no matter how many precautions you take. Even if you had an app that requires you to click one button to do everything,there are still people who will do it wrong. That said I think I know of one or 2 people in this Nokia 3 forum who were able to recover their phones using spflashtool AFTER the phone couldn't even be detected by their pc, even OST flashing was not possible .
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD

redweaver said:
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
Click to expand...
Click to collapse
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).

bigrammy said:
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
Click to expand...
Click to collapse
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post

redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it

bigrammy said:
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
Click to expand...
Click to collapse
So how did you get your phone back anyway?

redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.

redweaver said:
So how did you get your phone back anyway?
Click to expand...
Click to collapse
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.

SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
OK, one thing though, before flashing the recovery you might want to do a backup of the stock recovery if you don't already have one. That's what I did, so after I got root, flashed back my stock recovery. Magisk is the root manager ,
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
bigrammy said:
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
Click to expand...
Click to collapse
oh you mean you went through hoops to get your phone back? I thought you would say you got a stock recovery somewhere and flashed using spflashtool or used the ost method. I didn't actually expect you to outline the steps you used. BTW, first time I flashed twrp AFTER unlocking bootloader, I got stuck in a recovery bootloop too. I had to flash my phone with OST then retry the process again.
One other thing, I think OST is actually a propriety software that is supposed to work for lots of phones, at least I know that users of other non mediatek Nokia phones also use it to recover their phones (with the corresponding stock images of course)

SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
Magisk hide allows you get OTA's see the Magisk thread and yes it will work on any android version.
@redweaver
I am glad you got out of the loop but your clearly a more advanced user hence why I ask you to test. :good:
The OST is very convoluted for use on MediaTek devices and is very unnecessary it also requires unnecessary FIH software to be installed on the phone to work properly.
They likely choose this method to work across different SoC's but it's not what MediaTek use SPFlashTool is MediaTeks own software.
EDIT: Sorry lost internet for a while then.
I continue: Good news is I do not think they will be able to remove SPFlashTool use as it's binary on device which lives on a none volatile area ram chip or radio chip and is loaded at the factory so I doubt it can be updated via a OTA. :fingers-crossed:
Sony actually replaced this and this is the only device I have been unable to recover and even Sony were replacing the boards of bricked devices but if they had left the Mediatek binary in there it would not of been a issue as SPFlashTool would of been able to recover them. :good:

guys, old thread, i know, different device, i know, but ive been in the dark and this is what most resembles my issue.
any hints would be appreciated, read all 2 pages, can you believe it? im a very average xda enthusiast.
worries out of the way, my sincere thanks beforehand follow.
issue
carrier doesnt get in the way
oem doesnt get in the way
oem unlock toggle, check, adb debugging, you and i know the drill, no driver/cable issues
cannot for the life of me unlock bootloader, this one would take the newer command, however i tried them all ive come accross to no avail
output encourages me to unlock first, howwever not a clue is given as to how to accomplish it. this isnt the flash a file type of unlocking, either, at least not oem provided. going nuts.
go ahead and feel free to issue "advanced" directions (meaning, like your voicemail, instead of "for voicemail configurations press 8" and just "configurations 8"
spreatrum, not mtk
x120c
came with oreo go, treble enabled per getprop
i dont know what else, please

Any information on Root?

Want to buy this phone. Need it rooted to do a couple things. Has anybody gotten TWRP and root on it yet?

You can root it by first unlock the bootloader then install magisk via patch boot image method.

How should I get the boot image to actually use that method?

You can download the firmware here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/
Inside zips, find boot.img

Does anyone know anything about custom recovery TWRP yet that's what I'm looking for

there is no custom recovery

ahalol said:
You can root it by first unlock the bootloader then install magisk via patch boot image method.
Click to expand...
Click to collapse
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?

Thereplierbro said:
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?
Click to expand...
Click to collapse
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.

wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
Does the Verizon one have a greyed out "OEM Bootloader unlock"
Because I bought one off offer up that had the button available but it was purchased from Verizon
Also I asked Motorola for the unlock website an they said they haven't released it yet for Moto z4

Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...

wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
wraith1932 said:
Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...
Click to expand...
Click to collapse
All other phones, if the button is not greyed out and you can press the option (and it asked for your password) then it's unlockable. I know because I got a few freaking pixel phones with non usable Bootloader. Wasted about $1,000 looking for a cellphone to use with Sprint that I can root. Every one of them is Verizon.
https://support.motorola.com/us/en/solution/ms87215

DM Verity disabled too?
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)

Jade Eyed Wolf said:
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)
Click to expand...
Click to collapse
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly

Thereplierbro said:
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly
Click to expand...
Click to collapse
One of my main reasons for waiting to get one

Jade Eyed Wolf said:
One of my main reasons for waiting to get one
Click to expand...
Click to collapse
It's basically useless until then

Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.

battleof3 said:
Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.
Click to expand...
Click to collapse
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.

ahalol said:
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.
Click to expand...
Click to collapse
Dug a little deeper and bootloader is locked tight, no flashing for me. Returning and buying a secondhand LG V30 for cheap. It's unfortunate that carriers love their walled gardens.

See, this is why I was asking about DM Verity. You need to disable that first before flashing anything via ADB/Fastboot.
With DM Verity on, at system startup, the device generates a hash of the /system and /root directories. If the hash does not match the one from the factory, due to changes pushed via ADB or Fastboot or patching other system files with something different, the system reboots, again and again.
I had this same issue with my Z2 Play, which is why I brought it up here.
Rooting these devices is useless, unless you also disable DM Verity.

I tried to follow this method and ended up flashing the wrong boot image (I did go to the right software variant but it was outdated) so i had to go through and try all the images they had and none of them worked so i had to look elsewhere.
After some digging i found a VERY handy tool made by lenovo themselves that lets you update and recover the firmware.
If you use the rescue option and enter your phones info (it seems to verify your phones info so you can only download for devices you have) and it'll download the latest zip for you so you can get the boot image.
Here's the link to the smart assistant
TL;DR Open smart assistant, click flash, click "Go rescue", Click "Moto Phone", enter your phone's info (make sure your phone is connected in fastboot mode), click the download icon next to the file name.
Make sure you DO NOT click the rescue button when the download is finished as that will factory reset your phone, just copy the zip or boot image and close it

How To Guide [ROOT][GAPPS] Root and install GApps on stock Edge S/Chinese version

So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.

unlock the BL and get root is will make some apps fingerprint and face ID fail?

kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.

HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.

kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.

HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.

kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.

kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.

HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.

HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?

Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.

kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.

I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.

kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related

Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?

kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.

RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/

HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .

kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...

kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.

Question OnePlus 9 5G (T-Mobile) no Local Upgrade option, cannot flash partitions

MOD Edit: check post #25#25 before you proceed.
craznazn said:
This thread was created before I made the MSM conversion, hence the confusion. Probably could be locked now.
And if the OP is still reading this, for your own good don't mess with modemst1/2/persist unless you really know what you're doing.
Click to expand...
Click to collapse
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/

Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.

lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.

inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
I should still have the boot.img I backed up from stock 11.2.2.2 (T-Mobile). I'll attach it here when I get off work

LLStarks said:
Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.
Click to expand...
Click to collapse
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.

inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
This should be the stock boot.img from the 11.2.2.2 T-Mobile build. Named it that way so as to not confuse it with stock boot image from 11.2.4.4 (EU)
boot(old).img (Google Drive link)

mattie_49 said:
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.
Click to expand...
Click to collapse
Will heed your guys' warnings. Just was super curious (and confused) as to how others were able to get it to work

Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.

jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking

mattie_49 said:
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking
Click to expand...
Click to collapse
Yes, I am very aware of that. The issue is I have the T-Mobile version because I got if 1/2 off with a trade in. Will this warrant a trade after I pay it off? Maybe. But I would rather just put on Lineage OS if that becomes possible.

lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
you flash from bootloader (fastboot) or from fastbootd
FAILED (remote: 'Flashing is not allowed for Critical Partitions this is when you flash in fastboot
only fastbootd can flashh all partition

jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know there's a specific option under the development settings called 'stay awake', right?

TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse

I can not select it. It is greyed out for some reason.

TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse
On the T-Mobile version it is not selectable.

jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
Yeah that's BS because I definitely selected it while I was backing up my data before I converted from T-Mobile firmware.

jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
I'm on t-mobile version i can select it as well. Pretty sure everything in developers options is selectable. Some don't stick for whatever reason.

Ya, I don't know what this things deal is. But as soon as I get the ability to flash to international I'm doing it.

Where is the guide for flashing a OnePlus 9 from T-Mobile to International?

Btw for everyone following this thread, its an easy to miss step, but if you follow the guides for converting, all you have to do is go into fastboot and then use command “fastboot reboot fastboot”. This apparently puts you in fastbootd (never had to use this before, I would just use commands and flash stuff from bootloader screen but whatever) where you can then flash the needed partitions. Also, no hate to the guy who posted the recent conversion thread but it is super unorganized and a little too easy to miss that step, as well as MAKE SURE you read through the .bat file they provided because it is NOT correct. They have some typos in there so it wasn’t working for me at first. It’s a pain in the ass but I highly recommend going through each command, copy/paste, and read it to make sure there’s no typos then hit enter or you will run into errors like I did. Good luck

How To Guide WARNING: Read BEFORE Locking Bootloader

DO NOT LOCK THE BOOTLOADER WHILE ROOTED!
When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.
Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.
If you still want to lock your bootloader, make sure you can say yes to each of the following:
1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?
Spoiler: Restore Stock Boot
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Follow the instructions in the thread above.
Use only the boot and vendor_boot images.
Do NOT flash any images that end with "-magisk.img"
2. Have you made a backup of everything you do not want to lose when wiping the phone?
Spoiler: Make a Backup
The sdcard is part of the internal storage and is cleared by a factory reset
Copy everything you want to keep to a computer or USB-C storage device
Apps and settings can be backed up by enabling the Google Backup option
Open Settings
Select Google
Select Backup
Select Back up now
Wait for the backup to complete
3. Have you flashed raw firmware and made sure the phone and updates function normally?
Spoiler: Flash Raw Firmware
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Follow the instructions in the thread above.
If you perform a wipe, you may skip step 4.
4. Have you performed a factory reset and made sure the phone functions normally?
Spoiler: Factory Reset
Open Settings
Select System
Select Reset options
Select Erase all data (factory reset)
Follow the instructions
Once you have verified all of the above requirements, you are now ready to lock the bootloader.
Spoiler: Lock Bootloader
From the bootloader (volume up + power):
Code:
fastboot oem asus-csc_lk

Reserved for QA information

I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.

falhumai96 said:
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
Click to expand...
Click to collapse
Based on new information, it does seem possible to repair the issues caused by converting.
That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.

I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again

chairman011 said:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
Click to expand...
Click to collapse
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?

If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?

nexusnerdgeek said:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
Click to expand...
Click to collapse
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.

falhumai96 said:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
Click to expand...
Click to collapse
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.

twistedumbrella said:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
Click to expand...
Click to collapse
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?

The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.

Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks

0v3rkill said:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
Click to expand...
Click to collapse
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.

Andrologic said:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Click to expand...
Click to collapse
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks

0v3rkill said:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
Click to expand...
Click to collapse
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com

Andrologic said:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.

Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys

For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.
(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)
I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.
I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.
Right now, the phone boots to fastbootd & not further. Any help is much appreciated.
(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer . It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)

This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.

nexusnerdgeek said:
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
Click to expand...
Click to collapse
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.