Database Develop

Mediapad M3 Lite 8 - Bootloader Unlock Guide

Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:

I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?

I recently have been purchased the LTE version of this device. Although I cannot try this out currently, I probably will in the future so please keep us updated about your experiments for reference!

avkjbl5bak said:
I have also now been able to install TWRP by using the TWRP image specifically for BAH-W09 found on page 17 of the "TWRP (greatslon mod)" in the link provided by pitapart
thread. I can't post links yet which is why I'm typing to source....
I have been trying to flash SuperSU using the latest 2.82 zip but keep getting the error "Extracting Ramdisk - Failure, aborting", which is the same error I'm getting when trying to root using SRKtool, both the 2.1 universal version and the 2.0 Huawei version, using option 1 for Mate P8 or option 6 for systemless.
I've downloaded a system root version of SuperSU (google "supersu system mode", first XDA thread) and flashed using TWRP, it says it has installed but the SuperSU app doesn't show root, and typing "su" in TWRP console doesn't show I can do commands in superuser mode. Can anyone help?
Click to expand...
Click to collapse
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks

howgies said:
Hi,
Were you ever able to get your Mediapad M3 Lite 8 rooted? I really like this tablet but, need the 5 Ghz wifi band which requires root from everything I have read.
Thanks
Click to expand...
Click to collapse
I have my Mediapad M3 Lite rooted by magisk.
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
I download and installed latest magisk app.
I opened the magic app-> install -> install -> patch the boot image file which I then flashed through fastboot.
I then opened magisk -> install -> Direct install.
Everything works but like me you take a risk in not using the exact boot.img.
I tried and installed TWRP which worked but the volume keys would let me run the script I was trying to rebrand the phone. In the end it isn't necessary to root the phone.

sd26 said:
I followed the unlock guide and unlocked the bootloader.
I couldn't find my exact firmware I downloaded the most recent one I could find.
I extracted the boot.img with Huawei Update extractor and copied it to my phone.
Click to expand...
Click to collapse
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!

nicolap8 said:
Very bad idea and advice:
- people often uses wrong firmware or wrong version;
- a boot from a different version can be incompatible, you can be sure only too late!
The right thing is to boot to TWRP then in the console, using "dd" command do a copy of original boot!
Click to expand...
Click to collapse
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.

sd26 said:
Very poor reply, you did not read my post properly, just jumped in to demonstrate your superciliousness. No advice was given and you missed the word risk. More productive use of replying would have been to include the actual command required anyway which is:
dd if=/dev/block/boot-device/by-name/boot of=boot.img
Helping wasn't the point your trying to make.
Click to expand...
Click to collapse
if my reply is too poor, report it to mods...
A post like your IS an advice because people read and follow it. What is wrong is not that you write or my opinion but people behaviour
I read the "risk" word but a lot of people would not. This is also the reason I don't wrote the dd command: search and learn! Most of the messages you read here are of people who have broken their own terminal because just followed a post like your, without knowing what are doing.
N

sd26 said:
Everything works but like me you take a risk in not using the exact boot.img.
Click to expand...
Click to collapse
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc

#marcg# said:
I see in your first screenshot the fingerprint-id menuentry is gone.... does your fingerprint-sensor working properly ?
I rooted my mediapad m3 lite 10 in the same way, but my boot-image is the right version. ( installed is BAH-W09C100B257, firmware downloaded with the huawei firmware finder app is exactly BAH-W09C100B257) . My fingerprint menuentry is gone too.....and the sensor doesnt work (with the working registered fingerprint before the rooting)
Marc
Click to expand...
Click to collapse
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.

sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I have

