Database Info

XT926 kit kat issue

First of all sory formy english
I did update two days ago,but I have problem with my phone,it is locking and loose signal telephone and 3g,also battery finishing quickly.What is the problem I tried to enter 3g options but *#*#4636#*#* not working,how can I back 4.1.2 version
thanks you all

You cant go back so dont bother trying unless you wish to brick your phone....did you try an fdr

cmh714 said:
You cant go back so dont bother trying unless you wish to brick your phone....did you try an fdr
Click to expand...
Click to collapse
yes I did but still same

trapper66 said:
yes I did but still same
Click to expand...
Click to collapse
Since you're up to 4.2.2, (assuming locked bootloader?) then there is not much outside of a factory reset to fix your phone's problems.
You might just have to get a warranty replacement.

jewbydoo said:
Since you're up to 4.2.2, (assuming locked bootloader?) then there is not much outside of a factory reset to fix your phone's problems.
You might just have to get a warranty replacement.
Click to expand...
Click to collapse
thank you for answer my friend,what does it mean locked bootloader,how can fix this,ı made just download 4.2.2,nothing else,what should I do

trapper66 said:
thank you for answer my friend,what does it mean locked bootloader,how can fix this,ı made just download 4.2.2,nothing else,what should I do
Click to expand...
Click to collapse
If you have a locked bootloader, it means the phone is locked down to where you cannot use custom recoveries (like CWM or TWRP) and you cannot flash ROMs that have a different kernel than what is currently on your phone. There's a whole host of other things, but that's the main issue.
Unless your phone is on JB version 9.16.9 or earlier (AND no one has flashed a later version and then flashed back to the previous version), then you cannot unlock the bootloader on this phone anymore.

iBolski said:
If you have a locked bootloader, it means the phone is locked down to where you cannot use custom recoveries (like CWM or TWRP) and you cannot flash ROMs that have a different kernel than what is currently on your phone. There's a whole host of other things, but that's the main issue.
Unless your phone is on JB version 9.16.9 or earlier (AND no one has flashed a later version and then flashed back to the previous version), then you cannot unlock the bootloader on this phone anymore.
Click to expand...
Click to collapse
Now,I have problem like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't my phone unlock,I tried this way (motorola offical bootlader way) the and I saw message like this,your phone cannot be unlock
is it normal ?

trapper66 said:
Now,I have problem like this
View attachment 2781977
I can't my phone unlock,I tried this way (motorola offical bootlader way) the and I saw message like this,your phone cannot be unlock
is it normal ?
Click to expand...
Click to collapse
you cannot unlock the XT926 with the official unlocker from Motorola unless it's the dev edition. Only the XT925 can be unlocked via the Motorola unlocker (at least for the RAZR HD phones).
But, you are already on Kit Kat. You even quoted where I said if you are apply an OTA greater than 9.16.9 version, you CANNOT unlock your bootloader ever. Once you do that on an XT926, you've patched the exploit that allowed unlocking the bootloader and nothing will ever put it back because it's in a protected area that you cannot flash back to a previous version to put the exploit back in.
Sorry, once you took the KitKat upgrade, you've lost any chance of unlocking the bootloader. Don't even try to flash back to a previous version. You'll brick your device. This has been stated over and over and over again since the KitKat ota has been released.

iBolski said:
you cannot unlock the XT926 with the official unlocker from Motorola unless it's the dev edition. Only the XT925 can be unlocked via the Motorola unlocker (at least for the RAZR HD phones).
But, you are already on Kit Kat. You even quoted where I said if you are apply an OTA greater than 9.16.9 version, you CANNOT unlock your bootloader ever. Once you do that on an XT926, you've patched the exploit that allowed unlocking the bootloader and nothing will ever put it back because it's in a protected area that you cannot flash back to a previous version to put the exploit back in.
Sorry, once you took the KitKat upgrade, you've lost any chance of unlocking the bootloader. Don't even try to flash back to a previous version. You'll brick your device. This has been stated over and over and over again since the KitKat ota has been released.
Click to expand...
Click to collapse
thanks my friend,I totaly understand I must wait to fix or new update, I suppose
you any idea about my problem ? why it's happening,especially phone is on lockscreen,when ı using the phone,tapatalk whatsapp facebook,there is no problem ,when I locked my screen it will be block and restarting,two or three times a day

