MP MAN MP 720 original firmware found - Upgrading, Modifying and Unlocking

hey guys, new to this, just got a MP720, not much firmware about for this one, not must of anything really,
I did however find this site with links to the to original firmware from MPMAN,
using google translate haha, it seems the two flavours of chipset for this taplet,
Hynix NAND firmware:
https://dl.dropbox.com/u/29403117/MP720 An 2.3_Hynix.rar
Micron NAND firmware:
https://dl.dropbox.com/u/29403117/MP720 An 2.3_Micron.rar
Flash Tool:
https://dl.dropbox.com/u/29403117/upgrade tool and Introduction.rar
that said i have not tested these FW's and cant vouch for the safety of using them,
I'm not a developer but hopefully they could be usefull for making a cyanogenmod for it (fingers crossed haha) or some one who has bricked there tap,
source:
https://slo-tech.com/forum/t528078
I have downloaded these files so if the link becomes dead please let me know and i will send them

Firmware Testers Needed
Is theres anyone with a bricked MP720 to test these FW's? id like to upgrade my 2.2 tablet, but only if these FW's are known to work.
TESTERS NEEDED
thanks in advance

Tested firmware, working fine, so it is all good for anyone with a bricked mp720/MID7020
would this be usefull for making a custom rom?

Since last december, my tablet was bricked!!!
Wordked for me !!!
Thanks !!!!

Since no question has been asked here, moved to General section.

hail to the king baby!
works well! thank you!

when i tri to instal the firmware i have this errors
ERR_FWDN_DRV_IOCTRL_DEV_INITIALIZE
CFwdnPORT:evice_Init:FWDN RESPONSE PARAMETER FAILURE
Please HELP.

Hello, need help with mpman mp720, followed instsruction from "upgrade firmware introduction" but the firmware utility does not detect my tablet's nand memory even after i turn off device and start by pressing volume up and power button,when i do this the brand logo disapaear and screen is black only with lcd backlite on, the table is in the device manager recognized as Android device and android composite adb interface.
The tablet don't start and remains blocked at word "android".
Any suggestion is welcome.

ancient998844 said:
Hello, need help with mpman mp720, followed instsruction from "upgrade firmware introduction" but the firmware utility does not detect my tablet's nand memory even after i turn off device and start by pressing volume up and power button,when i do this the brand logo disapaear and screen is black only with lcd backlite on, the table is in the device manager recognized as Android device and android composite adb interface.
The tablet don't start and remains blocked at word "android".
Any suggestion is welcome.
Click to expand...
Click to collapse
Try whit this FWDN v7_2.09 if not work try another version of FWDN ,you must see this in FWDN Low format whole memory before download

I have manage with volume "-" and power
mine was hynix and has been flashed succesfuly
thanks

Related

Bricked hx2110 help