avkjbl5bak said:
Brand new here, looking to unlock, root and then flash a standard Android build or custom DeGoogled ROM for my new device. I was looking to find a way to unlock the bootloader to start and found that Huawei have stopped giving out unlock codes and that the info around unlocking wasn't great so I made a note of all my steps as below.
Please let me know if this works for you and if you have any issues, please also read and follow the guidelines carefully as there are lots of things like using all the applications as an administator and changing directories that are important.
I am also looking for a way to install TWRP or another recovery thing on this device so I don't brick it, as I want to root the tablet and muck around with it. Has anyone got any experience of doing this successfully and does anyone have links to methods to create a cloned backup of the standard OS?
This was done on a brand new Mediapad M3 Lite 8 (the Wifi version, not LTE) with Android 7.0, EMUI 5.1, CPN-W09, build CPN-W09C100B251 - BUT will probably work on the LTE version, the non-lite version and the 7 and 10 inch models.
IMPORTANT: This costs money and is done through the DC Unlocker tool, it costs 4 credits (4 euros/dollars) for the Mediapad M3 Lite 8 (Wifi, not LTE) as Huawei now do not offer the bootloader code AT ALL . I have copied/streamlined the steps below that were found as guides originally at the dc unlocker website, check their site guides to find originals.
Step 1 - Developer Options enable
Go to settings, about tablet, tap build number 7 times to unlock developer options
Go to developer options, enable OEM unlock, enable USB debugging
Step 2 - Enable manufacture mode
If your phone has a dialpad, enter dial pad code *#*#2846579#*#*
IF your phone doesn't have a dialpad, go to calculator and enter ()()2846579()()=
This willl take you to a developer menu, select "Project Menu", "Background settings", "USB ports settings", "Manufacture mode".
Step 3 - Install drivers
Connect your Android device to your PC with a usb cable and either install Hisuite from the connected drive that will attach, or download it from the Huawei website by searching for Huawei Hisuite and going to their official website.
To check this has worked, go to Device Manager on your PC and look for Modems - there should be an entry called Android Adapter Modem - if this is not present try disconnecting/reconnecting your device and restarting Hisuite.
Step 4 - Read bootloader code
Download the latest DC Unlocker tool from dc-unlocker dot com and extract it, then AS AN ADMINISTRATOR (right click and Run as Administrator) run the client.exe (was called dc-unlockerclient2.exe)
Click Select Manufacturer dropdown and change to Huawei Phones, not Modems, press the magnifier/search icon at bottom left and your phone info should be found. This should also
Step 5 - Buy credits from the dc unlocker site as a new user, try 4 credits first and then login with these new user details in the dc unlocker application on your PC, this will show your credits and the phone connected as well as the cost. Click the Unlocking icon on the top right and click Read botloader code to get your code. Make a note of this/copy it somewhere.
Step 6 - Go back to the folder that dc unlocker is in
Go into the unzipped folder and then copy the location of this folder by clicking on the address bar in File Explorer and copying this location, you'll have something similar to
C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403
Step 7 - Turn off your phone and turn it back on holding the Vol down and Power buttons to enter fastboot mode, connect your device to your PC
Step 8 - Open cmd by searching for cmd in windows, right click cmd and open it as administrator, you'll get the black and white windows terminal
In the terminal type "cd C:\Users\ExampleUser\Downloads\dc-unlocker2client_1.00.1403" (or the path for the latest version of the dc unlocker you have downloaded) without the quotation marks and with YOUR directory path as described above. The command cd just changes directory to the one you give. Your terminal should now show the above directory as the path in which it now sends commands, i.e the > mark is now displayed after the directory path we copied
Step 9 - Type "adb devices" without quotation marks to start the adb daemon
Step 10 - Type "fastboot devices" without quotation marks and you should see a device number with the word fastboot next to it.
Step 11 - Now type "fastboot oem unlock" without the quotation marks, followed by a space and then your bootloader unlock code i.e
fastboot oem unlock XYZ123456789
Step 12 - Your device should show a screen asking you to accept the unlock, then onto another screen where you should press the power key to continue onto booting your factory reset unlocked device.
Step 13 - You might have to disconnect the USB cable and reboot your device now, and you'll set up the device from scratch again - but now the bootloader unlocked, allowing you to load stuff like TWRP if you can find the right version - which I can't right now! :good:
Click to expand...
Click to collapse
Did you ever get and answer to your question about cloning or getting the original factory images. I've been trying on and off for 9months. I have unlocked the bootloader and backed up using TWRP (from the 10inch model), but when I relocked the bootloader everything fell apart... unstable boot loops, etc. not sure if I had to wipe recovery I burned with TWRP or what. Also TWRP does not back-up the data partition I think due to encryption (from other posts I read). My goal was to rebrand a pile of the Chinese version tablets I have to US because we use them in our product, and the US are not available, so rebranding would give me more time before to find a replacement. Any clues would help!!!