trapper66 said:
thanks my friend,I totaly understand I must wait to fix or new update, I suppose
you any idea about my problem ? why it's happening,especially phone is on lockscreen,when ı using the phone,tapatalk whatsapp facebook,there is no problem ,when I locked my screen it will be block and restarting,two or three times a day
Click to expand...
Click to collapse
There is no way to unlock it, ever. Don't wait for a fix, as there is no fix to unlock the bootloader. It was never meant to be unlocked. It was unlocked via a security exploit and that exploit was patched after 9.16.9. There is no way to "fix" it.
As for your phone restarting, I would say a factory data reset is probably your only cure. It wipes everything (including your internal SD card), so be sure to back up what you can, especially pictures, etc.

XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC Rom needed!

Guys please help! If anyone can get XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml stock rom please send the link... my moto turbo is soft bricked but no rom is flashing and recovery shows this "motorola/quark_reteu/quark_umts6.0.1/MGPS24.107-70.2-7/7"
bootloader locked and cant boot to enable unlock

Several Indians (including me) are facing the same issue as the desired version of stock rom is not available in the internet. Visit moto service center and ask them to flash the updated stock one

Is there any other way to get? The service centre is very very far away..

I believe no other way till now.

Sanjith2908 said:
Guys please help! If anyone can get XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml stock rom please send the link... my moto turbo is soft bricked but no rom is flashing and recovery shows this "motorola/quark_reteu/quark_umts6.0.1/MGPS24.107-70.2-7/7"
bootloader locked and cant boot to enable unlock
Click to expand...
Click to collapse
sourav92 said:
Several Indians (including me) are facing the same issue as the desired version of stock rom is not available in the internet. Visit moto service center and ask them to flash the updated stock one
Click to expand...
Click to collapse
The problem is Motorola apparently never publicly released the India (RETEU) "GS" region full image version of this firmware. They only released the partial image OTA.
XT1225_QUARK_RETEU_6.0.1_MPGS24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml
The "GS" denotes a newer version than just the "G". Once you update to the newer version via OTA -- or try to -- you will be installing a newer version of the bootloader, which can NOT be rolled back.
If your bootloader was UNlocked, you can flash ANY region firmware or any previous India firmware to recover -- previous version of Marshmallow, Lollipop, even Kitkat for the XT1225. Region wouldn't matter, with an unlocked bootloader. (Just be sure to NOT flash gpt.bin!)
If you had an unlocked bootloader, you could flash any one of the BLUE 6.0.1_MPGS24.107-70.2_cid7 images in the screenshot below. (RETLA and RETBR would be the best choices as they are the Mexico and Brazil XT1225 carrier unlocked firmware. India XT1225 would still work just fine on those.) But, as you see the most recent publicly released India (RETEU) image (in red) does not have the "GS". With an unlocked bootloader you could even flash that -- as long as you leave off gpt.bin from the flash commands.
With a locked bootloader and no public release of the full image firmware you need, I'm sorry but you have to go to a Motorola service center. This is one reason you should always unlock your bootloader... It gives you more choices for recovery.
http://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=DESC&show=50
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes @ChazzMatt, there is no other way if the bootloader is locked. I am the person who noticed that "GS" thing first, and we already had a discussion on that in other thread. That's why I gave him the only solution to visit Motorola Service center.

sourav92 said:
Yes @ChazzMatt, there is no other way if the bootloader is locked. I am the person who noticed that "GS" thing first, and we already had a discussion on that in other thread. That's why I gave him the only solution to visit Motorola Service center.
Click to expand...
Click to collapse
iv gone to the service center and gotten the latest update installed but it is kindoff bugged and freezes a lot when I launch some apps
also i enabled the oem unlocking and am trying to unlock the bootloader but it says failed to get unlock data when i do fastboot get unlock data

Sanjith2908 said:
iv gone to the service center and gotten the latest update installed but it is kindoff bugged and freezes a lot when I launch some apps
also i enabled the oem unlocking and am trying to unlock the bootloader but it says failed to get unlock data when i do fastboot get unlock data
Click to expand...
Click to collapse
Read my bootloader unlock guide. OEM bootloader unlock in Settings by itself does nothing, unless the OEM wants it to do something. This has always been true. In this case, Motorola is one of the OEMS who make you get a bootloader unlock code to actually unlock your bootloader; LG is another one that requires this. You request a bootloader unlock code and follow the steps in my guide.
[UPDATED GUIDE] How to unlock your MOTO MAXX/MOTO TURBO bootloader, install TWRP and gain root access