I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
On another note - I had purchased a working 2110 with a good mobo to replace this one if the flash is not repairable - is that a difficult procedure? Unfortunately, the 2110 I purchased was not working, but this may still be in the books at a later time, so some info would help.
Thanks!
Rustmonkey said:
I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
Click to expand...
Click to collapse
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
reggaepoo said:
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
Click to expand...
Click to collapse
You, my good sir, are a genius - worked great! Fixed BOTH 2110s
tangwd898 said:
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
Click to expand...
Click to collapse
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Rustmonkey said:
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Click to expand...
Click to collapse
really amazing !!!!!!
I just saved my hx2110 as per your step by step instruction now.
Thank you very much.
ok, well, I thought they were fixed... now one of them freezes at the bootup screen, even when I do a clean reset... I've tried reflashing multiple times to no avail... any ideas whats going on?
ok, got everything working - reflashed the non-working one back to an original 2003 rom - which made if freeze at boot - then upgraded it via pre-bl to 1.00.00.L - from here, it wouldn't do anything after filling the bar at the boot screen, but it didn't CRASH (as in lights out) - so I ran the pre-bl again and ran the flash program for 1.00.00.L again WITHOUT swapping between the 2495 and the 2110 - just put the 2110 in pre-bl and away we went - flashed, formatted, and booted - then proceed to upgrade to WM6 via 1.00.00.H --> 1.02.00.H --> WM6 - works GREAT!!!
Thanks for the help everyone!
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Hello,
I have run into some problems with a bricked hx2110.
I was flashing the IPAQ to a new ROM WM5 (Battery was full and I read all the instructions 10 times prior to flashing). While flashing, the progress bar went to 100% then faded out immediately and it wouldn't reset (clean reset). I put the battery in my friends hx3000 series and the battery I used was completely dead. It did flash to 100% though, but not matter how many times I try 1 + 3 + reset, it doesn't reboot. If I can figure out how to get it to boot, that would be great, but I can't get anything to come up with any key combinations.
To this point all I can do is get into Pre-BL mode 1.00.04. I have tried the below scenarios on two machines, both running windows XP SP2 (USB 2.0) with the firewall and virus software disabled.
http://forum.xda-developers.com/showthread.php?t=330382&page=4
1) I have tried the above links directions and used the the Universal Bootloader (Bootloader.exe). It gets to the point where it says "The PDA should be updating now" or something similar but nothing happens. I don't get any errors regarding communications (it sees the device when I hold the "Calendar" button until it says USB; windows then recognizes the device as "HP USB ..." so I know it's communicating).
2) I tried to use the Bootloader_GUI.exe beta so that I can watch the progress indicator but it just sits at 0%. There are no error messages so it is communicating but for some reason, the device won't let it flash (and the flash utility thinks it's doing something).
3) I tried the original ROM flash from HP (SP29856.EXE) and it recognizes the device, but because the current ROM on the PDA is hosed, when it does it's "verifying" process, it comes up with "?" marks as the model number and when it goes to flash it starts at .1% then says "FINISHED" immediately. The ROM utility thinks it flashed it correctly but it didn't flash anything. I'm guessing that the verification of the PDA failed and forced the utility to not flash.
Does anyone have ANY ideas of what to try? I wish I had another HX2000 series PDA and try the "swap" thing prior to hitting the update button but I don't. All I have to work off of it my sad bricked PDA and a full battery (friend keeps charging it). His PDA is an HX3000 series.
Any ideas would be appreciated,
Thanks!
Are you using a the HP flash program that is specified for your device?
2nd - you might be able to use your buddies device in a swap as well - not sure but its worth a shot - use HPs upgrade program, let it verify, then swap your device onto the same cable - overwrite the firmware in the update program for HIS device with firmware compatible with yours and then hit update - let us know if this works...
I am using the "official" HP flash program specific for the HX2110 (from their website - SP29856), bootloader.exe, and bootloader_gui.exe
I wanted to try my friends, but he won't let me touch his because I bricked mine lol (I swore nothing would happen to his but he still won't let me try it).
Anyway, I just copied over the ROM image (from HP) and stripped out the header (now showing 64 bytes before the ECEC). The ROM is for WM2003. I copied the ROM in binary using psdwrite.exe to an 256 MB SD card. As soon as I can get the battery back, I'm going to try to flash it from the SD card. If this fails, I am going to try to play around with MTTY / USB and manually call the ROM flash and see what happens.
Having another HX2000 series would make this easy (maybe a little TO easy )!
Bootloader never worked for me - but if you can get it to manually call the flash, more power to you good luck!
Well it was worth a shot. After spending the better part of the day with the PDA, I have made no more progress (can't get Pre-Bl to update). The only option I have now is to find someone with another hx2000 series that is willing to resurrect it from the dead for me (PM me if you can help - I will pay two way fare). Until that happens, it's going in the "broken" drawer with all my old comp stuff .
Thanks to all the tips and tricks that is posted on these forums and brighthand! There is a wealth of information on this topic and without them, I would have gotten nowhere in trying to repair the device (granted, I wouldn't have been intrigued to upgrade the ROM in the first place and would still have a working PDA, but that's besides the point ).
Best of luck to you all.
1).download original ROM from HP (sp29799) -extract files
2) download http://upload.dvhk.pl/content.php?id=88892 - replace files
3) flesh device.
bay!
link crash http://upload.dvhk.pl/content.php?id=88892 - replace files
Please it can raise it again, thanks
Absolut3k said:
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Click to expand...
Click to collapse
Same here.. is there another way to un-brick hx2110 on this problem ? thx ...
Solved, my hx2100 returns to be in this world
thank you i saved my ipaq

Storex Ezee'TAB901 root JB 4.1.1