sd26 said:
I did not have the fingerprint option activated so I checked it and found my sensor also does not work with the patched boot.img on. I could search and find the fingerprint menu entry but could not get it to operate. Reflashing the stock boot.img returned the sensor menu and fingerprint to normal but of course you lose root. More searching for solutions required.
Also I'm using the TWRP-3.2.1-bah-20180627.img recovery. The volume keys don't work so the hurupdater script I'd like to use aborts. Anyone got any other recovery for a CPN-W09C128B006?.
Click to expand...
Click to collapse
I successfully rooted my CPN-L09 without loosing fp sensor, have a look here: https://forum.xda-developers.com/mediapad-m3/help/to-patch-boot-img-magisk-v17-3-t3938629

Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex

bigprat9 said:
Hi
im a new member but have been using the site for ages.
my mediapad m3 is also wifi only and im trying to get the code for the bootloader to be unlocked except for the fact that my calculator app isn't scientific enough (lol) to include brackets.
what do I do to get the code or update my calc app?
alex
Click to expand...
Click to collapse
You have to use the calculator in landscape mode (turn on auto-rotate) and then the bracket buttons will appear.
So I finally got around to installing this on my stock version. I found 16GB was too limiting and I was hoping to use the SD card to expand the space so I could use it for a few more years. I purchased the code from DC_unlocker.
A couple of things I noticed while following the guide. To enter fastboot mode, holding down the volume down and power button doesn't seem to work. What you to do is while it's off, hold down the volume down button and plug in the microusb cable, while continuing to hold it down. You could also enter fastboot using an ADB command.
Also I couldn't wipe anything before installing the new roms, I got error messages. I'm not sure what that means. Anyways after installing android 9, it seemed to take a very long time to first boot. The graphic animation is going, but I wasn't sure if it was working so I hard reset once, tried to boot again and then waited again, hard reset again and put it down thinking I would have to look into the error messages and when I came back it was up and running.

Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.

