Database Info

Bricked MT6577 SoSoon/Senq X8 Elite 3, NO USB Debug/ADB, Stock Recovry No Roms to D/L

I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time

Hello have you tried a hard reset so far ?

-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it

can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations

-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"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"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.

the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope

-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk

-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.

Flashing Firmware: A Simple Guide

When it comes to flashing firmware for the XZ Premium, I know there is a plethora of information scattered through many threads in this section. Quite frankly, I was a little overwhelmed with the whole flashing process, and, despite everyone's best efforts, was totally lost. I just wanted to flash my USA XZ Premium to the Central Europe FW to enable the fingerprint reader, but I didn't want to alter the radios, etc like in the other thread that describes the process.
So, after a bit of trial and error, I decided to put together a simple guide that I hope is easy for those with a little less "flashing" experience. I'd like to point out that none of this information is my own; I'm simply compiling it in a way in which I believe will be helpful. This post is only possible because of all the people who have contributed in the various flashing threads thus far, so many thanks to all of them. Also, I know it's a touchy subject around these parts, but I wanted to give a shout out to the developer of Newflasher -- without his tool, we all still may not have method to flash our XZPs. Thank you, sir.
Anyway:
1. Find, download and install/extract Newflasher, XperiFirm, Flashtool and the official Xperia Companion application.
2. XperiFirm: download whichever variant of the FW you’d like to load. Be sure you are choosing the correct version of your hardware.
3. Flashtool: go to the application folder, then go to the drivers folder. Run this app, and check the boxes next to Flashmode Drivers and Fastboot drivers. You will need these installed to avoid any possible connection issues with Newflasher.
4. Open the folder which contains Newflasher so you can view all of the contents. Do the same with the firmware folder that you now have which was downloaded from XperiFirm (Ex. G8142_Customized CE1).
5. Copy all of the .sin files, as well as the partition and boot folders, from the firmware folder over to the Newflasher folder. Create a new folder name "partition," and extract the existing partition folders files (that you copied from the firmware folder) in to the new partition folder.
6. Power down your phone and wait 5 seconds. Hold the volume down button with the device powered off, and plug your device into your PC.
7. Run Newflasher.exe. You should now start to see the application working (this process took about 5-10 minutes for me). It will tell you when you can disconnect.
8. Open the Xperia Companion application, and, following the on-screen instructions, do a Software Repair on your device.
9. Start your device like normal, and you should have your new software loaded!
Thanks again to all who have contributed to this process!

thanks just flashed mine from Three over to the UK customised
working great

Thanks for the guide. But someone can make a YouTube video how to flashing xzp with newflasher please! Cant find one there ty.
Sent from my G8141 using Tapatalk

Question
If I flash my phone ( details in screenshot) will it remove demo mode application that installed in it? Retail demo mode.
{
"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"
}
Thanks in advance. Don't be hard on me I am new to this. :fingers-crossed:

For those left still confused by the lack of detail above, here's a more visualized and well explained flashing method I found and mentioned in my XZP flashing thread a while back. Also has links to newflasher - which this one doesnt
https://forum.xda-developers.com/showpost.php?p=73176149&postcount=3

Ok it worked for me, just the step of repairing with pc companion did not work, pc companion restores firmware original telcel MX, so after flashing no longer repair with pc companion and finally worked.
Firmware flashing 45.0.A.7.120 generic Latam
Thanks for this tutorial !!! I hate the telcel personalization !!!

kinkyK said:
thanks just flashed mine from Three over to the UK customised
working great
Click to expand...
Click to collapse
After flashing what system apps were preinstalled? Im just wonderinf because I just got my XZ premium today and there seems to be a fair bit of bloat I wanna get rid of but cant with out root and dont wanna root because of drm, also because there isnt much support.

Just the standard Sony stuff really mate no operator stuff
Seems much better like

kinkyK said:
Just the standard Sony stuff really mate no operator stuff
Seems much better like
Click to expand...
Click to collapse
Did you have spotify pre installed?