hi,
After spending many time trying to root my storex tab 901 I bought in france (Already installed on 4.1.1 with google play), Iwas finnaly able to root it using adb and command line.
to do so:
- Download attached file
- Download from google SDK usb_adb_driver
- Go to your device parameters-> USB -> enable debbuging mode
- create a c:\root folder on your windows XP computer then Extract the zip file attached into it.
- Plugin your device to the computer, when prompted for driver, use google sdk USB_ADB_Driver
- When done, open a windows terminal command line
- type: c:
- type: cd \
- type: cd root
- type: cd rootkit
- type: go.cmd
If everything goes well, your tablet should reboot. you can try installing the free app from google store called "Root checker" to confirm your device is properly rooted.
Also, if you lost the original rom and live suite, here is the link to download the latest build from storex web site:
(I will post the link later when I find it)
JB 4.2.2
CAUTION: USE THIS ROM AS YOUR OWN RISK.......Be sure you have the official rom in case it is not working for you. It appears that even though you have the same tablet Reference, depending on when you buy it, hardware might be a bit different and most likely you will take the risk of having a unusable Touch screen or wifi...
I found out you can fully use your Ezee Tab 901 4.2.2
you can install rom from Manta MID 13.
You will be able to install the rom using Livesuite.
Gain:
- Android 4.2.2
- Root Access out of the box
- Play store installed.
Everything will be working
For the link type in google:
MID13 Android 4.2.2 Jelly Bean - Manta Multimedia Info
select google link called: manta.info.pl
select the link catshare or 4shared.
Start live suite 1.7, select the download img file, do a format when prompted. You done.
When the tablet restart, go to the parameter icon, and change language to French or english
Procedure on the Ezee tab 901 with livesuit:
- completly turn off the tablet, unplug cable
- start livesuite and select the downloaded image file
- keep the VOL- button pressed and plug the usb cable
- without releasing the VOL- button press the Power button 6 times.
- You should hear windows sound saying a USB device has been plugged
- if windows request it, install the driver from Livesuitefolder\usbdriver
- Livesuite should automatically start the flashing process.
- when prompted, "Format device" press YEs.
- When it s 100% you tablet should reboot.
Done.
Note: I did not invent anything, thanks to the good work of MANTA team members. I just found out this rom works on my tablet out of the box.
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
samus64 said:
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
Click to expand...
Click to collapse
Hi,
did you try going into recovery mode and factory reset? (shutdown tabel completely and keep press on volume+key then press power button)
in the menu, using vol+/- scroll down to wipe factory reset and validate by pressing the power key.
Let me know how it goes.
btw, are you sure your tablet is a Ezee tab 901 and not 971?
Cheers
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
samus64 said:
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
Click to expand...
Click to collapse
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
pierrottls31 said:
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
Click to expand...
Click to collapse
Yep the wifi switch is exactly what i've got on this storex. Thanks for your help anyway. Ho and by the way, I properly rooted it with you first tuto
Cheers.
Fast custom ROM 4.2.2 by TOxico for Ezee tab 901
Guys,
I manage to find a very fast and usable rom for our tablet: (THanks to Toxico.) this rom will change your life.
All information and download are in the thread here:
http://forum.xda-developers.com/show...php?p=42274265
It should basically work on any A13 device with livesuit (tested on my Ezee tab 901 and on my 704CET mem up)
This rom comes with no TS driver, but there is all explanation and download to install the needed driver.
note: you might loose the camera though. I encourage you to read the full thread before going further and flash your tablet.
If you want to know the driver used on your tablet, run a adb shell and type lsmod (You will have a list of loaded/used driver.)
Dont be scared, everything is written in the toxico's thread
My only advice, if you dont know how to use adb, do not try it, this is not that easy.
I hope this will help.
Best regards.
As usual do it at your own risk and even more: make sure you have the original rom... just in case
Tutorial for 971.
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
MaedaKeiji said:
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
Click to expand...
Click to collapse
Hi, sorry i cant help you, it looks like the 971 is using a10 cpu, sôit can be different.
If you know what you are doing, u can try to backup your original firmware and test the solution i have provided from toxico in py post above. But there is no warranty it s going to work.
Any case, donnot forget google is your friend
Good luck
Unfornetly it seems google doens't like this tablet...
I'll see what I can do with some backups and all.
Thanks anyway!

[REVIEW] Teclast X89 Baytrail Tablet Dual OS (Windows & Android)