lawhec said:
Hi, I'm hoping someone can help me out here.
A few days ago, I followed the instructions unlocking the bootloader of my Mediapad M3 lite 8 (CPN-W09) and sure enough, I successfully unlocked the bootloader. However I've now run into another problem - I cannot get the FRP on the tablet to be unlocked!
Nothing I've tried seems to get it to unlock. The (only) Google account used on the tablet has been my own, and it's been no problem signing back into my account when factory resetting the tablet. One time when investigating it, after a factory reset it did say that it was "restricted" but again, adding my Google account details on the setup was no issue, but even after then deleting the account (which, if I'm right, should set FRP to "unlocked") when I enter into fastboot mode it still shows FRP as locked! And it shows it no matter what I do, wherever the Google account is "active" on the tablet or not, and the last four or five times I've did a factory reset with both data and cache partition wipes done and nothing budges. I think I'm at a lost cause here - the "OEM Unlock" option in the developer settings is totally greyed out. ?
Of course, the tablet is still "usable" but there is no way to carry out special functions after unlocking the bootloader, like rooting, install TWRP, custom ROM etc. and it just kinds of stands in a limbo.
I've tried searching here on XDA and the web in general, high and low, to see if this problem has affected anyone else, and strangely it doesn't seem to happen to anyone else!
For the record, I've also tried hardreset.info's FRP unlock tool which claimed to be successful, but it clearly wasn't!
I hope someone out there might have a solution to my woe - as I think I've partially crippled by M3 Lite 8 otherwise by trying to unlock the bootloader.
Click to expand...
Click to collapse
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .

surdu_petru said:
You could try to lock bootloader back, and before to unlock bootloader again, first just unlock OEM .
Click to expand...
Click to collapse
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!

lawhec said:
I did try this at the time, and I couldn't get it to work. But I had another try at it yesterday and I managed to get the bootloader locked again, toggle OEM unlock to "off" and unlocked the bootloader once more and it worked!
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
I used to do some rooting previously with Android handsets in the past, but the last time was two years ago (rooting & upgrading an Alcatel handset to Android 6.0) and FRP was new to me, throwing me off.
I've donated some Euros to you as an appreciation for your work & advice. Merci beaucoup!
Click to expand...
Click to collapse
Thank you very much too

Hello
I followed the steps here to unlock the bootloader with my btv-dl09, that worked fine even its not lite.. :fingers-crossed:
but now, any clues? may i ll try the way of lawhec with
lawhec said:
So after doing this, I tried to get TWRP 3.3.1-1 flashed but it would stay frozen on the screen - I then read that I needed to install TWRP 3.2.0-0 first, install the August 2019 Lineage 16 firmware, then go back to the bootloader, flash TWRP 3.3.1-0, check everything was OK and then return to bootloader to finally flash TWRP 3.3.1-1. Success! I then flashed the latest Lineage OS 17.1 firmware along with Open Gapps (ARM64, Android 10, nano) and so far everything has worked OK. I just need to download all my apps again, but I'm sure it will give my CPN-W09 a new lease of life!
Click to expand...
Click to collapse
but cant find the TWRP 3.3.1-1?
may u Mean
[Recovery][Official] TWRP 3.3.1-10 [G97*0][Snap][3.Jan.20]
[Recovery][Official] TWRP 3.3.1-12 Snapdragon [N97x0][10.Nov.19]
[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J6+/J610F/FN/G/DS
???
if so, why u choose one of these? No Clue for me^^ plz let me know
greetz
ADD: just found
Developed By :letschky
twrp-3.1.1-1-next.img
Jul 13, 2017 | 03:32PM
maybe these? looks pretty old but still working? Oo

Rooting woes

So I unlocked the bootloader on my Alcatel 1, but when it comes time to rooting it I get an error.
FAILED (remote: Only system partition can be flashed)
I don't know what it means or why I get the error, I just know that I cannot gain root with this error. I was hoping someone here could help me figure this out.
Thanks
MikePysh

Hey! If Android 9 (LineageOS 16) is your thing (No GApps), see my post of how to root the Alcatel 1. ( https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713 )
I hope you root your device, have a nice day!
(Note tested with 5033X but i´m pretty sure it works on all 5033s, since it uses an global system image (GSI))

stevegsames said:
Hey! If Android 9 (LineageOS 16) is your thing (No GApps), see my post of how to root the Alcatel 1. ( https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713 )
I hope you root your device, have a nice day!
(Note tested with 5033X but i´m pretty sure it works on all 5033s, since it uses an global system image (GSI))
Click to expand...
Click to collapse
Question for you (or anyone)- I am a long-time Sony Xperia user, but I got a hold of a TCL A501DL, (Alcatel A1 TracFone variant), and have no access to fastboot/bootloader. Boot to recovery works fine, but no option for bootloader. ADB recognition works fine, but 'adb reboot-bootloader' command just reboots to system. Volume+ power button combos, as well as holding any keys while connecting, doesn't do anything. I reached out to TCL on the phone and by email, one rep told me that maybe hard-reset might make it work, (it didn't); another rep told me that there is a way to do it, but they aren't authorized to tell me what it is, and another one told me that they don't support it, so they don't have documentation about it.
'OEM unlocking' is checked in settings, and ADB debugging.
Any ideas? Thanks

Yeah....
[/COLOR]
levone1 said:
Question for you (or anyone)- I am a long-time Sony Xperia user, but I got a hold of a TCL A501DL, (Alcatel A1 TracFone variant), and have no access to fastboot/bootloader. Boot to recovery works fine, but no option for bootloader. ADB recognition works fine, but 'adb reboot-bootloader' command just reboots to system. Volume+ power button combos, as well as holding any keys while connecting, doesn't do anything. I reached out to TCL on the phone and by email, one rep told me that maybe hard-reset might make it work, (it didn't); another rep told me that there is a way to do it, but they aren't authorized to tell me what it is, and another one told me that they don't support it, so they don't have documentation about it.
'OEM unlocking' is checked in settings, and ADB debugging.
Any ideas? Thanks
Click to expand...
Click to collapse
My 6058D (Idol 5) has the same problem. No bootloader access. One of the reasons I chose my current phone (OnePlus 6). Does that phone have a custom skin for tracfone? My A1 is from a carrier here called NOS, and the phone is rebranded as NOS Novu 4, but it is still an A1 (5033X)

