Database Info

Next8P12 (Big Lots 'Black Friday Edition' Nextbook)

{
"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'm seeing a lot of confusion on the forums about the Nextbook Big Lots released on Black Friday so I see it worth making a thread over.
This Nextbook does *not* use the Rockchip RK2918. If you look at the build info and do a little research (http://yifang.en.made-in-china.com/...-4-0-Tablet-with-Amlogic-8726-M3-M805MC-.html) it's got an Amlogic 8726-M3 under the hood. That's the M3 chip people keep mentioning here.
I have gathered much information on this 'new' Nextbook and posted it here. I have found what I think to be a jtag mode where, as people described, "M3-Chip" shows up in device manager. That forum thread has an Android System Info dump posted and for the sake of space I won't be reposting it here so go there and check it out. I only omitted non-relevant personal info and replaced with a [Removed] tag.
I would really like to see some genius minds at work getting this tablet rooted and the 'ROM Train' chugging. I have donated my talents of information gathering. I'm calling for someone to pick up the torch and work it from here. I've noticed at least two people that said they bought at least 3 of these so maybe someone can work with someone on donating a device to a cause and XDA can add another 'rooted knotch' to it's seemingly infinitely long belt'
---
[Update]
Here is the chip MFG's original source code to include kernel and all the toppings. This should be good starter info: http://openlinux.amlogic.com/wiki/index.php/Arm/Platform_Info/Information_for_8726M/Build_system_for_8726M_Howto. Also I've brought Slatedroid in the loop on this one so hopefully we can get the ball moving quickly.

What's up...just got one of these as well and of course like other people I was surprised to find out this wasn't rk29 as I was super ready to root this thing...I have absolutely no idea if this will help any and you may have already come across this site but it seems that the admin here (finless) knows how to work with these devices.
I don't know if that would go for this particular version with the m3 chip but anybody else who can get this rooted would be of great help. I wish I knew how to do it myself because I would but I'm only good for graphics...glad I came across this thread and to see you gathering much needed info, I'll stay tuned and if I stumble across anything that can help I'll be sure to post it here.

I have one of these units as well and would like to get it rooted. Just chiming in.

therealrayzzor said:
What's up...just got one of these as well and of course like other people I was surprised to find out this wasn't rk29 as I was super ready to root this thing...I have absolutely no idea if this will help any and you may have already come across this site but it seems that the admin here (finless) knows how to work with these devices.
I don't know if that would go for this particular version with the m3 chip but anybody else who can get this rooted would be of great help. I wish I knew how to do it myself because I would but I'm only good for graphics...glad I came across this thread and to see you gathering much needed info, I'll stay tuned and if I stumble across anything that can help I'll be sure to post it here.
Click to expand...
Click to collapse
Thanks for the info! I have made some progress. Here's a thread on Slatedroid that has the M3-Chip driver and low level flash utility: http://www.slatedroid.com/topic/39037-amlogic-low-level-flashing-tool/
I am tinkering with it a little but I'd encourage someone smarter than I to have a look at it as well in case I fail. To get the tablet in the proper mode do vol up + plug in usb with device powered down. I'll go ahead and attach related files here for convenience. You will need to disable driver verification to get the driver installed.
My first attempt I think I might have bricked the tablet. I'll give more info as I get it.

Yeah I fu-barred it. Anyone with experience w/ AmlogicBurningTool -or- someone who can extract the firmware so I can flash; I think I wiped my device tinkering with this utility. Any help would be appreciated as I'm dead in the water until I get the device bootable again.
[Update] I contacted Nextbook on this issue. The sup seemed pretty pissed when I let him know what I was attempting to do but for being forthcoming he agreed to see about getting me the original firmware zip file. As per usual I will update should I get any info.

Nice job! Thanks for all the work on this. I've got one I'm willing to hack on too. Not sure how to get the firmware off of it but I'm willing to try anything. I've been looking around and I supposed I'd need to run the burning tool with the device in IPL (not sure if that's what it's called) to take the firmware off? Let me know how I can help.

I'm on a thread now with Finless on FreakTab and he said he can build a rom for us to get root...he just needs the stock rom to work with...I'm waiting on some type of instructions in case I need to take it from my tab and give to him.
Maybe this could be the break we're looking for.

therealrayzzor said:
I'm on a thread now with Finless on FreakTab and he said he can build a rom for us to get root...he just needs the stock rom to work with...I'm waiting on some type of instructions in case I need to take it from my tab and give to him.
Maybe this could be the break we're looking for.
Click to expand...
Click to collapse
I sure hope so.........this stock rom sucks! I've been trying to mess around with it and install some apps from SDcard but having absolutely no luck. Now mine wont even boot. Going to have to reset to out of box.

mascondante said:
Yeah I fu-barred it. Anyone with experience w/ AmlogicBurningTool -or- someone who can extract the firmware so I can flash; I think I wiped my device tinkering with this utility. Any help would be appreciated as I'm dead in the water until I get the device bootable again.
[Update] I contacted Nextbook on this issue. The sup seemed pretty pissed when I let him know what I was attempting to do but for being forthcoming he agreed to see about getting me the original firmware zip file. As per usual I will update should I get any info.
Click to expand...
Click to collapse
If they provide you with a copy, Finless can root it for sure.

shaunmt said:
If they provide you with a copy, Finless can root it for sure.
Click to expand...
Click to collapse
That would be awesome. My folks are getting me a Google Nexus 10 for Christmas. If I can get this one working I might be tempted to spend that money on something else. I feel really really dumb for wiping the NAND just because it was in Chinese and I clicked a random button. I thought surely it'd give some sort of popup warning to alert me I'm being an idiot first. But it happily wiped the thing no questions asked. So, when we get to the point of flashing a firmware in; If we have to use the low level flash tool be really freakin sure you got it in English and you read the instructions thoroughly before flashing. It's not normally like me to do something that dumb but I've not been getting good sleep and I've been in a real big rush to get this project done.
Lesson of the day:

So no one has been able to install google play on it so far ?

kristibaee said:
So no one has been able to install google play on it so far ?
Click to expand...
Click to collapse
That would require root access which has not yet been obtained. Once someone successfully roots it, installing market will be easy. Stay tuned.

No go on a ROM from TS
I opened a ticket with tech support to try to get the ROM from this thing and they said it's not available to consumers... I figured I'd get some response like that but just thought I'd give it a shot. +1 for a customer "needing" the ROM on their end.
So your tab is still not booting mascondante?!?

tread_water said:
I opened a ticket with tech support to try to get the ROM from this thing and they said it's not available to consumers... I figured I'd get some response like that but just thought I'd give it a shot. +1 for a customer "needing" the ROM on their end.
So your tab is still not booting mascondante?!?
Click to expand...
Click to collapse
nope after i wiped the nand it fails at the first phase of flashing

Still haven't heard back from Netbook.
Sent from my Nexus 10 using XDA Premium HD app

Still hoping someone will root this thing and make a decent ROM. Please?

My Ramos W13Pro AMlogic was pre-rooted in a way. I was able to ADB to it and type su and got the # prompt back.
What we need for sure is uImage dump (boot.img is the same). This will give us the kernel and boot which is the most important part!
Get Android Terminal Emulator. Run it and at the $ prompt type su
If it returns with # it means you have root access.
If you do not get # it is not pre rooted. However you can do this command without root I think
cat /proc/mtd
This will show the mounted blocks. We need to dump those to SDcard using DD command.
Bob

Nextbook ADB access
Bob, I've been lurking for a while on XDA and on your own Freaktab site trying to get this Nextbook 8p12 / 8SE with amlogic chip rooted as a christmas present for my son. I've managed to get the market and google services framework installed on the thing but they force close due to other necessary files missing. I saw your post above and jumped right into ADB on this thing, but got a permission denied error on the DD command trying to copy the bootloader. Any suggestions? Many thanks!

We may have a breakthrough over at freaktab.com!
Stay tuned...

eegorr: Could you link the discussion so folks from here can have a look at the progress?

Help. Sim issue + unable to update + others.

Hi guys, I require some help here to fix and update the 1+1.
List of issues :
1. Unable to update (currently on CynogenMod 11.0-XNPH22R. Android 4.4.2 Kitkat), the update is available but wont install, takes me to the recovery and am not sure how to proceed. If I update does it mean the whole phone will be wiped?
2. Sim card is no longer recognized (out of a sudden), read some place where some users were got it fixed by an update to squash the bug by One plus support and team viewer.
Questions :
1. How do I perform a complete back up? (phone is probably not rooted) my Google account is synced but I have no idea what is covered.
2. How to root if I need to without bricking it?
3. Can I install / flash the latest update or do I have to do it incrementally?
4. Now that One Plus parted with CynogenMod and came up with H20, which do I go for? Kindly do give me a summary as to the pros and cons of both or your thoughts about it.
5. Err, how do I flash the latest update? Is there a step by step manual?
I apologize in advance if my questions have already been answered in previous posts and also thank those whom will be kind enough to help a noob out like me here.
Attached was what i saw when trying to update to 36R.
{
"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"
}

Vsmh said:
Hi guys, I require some help here to fix and update the 1+1.
List of issues :
1. Unable to update (currently on CynogenMod 11.0-XNPH22R. Android 4.4.2 Kitkat), the update is available but wont install, takes me to the recovery and am not sure how to proceed. If I update does it mean the whole phone will be wiped?
2. Sim card is no longer recognized (out of a sudden), read some place where some users were got it fixed by an update to squash the bug by One plus support and team viewer.
Questions :
1. How do I perform a complete back up? (phone is probably not rooted) my Google account is synced but I have no idea what is covered.
2. How to root if I need to without bricking it?
3. Can I install / flash the latest update or do I have to do it incrementally?
4. Now that One Plus parted with CynogenMod and came up with H20, which do I go for? Kindly do give me a summary as to the pros and cons of both or your thoughts about it.
5. Err, how do I flash the latest update? Is there a step by step manual?
I apologize in advance if my questions have already been answered in previous posts and also thank those whom will be kind enough to help a noob out like me here.
Attached was what i saw when trying to update to 36R.
Click to expand...
Click to collapse
1. You can't make a full backup without a custom recovery and root. In order to install a custom recovery you'd need an unlocked bootloader. If you're bootloader isn't already unlocked you can unlock it but doing so will wipe all of your data.
2. Have you not looked around this forum before posting this? There are guides available, and very easy to find. This is mine
http://forum.xda-developers.com/showthread.php?t=2839471
3. You can install the latest update with the stock recovery that you have installed currently. You can get the update here:
https://www.androidfilehost.com/?fid=24052804347761631
Simply put it on your phone, boot into recovery, and use the "apply update" option to install it. If you're not sure how to manually get into recovery, here's how. Hold power to turn the phone off. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
4. Use Google and you'll find your answer, there are plenty of resources online discussing this already. The first rule of XDA is to search before posting, reducing the need for redundant questions like this one.
5. Already answered this in point 3.
Honestly, all of these questions that you've asked have all been asked and answered before, did you search at all before creating this thread?

Heisenberg said:
1. You can't make a full backup without a custom recovery and root. In order to install a custom recovery you'd need an unlocked bootloader. If you're bootloader isn't already unlocked you can unlock it but doing so will wipe all of your data.
2. Have you not looked around this forum before posting this? There are guides available, and very easy to find. This is mine
http://forum.xda-developers.com/showthread.php?t=2839471
3. You can install the latest update with the stock recovery that you have installed currently. You can get the update here:
https://www.androidfilehost.com/?fid=24052804347761631
Simply put it on your phone, boot into recovery, and use the "apply update" option to install it. If you're not sure how to manually get into recovery, here's how. Hold power to turn the phone off. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
4. Use Google and you'll find your answer, there are plenty of resources online discussing this already. The first rule of XDA is to search before posting, reducing the need for redundant questions like this one.
5. Already answered this in point 3.
Honestly, all of these questions that you've asked have all been asked and answered before, did you search at all before creating this thread?
Click to expand...
Click to collapse
Hi, first and foremost, allow me to extend my gratitude despite my serious ignorance of the 1st Rule.
I did come across some posts but didnt really pay much attention to it as it seems this was a combination of issues and some things may even have changed since then. However yes, i understand that it is no defense and for that I apologize.
I will look into your reply.
I have this question (despite reading how you will probably not side any ROM as to respect the devs)
In your opinion Is CM12 or Oxygen OS stable? I saw that there were 300 pages of complaints (CM12) and quite a number of complaints for Oxygen OS too. I am really torn between them.

Vsmh said:
Hi, first and foremost, allow me to extend my gratitude despite my serious ignorance of the 1st Rule.
I did come across some posts but didnt really pay much attention to it as it seems this was a combination of issues and some things may even have changed since then. However yes, i understand that it is no defense and for that I apologize.
I will look into your reply.
I have this question (despite reading how you will probably not side any ROM as to respect the devs)
In your opinion Is CM12 or Oxygen OS stable? I saw that there were 300 pages of complaints (CM12) and quite a number of complaints for Oxygen OS too. I am really torn between them.
Click to expand...
Click to collapse
I don't really use either of those ROMs so I can't really comment on them. I used both for a very short period of time though, and both seemed stable. Honestly, most bugs that people experience are the result of their own doing. The only way you'll know which one you like is by testing them yourself.

Setting phone back to defaults for dummies

It doesn't appear anybody knows what to do with this http://forum.xda-developers.com/general/xda-assist/incoming-calls-answered-vener-make-to-t3500914 and I now have to go back to full factory stuff with no custom recovery and stock os to find out if this is a hardware issue. I did a TWRP restore from several months ago when the phone worked fine and it still has the incoming call issue from the link above. Did a factory wipe in Teamwin, same thing.
Rooted Sprint Galaxy S6 on Lollipop 5.1.1 with Teamwin recovery
http://tiribulus.net/pix/Phone/1.png
http://tiribulus.net/pix/Phone/2.png
Please pretend than I am a not particularly precocious ten year old who needs to make this phone as if I just took it outta the box. I have searched here and around the web. All I find elsewhere are paid download sites or 3 hour downloads and here I can't make heads nor tails out of the volumes of impressive information in these forums.
I do have PC skills, and this is my first smart phone and getting it rooted and the recovery installed and all that wasn't too tough back when I got it 15 months ago. It appears restoring it back to stock is quite a bit tougher.
I have to see if incoming calls still don't work when the machine is totally stock. Is there a way to do this without a 3 hour download and a masters in computer science? I sure would be most grateful for any help with this.
Thank you.

You can simply do "Rescue firmware" via Smart Switch.

forumber2 said:
You can simply do "Rescue firmware" via Smart Switch.
Click to expand...
Click to collapse
Thank you sir! I will have a look at this a bit later tonight when possible.

This won't work with Teamwin recovery right?

I have none of the boot options in this video. Not that I don't appreciate it.

I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.

http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448

brenner650 said:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Click to expand...
Click to collapse
I appreciate that sir, but like I say, I never get step 4. It doesn't exist for me. As soon as I click the device initialization tab I get 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"
}
If I proceed, I get this:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix. That's what started this whole thing:
http://forum.xda-developers.com/spr...er-make-to-t3500914/post69641921#post69641921

Tiribulus said:
I have none of the boot options in this video (TeamWin). I also have totally different options in SmartSwitch. Not that I don't appreciate it. It doesn't have an option to search like the video says and already has an upgrade in there. I deleted my google accounts like it said and now I have this:
http://tiribulus.net/pix/Phone/smartswitch.jpg
Root will mess up the mobile phone, but the whole point is getting rid of root and fixing the mobile phone. . Again, it's not that I don't appreciate the help, but this is what I've been going through. None of the instructions I find match what I have,.
Click to expand...
Click to collapse
You won't do anything on TeamWin.
1. Open Smart Switch on PC.
2. Turn Off the phone. Press Volume down (not up) & Home button & power button. When you see the warning screen, just press volume up once. If you see "Downloading" screen, plug into PC
3. Do "Rescue Firmware" via Smart Switch.
Thats it.

Tiribulus said:
It tells me the update may fail if it's rooted and being unrooted is one of the goals of this. It also says that the mobile phone function may not work, but it's exactly the mobile phone function that's not working now and I've been trying to fix.
Click to expand...
Click to collapse
Well they had to write that, because if something happens during flashing it is not their fault, and you have been warned.
You can also uninstal supersu, and download that same fw Smart Switch would install from another internet source, and it will probably be a painfully slow download, but that is up to you.
I cannot guaratee you that Smart Switch emergency initialization would solve your phone issues, but it is the way to unroot and for the phone to become officially stock, offcourse knox will stay tripped if it was tripped during rooting (and probably is, unless you are on 5.0.2. and were using ping pong root).
I used Smart Switch emergency a lot, and it was always succesfull, just follow instructions, connect your phone in dowload mode when it asks for it, and there should be no problems getting to stock.
...I saw just now, in your other topic that you have fixed it /thumbs up!

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.

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