Hi all!
i wrote reviews for two devices that are very interesting on checking together.
iPega 9023 rev2 -> Telescopic bluetooth controller for smartphones/phablets/tablets and standalone usage.
Teclast X89
There is a summary of the Teclast X89 Device. (sorry, but i can´t post complete article here, due the limitations of the characters by message on this forum)
_______________________________________________________________________________
[REVIEW] Teclast X89 Baytrail Tablet Dual OS (Windows & Android)
​
Acknowledgments
To Geekbuyingstore for send me a sample of their product Teclast X89 to test it and write this review.
Note about this review
This article is the first part of the main review of the device. Currently i get bricked the device when trying to update/install a clean windows version, and i can´t keep testing for now, until i found the way to recover it
When i get the device unbricked (if i get this), i will post a second part with steps for recovery, firmware update, tips and tricks for this device.
This article is based on general usage of the device, and for windows get many videos of games running directly on the device itself, for showing what you can expect of this.
For technical info and benchmarking on windows, when i get this device operative again, i will update this article with these sections.
Apologize if the article is not enough informative as you can expect. I'll do my best to bring a second part with more info about this device.
Product showcase(Checking of the external view of the package)
First of all, i never mention about packaging of the store that sent to me their articles, because usually i don´t consider interesting to mention, but this time i will do an exception because i get so pleased about this point.
For this review, Geekbuying sent to me two devices (but i wrote in different articles) that correspond to a suggested (by me) combo for use together:
Tablet Teclast X89
iPega 9023 controller
Both of them come in the same package, but fully protected, first with the typical plastic with bubbles, covering all the content:
​
Then, there is a bag with protective system for avoiding shocking of the devices.
​
The package arrives without any kind of problems, with the original packaging of the devices in perfect condition.
I wanted to remark this because is not usual that stores give this attention on the devices they send.
Now, back to the device itself. the packaging of it is simple, but all main texts are in chinese.
​
In the front we found the name of the product (Teclast tPad), and the Intel logo, that give to us a main clue about what is inside.
​
Back part is the description of the product in chinese
Note that there is no info about the specific model of the tablet (Teclast X89)
Inside we found the basic distribution of the package
​
Product information
​
According with the manufacturer, or searching info on web pages, we can found many sources of information about the device and sometimes these information may be not consistent (may be different from one web page to other), and this may cause some confusion for anybody that wants to get info about this product.
On this section i will post the info i get from the manufacturer (or is not possible, the web page that i consider more reliable), listing only the relevant points for a tech analysis of the product, and omit these points that don´t get any relevant info about the device (as many time we found on many pages, things such video capabilities, mail capabilities, etc, that really are software based features that we can install on the device, and not a real feature of the device itself)
I did not found the official specs on Teclast webpage. There is the specs of the previous version (X89HD), but not for this specific device (Teclast X89, or Teclast X89 Retina Display)
Operating System: Android 4.4 & Windows 8.1 OS (Dual Boot)
Model: Teclast X89 Dual OS
Announced: 2014-07
Color: White
Shell Material: Plastic
Display
Size: 7.9 Inch
Resolution: 2048*1536
Display Technology: IPS Retina capacitive touch screen
CPU&GPU
CPU Manufacturer: Intel
CPU Model: Bay Trail-T Z3735F
CPU Core: Quad Core
CPU Speed: 1.83GHz
RAM&ROM
RAM Type: DDR3L
RAM: 2GB
Hard Drive Type: eMMC
Hard Drive Capacity: 32GB
Extend Card: T-FLASH(Support 32G MAX)
Other Functions
Camera
Front: 2.0MP
Back: 5.0MP (Autofocus)
HDMI: Up to 1080p
3G: Supporting external 3G modem
Bluetooth: 4.0
GPS: NO
G-Sensor: Four way
Power
Battery Type: Li-ion battery, 5000mAh
Battery / Run Time(up to)
Wifi On: 4 hours
Wifi Off: 8 hours
Power Device Type: AC Adapter, AC 100-240V
Charging Voltage: DC 5V, 2A
Communications
Wireless ConnectionWIFI
Wireless Protocol802.11 b/g/n
Dimensions200 ×138 ×7.4mm
Net Weight512g
Connectors Ports
1 x Micro USB Port
1 x Earphone jack
1 x Micro HDMI port
1 x Micro SD Card slot
​
Hope you found interesting and useful.
_______________________________________________________________________________
Zalu2!
Not booting to windows after root
Hi,
I was reading your review about teclast x89, it is awesome.
I was following your instruction for rooting my dual boot teclast x89 (E7ED), and everything went great, i was rooted.
But then my problem apear, i can't boot into windows. Menu for selecting which OS to boot, dissapear. I try every single combination of key, but everytime it boots to Android. CAN YOU PLEASE HEEEEELP ME?
Thanks
djshorty said:
Hi,
I was reading your review about teclast x89, it is awesome.
I was following your instruction for rooting my dual boot teclast x89 (E7ED), and everything went great, i was rooted.
But then my problem apear, i can't boot into windows. Menu for selecting which OS to boot, dissapear. I try every single combination of key, but everytime it boots to Android. CAN YOU PLEASE HEEEEELP ME?
Thanks
Click to expand...
Click to collapse
Hi.
The rooting method will not affect to booting selectiong of OS.
of select, power on the device, and after release the power button, press VOL- & VOL+ at the same time.
the device will ask you to select an Operating System.
another way is connect any USB keyboard (via USB OTG cable), and when turning on the device hit quickly and repeat the "supr" key, for entering to BIOS.
once you get on BIOS interface, go to second screen and select "OS Selection" (or something this way, sorry i can´t check now) as first booting method.
This will enable the OS selection screen
check my review (on my blog) and follow the instructions for configuring the bios for select OS, and add more time for pressing Supr (by default is 1 or 2 seconds, i don´t remember. i suggest 4 or 6 seconds)
Greetings!
Deen0X said:
Hi.
The rooting method will not affect to booting selectiong of OS.
of select, power on the device, and after release the power button, press VOL- & VOL+ at the same time.
the device will ask you to select an Operating System.
another way is connect any USB keyboard (via USB OTG cable), and when turning on the device hit quickly and repeat the "supr" key, for entering to BIOS.
once you get on BIOS interface, go to second screen and select "OS Selection" (or something this way, sorry i can´t check now) as first booting method.
This will enable the OS selection screen
check my review (on my blog) and follow the instructions for configuring the bios for select OS, and add more time for pressing Supr (by default is 1 or 2 seconds, i don´t remember. i suggest 4 or 6 seconds)
Greetings!
Click to expand...
Click to collapse
thanks for the reply,
i try both of your method but no luck,
First, i select power on the device, and after release the power button, press VOL- & VOL+ at the same time. It goes in "dmx" fastboot mode,
Second,
When i enter in bios (supr-del key), in boot manu i have 3 options:
1. UEFI OS (it boots directly to android)
2. Windows boot manager (it boots directly to win)
3. UEFI: built in EFI shell( it opens shell)
can you please check in your tablet what option you have at boot manu?, are they same with mine, what did you select?
What ever i try, i can only boot to android or windows, i cant get screen where i can choose what os to start. Before it was screen this screen
with Operating System selection, but now is gone..
please help!!
p.s in windows now, touch is not working, android is ok.
Thanks
djshorty said:
thanks for the reply,
i try both of your method but no luck,
First, i select power on the device, and after release the power button, press VOL- & VOL+ at the same time. It goes in "dmx" fastboot mode,
Second,
When i enter in bios (supr-del key), in boot manu i have 3 options:
1. UEFI OS (it boots directly to android)
2. Windows boot manager (it boots directly to win)
3. UEFI: built in EFI shell( it opens shell)
can you please check in your tablet what option you have at boot manu?, are they same with mine, what did you select?
What ever i try, i can only boot to android or windows, i cant get screen where i can choose what os to start. Before it was screen this screen
with Operating System selection, but now is gone..
please help!!
p.s in windows now, touch is not working, android is ok.
Thanks
Click to expand...
Click to collapse
If you has been removed this View attachment 3193425
TRY IT →bbs.teclast.com/forum.php?mod=viewthread&tid=389148
mooncake5874 said:
If you has been removed this View attachment 3193425
TRY IT →bbs.teclast.com/forum.php?mod=viewthread&tid=389148
Click to expand...
Click to collapse
Yes, i removed that Stupid of me
Thanks, i will try this, but i dont know chinese, i try to download and tell you results.Is this apk?or all firmware?
Thanks
djshorty said:
Yes, i removed that Stupid of me
Thanks, i will try this, but i dont know chinese, i try to download and tell you results.Is this apk?or all firmware?
Thanks
Click to expand...
Click to collapse
I made the same mistake:crying:,but I can't find download for this apk at that time. so I reinstall all firmware.
this APK backup. file path“/system/app/”
↓
View attachment VManager.apk
GOOD LUCK!
mooncake5874 said:
I made the same mistake:crying:,but I can't find download for this apk at that time. so I reinstall all firmware.
this APK backup. file path“/system/app/”
↓
View attachment 3193597
GOOD LUCK!
Click to expand...
Click to collapse
Thanks,
i install it but no luck.
Should i open this program and select something, or is it enough thaat i installed it?
ANd it will be very good if someone who knows to make a tutorial in english to flash new firmware from scratch (instaling dual boot, android, windows) like x98, that is good tutorial.
Thanks
djshorty said:
Thanks,
i install it but no luck.
Should i open this program and select something, or is it enough thaat i installed it?
ANd it will be very good if someone who knows to make a tutorial in english to flash new firmware from scratch (instaling dual boot, android, windows) like x98, that is good tutorial.
Thanks
Click to expand...
Click to collapse
Maybe you can use google translation
mooncake5874 said:
Maybe you can use google translation
Click to expand...
Click to collapse
I use google translate, but it is awful, i downlod tutorial pdf file, and translated, but i am afraid that i can make mistake because translation is awful.
If someone who knows chinese and english can translate it right it will be good.
Or someone can confirm that tutorial for x98 3g is the same as this only the files are different, that is also good think to do.
currently, i'm writting a second part of the review, with instructions for flashing the device, installing android and windows (both)
for now, i'm a little bit busy and i can´t give so much time, but let me some days and i will publish this part of the review, for helping flashing the device.
Deen0X said:
currently, i'm writting a second part of the review, with instructions for flashing the device, installing android and windows (both)
for now, i'm a little bit busy and i can´t give so much time, but let me some days and i will publish this part of the review, for helping flashing the device.
Click to expand...
Click to collapse
Thanks for everything i manage to repair my tablet by installing dual boot.
If you need help about your review, i can help just tell me. And as suggestions to your review, you can write what apps are safe to remove, so people cant get into trouble like me. Also you can write how can we install only android or only windows, for big storage 32gb to be used only for 1 system
Thanks everybody.
Hibernat does not work
Hello X89 owners,
i also have the newest dual boot retina display version and i am really impressed by the tablet. All works fine and great performance. Only one thing does not work that worked fine for all my other windows tablets i use before. I am not a big fan of connected standby because it still drains battery, so i use "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" command to hibernate the devices (because default button is not visible).
Unfortunately it does not work with the teclast x89. If i run "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" hibernate command it shuts down the tablet but after reboot it does not restore the hibernate state, it simply boots up normally. I also checked event log having error:
error: Windows failed to resume from hibernate with error status 0xC000000D.
I also tried recreating hiberfil.sys and checking disc consistence. But nothing helped. So can you try this on your devices? I simply want to know if its a general Teclast X89 problem...
Thx and br
Arangato
Hi Arangato.
I'm doing some testings with MeegoPad T01 (similar baytrail than Teclast), and as you i can´t get this thing to hibernate by command line
messing with the device, in some moment i get an effective hibernate state, but i'm not sure how i get.
in some testings, after unplug the power and connect again, the device boot windows (quick than normal) from scratch, and show me the application i get running previous the sleep (burnout paradise)
i will keep doing tests, but i really don´t know how to replicate for now. This messages really is for confirme that there is some way to do a sleep on this device, but of course, is not the standard way.
i'm thinking now... may be when i sleep the device, i think i keep the power button pressed to shutdown... for long time, after this unplug power source, wait few seconds and plug again. (something like this i did, i think)
keep testing...
"powercfg -h on" should enable hibernate mode
But the difference between a cold boot and hibernate resume is not that long
aitnog said:
"powercfg -h on" should enable hibernate mode
But the difference between a cold boot and hibernate resume is not that long
Click to expand...
Click to collapse
i tried but did not enabled.
yeah, may be on timing is the same, but there is a good difference. With Hibernating, when you get back, get all the tasks you're doing in the same status (games, work, etc). i really prefer hibernate than complete turn off for this reason.
but thanks anyway.
i recovered the tablet and doing some testings (but for now i´m centered on other devices i must release reviews).
meanwhile, i published the guide for flashing and recover the device, translating the original in chinese, and adding some other stuff that may be useful.
http://manguiro.blogspot.com/2015/03/guide-teclast-x89-installation-guide.html
Note: if your device cannot recover (like mine) with normal steps, or there is some message about corrupt partition table, invalid disk, etc, you must do some manual steps (the flashing tool can´t handle this)
i will put my steps on other article (really, i need to publish another reviews first), but basically i opened the flashing xml file, and check that there are some commented lines that, if you uncomment, the flashing tool will omit anyway, then you must do these steps manually, from fastboot command.
with this, i be able to 100% recover the device. Now i get android and windows working without problems.
hope you found useful.
Touch has stopped working! In windows.
djshorty said:
Thanks for everything i manage to repair my tablet by installing dual boot.
If you need help about your review, i can help just tell me. And as suggestions to your review, you can write what apps are safe to remove, so people cant get into trouble like me. Also you can write how can we install only android or only windows, for big storage 32gb to be used only for 1 system
Thanks everybody.
Click to expand...
Click to collapse
Hey my touch stopped working in windows too.
Anyone have any idea how to fix it? I have only had this for 1 hour and now it is useless for what I got it for...
I need to find out how to restore the touch capabilities to windows. I tried refreshing, it happened after I went to android for the first time.
I've got the Atom Z3736 Win 8.1 version of this but does anyone know if it's possible to install dual boot because this version uses the Z3735?
Because just about all the forums for this device are in Chinese and using Google translate is a nightmare to even find the right people to ask.
com.android.systemui keeps crashing when charging level at 100%
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Hello Deen0X, thanks for your reply and explanation. Now i know it seems to be a general problem. If you have a tablet like this connected standby is activated and with this hibernate is also enabled by default (you should find a hiberfil.sys file in C root, its used for fast boot option) so you normally can hibernate with the command i mentioned before: "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" this works fine for my other acer win 8.1 tablet (OOTB system) directly after install. But not for the Teclast x89. Of course having a normal boot and restore from hibernate is pretty same time, also fast boot does not have that big impact. I like hibernate because it "freezes" actual system status without draining battery after that.. i often have several browser windows opened, some other metro apps and i like to resume to that state and not to have a clean boot.
@Deen0X: could you check your event log? Is there also the message that device could not restore from hibernation?
So keep me updated, or maybe anybody else can try the "%windir%\System32\rundll32.exe powrprof.dll,SetSuspendState" command to hibernate the teclast x89 dual boot. It will not harm the device. I have the experience if hibernation is disabled and you run this command it simply locks the screen..
Thx and br
Arangato