Has anyone had any luck rooting an Alcatel Verso 5044c (cricket mobile). I've tried the rooting methods here and a few others but I cannot get fastboot to recognize my device. Adb works fine when the phone is booted up but when in recovery it shows the device is "unauthorised". I've checked my drivers and they are installed correctly and working but still no fastboot access. Recovery on this phone is locked to the point that it only has options to wipe cache or FDR. Another thing that happens is when you use adb to reboot the phone into the bootloader it just power cycles and doesn't actually go into the bootloader. Can anybody help?

MikePysh said:
So I unlocked the bootloader on my Alcatel 1, but when it comes time to rooting it I get an error.
FAILED (remote: Only system partition can be flashed)
I don't know what it means or why I get the error, I just know that I cannot gain root with this error. I was hoping someone here could help me figure this out.
Thanks
MikePysh
Click to expand...
Click to collapse
Same issue here. I unlocked the bootloader and yet I can't flash anything apart from system partition. I'm getting the same error as you.
Trust me, my bootloader is unlocked, as the oem unlock is greyed out.

levone1 said:
Question for you (or anyone)- I am a long-time Sony Xperia user, but I got a hold of a TCL A501DL, (Alcatel A1 TracFone variant), and have no access to fastboot/bootloader. Boot to recovery works fine, but no option for bootloader. ADB recognition works fine, but 'adb reboot-bootloader' command just reboots to system. Volume+ power button combos, as well as holding any keys while connecting, doesn't do anything. I reached out to TCL on the phone and by email, one rep told me that maybe hard-reset might make it work, (it didn't); another rep told me that there is a way to do it, but they aren't authorized to tell me what it is, and another one told me that they don't support it, so they don't have documentation about it.
'OEM unlocking' is checked in settings, and ADB debugging.
Any ideas? Thanks
Click to expand...
Click to collapse
Ive got bootloader unlocked, gained fastboot, and have written a working twrp for the a501dl but gotta make the recovery survive a reboot. I'll post a guide soon as I get it to survive.

stevegsames said:
Yeah....
[/COLOR]
My 6058D (Idol 5) has the same problem. No bootloader access. One of the reasons I chose my current phone (OnePlus 6). Does that phone have a custom skin for tracfone? My A1 is from a carrier here called NOS, and the phone is rebranded as NOS Novu 4, but it is still an A1 (5033X)
Click to expand...
Click to collapse
Check out my guide for the 6060C because you may be able to get fastboot access with it but the recoveries won't fit your version of the idol5. Is it MTK?

levone1 said:
Question for you (or anyone)- I am a long-time Sony Xperia user, but I got a hold of a TCL A501DL, (Alcatel A1 TracFone variant), and have no access to fastboot/bootloader. Boot to recovery works fine, but no option for bootloader. ADB recognition works fine, but 'adb reboot-bootloader' command just reboots to system. Volume+ power button combos, as well as holding any keys while connecting, doesn't do anything. I reached out to TCL on the phone and by email, one rep told me that maybe hard-reset might make it work, (it didn't); another rep told me that there is a way to do it, but they aren't authorized to tell me what it is, and another one told me that they don't support it, so they don't have documentation about it.
'OEM unlocking' is checked in settings, and ADB debugging.
Any ideas? Thanks
Click to expand...
Click to collapse
for the a501dl use mtkclient to unlock bootloader and flash a custom recovery/patched magisk boot: https://github.com/bkerler/mtkclient