[Guide] Unlocking the bootloader

The Nokia 7.2, surprisingly, comes with an unlockable bootloader. The information is shared by TechMesto and I am just re-using it to create this guide.
Notes:
Unlocking the bootloader may void the device's warranty.
All existing data on the device will be erased.
To unlock:
Update: Nokia has disabled the unlock ability with the December MR. You can only unlock if you downgrade your phone to an old release first. You can get it at Nokia Care or by buying remote flashing services.
Before you start: Make sure that you have platform-tools downloaded on your PC. You need to open a CMD or Terminal window in the folder where you have saved the platform-tools, unless you have installed them system-wide.
• First of all, enable Developer Options by tapping 7 times on BuildID in "About phone".
• Then go to developer options and enable OEM Unlocking option.
• Now reboot the phone into bootloader/fastboot mode. You can use the adb command:
Code:
adb reboot-bootloader
or else use hardware keys to reboot to bootloader mode.
• Make sure the phone is detected in fastboot mode. Then send the OEM unlocking command:
Code:
fastboot flashing unlock
• Confirm the unlock on the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• That's it!
You can also do the unlock_critical if you plan to flash the bootloader.

Reserved for future use.

I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?

KohGeek said:
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
Click to expand...
Click to collapse
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.

singhnsk said:
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
Click to expand...
Click to collapse
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.

KohGeek said:
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
Click to expand...
Click to collapse
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.

singhnsk said:
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
Click to expand...
Click to collapse
I was curious too, it kicked me off the bootloader screen when I was doing that on version 060, but it seems all is well now

https://nokiamob.net/2019/11/02/off...nlock-the-nokia-7-2-and-nokia-6-2-bootloader/

I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??

Coolboy996 said:
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Click to expand...
Click to collapse
You can use TWRP or patched image to root the 7.2

Can confirm that it is still unlockable. Got 2 of them today from Argos in the UK (Scotland). They are on 00WW_1_130 with security batch from 2019/08/05.
Only thing I had to do was enable internet and reboot to get the option to stop being greyed out.

Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.

allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Are you sure? Has Horrendously Menacing Dicks actually started blocking people having reasonable control of their 7.2 devices after letting them have it for so long?

allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Yep. They blocked the ability with the most recent December MR.

singhnsk said:
Yep. They blocked the ability with the most recent December MR.
Click to expand...
Click to collapse
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.

CGarz said:
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
Click to expand...
Click to collapse
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.