RJASSI21 said:
After flashing what system apps were preinstalled? Im just wonderinf because I just got my XZ premium today and there seems to be a fair bit of bloat I wanna get rid of but cant with out root and dont wanna root because of drm, also because there isnt much support.
Click to expand...
Click to collapse
Try this tutorial. I've successfully deinstalled some system apps without root:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/

RJASSI21 said:
Did you have spotify pre installed?
Click to expand...
Click to collapse
Yes m8

kinkyK said:
Yes m8
Click to expand...
Click to collapse
OK thanks for the info.

If you flash the ce1 firmware to the us xzp do you retain the ability to receive ota updates? Do any problems arise from flashing international Firmware?

IS33D34DP30PL3 said:
If you flash the ce1 firmware to the us xzp do you retain the ability to receive ota updates? Do any problems arise from flashing international Firmware?
Click to expand...
Click to collapse
You'll still be able to receive OTA updates. No problems /should/ occur when flashing the international firmware. My brother has the XZP (US Variant) and I him flash a UK firmware to enable the fingerprint sensor.

IS33D34DP30PL3 said:
If you flash the ce1 firmware to the us xzp do you retain the ability to receive ota updates? Do any problems arise from flashing international Firmware?
Click to expand...
Click to collapse
CE1 seems to get FW updates later rather than sooner, so keep that in mind when flashing.

The_Newtype said:
CE1 seems to get FW updates later rather than sooner, so keep that in mind when flashing.
Click to expand...
Click to collapse
I flashed my US version with 45.0.A.5.1 when i got it. I'm yet to receive an OTA.

Guys I need help to finishing flashing my XZP
Guys maybe im doing something wrong or missing something here, please someone guide me because this is my 1st time flashing a phone.
Im trying to flash my US version XZP dual sim (G8142) to Central Europe(CE1) firmware to enable fingerprint sensor, but when I start newflasher, it wont do anything, and it just says: Optional step! Type 'y' and press enter if you need Gordon flash driver, or type 'n' to skip. This creates GordonGate.7s archive in the same dir with newflasher.exe!
and it just stays there and do nothing, what should i do? type 'y' or 'n'? i dont know what are the next steps...
Because in step #7 you said that you will see the application working (about 5-10 minutes), but in my case I dont know what im missing because when I start the program it just doesn't start doing its thing.
someone please tell what im doing wrong or if I should install that Gordon flash driver because I really wanna enable the fingerprint.

johnpgv said:
Guys maybe im doing something wrong or missing something here, please someone guide me because this is my 1st time flashing a phone.
Im trying to flash my US version XZP dual sim (G8142) to Central Europe(CE1) firmware to enable fingerprint sensor, but when I start newflasher, it wont do anything, and it just says: Optional step! Type 'y' and press enter if you need Gordon flash driver, or type 'n' to skip. This creates GordonGate.7s archive in the same dir with newflasher.exe!
and it just stays there and do nothing, what should i do? type 'y' or 'n'? i dont know what are the next steps...
Because in step #7 you said that you will see the application working (about 5-10 minutes), but in my case I dont know what im missing because when I start the program it just doesn't start doing its thing.
someone please tell what im doing wrong or if I should install that Gordon flash driver because I really wanna enable the fingerprint.
Click to expand...
Click to collapse
You need to extract the Gordon flash driver and install it manually

hi all, good to be here
thanks for tutorial, sounds good
two questions only:
the downloaded firmware (CE1) contains much more files inside as mentioned in the 5th step of the tutorial
are these files really not needed?
and
if something may go wrong and flashing will be unsuccessful, will it harm the phone? if yes, can i restore the last firmware with Xperia Companion?
thank you

help
Is there anyway possible that you could post a video of how to do it. I'm a better visual learner and I have been struggling for quite sometime now to complete the task so that I could flash my US version xz premium to the Central Europe so that I may use my fingerprint scanner.

flashed wrong bootloader

Idk what to do I flashed the wrong bootloader on my S7 (snapdragon) through flashfire and now I get a black screen with a blue LED with a green LED slowly blinking behind it. How to recover? Right now I'm just letting it die. Can't hard reset either.

rifek4 said:
Do a download mode is working for you?
Click to expand...
Click to collapse
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..

savagevegeta said:
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..
Click to expand...
Click to collapse
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7

