Database Info

XZ Root/TWRP/ROM Help

Hi XDA,
It's been a while since I've done any work on any phones, I've previously used roms on Galaxy S and SIII. But those are a while ago as you can see. I've got an Xperia XZ, the bootloader is currently unlocked. But I cannot, for the life of me, get any further despite following several guides and programs. So I'm at a loss.
At this exact moment, I have my XZ connected to my pc with the blue light on. CMD in ADB/Fastboot cannot detect the device. My understanding is I need to flash the kernal and recovery first, then I can consider flashing a custom rom.
Would anybody be able to assist me? I dropped this project a few months ago, so I'll need to check what rom I was going to use and update the img files I have.
Thanks

Installed fastboot abd on pc?

Yep, that's been installed. I do have an issue which I thought/think is driver related as the daemon doesn't always start, and doesn't detect the phone correctly either.

What OS is on your computer?

Windows 10, I also tried Linux Mint but didn't get much further.

Have you disable the drivers vetification?

Yep!

Can flashtool detect your device? Sorry for all the questions but got to start somewhere and have you tried changing USB ports and cables?

No, the questions are good. There will be something wrong that I can't find, so we need to work it out somehow.
Flashtool doesn't consistently detect the device. The computer does, flashtool doesn't. I have changed the cables with some success, but that hasn't helped me progress much further.

Hmm, have you install the drivers from Sony developer site? Also try it on another computer..i wonder if you have a bad connection port on your phone thus the reason I asked about another computer.. Try reinstalling fastboot and adb, drivers etc. with your anti-virus disable.. And does Sony companion work? USB debugging turned on?
Sounds silly but sometimes we forget, like redoing doing your phone from scratch and you can't delete some stuff and only to remember later that you forgot to install busybox or mount your system partition.. lol

Thanks Lilbrat,
I'll be doing a fresh install, hopefully this weekend. And will cover what you have mentioned and report back. Thanks!