That really sucks. Now no devs will buy it =(.

allc0re said:
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
Click to expand...
Click to collapse
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.

bkttk2 said:
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
Click to expand...
Click to collapse
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.

Lamtanloc512 said:
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Click to expand...
Click to collapse
Think we may be out of luck then, but one last suggestion. I noticed when reading through the thread on user indicated they were using "flash" instead of "flashing" when trying to unlock the bootloader.
I know I personally did the same thing at first. Did anyone confirm that "flashing" was used?
I know the older methods used flash. Just asking.

Bought used Pixel 3: Is firmware custom?

Folks,
I bought a used Pixel 3, seller said it was only used for testing. Bootloader is unlocked, and the firmware version doesn't match anything listed on the Google site, but it may just be an older version no longer listed. Can anyone help me determine if this is a standard Android build? Build number: blueline-userdebug 10 QP1A.190514.001 5563344 dev-keys

Scooberjake said:
Folks,
I bought a used Pixel 3, seller said it was only used for testing. Bootloader is unlocked, and the firmware version doesn't match anything listed on the Google site, but it may just be an older version no longer listed. Can anyone help me determine if this is a standard Android build? Build number: blueline-userdebug 10 QP1A.190514.001 5563344 dev-keys
Click to expand...
Click to collapse
You can flash any firmware and bring it up to speed wit hthe latest, then relock yur bootloader if you dont want to tinker your Pixel 3
Follow the official instructions in the link below (from Google)
full factory image https://developers.google.com/android/images#blueline
Instructions: Look towards the top of that same page, linked above

BBobby said:
You can flash any firmware and bring it up to speed wit hthe latest, then relock yur bootloader if you dont want to tinker your Pixel 3
Follow the official instructions in the link below (from Google)
full factory image
Instructions: Look towards the top of that same page, linked above
Click to expand...
Click to collapse
Yes, I saw that and thought I might do it. Was a little confused by the fact that for the latest version there are two files with nearly identical names, one ending in Verizon. Is that for phones on the Verizon network or phones purchased from Verizon? Mine was advertised as unlocked, but I don't know how to verify that. If I use the wrong one I guess I will have problems? Should my phone update to the latest automatically if my ROM is stock?

Scooberjake said:
Yes, I saw that and thought I might do it. Was a little confused by the fact that for the latest version there are two files with nearly identical names, one ending in Verizon. Is that for phones on the Verizon network or phones purchased from Verizon? Mine was advertised as unlocked, but I don't know how to verify that. If I use the wrong one I guess I will have problems? Should my phone update to the latest automatically if my ROM is stock?
Click to expand...
Click to collapse
Reboot your phone. If a warning message comes up as your phone reboots that says your bootloader is unlocked, then it is unlocked.

Tulsadiver said:
Reboot your phone. If a warning message comes up as your phone reboots that says your bootloader is unlocked, then it is unlocked.
Click to expand...
Click to collapse
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?

Scooberjake said:
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Click to expand...
Click to collapse
Use the version that matches your carrier. If on VZ use that image. It will not lock the bootloader, just some modem changes.
You can go back and forth all you want.

Scooberjake said:
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Click to expand...
Click to collapse
If the bootloader is unlocked, it was not purchased at Verizon. Verizon phones have locked bootloaders. I have a google purchased unlocked phone that works fine with a Verizon SIM.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I can use this second one (since I am one Verizon) regardless of where the phone was purchased?
The bootloader is definitely unlocked (got the message on the phone). But I thought all Pixel 3 phones could be unlocked,not just the ones bought directly from Google.

Scooberjake said:
So I can use this second one (since I am one Verizon) regardless of where the phone was purchased?
The bootloader is definitely unlocked (got the message on the phone). But I thought all Pixel 3 phones could be unlocked,not just the ones bought directly from Google.
Click to expand...
Click to collapse
Yes, the VZ one.
No, only phones purchased through Google can be bootloader unlocked. VZ purchased phones can not. Some EU 3s can be bootloader unlocked after the contract is up.
All can be SIM unlocked.

One last question. Can I sideload an OTA rather than flashing the full factory image? I don't understand when to do one and when to do the other.

Scooberjake said:
One last question. Can I sideload an OTA rather than flashing the full factory image? I don't understand when to do one and when to do the other.
Click to expand...
Click to collapse
In your case flash the full factory image, including the wipe, since you're not real sure what firmware the phone is currently on. In the future you can do the ota if you want or the factory image without the wipe.

Question P11 [Solved] [HELP] Bootloader unlock, Unknown Command

Hi! I'm trying to unlock the bootloader of my Lenovo Tab P11 (TB-J606F, Latest software), but none of the command (without fastboot devices) works...
I've tried :
fastboot oem unlock
fastboot flashing unlock
Also, I got sn.img from zui website but it also didn't work.
When I type
fastboot flash unlock sn.img
(Which is based on their description)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FAILED (remote : unknown command)
I've tried both my laptop and desktop (which is all AMD-based) but nothing worked.
Is their any tips for me?
Thanks

I have Lenovo TB-J706F, maybe it's same.
I successfully installed TWRP and root.
Do you try fastboot oem unlock-go ?
Please read this and this.

d1m-ON said:
I have Lenovo TB-J706F, maybe it's same.
I successfully installed TWRP and root.
Do you try fastboot oem unlock-go ?
Please read this and this.
Click to expand...
Click to collapse
On my tablet the process failed, I don't know at what point.
I think because of the step of flashing vbmeta (I think) and now I can not even enter TWRP, it does not start Android and neither recovery, it only returns to fastboot every time it turns on.
Do you know any solution to this?
I have already tried to reinstall the OS with the Lenovo tool

byraan said:
On my tablet the process failed, I don't know at what point.
I think because of the step of flashing vbmeta (I think) and now I can not even enter TWRP, it does not start Android and neither recovery, it only returns to fastboot every time it turns on.
Do you know any solution to this?
I have already tried to reinstall the OS with the Lenovo tool
Click to expand...
Click to collapse
Well, I was able to fix it by making various combinations and attempts in the Qualcomm QFIL application until it answered correctly
Now I rooted without flashing vbmeta.img and the file no-verity-opt-encrypt.zip and it still works (those files gave me a bad feeling)

Congratulations! I didn't get it right the first time either.
Install TWRP, set up your tablet, make a copy in TWRP. Note that TWRP does not make a copy of the Storage folder - pictures, videos, music. But it makes and restores a copy of everything else perfectly. I had a chance to see this yesterday.

byraan said:
Well, I was able to fix it by making various combinations and attempts in the Qualcomm QFIL application until it answered correctly
Now I rooted without flashing vbmeta.img and the file no-verity-opt-encrypt.zip and it still works (those files gave me a bad feeling)
Click to expand...
Click to collapse
Um.. Did fastboot oem unlock-go worked in your case?

byraan said:
Well, I was able to fix it by making various combinations and attempts in the Qualcomm QFIL application until it answered correctly
Now I rooted without flashing vbmeta.img and the file no-verity-opt-encrypt.zip and it still works (those files gave me a bad feeling)
Click to expand...
Click to collapse
Where you bought your tablet?
Can you take a look insyde /system/app_backup folder? What apps are there? Give me a screenshot, please, if you don't mind, or just list it.

d1m-ON said:
I have Lenovo TB-J706F, maybe it's same.
I successfully installed TWRP and root.
Do you try fastboot oem unlock-go ?
Please read this and this.
Click to expand...
Click to collapse
Well, It still doesn't work..
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.029s

jupitkr said:
Well, It still doesn't work..
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.029s
Click to expand...
Click to collapse
A hour ago I was trying get serial number for TB-J606F on zui website and answer was: Enter correct serial numer, ahaha

d1m-ON said:
A hour ago I was trying get serial number for TB-J606F on zui website and answer was: Enter correct serial numer, ahaha
Click to expand...
Click to collapse
Oh I solved that problem by selecting Lenovo Phone(which is the first option : "Lenovo手机") and wrote imei1 000000000000000 (0*15). It worked in my case.

d1m-ON said:
A hour ago I was trying get serial number for TB-J606F on zui website and answer was: Enter correct serial numer, ahaha
Click to expand...
Click to collapse
And One more, Lenovo's mail would be in your spam mail folder!

jupitkr said:
And One more, Lenovo's mail would be in your spam mail folder!
Click to expand...
Click to collapse
Thank you, will try again. I know about Spam folder, was checked.
Did you manage to unlock it or not?
PS. Successfully received sn.img, thanks so much !!!

d1m-ON said:
Thank you, will try again. I know about Spam folder, was checked.
Did you manage to unlock it or not?
PS. Successfully received sn.img, thanks so much !!!
Click to expand...
Click to collapse
I'm happy to hear that.
I still failed to unlock it... Ahaha...
Can you try it on your device please?

jupitkr said:
I'm happy to hear that.
I still failed to unlock it... Ahaha...
Can you try it on your device please?
Click to expand...
Click to collapse
I have a different tablet. TB-J706F, I was trying to get a sn.img for a forum mate. He was going to try the unlock today. I will let you know the result when it happens.

d1m-ON said:
I have a different tablet. TB-J706F, I was trying to get a sn.img for a forum mate. He was going to try the unlock today. I will let you know the result when it happens.
Click to expand...
Click to collapse
Thanks. I'll wait for your reply!

jupitkr said:
Thanks. I'll wait for your reply!
Click to expand...
Click to collapse
jupitkr, I remember, look this: https://forum.xda-developers.com/t/pad-11-tb-j606f-unlock-magisk-rooooot.4288159/​

[None]

d1m-ON said:
jupitkr, I remember, look this: https://forum.xda-developers.com/t/pad-11-tb-j606f-unlock-magisk-rooooot.4288159/​
Click to expand...
Click to collapse
Thanks. Do you know what the firmware version is? Mine is 210421 but still doesn't work.
If it has lower version, I'll try downgrade.

jupitkr said:
Thanks. Do you know what the firmware version is? Mine is 210421 but still doesn't work.
If it has lower version, I'll try downgrade.
Click to expand...
Click to collapse
Asked him, waiting for answer...
PS Got answer! S120184_210520_ROW, upgraded two days ago.
PSS. Third user got unlock: https://4pda.to/forum/index.php?showtopic=1014576&view=findpost&p=107206283

d1m-ON said:
Asked him, waiting for answer...
PS Got answer! S120184_210520_ROW, upgraded two days ago.
PSS. Third user got unlock: https://4pda.to/forum/index.php?showtopic=1014576&view=findpost&p=107206283
Click to expand...
Click to collapse
No update available through OTA, so I'm flahsing the firmware by Lenovo rescue and smart assistant.