*Detection* said:
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7
Click to expand...
Click to collapse
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?

savagevegeta said:
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?
Click to expand...
Click to collapse
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult

*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
I am open to suggestions on what tools i may use. Im trying the flash tool as soon as i get home.
I tried to downgrade using flashfire after rooting the device but it failed and thats why it's dead.
At first it was just a blue light with a green one blinking behind it, but i let it die over night in hopes of being able to recover it in the morning. Now, there isnt even the light.
The battery isnt dead according to my multimeter.
While the bootloader is locked, it HAD engineerboot so maybe that allows something. :/
I would have taken it to a repair shop but the closest one knows nothing about software issues and only suggest hardware repairs, hence me wanting to replace the motherboard.
I'm going to search how to fix it with linux since i have a linux machine, i just have no experience with it at all. At least pushing the bootloader will help an awful lot. If you have any knowledge on any of these, even the slightest, do share. Ill do some research meanwhile and if i find a fix, I'll post it. This phone was so good and i miss it dearly, which is why i need all the help and research i can get.
Apparently no one has ever bricked the snapdragon version of this phone, given the lack of any google results similar to this situation on this phone. ;-;

*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
Its in QUSB_BULK now. At least the computer SEES it

savagevegeta said:
Its in QUSB_BULK now. At least the computer SEES it
Click to expand...
Click to collapse
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
---------- Post added at 22:51 ---------- Previous post was at 22:25 ----------
Not sure how to enable the bootloader update function, if it will enable once you load firmware into the sections on the right, but try ODIN 3.12.10
{
"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"
}
---------- Post added at 22:53 ---------- Previous post was at 22:51 ----------
https://forum.xda-developers.com/showthread.php?t=2711451

*Detection* said:
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
Click to expand...
Click to collapse
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5