luridphantom said:
for the a501dl use mtkclient to unlock bootloader and flash a custom recovery/patched magisk boot: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
If you or anyone happen to have a stock rom/custom rom of the TCL A501DL and can post it, I'd appreciate it! I haven't tried the new mtk client but will give it a shot this weekend.

Buenas, tengo un problema con mi Alcatel Modelo 5007A, un núcleo del GPU me Dice que está desconectado, como puedo volver hacerlo funcionar?

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

Can we get a video of how to do this?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.

AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.

#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks

#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.

Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project

So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader

MOD EDIT:
This is the latest version
这是最新版本

#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?

for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"

gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them

Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.

gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com

any luck with that? can I backup my firmware before doing it?

darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

Question Bricked OP 10 Pro - Help

Hello All,
I managed to brick my OP 10 Pro
It happened when I locked the bootloader before uninstalling Magisk.
I am now in a forever bootloop, see video:
Your browser is not able to display this video.
It will not boot into fastboot for love nor money.
There is no time for adb to load into fastboot as it is constantly resetting.
If I hold all three buttons when it is not connected to anything, it does nothing.
If I hold all three buttons while the phone is connected to the computer, it goes into EDL mode and Qualcomm drivers appear in the device manager, but it still fails to shows as 'adb devices' or 'fastboot devices'
I dont know what to do.
Help :-/

Lynxy0 said:
Hello All,
I managed to brick my OP 10 Pro
It happened when I locked the bootloader before uninstalling Magisk.
I am now in a forever bootloop, see video:
View attachment 5586583
It will not boot into fastboot for love nor money.
There is no time for adb to load into fastboot as it is constantly resetting.
If I hold all three buttons when it is not connected to anything, it does nothing.
If I hold all three buttons while the phone is connected to the computer, it goes into EDL mode and Qualcomm drivers appear in the device manager, but it still fails to shows as 'adb devices' or 'fastboot devices'
I dont know what to do.
Help :-/
Click to expand...
Click to collapse
Need msm

Theres no msm tool yet you have to wait for it

Is there anyone that had a look on Baido ?I tried everything under the sun.
I downloaded this from mega which has the full firmware files
https://mega.nz/folder/vMYSxBgI#LJXkyX-Ue9a4iFZPQmc80w
The closest I got was downloading the QFIL to flash it in EDL mode, but I couldnt get it to work...

I once took a bricked OP6 (hardly a month old) to service center. They fixed it, no questions asked.

I guess times are tough. GSMMAFIA steals OP software and sells it to you.

g96818 said:
I guess times are tough. GSMMAFIA steals OP software and sells it to you.
Click to expand...
Click to collapse
Considering there's a thred in this forum exactly for that...

The same thing happened to me on my NE2215...
Told OPO support it was the latest update that did it.. they are offering to repair it, still under warranty, for free.
from what I hear it can take 3weeks to 3 months to get it back.
Need a MSM tool
How I happened to me...
i wanted to get the latest OTA, so I removed Magisk, changes boo.img back to stock, reset the phone, and then when to turn flashing off (lock the bootloader)
on the rest step of Locking the bootloader back, is when it looped into this as well....

I know this isnt helpful right now, but NEVER re-lock your bootloader. I've seen far too many people brick their ****. Why unlock it to begin with? When you relock the bootloader, anything that's not signed will not boot. I hope you get your phone fixed. Good luck to you bud

can you please tell me your mobile after hard brick have a pc connection ? beacause my phone also bricked and totally terned off no button combination no charging no pc connection
<Moderator Edit>: Quote removed since post deleted.

lordxcom said:
The same thing happened to me on my NE2215...
Told OPO support it was the latest update that did it.. they are offering to repair it, still under warranty, for free.
from what I hear it can take 3weeks to 3 months to get it back.
Need a MSM tool
How I happened to me...
i wanted to get the latest OTA, so I removed Magisk, changes boo.img back to stock, reset the phone, and then when to turn flashing off (lock the bootloader)
on the rest step of Locking the bootloader back, is when it looped into this as well....
Click to expand...
Click to collapse
Why did you try a super complicated route to update? There is no need to do reboot or lock your bootloader after restoring (not removing) magisk in order to do the ota update.