Urgent Help Needed!

Hello....I bricked my I927 when I accidently formatted my efs partition when using EFS professional .....my phone boots in download mode.....but only boots till samsung logo screen.....I tried various things like installing stock GB and ICS through odin and installing custom firmware but phone boots onle till samsung logo and then lights up with sone stange colored thin lines and screen goes off.....In TRWP I get a "unable to mount preload" error whenever I try to install somethiing.....I suspect that the EFS partiton is corrupted and needs to be repartioned....I had backupped the efs folder when my phone was working before.....its in a tar format.....I read somwhere that someone made a recovery.zip out of his backedup EFS.IMG and flashed it with CWM solved his problems which were exactly similar to mine.....can somebody on the forum make a recovery.zip for I927 with update binary and script so that I can add the backedup EFS image to it and flash it with CWM? Please.....this would also help many others who are facing similar issues.....and also what do I do regarding the "unable to mount preload" error? I need to repartition and tried to install hemdall.....but get the common .dll error even after following all the instructions and installing C++ 2010.....
Hi, k one thing after the other.
Do you have repartitioned anything?
Do you have adb in place and does adb works when in TWRP?
The easiest thing would be to connect by adb then mount /efs and then restore the efs backup. The good is that you will have a good chance to recover your device. Maybe you need to reformat /efs but that depends.
Which timezone do you live? Maybe a Teamviewer session would be helpful?
.
Thank you for your reply sir...
THANKS FOR THE REPLY SIR....YES I WAS ABLE TO GO INTO CWM RECOVERY AND CONNECT THE PHONE WITH MINIMAL ADB FASTBOOT.....AND AFTER SPENDING ALMOST 2 DAYS CONTINUOUSLY TRYING TO FIND THE PROBLEM USING GOOGLE, I TRIED DIFFERENT COMMANDS ON ADB TO GET EFS BACK OJ THE PHONE....BUT WITH NO SUCCESS...... MY EFS BACKUP IS IN TAR FORMAT......IT WAS MADE USING GALAXYSIMUNLOCK BY SPOCKY.....I LATER TYPED IN 'ADB MESG'.....OR SOMETHING SIMILAR TO THAT COMMAND, AND FOUND OUT THAT ALL THE PARTITIONS ON mmcblk0 were mangled up with strange letters.....for eg, p1, p2, p3 and so on had strange characters written next to them.....SO I TRIED TO RE-PARTITION THE WHOLE THING WITH SDPARTED......AND IT RE-PARTIONED THE SYSTEM (AROUND 7000MB).....MMCBLK01 (AROUND 500MB).....AND ANOTHER THING I CANT REMEMBER NOW.....BUT WHEN IT FINISHED THE JOB, IT GAVE ME A mmcblk02 ERROR.....AND WHEN WHEN I CHECKED MY PHONE ON CWM SCREEN, IT GAVE ME A LIST OF CACHE ERRORS.....AND WHEN I SWITCHED OFF THE PHONE AFTER THAT IT REFUSED TO POWER ON.....IT WAS NOT EVEN GOING INTO DOWNLOAD OR RECOVERY MODE.....BATTERY HAD ENOUGH POWER....SO ITS NOT BATTERY FAULT......I SUPPOSE THAT SINCE THE PARTITIONS WERE FORMATTED THE PHONE BECAME COMPLETELY DEAD......CAN YOU TELL ME IF THERE IS ANY WAY WHERE I COULD GET THE COMPUTER TO RECOGNIZE MY PHONE USING A 'DEAD PHONE USB FLASH' OR SOMETHING.....AND THEN FLASH A BLANK BOOTLOADER AND THEN WRITE CWM?
I LIVE IN INDIA SIR.....+5.30 GMT.....I DO NOT KNOW ANYTHING ABOUT TEAMVIEWER.....IS IT AN ANDROID APP? CAN YOU EXPLAIN MORE IN DETAIL SIR?
PLEASE LET ME KNOW HOW TO GET THE COMPUTER TO RECOGNIZE THE PHONE AGAIN......
Well.. that sounds not that good...
Teamviewer (www.teamviewer.com) is an easy to use and free remote control software for your PC (it runs on both Linux and Windows). We could do a remote control session if you like. I can try to help but cannot promise anything.
I live in Germany: GMT +1. Send me a PM if you want to give that a try. Next Monday. Tuesday or Thursday would be possible on my site. At least for getting a short overview.
.
Thank you sir,
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Ok I have made one. It want to say it was VERY hard to find the correct instructions to do so and therefore I'm absolutely not sure if that will work for you!
Test it if you like but again: I have no idea if that would damage anything more than it is now!
See --> http://forum.xda-developers.com/cap...od-unbrick-debrick-hard-bricked-i927-t3285505
If it worked for you (would be like a miracle) then please report back!
If it does NOT work for you please report back, too!
thanks
xdajog
.
UPDATE:
Besides the link I posted --> Could you please also try the following:
1) Power on your device and directly after that:
2) Press and hold down Vol Up + Vol Down (both the same time)
3) You should see a warning message like the attached one which is the APX mode
4) you need to release the vol buttons immediately after you see the APX mode otherwise it will continue to the non working download mode.
Does teamviewer require internet connection with a lot of data?
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Uhm do you have read my above post??
.
1927 wouldn't boot.....Help.
Ohhhh Thank you.....thank you.....thank you for your kind reply Sir.....how good of you to take all your precious time to help me.....I greatly appreciate all your hard work Sir.....wonderful...*.I wanted to download your img file to try it out and when I read the reply of brother Bubor, that the I927 woudnt boot from the SD card when the bootloader is bricked, I was very disappointed. Like I said before, I have a very very slow internet connection with very less data left....and according to brother bubor's reply I doubt this will work....It looked like he was sure that it wont work....I tried to get into APX mode as the link that brother bubor posted had mentioned, but no luck, as the phone is not going into APX mode.....I remember that when I was trying to get to the APX mode the first time, the computer flashed a notification that the APX driver was not successfully installed.....but after that I tried the method more than a dozen times, but the computer was not recognizing the phone to go into APX mode.....Does the phone go into APX mode when the full internal phone system is formatted? I tried your second method on trying to get to APX mode, but nothing happens.....the computer is not recognizing the phone.....The battery had about 30% power in it when the phone got bricked 2 weeks ago.....Dont know if the battery drained all these days of not using the phone.....And even if I get to the APX mode, I have no idea how to proceed from there to repartition the internal phone system and get back download mode.....In the link that brother bubor posted the person who made the thread has made some files to be used when one gets into APX mode.....The PIT and emmc files which are necessary for repartitioning the system and getting the bootloader work are found in that zip file.....But that zip file is for the I9103 Galaxy R.....there isnt something like that available for the I927 yet.....And is brother bubor sure that the unbrick.img file wont work on the I927?
Give it a try with my unbrick image.
we all don't know.
.
xdajog said:
Give it a try with my unbrick image.
we all don't know.
.
Click to expand...
Click to collapse
Hi @alvcross: any update on this?
have you tried the SD card unbrick?
You said you cannot open the APX mode but what happens when you press the buttons for accessing the APX mode?
Try it even if you see a blank screen and then connect your Cappy with USB to your computer --> you should get a message about a missing driver or similar.
If that works I tell you how to proceed.
xdajog said:
hi @alvcross: Any update on this?
Have you tried the sd card unbrick?
You said you cannot open the apx mode but what happens when you press the buttons for accessing the apx mode?
Try it even if you see a blank screen and then connect your cappy with usb to your computer --> you should get a message about a missing driver or similar.
If that works i tell you how to proceed.
Click to expand...
Click to collapse
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
alvcross said:
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
Click to expand...
Click to collapse
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
xdajog said:
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
alvcross said:
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
Click to expand...
Click to collapse
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
xdajog said:
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes Sir....I understand....
alvcross said:
Yes Sir....I understand....
Click to expand...
Click to collapse
Ok could you please try these driver package here: http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Follow the instructions there for installing
The next step (if the driver would work for you) will be to flash a working PIT to your device to make sure you are using the correct partitions.
Afterwards we will flash the bootloader (may absolutely brick your device if not done correctly) and then --> if all goes fine --> you should be able to flash in download mode whatever you want to.
So it is still a long way to go and I need to check all the steps first before actually we can proceed.
That may take longer so do not expect that this will be something in the next days.. sorry.
Update:
If the above universal driver do NOT work for you: Test these one here View attachment apx_driver_samsung.zip
.
Thanks for the speedy reply Sir......Ill do as you said and let you know Sir......thank you.....thank you.....thank you Sir....
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
alvcross said:
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
Click to expand...
Click to collapse
nvidia apx isnt fastboot/adb device. You can found tool on nvidia site ( more info https://ac100.grandou.net/nvflash ), this tool can read and write whole flash.
Before you could use nvidia's tool, you must send an uniq blob to your phone. APX mode is useless without this blob.
This blob is uniq for every phone.

AC8227L - Mediatek components + unknown MCU - Bricked device help from PCB pictures

Hi all,
So I managed to successfully root and dump various bits of firmware etc over the past few weeks and generally had no issues(apart from the LED front panel lights not working(did at first), which is the main reason I was trying to rectify) - I have flashed from USB using a .bin also dumped preloader and rom etc via a scatter file using SP Tools after finding a rom entitled 8277L in the filenames, this worked perfectly(but still without the LEDS's) - Link to bought device(a cheap chinese one) - https://www.ebay.co.uk/itm/Single-On...53.m2749.l2649
Main issue: Now I have bricked it - I selected the format all part in SP-Tools thinking it would allow me to flash from fresh to stop the stock and TWRP recovery from timing out(I successfully ported TWRP over, but after about 30-40 seconds it was rebooting the device, bizarre!) - When the head unit is powered on it turns on the display but that is all, just a light black screen. I've tried recovering again via USB and SP tools but I think I'm almost out of luck. SP Tools doesn't read from the device or detect it, and yes I have the correct drivers installed under Windows. No screen swiped or button presses help in getting into any bootloader or update mode.
I am really hoping, anyone could help identify the UART pins on the board - yes I've now taken it all apart - in the hope I can flash a bootloader image which I guess is what is now wrong and has been erased??
I've really been digging into this and researching on Russian websites and getting lot's of interesting information including from XDA thankfully, but not this issue. I have included some pretty much hi res images, some are dark but I have redone some, everything is readable but I've googled and googled for model/part/serial numbers etc and have had no results that helped to indentify where I could potentially find the UART connection.
If anyone has the same unit or similar it would be great to share the knowledge so perhaps we can help bring the info together and help other debrick this device if there are any!
Many thanks, for anyone who cares take a look!
https://imgur.com/a/8Qz8ESP - all high res images
AC8227L - Mediatek components + unknown MCU - Bricked device help from PCB pictures
info
hi,
i have the same problem , i don't know how to fix it
info
please check this
4pda.ru/forum/index.php?showtopic=930058&st=160#entry81152859
forteon said:
please check this
4pda.ru/forum/index.php?showtopic=930058&st=160#entry81152859
Click to expand...
Click to collapse
Thank you, will try this out.

Categories

Resources