savagevegeta said:
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5
Click to expand...
Click to collapse
Yea I know about the one for the S5, that was my phone before the S7, maybe PM that dev (He's from XDA) on the S5 forums and see if he could help you out?

Vortex SYNQ Dev Thread (TWRP Image & Bootloader Unlock!!!)

During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
UPDATE: We now have enough people to really get the ball rolling for some development for this phone, so as we accomplish more things we'll post them here

Anything you try from here, you do so at your own risk. This may void your warranty, break your device, etc.
HOW TO UNLOCK THE BOOTLOADER
Go to Settings>About Phone>Build Number and tap this a lot really fast to enable developer mode
Go to the new developer mode option in the Settings menu, check the switch that says Allow OEM Unlock
Plug your phone into your computer, enable ADB Debugging, open up a terminal on your computer, and initiate an "adb reboot fastboot" to put the device into fastboot mode
In your computer terminal again, type in "fastboot oem unlock". If it fails, run it again. If it fails again, reboot to fastboot one more time and try a couple more times. Eventually it should work after a couple tries, it did for us
Confirm the device unlock on the phone (pressing volume up at the prompt I believe), and wait for the phone to reboot. Note that it's not stuck in a bootloop at this point, it's just factory resetting after the unlock, so give it time to work
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 1
Pull a recovery image from the phone with SPFT using a proper mtk6739 scatter file which I can't exactly find
Port TWRP to the phone from another device's mtk6739 TWRP image with carliv image kitchen tool, and flash it back to the phone with SPFT
Flash Magisk in TWRP, reboot, profit
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 2
Pull a boot image with SPFT
Use the Magisk APK to inject magisk into the boot image
Flash the boot image back with SPFT (or maybe fastboot), reboot, profit
HOW TO FLASH TWRP TO THE PHONE (STILL EXPERIMENTAL)
Download the TWRP image from here
Reboot to the bootloader
Assuming you unlocked the bootloader from before, just do "fastboot flash recovery [imagename]" to get it on there
If fastboot complains about it not being able to flash, try running the command one more time
CUSTOM ROMS FOR THIS PHONE
This phone came with 8.1 Oreo, so that means it has to be Treble enabled. I'm no expert with Treble stuff but I believe GSIs made for arm a-only partitions SHOULD work on here. We haven't tested this for ourselves yet though
Like mentioned before, feel free to drop by and leave a message if you're willing to help us out on our endeavors. I also want to try and get 'Thew a working recovery on his phone again if possible, since for some reason when we try to flash back the image we pulled (with our "best guess" mt6739 scatter file) it didn't work

i might have one.. i will check as soon as i get to the shop

jasonmerc said:
During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
Unfortunately during our testing, he seems to have messed up his recovery image and is unable to restore a stock one on there. If there's any other owners out there willing to help us out (and maybe willing to risk their device for some test builds of TWRP too) I beseech thee to make yourself known.
Click to expand...
Click to collapse
i have one .. if you need

desbloqueokings said:
i have one .. if you need
Click to expand...
Click to collapse
Check your PMs on here, just sent you something

So the other 6739 scatter files we found didn't exactly work for this phone, so we pulled our own with a tool we found on Hovatek. This isn't a "port" from another phone, this directly came from the Synq itself.
Give major thanks to @desbloqueokings for pulling this for us!

The group we had seems a bit inactive now, so I'll post my new creations up here for all you guys here to test and tell us all if it works or not. One is a patched boot image that contains Magisk, all you'd need to do for that is flash the boot image and install a Magisk APK and you should be good to go for root. The other is a dirty port of TWRP Recovery I did from another MT6739 phone. It was hard finding an image to port from, so I want to give a huge thanks to @lopestom who sent me a 6739 image he had that I could port from
PLEASE BE AWARE THAT THESE ARE TEST IMAGES. I DONT HAVE THIS PHONE MYSELF AND CANT TEST IT MYSELF, SO IM NOT SURE IF THESE WILL WORK OR NOT. PLEASE MAKE A BACKUP OF YOUR CURRENT BOOT & RECOVERY IMAGES WITH SPFT USING THE SCATTER FILE ABOVE BEFORE TRYING ANY OF THIS. WHAT YOU DO TO YOUR OWN PHONE IS YOUR OWN RESPONSIBILITY. WHILE I WILL TRY TO HELP YOU IF SOMETHING BREAKS, IM NOT RESPONSIBLE FOR WHAT YOU CHOOSE TO DO
With that being said, here's the Mega folder containing the boot and recovery images. You can either flash these through SPFT like most people do with mediatek phones, or through fastboot, whatever you can get working. I'd also recommend you unlock your bootloader using the method posted above before doing any of this
Let me know if this stuff works or not, if you choose to flash it

Our victory was bittersweet, but a victory nonetheless
We got a working recovery image from @lopestom that seems to work fine on the surface, but when we need to flash the zip that disables dm-verity (disables force encryption) it supposedly breaks the /system partition on the stock ROM. My recommendation would be to take a backup of your /system directory in recovery before trying to flash anything. But since this is a Treble-enabled device, that means GSI ROMs could also work when flashed.
Here's a link to the recovery image we were using. We flashed it in fastboot with an unlocked bootloader but I imagine it would work just fine in SPFT too. I was told by the person that made the image that it's apparently not a good idea to flash the disable-force-encryption zip on a dirty port of a TWRP image like this (and to also never wipe /data). While you should be able to use this TWRP to flash something like Magisk, don't do those other two things for now.
Here's some screenshots from @Matthew702 to show the phone booting to TWRP (we made the mistake of trying to wipe /data and trying to flash the disable-encryption zip, please do not do 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"
}

Thank you!

You guys are amazing.
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx

xAlimorAx said:
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx
Click to expand...
Click to collapse
Yeah it showed up in Russian for our tester too. Not sure why it does that, but otherwise it should still work fine

Need your assistance
Season greetings to you my friend, I ended up formatting my vortex synq using Sp flash tool, after attempting to root, now I have black screen only vcom for sp flash tool works but I need preloaded files and others to unbrick, it was gonna be a Xmas gift for my aunt, but I messed it up, wont turn on just vcom when connected to PC, I have the files stckboot and recovery but sp tool needs pre-loader error, plz help me

Please back up vortex synq
Good I ask for a help to see if someone will have or could make a back up for this vortex synq cell phone since some of us have problems in the firmware when modifying it and we do not have a previous backup if someone can collaborate, it would be infinitely appreciated.