since this is your first Xperia device, you must first familiarize yourself with the ENVIRONMENT and TOOLS in which SONY Xperias can be played with !
some basics I wrote for X, but applies for XZ also , please read as it will be helpful!
https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
now
since your boot is already unlocked so I can safely assume that you don't have TA.img file at all!
this leaves you with only two solutions
1. install 3rd part ROMS
2. flash sony STOCKROM and flash MODDED kernel (most of us do this)
your XZ has project name by SONY called KAGURA, your device on xperifirm is recognized by this name, dual/single you have to specify
from flashtool, xperifirm, download latest firmware 41.3.A.2.157 under KAGURA, close xperifirm and FLASHTOOL will start creating FTF file AUTOMATICALLY, click OK to any script question. and let it create ftf for u
flash it on your XZ,
send me kernel for 41.3.A.2.157, i will patch it for u! (patching guide is given in this forum but at this point i think it will be too much for you, so i will fix the kernel for u)
KAGURA twrp can be found at https://dl.twrp.me/kagura/ ( unlike SAMSUNGS, sony Xperias don't have inbuilt RECOVERY )
flashing recovery is MUST!
when device is switched off, connecting USB CABLE to PC and MObile while
1. HOLDING VOLUME UP KEY (blue LED) is FASTBOOT MODE (used mainly for sending twrp and kernels )
2. HODLING VOLUME down KEY (GREEN LED) is FLASHMODE (used mainly to FLASH stock roms using FLASHTOOL
you must install
1. Xperia Companion
2. flashtool ( www.flashtool.net) (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ)
3. install minimal adb and fastboot 1.4x from XDA (google it)
4. using these TOOLS you can
a-flash firmwere
b flash recovery
c flash modded kernel
d boot in to recovery (twrp) and flash MAGISK 16.x .zip from twrp + drm patch files! ( i will give you later with modded kernel)
e reboot and your device will wakeup ROOTED having DRM FIX! ---- switch off the SOFTWARE updater using any ROOT APP FREEZE app from playstore!

Currently working through a reinstall of flashtool etc, I can detect the phone using the Sony Companion tool, so thats positive. I haven't seen any notification that drivers have installed, but I do have the XZ drivers unzipped here.
Edit1: It doesn't detect or anything when the blue or green lights are on phone either. Not sure about them at this point.
Edit2: Just going through your guide as well Yasu, I cannot locate "sony Xperia X motherboard drivers (sa0107)" or anything similar to my device. Just throwing that out there. Installing the two common results in Sony Mobile Communications (ggsomc( USB (11/10/14 3.1.0.0) installing, but Google. Inc (WinUSB) AndroidUsbDeviceClass (12/06/10 4.0.0...) failing.
Will continue. Derp, just noticed I have a completely different flash tool. Sony Mobile Flaster by Androxyde, v0.9.25.0 but atleast it detects the connected device more than previously.
21/004/2018 13:04:44 - INFO - List of connected devices (Device Id) :
21/004/2018 13:04:44 - INFO - - USB\VID_0FCE&PID_0DDE\CB512CK84Q Driver installed : false
21/004/2018 13:04:44 - INFO - List of ADB devices :
21/004/2018 13:04:48 - INFO - - none
21/004/2018 13:04:48 - INFO - List of fastboot devices :
21/004/2018 13:04:50 - INFO - - none
Edit 3: Right, forgot to disable Win10's driver signature. Fixed that part again.

Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.

AVeers said:
Downloaded the wrong firmware, so just working on that again (41.3.A.2.157 / R1E).
I was planning to flash Rudy's AOSP Oreo, but I'll have to go back and see as I chose that several months back.
Edit1: Completed flash. Phone is now 41.3.A.2.157, kernal 3.18.66. Android 8.0.0, bootloader unlocked. Rooted says no. This is certainly a lot more difficult than I remember!
Edit2: Recovery flash completes when command is ran, but adb does not register the device being listed, fastboot does. So I've hit the stump again with being unable to successfully flash twrp-3.2.2-0-kagura.img as recovery.img
Edit3: Last one for today. I can't open recovery from my phone, but can force it with fastboot boot recovery.img which has worked. However, it has loaded to a Mount - Decrypt Data screen and wants a password. I'm not aware of a password being required, and if I recall the device is encrypted. Ouch, should have seen this coming.
Click to expand...
Click to collapse
1. as i mentioned " (after installing goto C:\flasthool\Drivers folder and install the driver.exe select COMMON Fastboot / flashmode drivers + z5/z4/z3 family of all drivers (there is no XZ , as Z5p drivers supports XZ) "
2. once these drivers are installed, you will get SOMC notification when very first time you connect your XZ in any MODE (volume up / and /or / volume down)
3. while flashing firmware, if you didnt tick WIPE areas, you will get encryption error , you must perform CLEAN FLASHING
4. before booting in to twrp, you must flash MODIFIED KERNEL - you can take modded kernel from my post in this forum
5, boot into twrp, flash drm fix files, flash magisk and wipe delvik cache/ cache and Reboot!

Yep, I see what you mean now. I missed the options on the flash screen, I thought it was odd that the time it took didn't match anything close to the times you described.

That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.

AVeers said:
That didn't end well, clean flash, flashed kernel, TWRP booted correctly this time from the phone. Except phone now won't boot past the Sony logo.
I was also comparing your instructions against korom42's, and another third party. Which naturally are all similar and straight forward, still didn't help.
Click to expand...
Click to collapse
did you flash the modded kernel?
if you simply flash magisk on original kernel!
you will be stuck on SONY LOGO

OK, I still following this with some interest, as a bit of clarification seems to be needed.. Now granted for some reason Flashtool doesn't have the XZ drivers even the newest version but there are mb drivers on Sony Developer site.. https://developer.sony.com/develop/drivers/ . (see pic)
@AVeers, more computer questions reason being you said Flashtool is seeing your phone a bit better, which leads me to believe you're still having driver issues.. Are you on a laptop or a desktop? If it's a desktop have you tried plugging your USB into the rear panel, straight into the mb also have you tried disabling your anti-virus when installing your drivers? Oh, and where are you located as your firmware is for the middle east, if I remember correctly..

Hi Mate,
I won't be able to work on this further until the weekend. But I do have those drivers from Sony here. And have been using firmware as per Australia (generic). Which is correct for my location.
The phone is plugged into the mobo via rear panel, and this is a desktop running Win10. I'm in test mode to eliminate the driver signing issue. I have not disabled the anti-virus, but I haven't had issues before.
When I run the flash for the firmware, boot.img or twrp.img, it takes seconds to complete, generally less.

How to fix MOTO G7 / xt1962-1 stuck in Bootloader (stuck in fastboot) unable to boot

I do not have 10 posts yet, remove underscores from urls. I will edit this when I have 10 posts, I'm sorry for the slight inconvience.
Hi, new here! I recently acquired a Motorola G7 (xt1962-1/river_amz) from my sister. The device did not boot. It mentioned that the device did not start-up successfully, something in relation to slot/a and slot/b, and that I needed to utilize a Software Repair Assistant.
Non-Verizon devices cannot utilize this Software Repair Assistant, I tried and it hung at Processing Device Info. For Non-Verizon devices there's a piece of software called Lenovo MOTO Smart Assistant which can be found: https://support.lenovo.com/us/en/downloads/ds101291
This option did not work for me as the Bootloader did not for some reason allow the device to overwrite some of the content (permission was denied device side.)
The MOTO Smart assistant was good for downloading the devices software. So you do the following:
Download and install the smart assistant software
Click the flash option and then the rescue option
Click moto phone
Select moto g (7th gen)
Select xt1962-1 and then next to target and firmware name there's a download button press that and the firmware will start downloading
You can follow the onscreen instructions for that program, like I said however, it didn't work for me so I'm just going to tell you the steps I went through to get the device working. If you have other solutions, I, as well as the rest of the MOTO G7 users will be happy to hear what worked for you I'm sure.
I tried downloading the files from /moto-g7/development/moto-g7-river-xt1962-1-firmware-29-114-t3913673 on this site and flashing those with some of the below mentioned methods but, no dice.
The default firmware download directory is C:\ProgramData\LMSA\Download\RomFiles btw.
I didn't want to fuss with trying to get RSDlite working on Windows 10. I found that an older PC with a 32-bit install of Windows 7 was far easier to manage, so, that's what I went with.
To follow what I did:
Download RSDlite 6.2.4 from rootjunky's site via: http://rootjunkysdl.com/files/?dir=Android Programs
Download 32-bit drivers from: http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola if LMSA did not install them already
Copy the firmware folder to your desktop or somewhere easy to work from
Ensure your device is in bootloader mode
Open RSDlite and your device should be detected
Select the firmware folder and open flashfile.xml with RSDlite and press start
Let the process finish and don't interupt or you will have to do it all over again
The phone should boot, you will more than likely have to sign into an google account that's already been in use on that device (due to FRP)
You can also use the XML to BAT method, that didn't work for me (remote permission denied/device side)
I hope this helps some people who struggled like I did. Also, sorry if some things are badly worded if at all. I'm autistic and have trouble explaining and expressing things.
Check out my stock resources thread: https://forum.xda-developers.com/moto-g7/development/riveramz-stock-resources-t3917937/

Worked perfectly!
Thanks! I had the same issue (my wife's Moto G7 stuck at the bootloader) and was able to follow your directions, so much appreciated.
The only change I made was to follow the directions at this video (go to youtube/watch?v=njXQYn53SPc) to perform the XML to BAT instead of using RSDlite (since I was on Windows 10).
It worked perfectly and fixed the issue--and the great thing was that by converting the servicefile.xml instead of flashfile.xml, I was able to retain all the data on the phone.
The overall sequence of steps (listed in detail, since this was my first time flashing. Remove underscores from URLs):
Download Lenovo Assistant from your link
In Lenovo Assistant, go to Flash, then Rescue, then select model of phone. Click to download the firmware (but do not actually click the "rescue" button).
Download Google's Platform Tools (to get fastboot and ADB)
Make a folder to hold everything (called "flash")
Copy the downloaded firmware folder from C:\ProgramData\LMSA\Download\RomFiles to flash folder. Copy the fastboot, adb, and adb dll's from the Platform Tools to the firmware folder (per the video).
Copy and edit commands from servicefile.xml to a new servicefile.bat, as described in the video. Place this file in the firmware folder.
Run batch file in command prompt from the firmware folder.
That got the phone running again, with all data intact.

Thank you so much, worked like a charm.

Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Sent from my Samsung SM-G973U1 using XDA Labs

mattmsr82 said:
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Click to expand...
Click to collapse
May need to use a
Loader file or blankflash
See
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342.
Sent from my mata using XDA Labs

I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
start up failed
your device didn't start up successfully.
use the software repair assistant on computer
to repair your device
connect your device to your computer to get
the software repair assistant.
AP fastboot flash mode (secure)
no bootable a/b slot
failed to boot Linus.falling back to fastboot
Fastboot reason: fall-through from normal boot mode
USB connected
Click to expand...
Click to collapse

MrCabana said:
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
Click to expand...
Click to collapse
I ended up sending my phone back to Motorola, they they fixed it and sent it back overnight...
Sent from my Samsung SM-G973U1 using XDA Labs

Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!

I don't have a Windows 10 PC...plus, if I screw up my phone, I'll catch hell from the wife...lol
SO...that being said, if someone has an XT1962-6 'River' RETIN phone running Android 10 w/June Sec. Patch....I'd be willing to 'donate' to their paypal for a copy of my phones fw! Anyone interested plz pm me. Thx!

Good day, your post was very useful for me, bring back my phone, Im very grateful, thanks, sorry for my english

switch off your phones and connect usb.
first install drives to your pc by searching where to find device drivers motorola
then download lenovo smart assistant and press rescue

Hi. Im new here too. Well been for a while just my second post and the first time iv actually been able to flash a rom. I have the same problem. No bootable slots. I know exactly what i did wrong. I knew it the moment i hit the reboot button. However, i run zorin 15 on my pc and the levono assistant don't support linux. Anyone know where i can acquire the assistant running linux? Greatly appreciated in advance.

Thank you very much sd86 and chi2 for your research and help
Sadly my phone can't boot after flashing clean OS
I don't want to erase UserData partition, but it seems error is there (as it's only left partition untouched).
As I still would like to keep my data (this is the most important thing on our mobile devices) the only one hope is to unlock bootloader, flash recovery partition (eg. with TWRP) and then perform a backup from recovery software.

Help installing custom ROM on Moto g8 plus

Code:
Boot failed. Press POWER KEY to retry.
Your device didn't start up successfully.
Follow these instructions if the failure cannot be recovered after retrying.
If this is a Verizon device, please use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assistant did not help for any reason, please contact customer care for furthur assistant.
AP Flashboot Flash Mode ( Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Hi everyone,
I've wanted to root my Android phone for a while now, so I decided to do it these holidays, following instructions on getdroidtips ( How to Install Lineage OS 17.1 for Moto G8 Plus | Android 10 [GSI treble] (getdroidtips.com) ). I couldn't boot into TWRP recovery mode for some reason, (maybe it didn't install properly) so I tried to install Havoc OS using ADB. My phone then rebooted several times and then gave an error message, saying I could either try rebooting again or factory reset. I chose factory reset and went through the whole process again twice, the third time with Lineage OS. It then gave a different error message (in the code block). I can use the volume keys like in the bootloader, but couldn't get it to boot. I also can't access the phone over ADB.
This was my first time messing with Android beyond basic ADB commands, so I didn't really know what I was doing. I might have messed up the instructions or made some other mistake. All of my data is backed up, so all I'm hoping for is to either boot Lineage OS or somehow flash the stock ROM again.
Does anyone know how to solve this issue?
BTW I am not on Verizon.

I've run into a few of these situations. I also tried this version of Android as a Custom Rom and got a Boot Loop
I had to use TWRP to reinstall my TWRP backup.
Just in case you don't have TWRP or TWRP access for some strange reason you could try this:
I have a moto g8 plus xt2019-2
Motorola_Moto_G8_Plus_XT2019-2_DOHA_RETBR_9.0_PPI29.65-43_(MobileGuru4.com)
Motorola Flash File For All Model (Stock ROM) - Mobile Guru4
Download Motorola Flash File for all Motorola models. Here all Stock ROM and firmware files given for Motorola phones are official original files
www.mobileguru4.com
Search for this on google, when you find it download it. Then inside the zip file once you unzip it find the directory that is labeled - firmware
Inside that directory there's a file labeled "flashfile.bat" This setup uses ADB with ADB Fastboot on the phone. I assume you know how to get ADB Fastboot on your phone. When you execute the above file you will see it working in the command prompt on your computer. Let it run. It will not show anything on your phone until your phone reboots. This is what I use as a DISASTER BACKUP in case TWRP is unusable or in any way I'm unable to get to it.
I hope this helps you, it worked on my phone.

Thanks for the reply. Unfortunately, I can't try it because I've already sent the phone away to be repaired. The repair company said they would have to send it away when I originally emailed them. The repair company had a no fix no fee arrangement, so if they can't do it I'll try using fastboot. Hopefully that will happen and I won't have to pay $200.

sorry my english, i have the same problem and already try everything, rsa always fails and rsd lite does not recognize my device in windows 10, i tried to short the motherboard and it didn't work, i am seriously thinking about changing the motherboard or sell the parts

Blackview Tab 8 unlocked Bootloader, but how to magisk?

Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo

Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards

I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?

nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.

I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.

2.0.4DJB TCL 10 Pro Firmware Update

This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch

KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.

JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.

KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.

JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to

KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.

Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.

JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar

Well you're in luck as it is just a .bat file program simple notepad++ will do.

I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.

Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol

@KaptinBoxxi Sounds like you have Ambient Display on for notifications.

mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD

that sucks... could try reseating the screen's ribbon cable :-/

can anybody share the full update rom about android 11?

top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page