g96818 said:
Why did you try a super complicated route to update? There is no need to do reboot or lock your bootloader after restoring (not removing) magisk in order to do the ota update.
Click to expand...
Click to collapse
i took the old approach it appears... what is the new way to roll ?

lordxcom said:
i took the old approach it appears... what is the new way to roll ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/

Eventually, I took out insurance on the phone and a week later I said its not working. Insurance support werent very technical and they replaced my phone after a week. Alernatively, I could of sent it off to OP...

i bricked my op10p same way like you... i went to store where i bought it and they sent it to repair after that i got info that they switched motherboard from it

File Unbrick : https://drive.google.com/file/d/1Hmu1SFF9N3fzIczg9L1WjBGwNEjTa0y7/view?usp=sharing
Mod Edit: YouTube Video Link Removed

maison1989 said:
File Unbrick : https://drive.google.com/file/d/1Hmu1SFF9N3fzIczg9L1WjBGwNEjTa0y7/view?usp=sharing
Video
Mod Edit: YouTube Video Link Removed
Click to expand...
Click to collapse
a complaint. Submit your login information.

El mismo problema aquí, ¿has logrado resolverlo?
Same problem here can you help me please

kurador911 said:
El mismo problema aquí, ¿has logrado resolverlo?
Same problem here can you help me please
Click to expand...
Click to collapse
Best solution: throw your phone in trash, also boycott OppoPlus and don't buy from BugPlus anymore
F*ck OnePlus !!

Everyone listen to the google logo user. Oppo is hostile to rom developers and releases broken source code and restricts msm. They're just the apple of android products nowadays

Moto G5s baseband not found (unknown) 😢 IMEI 0 please help

I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help

i think this vid will help