I know this post is old but if somebody can backup the firmware from this it would be awesome, because i am trying to restore my vortex snyq (its hard bricked) but i can't find the preloader for this phone anywhere, when i tried to flash the preloader with sp flash tool it gives me this: STATUS_DA_HASH_MISMATCH, the preloader has to match this phone, if anyone has a backup of the firmware feel free to post it here or dm me, but yeah just wanted to post here.

also need firmware having the same issue ages now
any help much appreciated
safe 2021-2022

use this to unlock bootloader and backup fw https://github.com/bkerler/mtkclient

Making this post to do a dump of the Vortex Synq stuff I had on Mega. XDA allows us to upload large files to here now, and my Mega account is getting pretty full, so I want to transfer everything I have that's Vortex Synq related from there to here. That means any download links pointing to my Mega will be broken, but all of that stuff previously linked by me can be found in this zip.
disclaimer
Feel free to use any of my stuff in any way you see fit. The only thing I ask is that if you do improve on something, share it with everyone else and don't just keep it for yourself. Keep it going for the good of the community/public.
Also, know that it's been a long time since I've messed with this phone, so I don't remember what mods/images/etc in my Mega repo are functional or not. Anything contained within this zip, FLASH AT YOUR OWN RISK.
/disclaimer

Help - Device after Flash Rom not able reboot

Dear XDA Guru / Expert,
Good Day. I need help urgently here.
2015 i purchase Mi 4i mobile device and took many nice photo but forgot transfer out.
2021 last month i open this Mi 4i would like to download the file , unfortunately this device perform Auto upgrade.
Half way while auto upgrade , this mobile running out of battery.
After reopen , it keep appearing the Mi Logo.
I check many website mentioned i need perform FASTBOOT to Flash the ROM.
I checked also the bootloader is not lock.
However i did perform the Flash the ROM with lastest ROM / Factory ROM.
Please give me some advise what i should do in order for me can go back to normal ?
So that i can download the photo out from this mobile ?
Appreciate & welcome your reply.
Thank you

ak9999 said:
Dear XDA Guru / Expert,
Good Day. I need help urgently here.
2015 i purchase Mi 4i mobile device and took many nice photo but forgot transfer out.
2021 last month i open this Mi 4i would like to download the file , unfortunately this device perform Auto upgrade.
Half way while auto upgrade , this mobile running out of battery.
After reopen , it keep appearing the Mi Logo.
I check many website mentioned i need perform FASTBOOT to Flash the ROM.
I checked also the bootloader is not lock.
However i did perform the Flash the ROM with lastest ROM / Factory ROM.
Please give me some advise what i should do in order for me can go back to normal ?
So that i can download the photo out from this mobile ?
Appreciate & welcome your reply.
Thank you
Click to expand...
Click to collapse
Probably when you flashed the firmware through fastboot you have overwritten the files in there. As your bootloader is unlocked the better would be to flash a custom recovery on it and then pull all the files you want.

SubwayChamp said:
Probably when you flashed the firmware through fastboot you have overwritten the files in there. As your bootloader is unlocked the better would be to flash a custom recovery on it and then pull all the files you want.
Click to expand...
Click to collapse
Hi SubwayChamp,
Good Day. Yea - i do agree your point of view, First of all thanks for your reply.
I flash my ROM previously on this device too , after complete the flash it working well.
Before i flash the ROM , the device perform auto upgrade but half way no battery & it force to shut down , after reopen it stuck at MI logo so without any choice i only choose to flash the ROM.
Actually i am not so expert on android ROM, by the way what is different between custom recovery vs those i got from XiaoMi official ROM ?
Mind tell me more on how to fix it please ?
Thank you

ak9999 said:
Hi SubwayChamp,
Good Day. Yea - i do agree your point of view, First of all thanks for your reply.
I flash my ROM previously on this device too , after complete the flash it working well.
Before i flash the ROM , the device perform auto upgrade but half way no battery & it force to shut down , after reopen it stuck at MI logo so without any choice i only choose to flash the ROM.
Actually i am not so expert on android ROM, by the way what is different between custom recovery vs those i got from XiaoMi official ROM ?
Mind tell me more on how to fix it please ?
Thank you
Click to expand...
Click to collapse
To know which direction to take, first we have to know how exactly you flashed the ROM you mentioned, which ROM was and through which tool.

Hi SubwayChamp,
Good Day. thanks for your reply.
I using official xiaomi - MiFlash as the tools to reflash the ROM.
ROM that i use - ferrari_global_images_6.7.5_20160523.0000.23_5.0_global
You may find attached Flash Log as reference.
Hope you can give me some good idea to resolve this issue.
Thank you

ak9999 said:
Hi SubwayChamp,
Good Day. thanks for your reply.
I using official xiaomi - MiFlash as the tools to reflash the ROM.
ROM that i use - ferrari_global_images_6.7.5_20160523.0000.23_5.0_global
You may find attached Flash Log as reference.
Hope you can give me some good idea to resolve this issue.
Thank you
Click to expand...
Click to collapse
I saw in your other thread flashing process took only 94s, if it is the case then it's not flashing properly.
From the three options that's above on the tool, don't remember to use only the option format data, not relock bootloader or try to keep your data. (picture of reference)
{
"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"
}
And also in case you used fastboot to flash your device, I recommend you try through EDL mode

SubwayChamp said:
I saw in your other thread flashing process took only 94s, if it is the case then it's not flashing properly.
From the three options that's above on the tool, don't remember to use only the option format data, not relock bootloader or try to keep your data. (picture of reference)
View attachment 5482635
And also in case you used fastboot to flash your device, I recommend you try through EDL mode
Click to expand...
Click to collapse
Hi SubwayChamp,
Thanks for prompt reply.
I think what you mentioned make sense - it's not flashing properly.
My Question
================
1) Related with Option to Flash
I am using save user data option at this moment.
But the option you suggest clean all & Lock will clear all my existing Picture or File from this mobile right?
2) Related your recommendation EDL mode
I don't think i able go others mode except Fastboot now because whenever my mobile open it's in Fastboot only.
Sorry to say actually study computing but i am newbie in all these , i don't even know what's EDL mode.
Thanks for your input.

ak9999 said:
Hi SubwayChamp,
Thanks for prompt reply.
I think what you mentioned make sense - it's not flashing properly.
My Question
================
1) Related with Option to Flash
I am using save user data option at this moment.
But the option you suggest clean all & Lock will clear all my existing Picture or File from this mobile right?
Click to expand...
Click to collapse
Not the option Clean all & Lock because this will lead your hopes even far distant, a locked device with Qualcomm only can be flashed through EDL mode, fastboot mode will be impossible if you relock bootloader. I suggested using the option Format data because WHEN the flashing is successful one of the things that avoid the device to boot normally is the old data that it is still there. Anyway, this won't make difference while you don't get the tool to flash properly.
ak9999 said:
2) Related your recommendation EDL mode
I don't think i able go others mode except Fastboot now because whenever my mobile open it's in Fastboot only.
Click to expand...
Click to collapse
Some Xiaomi devices, while bootloader is unlocked can be sent to EDL mode using hardware buttons, with device off pressing the both volume buttons at exactly the same time you connect your device to PC, in case this method doesn't work you should need to use "the test point method" is a way slightly difficult to get it but... to flash through EDL mode you need to install the Qualcomm 9008 USB drivers https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
And if you want to keep trying in fastboot mode, you could switch to other Mi Flash tool versions if it makes difference. Always is better to move all your firmware to the same directory where Mi Flash tool is, also avoid all the spaces in the path/name.
ak9999 said:
Sorry to say actually study computing but i am newbie in all these , i don't even know what's EDL mode.
Thanks for your input.
Click to expand...
Click to collapse

{Mod edit: Quoted post has been deleted - Oswald Boelcke}
What does this mean? You only quoted my post.

{Mod edit: Quoted post has been deleted - Oswald Boelcke}
Actually i din't not flash any file at first, it stuck at MI Logo due to some auto upgrade , i not sure it's MIUI Upgrade or Android Upgrade but i saw the word Android ......too bad half way due to my batery issue.......when i reopen MI Logo keep appear so i wish reflash the ROM able to help but it seem.....not really....