Greetings everyone. Sorry if I posted this in the wrong forum. Please move this in appropriate forum if I made a mistake. Believe me, for the last 7 days I have searched all of xda and internet, followed innumerable guides, FAQs and workarounds and none worked. So, as a last resort I am starting this thread
Device: Motorola Moto G5s Plus XT1804 ......4GB _64GB variant
Problem: 1) Baseband not found (unknown) Original Baseband: M8953_52.61.07.98R SANDERS_INDIADSDS_CUST
2) IMEI 0 (Sim cards are not detected).
I bought this refurbished phone about an week ago after my last LG went kaput. I was happy by the build quality of the phone. But it only ran Android 8.1 Oreo. So, I decided to put a custom ROM in it. I am not exactly a newbie to the world of CyanogenMods, Lineage OSes and Pixel Experiences. Or, so I thought. Anyways, after a lot of searching I finally decided on Dot OS 5.2 Official Android 11 version. The ROM looked very pleasing and the reviews looked positive. So, I got the unlock key from Motorola website, unlocked the bootloader, put in official TWRP recovery in it. Everything went like a breeze and in all that excitement I forgot to take a backup of the persist, efs and other partitions. A very costly mistake it seems. DotOS booted fine and looked really fresh till I found that there is a small cross near the SIM card network signal triangle up righthand side corner and the signal is only LTE and not VOLTE. I was using a Vodafone Sim card at the time. Although VOLTE option was enabled in SIM settings. To confirm my doubts regarding VOLTE I switched to a JIO Simcard and alas I was not able to make a call without redirecting through the horrid JIO calling app. VOLTE was indeed not working. So, I looked up for a fix and I found a Volte ZIP file from here https://www.google.com/url?sa=t&sou...0QFnoECBAQAQ&usg=AOvVaw0YgJvCjQWXXV8WQSJkxBOK . This was the starting of my troubles. I flashed the universal VOLTE fix zip from TWRP and it flashed fine. On rebooting, I found to my shock that my phone was not turning on. I pressed and held the power key and there was no sign of life. I couldn’t go to the fastboot bootloader or recovery. Only the white led blinked at the top when connected to the charger. My phone was apparently hard bricked. I searched frantically for a solution in this forum and YouTube wherein I found that one can bring it back to life by doing a blankflash. Found the blankflash file here https://www.google.com/url?sa=t&sou...wQFnoECAsQAQ&usg=AOvVaw1eVdBWGVFr8aiqLdP-ZkeT followed the instructions and it flashed my bricked device back to fastboot. I was relieved for a moment but the next I found that the Bootloader version has downgraded from BL C2 07 to BL C0 05. I knew something was wrong as bootloader downgrade shouldn't be possible. Also the unlock and rooted status were also lost and the baseband was unknown at this point. Anyways the device was recognised as a fastboot device and I tried to flash the stock ROM latest version using the fastboot. But, only then I realised there was something wrong with the bootloader. It gave errors like security downgrade, permission denied, preflash validation failed, remote command failed. At this point I was truly confused and worried. Why would it think the latest bootloader to be a security downgrade to a supposedly old bootloader and prevent me from flashing it. However it did flash the other files like gpt.bin for partition, oem.img, boot.img, system.img sparsechunks and everything else. I booted back to Android 8.1 Oreo and everything seemed working except my IMEI now read zero and my Simcard was not recognised by the device. After that I again unlocked my bootloader. Somehow the original unlock key worked and the bootloader screen said flashing unlocked but the bootloader didn't behave like an unlocked bootloader. The TWRP installed fine but couldn’t install the latest Pixel Experience. The flash screen said PE 11 was for Sanders and my device is (blank no name). I tried both the normal and plus and both behaved similarly. Lineage OS unofficial builds behaved similarly. I again tried Dot OS and Arrow OS and both installed fine except there was no signal. For a moment I tried to forget about the bootloader but concentrated on recovering my IMEI and Baseband but I couldn’t. For nearly 5 days I tried different guides including a detailed guide using Validus Sanders ROM but none worked. My EFS folder has files around 12 megabytes but my Persist seems deleted at zero bytes. The IMEI keeps changing between null, zero and unknown depending on the 20 something ROMs I tasted on this device. At this point, I am at a loss. This was to be my main phone and I am financially crunched. I can't buy another phone right now. I think that blankflash bootloader is corrupted and it is giving me permission denied errors. Even Magisk won't work properly. I even tried using the official rescue and smart assistant tool by Lenovo and it failed at 47 percent. I tried in different computers and Win7 to Win 11 OSes but it was of no use. I also tried getting a QCN file but I couldn’t get one for the device to recover the IMEI. Please suggest something if anyone of you can save this poor device of mine. Thanks in advance

Raghaov said:
i think this vid will help
Click to expand...
Click to collapse
Thanks for the quick reply but my phone is soft bricked now. It was hardbricked and I uses a faulty blankflash bootloader to bring it back to life. My device is softbricked now. I have lost my baseband and I have no IMEI. I cannot take calls and no mobile data. Can you show me a way to go to edl mode in my device. Thanks again.

can your phone turn on if yes can you root it with magisk
if yes then pls tell me i will tell you

I can do everything except calling and mobile data. Yes, I have rooted with Magisk and have root access. But my baseband is unknown and my IMEI is showing zero. I can't call or access mobile data. Although I can use wifi

I have tried what is shown in this video already. Didn't work

I think the blank flash bootloader was corrupt or of a different region.

so go to magisk manager and on top-right corner you will see setting click the button right next to it and click on reboot to edl

I didn't even knew that. Trying asap. Will update

Doesn’t work. Reboots back to system.

Updated Magisk to latest and tried both edl and download mode like you said brother. Everytime boots back to system. Am I missing something. The phone was not connected to the PC at the time

I am on stock Oreo now. Rooted and twrp installed

An interesting observation while installing Xposed, it gave an error that the device is not rooted properly

I have an untouched dump file for my model. The whole thing. Could you please guide me how I can restore my smartphone from that.

can you flash it through adb sideload fastboot twrp etc

I don't know but I sold the device. I bought a new one. Thanks @Raggaov for the help.

you're welcome