I am not responsible for anything that may happen to your unit by flashing the recovery image.
You do it at your own risk and take the responsibility upon yourself.
Edit 20.05.2018
Updated mtcdmcutool to preapre FULL recovery image (Now after flash recovery image is possible to future update to newer/other version using the standard dmcu.img upload procedure :victory
Before you start you must know what is MCU and what is bricked MCU (this is not the same what bricked SOM: "my Android do not want boot", "my unit stucked at bootlogo" ...)
What you need:
STM32 ST-LINK utility => http://www.st.com/en/development-tools/stsw-link004.html
ST-LINK/V2 programmer, for example => https://i.ebayimg.com/images/g/TE0AAOSwAYtWGQqG/s-l500.jpg
tool to prepare recovery image => https://www.sendspace.com/file/u0vl8w
Steps:
install ST-LINK utility on your PC
find pins on your board: SYS_SWCLK,SYS_SWDIO,+3.3V,GND. Some boards has special pinpads for that:
{
"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"
}
connect appropriate wires to ST-LINK/V2 programmer and board
prepare recovery.bin using tool:
Code:
mtcdmcutool.exe -r dmcu.img recovery.bin
in ST-LINK utility connect to MCU. Should be identified as: STM32F091xB-xC
erase MCU (Target->erase chip)
program/flash file recovery.bin [Start address = 0x08000000]
There is another method to flash MCU.
Instead of ST-LINK/V2 programmer, it is possible to use TTL USBtoUART converter. But it requires a little bit more hardware modification. Maybe @Kayhan 17# will write some guide how to prepare and flash MCU. He did it already here
RemmeberThis is not FULL MCU firmware image. So you will not be able to change the MCU firmware to newer/other version using the standard dmcu.img upload procedure. If you want a newer version you must repeat flash MCU according to steps above
Hello!
This will work for a PX5? My head unit won't turn on, just turn on the leds in the unit 3 times and nothing else. The seller is Witson (MX) and I never got into the recovery in this unit. I tried all the procedure that I read but none of them worked to get into recovery (except the one that requiere some hardware modifications).
Thank you!
paniqueado said:
Hello!
This will work for a PX5? My head unit won't turn on, just turn on the leds in the unit 3 times and nothing else. The seller is Witson (MX) and I never got into the recovery in this unit. I tried all the procedure that I read but none of them worked to get into recovery (except the one that requiere some hardware modifications).
Thank you!
Click to expand...
Click to collapse
No, sounds like your SOM or mainboard is faulty. I'd be happy to look at your unit, with return freight.
marchnz said:
No, sounds like your SOM or mainboard is faulty. I'd be happy to look at your unit, with return freight.
Click to expand...
Click to collapse
That explains everything, hahaha. The unit came with a PX3, I installed Malaysk and it was working for a week, after I rebooted it one day it never turn on again. The seller sent me another PX3 board as warranty and it worked for 3 months, then it stop working suddenly one day when I turned on the car.
So then I bought a PX5 board, it worked for 6 months. One day I was driving using only Play Music app and the stereo froze, I turned off the car but the unit did not work again, so I removed it I re installed the original unit. Then after 4 months later I tried to fix it using a PSU but in the moment that I turned it on, the headunit boot and worked normally, I was happy and reinstalled it into my car, but it just worked for a few days. It stopped working when I turned on the car and it was on reverse gear, when I change to first gear the screen flashed and that's it (switch between camera and the main screen).
Sorry for the long story.
Where are you? To see how much is to send it. I can send it from the US.
Thank you!
paniqueado said:
That explains everything, hahaha. The unit came with a PX3, I installed Malaysk and it was working for a week, after I rebooted it one day it never turn on again. The seller sent me another PX3 board as warranty and it worked for 3 months, then it stop working suddenly one day when I turned on the car.
So then I bought a PX5 board, it worked for 6 months. One day I was driving using only Play Music app and the stereo froze, I turned off the car but the unit did not work again, so I removed it I re installed the original unit. Then after 4 months later I tried to fix it using a PSU but in the moment that I turned it on, the headunit boot and worked normally, I was happy and reinstalled it into my car, but it just worked for a few days. It stopped working when I turned on the car and it was on reverse gear, when I change to first gear the screen flashed and that's it (switch between camera and the main screen).
Sorry for the long story.
Where are you? To see how much is to send it. I can send it from the US.
Thank you!
Click to expand...
Click to collapse
New Zealand. It sounds like it has a bad connection, or dry solder joint.
paniqueado said:
Hello!
This will work for a PX5? My head unit won't turn on, just turn on the leds in the unit 3 times and nothing else. The seller is Witson (MX) and I never got into the recovery in this unit. I tried all the procedure that I read but none of them worked to get into recovery (except the one that requiere some hardware modifications).
Click to expand...
Click to collapse
It seems that MCU is working beacuse MCU is responsible for the blinking of leds. Just like @marchnz wrote, problem may be with wire connections. At the beginning check what the state of ACC, then ACC-DET is.
@Wadzio. I was amazed to find this thread, hopefully can fix my PX5, the order of pins in my image is correct?
sibeng said:
@Wadzio. I was amazed to find this thread, hopefully can fix my PX5, the order of pins in my image is correct?
Click to expand...
Click to collapse
Yes, those that pads but you wrong mark signlas. Look at the schematic:
For me should be:
But the surest solution is to check the connection between the pads and CPU pins (according to the scheme of course)
Wadzio said:
Yes, those that pins but you wrong mark signlas. Look at the schematic:
Click to expand...
Click to collapse
yes, wrong mark
Thank you, i'll try later
---------- Post added at 09:36 PM ---------- Previous post was at 09:11 PM ----------
One more question, when the process will be run, the main power supply HU must be connected or not.
or just the + 3.3V power source from the ST-Link USB pin
sibeng said:
yes, wrong mark
Thank you, i'll try later
---------- Post added at 09:36 PM ---------- Previous post was at 09:11 PM ----------
One more question, when the process will be run, the main power supply HU must be connected or not.
or just the + 3.3V power source from the ST-Link USB pin
Click to expand...
Click to collapse
To be sure to turn it off.
+3.3V from ST-LINK for flashing is enough
Wadzio said:
To be sure to turn it off.
+3.3V from ST-LINK for flashing is enough
Click to expand...
Click to collapse
Ok, i noted
First attempt, can't read memory? any suggestion
in some documents mention, The only way to disable the Read Protection is with the Load Flash Demonstrator Software from ST. After to disable the read Protection the FLASH memory is erased (mass erased).
So @kayhan 17 solution with USB Uart maybe working, or somehow
https://forum.xda-developers.com/an...ide-to-recover-dead-mtcd-device-uart-t3750224
sibeng said:
First attempt, can't read memory? any suggestion
Click to expand...
Click to collapse
The memory can not be read because all MCUs have "Read protection" enabled by the manufacturer
First try erase MCU (menu Target->erase chip)
can't perform erase chip, there is an error message when entering the erase chip menu
in another article said: unlock the flash by setting the read out protection to 0 using the ST-Link utility
ok after I update the ST-Link firmware, change the frequency to 1.8Mhz (do not know, useful or not), can successfully erase chip, but so will upload the .bin file, error again "no target connected", stuck at 0x080000B0.
On Log file: "System reset has not raised up after 2 seconds. Sys reset req"
I will not despair to try again
sibeng said:
ok after I update the ST-Link firmware, change the frequency to 1.8Mhz (do not know, useful or not), can successfully erase chip, but so will upload the .bin file, error again "no target connected", stuck at 0x080000B0.
On Log file: "System reset has not raised up after 2 seconds. Sys reset req"
I will not despair to try again
Click to expand...
Click to collapse
Strange. Which tool do you use? ST-LINK v2 similar to that: link ?
---------- Post edited at 15:41 PM ----------
Maybe this link/conversation will help you: link
Wadzio said:
Strange. Which tool do you use? ST-LINK v2 similar to that: link ?
Click to expand...
Click to collapse
yes, maybe i get the defective type, i will try with another st-link
@Wadzio, You are amazing, really great. Your help is successful.
ST Link clue is, connect the main power suply when connecting with PC, can not use power supply from USB.
and managed to write MCU.
restart and upadate the firmware image.
Thank you very much, without you I will be confused.
greetings from Indonesia :good::good::good::good::good:
Could anyone tell me How can I use mtcdtool.exe???
And how do I prepare recovery.bin????
Thanks in advance
Related
First Off, Huge thanks to F50+ This man sacrificed his tab to locate these resistors.
introduction
I'm not kidding when I say UnBrickable. Modifying the OM pins means you can boot from USB, UART or MMC. This makes the device quite UNBRICKABLE. There is nothing you can do software wise to prevent the device from booting into this mode. We are communicating with the unrewritable, efused IROM on the processor. It's the thing that makes the system on a chip into a "system on a chip".I am here now to tell you how to turn your Samsung P1000 into a KIT-S5PC110 development board. The KIT-S5PC110 development board is the platform used to develop our phones. There are some differences between this mod and the official development platform. The S5PC110 has a removable internal SDCard and no touchscreen.
Why would you want to do this? When you plug in the battery and connect it to the computer in "off" mode, it will become an S5PC110 board awaiting download of a program to run. This occurs long before anything like software or firmware enters the processor. This is the IROM of the device awaiting commands or a power on signal.
How could it possibly be better then JTAG? Let's count the ways....
1. The only part required is a wire.
2. No shipping time.
3. No cost for a box to interface the computer.
4. Permanent.
5. Can be done as a preventive measure.
6. Gives the ability to test new Bootloaders temporarily.
7. Allows development of the entire system.
8. Removes worry about flashing and acts as a backup.
After performing this mod:
Remove the battery, replace the battery, your phone will connect to the computer via USB and await commands. Otherwise it will pretty much act like a P1000. See the Special Instructions section.
Part 1:Hardware Modification
You will need:
1. Get someone who knows what they're doing with a soldering iron. If they don't know what flux is, then they don't know what they're doing. You can send me a PM(or email my [email protected]) or Connexion2005(aka MobileTechVideos.com).
2. Soldering iron - make sure it's sharp, if it's not sharp, then sharpen it, flux it and retin it.
3. fFux
4. Solder
5. Tweezers
6. A relay (possibly- for the wire within to use as a bridge)
7. A #1 tri-blade driver
performing the modification:
1. tear apart your Galaxy Tab... Make sure to take out your SIM and external SDCard before you do this.
1A. Remove the screws.
1B. Separate the top case from the bottom case
****VIDEO OR PICTURES NEEDED*****
2. Perform the mod as follows: remove the xOM5 resistor and jumper the non-grounded pad of xOM5 to the same side of xOM0 or xOM3.
{
"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 will be able to give more detail after I have performed this modification myself.
3. reassemble the Tab.
Special Instructions
This replaces the battery charging sequence. The normal battery charging sequence can be activated by holding power for 4 seconds, then plugging in the device, or you can use an authentic Samsung Charging Cable for charging the battery
To turn on the device, and operate in normal mode, you must hold the power button for 5 seconds.
Part 2: Software Based Resurrection
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
The entire software resurrection can be summed up like this
Here is a Galaxy Tab specific video
Unbricking:
1. Apply UnBrickable Mod to your device: see Hardware Modification section
2. Run The Ultimate UnBrickable Resurrector. You can find the Resurrector here in our SVN repository http://code.google.com/p/hummingbird-hibl/downloads/list
When you see this image you are in S5PC110 SEC SoC mode. When you see this mode you must proceed to step 2.
If it will only show this image, then you have not performed the modification correctly, or you have a hardware problem.
If it shows this, regardless of what's on your screen, you're in download mode. Proceded to step 3.
2. Click the Download Mode button (then click the one next to it). I find it's easiest to click Download Mode, type a password, plug in the device, then press enter.
3. Run Heimdall One-Click to flash firmware on your device. http://forum.xda-developers.com/showthread.php?t=1323527
4. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software.
reading material
Creating your own Samsung Bootloaders: http://forum.xda-developers.com/showthread.php?t=1233273
KIT-S5PC110 manual: http://www.mediafire.com/?94krzvvxksvmuxh
how to use DNW: http://tinyurl.com/dnw-how-to
Flash using openOCD and DNW: http://www.arm9board.net/wiki/index.php?title=Flash_using_OpenOCD_and_DNW
another DNW example: http://www.boardset.com/products/mv6410.php
ODroid dev center: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
drivers and utilities
This will be an ever expanding list
Linux Automated UnBricker:http://code.google.com/p/hummingbird-hibl/downloads/list
Windows Drivers http://forum.xda-developers.com/attachment.php?attachmentid=678937&d=1312590673
Windows Download Tool DNW: http://forum.xda-developers.com/attachment.php?attachmentid=678938&d=1312590673
Windows Command Line tool: http://forum.xda-developers.com/showpost.php?p=17202523&postcount=27
Linux DNW Utility: http://dev.odroid.com/projects/uboot/wiki/#s-7.2
Linux ModeDetect tool: http://code.google.com/p/hummingbird-hibl/downloads/list
firmware
Bootloader Hello World by Rebellos http://forum.xda-developers.com/attachment.php?attachmentid=698077&d=1314105521
UnBrick tool http://forum.xda-developers.com/showthread.php?t=1242466
Conclusion
Congratulations. You now have a device which works like a KIT-S5PC110 with an OM Value of 29. Now get to developing some serious custom software. See here for setting up the UART output http://forum.xda-developers.com/showthread.php?t=1235219
Omg this is incredible!!! You are a genius!!!
Summoned by my Heretic Tab
Yeah this is a genius idea for our galaxy tabs. With this, I no longer have to worry about bricking my device via odin because of my ****ty faulty HP laptop. (it happened once and i had to send it overseas for warranty repairs, 2 months w/o my tab )
lambstone said:
Yeah this is a genius idea for our galaxy tabs. With this, I no longer have to worry about bricking my device via odin because of my ****ty faulty HP laptop. (it happened once and i had to send it overseas for warranty repairs, 2 months w/o my tab )
Click to expand...
Click to collapse
I still need to prove it works.
Good going Adam
Congratulations～～～～～
guaiwujia said:
Congratulations～～～～～
Click to expand...
Click to collapse
Its way too early for that... save that for the how-to thread.
how to
Looking forward to trying this on my tab. You mentioned firmware would need to be made,I assume stock boot loaders could be used right away?how do we know which is grounded pad? What is the relay for?
Cheers
david
diagdave said:
Looking forward to trying this on my tab. You mentioned firmware would need to be made,I assume stock boot loaders could be used right away?how do we know which is grounded pad? What is the relay for?
Cheers
david
Click to expand...
Click to collapse
Finally!
diagdave said:
Looking forward to trying this on my tab. You mentioned firmware would need to be made,I assume stock boot loaders could be used right away?how do we know which is grounded pad? What is the relay for?
Cheers
david
Click to expand...
Click to collapse
Until I'm able to actually perform this mod on a device, I can't tell you anything. I don't know any more than what's in the first post.
AdamOutler said:
Until I'm able to actually perform this mod on a device, I can't tell you anything. I don't know any more than what's in the first post.
Click to expand...
Click to collapse
I'm gonna go ahead and guess that you don't have a device to test this on? Or just lack of time?
A bit of an update... Someone contacted me via PM to let me know that they bricked their device in the rare S5PC110 mode. This can happen if you damage your IBL from the IBL+PBL partition, or if the device realizes it cannot boot before attempting to do so. They were able to get their tab into download mode using the Linux Resurrector from the first post.
So, we've got the software part verified. Now, we need confirmation that the hardware mod will allow the device to enumerate as a "S5PC110 SEC SoC" on a Linux based system.
Someone please confirm that after the modification the device shows "S5PC110 debug mode" in Linux with the ModeDetect utility here: http://code.google.com/p/hummingbird-hibl/downloads/list
AdamOutler said:
A bit of an update... Someone contacted me via PM to let me know that they bricked their device in the rare S5PC110 mode. This can happen if you damage your IBL from the IBL+PBL partition, or if the device realizes it cannot boot before attempting to do so. They were able to get their tab into download mode using the Linux Resurrector from the first post.
So, we've got the software part verified. Now, we need confirmation that the hardware mod will allow the device to enumerate as a "S5PC110 SEC SoC" on a Linux based system.
Someone please confirm that after the modification the device shows "S5PC110 debug mode" in Linux with the ModeDetect utility here: http://code.google.com/p/hummingbird-hibl/downloads/list
Click to expand...
Click to collapse
I pinged you on IRC, but ModeDetect shows "S5PC110 UnBrickable Debug"
Found a well-documented teardown manual at ifixit
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1
lilstevie said:
I pinged you on IRC, but ModeDetect shows "S5PC110 UnBrickable Debug"
Click to expand...
Click to collapse
Great.. Can you run the resurrector and verify that it goes into download mode?
AdamOutler said:
Great.. Can you run the resurrector and verify that it goes into download mode?
Click to expand...
Click to collapse
yep, it does, only difference is that it is not a bootloader designed for this device, it turns the LED flash on, and doesn't bring the screen up, but in any case, heimdall can communicate, although I have not tried flashing from it yet
lilstevie said:
yep, it does, only difference is that it is not a bootloader designed for this device, it turns the LED flash on, and doesn't bring the screen up, but in any case, heimdall can communicate, although I have not tried flashing from it yet
Click to expand...
Click to collapse
Awesome. Try running a heimdall print-pit or a close-pc-screen to verify everything works. Ill get a one-click back to stock and a one-click CWM prepared for testing later tonight if that works.
If you have the tools available, it would be good to probe around for the UART output from the device. UART is the first step to porting other OSs to a device.
My setup is an Arduino Mega. For probing I connect the RX line to a small piece of wire with a sewing needle attached. I ground the ground on the Arduino to the ground on the board. I then run minicom -D /dev/ttyUSB0. Set the options to 8n1 flow control off. Then probe around on the board while repeatedly pressing the power button so as to trigger UART transmission without turning on the device. Once you find a point with weird question marks, hold the power button, take a picture and annotate it.
The most common points are on the JTAG port. Usually they are opposite of the processor 's pin 0 dot. The RX and TX are always side-by-side. This would help people develop this device.
guys, you're **cking best! I was waiting for that! so, I have 2 questions:
1) if I disassemble my tab I will lose my warranty any way, isn't it?
2) I'm not sure with my english so can anybody translate it in russian (please no google translate, I don't want to loose my beutiful device).
thanks for answers
p.s. is there any disassemble instuctions?
AdamOutler said:
Awesome. Try running a heimdall print-pit or a close-pc-screen to verify everything works. Ill get a one-click back to stock and a one-click CWM prepared for testing later tonight if that works.
Click to expand...
Click to collapse
I did that before posting it worked, that was part of my confirmation
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
AdamOutler said:
If you have the tools available, it would be good to probe around for the UART output from the device. UART is the first step to porting other OSs to a device.
My setup is an Arduino Mega. For probing I connect the RX line to a small piece of wire with a sewing needle attached. I ground the ground on the Arduino to the ground on the board. I then run minicom -D /dev/ttyUSB0. Set the options to 8n1 flow control off. Then probe around on the board while repeatedly pressing the power button so as to trigger UART transmission without turning on the device. Once you find a point with weird question marks, hold the power button, take a picture and annotate it.
The most common points are on the JTAG port. Usually they are opposite of the processor 's pin 0 dot. The RX and TX are always side-by-side. This would help people develop this device.
Click to expand...
Click to collapse
UART is pin 20 (RX) and 21 (TX) on the docking port, we have actually had this for a while, The jtag port is different on this device, it is along the edge of the board and coated so you need to scrape them back to get access.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
devilng said:
guys, you're **cking best! I was waiting for that! so, I have 2 questions:
1) if I disassemble my tab I will lose my warranty any way, isn't it?
2) I'm not sure with my english so can anybody translate it in russian (please no google translate, I don't want to loose my beutiful device).
thanks for answers
p.s. is there any disassemble instuctions?
Click to expand...
Click to collapse
yeah you will lose your warranty when opening the device,
before getting someone to translate I would really make sure you know how to solder, I needed to use liquid flux to aid getting this done, and I don't normally use it ever, the points where you need to solder are fairly small.
Got my replacement display assembly a couple days ago and went on to replace the screen. Connected everything back and everything seems to work - except for the touch screen functionality.
Checked the ifixit tutorial for display assembly replacement and found that someone commented that he has the exact problem, stating he found a guide to "remove the metal protection over the connector to properly disconnect it and reconnect after"
{
"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"
}
Checked the connection multiple times, seems to be connected properly, which makes me assume that what he did works. Thing is - I don't understand how am I supposed to remove everything and put it back together.
Any help?
Thanks.
firecharge said:
Got my replacement display assembly a couple days ago and went on to replace the screen. Connected everything back and everything seems to work - except for the touch screen functionality.
Checked the ifixit tutorial for display assembly replacement and found that someone commented that he has the exact problem, stating he found a guide to "remove the metal protection over the connector to properly disconnect it and reconnect after"
Checked the connection multiple times, seems to be connected properly, which makes me assume that what he did works. Thing is - I don't understand how am I supposed to remove everything and put it back together.
Any help?
Thanks.
Click to expand...
Click to collapse
The copper looking piece is held in with small clips around the edges. I used a small flat head inserted into the corners and pried straight up to lift it out of the clips. It came off pretty easily. Then you just need to line it back up with the clips and press down to replace it.
Sent from my ASUS_Z00A using Tapatalk
buddy factory reset your device once. there might be difference in touch version.
kenbo111 said:
The copper looking piece is held in with small clips around the edges. I used a small flat head inserted into the corners and pried straight up to lift it out of the clips. It came off pretty easily. Then you just need to line it back up with the clips and press down to replace it.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks
That worked great - though there is a different issue now.
Phone seems to keep locking and unlocking itself every few seconds.
Seems to be an issue in the connection between the bottom and top parts of the mobo.
Any idea about what could be the issue here?
Hi, I don´t want to make new thread, maybe someone can tell me how to fix my problem.
I changed Lcd+touch for my ZE500CL/Z00D and first Touch Panel Firmware update failed, but after hard reset trough recovery it started to work. But now every time I turn it off nad on / or just reboot, it updates touch panel firware.. luckily successfully... but every time.. I use last official SW version (V12.16.5.126 ).
Mairo said:
Hi, I don´t want to make new thread, maybe someone can tell me how to fix my problem.
I changed Lcd+touch for my ZE500CL/Z00D and first Touch Panel Firmware update failed, but after hard reset trough recovery it started to work. But now every time I turn it off nad on / or just reboot, it updates touch panel firware.. luckily successfully... but every time.. I use last official SW version (V12.16.5.126 ).
Click to expand...
Click to collapse
really appreciate that its good to not to start new threads without any actual requirement
flash raw firmware once. you can get the firmware from following thread
https://forum.xda-developers.com/zenfone2/help/guide-bring-to-life-zenfone-2-ze500cl-t3503144
sukhwant717 said:
really appreciate that its good to not to start new threads without any actual requirement
flash raw firmware once. you can get the firmware from following thread
https://forum.xda-developers.com/zenfone2/help/guide-bring-to-life-zenfone-2-ze500cl-t3503144
Click to expand...
Click to collapse
it looks too much struggle, so if there is no other way then I leave it so. ( I have Win 10 and usb keyboard, so I can´t disable driver signatures ). Or can I flash this raw.zip in root folder like odher updates?
Mairo said:
it looks too much struggle, so if there is no other way then I leave it so. ( I have Win 10 and usb keyboard, so I can´t disable driver signatures ). Or can I flash this raw.zip in root folder like odher updates?
Click to expand...
Click to collapse
buddy that link was to get raw firmware only. you do not need to disable signature enforcement. just download rar firmware file and flash it with AFT. use the only section flash raw firmware. you need to install only asus usb driver
sukhwant717 said:
buddy that link was to get raw firmware only. you do not need to disable signature enforcement. just download rar firmware file and flash it with AFT. use the only section flash raw firmware. you need to install only asus usb driver
Click to expand...
Click to collapse
impossible to find proper step by step AFT using guide, 1. like do in need first unlock bootloader? 2. when I boot (power + vol up) fastboot mode then AFT dont find phone and "fastboot cmd waiting" .. . is in red, everywhere I can see users have blue text there. 3. do in need activate USB debuging?
Flashing is not something unknown for me , I have using 3 years Nexus 5 and still using it, but flashing asus devices is unknown and strange.
I better leave this phone as it is. I hope user have extra 10 sec time to wait touch panel update on every boot.
Mairo said:
impossible to find proper step by step AFT using guide, 1. like do in need first unlock bootloader? 2. when I boot (power + vol up) fastboot mode then AFT dont find phone and "fastboot cmd waiting" .. . is in red, everywhere I can see users have blue text there. 3. do in need activate USB debuging?
Flashing is not something unknown for me , I have using 3 years Nexus 5 and still using it, but flashing asus devices is unknown and strange.
I better leave this phone as it is. I hope user have extra 10 sec time to wait touch panel update on every boot.
Click to expand...
Click to collapse
to use AFT all you need is device in fastboot mode. check if drivers are properly installed. which version of AFT you are using?
Here are my notes regarding the Eonon GA6164F and recovering from a black screen, cant boot, cant get into recovery.
Thanks to all the members and information on this site who i was able to piece together to come up with this solution.
I still dont know if my assumptions are totally correct, (please comment if i need to learn more) .
--
Back Story : My device was shipped with a Dec 2016 Android 5.1.1 build, and my steering wheel keys on my Camry were not all working.
Skip track and Back track were doing the same action, I tried re-learning/mapping in "WheelKeys Study" but nothing fixed it.
I resorted to using Vol - + for volume, Skip forward = skip track, MODE button (underneth) as = skip back.
I contacted Eonon about this, and they gave me a new Android build to try, update.img.
I wasnt able to update using the Settings - About - Software Update. (Error finding file).
I wasnt able to update using the standard recovery options (RES button, power etc.)
I did notice it was looking for dupdate.img.
I renamed my update.img file to dupdate.img and it was able to install via the Settings - About - Software Update.
The device rebooted , installed, then nothing... just a black screen.
I couldnt get any display up no matter what i tried.
After 24 hours or so of testing/trailing etc. I did manage to get it back working.
Im certain it was a bad update file because once i had it working again, i re-applied the update file i was supplied and sure enough, it broke it again.
These are my notes on how i recovered it.
--
Reboot into recovery on a healthy device
----------------
Hold RES
Press Power
Release RES (while still holding power)
Let go of power 1-2 secs after
Should reboot into recovery
---
Boot into recovery and restoring on a un-healthy device
----------------------
If cant boot into recovery
Download a Malaysk android build file (you may need to sign up to the hosting server site, and then add to downloads, then you can download to your computer from there)
Create bootable SD card using 'rockchip create upgrade disk tool v1.4'
(Run .exe as admin, dont check 'SD Boot', just leave 'Upgrade Firmware'
(If you cant see your USB drive, check that you have right clicked-Run as Admin in windows on the .exe)
Select Malaysk MTCD dupdate.img file
First post has download links
https://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development/rom-malaysk-roms-mtcd-device-t3385309
Fully power off device (unplug from the back/or remove neg battery from car).
Insert new-bootable SD card into GPS slot
Plug device back in (or reconnect neg. battery cable to car)
- Device will boot into recovery and complain about no update file (thats fine) the Bootable SD card is just to get you into recovery.
{
"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"
}
Once in recovery, remove the GPS slot SD card and plug in a USB stick with an update.img
(my machine was looking for dupdate.img so i had to rename it).
Press power button to skip down the settings
Hold power button to select an option
Select 'Update system/mcu image from usb and clear all'
<processing>
Device reboots
Toyota logo shows (never progresses)
Press RES
Device reboots
Toyota logo shows
Android is starting (optimizing app XX of XX)
Malaysk recomends once the build is installed, to reboot into recovery once again using the normal method of buttons (RES + Power etc.) and 'wipe all data/factory and cache reset'
--
Now i am running a 10.8 build, because i was having trouble with the Google services on the latest, and i need to learn more about the 11.4 build and the MicroG stuff that replaces the Google services.
I am still suffering from the steering wheel controls issue, but at this point... i dont care...
I found i am getting a lot of "unable to read file" from the m4a files i have on my SD or USB card/stick and i need to learn more about how to get the steering wheel controls to action "other" music apps, i believe this is to do with the MTCD-Keys stuff, but going from what seemed like a dead device to this point, i want to wait a while before i start playing with it again.
I have added pictures in the thread, but they are linked to a photobucket, so i have also added them as attachments in case that photobucket account ever goes down.
Eonon Issue HELP!!!!
I have a Eonon Radio similar to this unit except it originally had 4.2.2 on it I recently tried to update it to 4.4.4 and mcu 2.81 which worked perfectly until restarting the car overnight. Radio booted into cannot find e:\
I then reverted back to 4.2.2 but I can get to the 4.2.2 recovery mode but every update.img I try to use only puts me into a reboot mode of the KiKat screen Maylay Mod Splash. Anyone out there can help suggest something?
I seem to have a half baked system that I can get into the recovery mode for 4.2.2. but the update.img says it cannot find it in the GPS sd card.
rogerradio said:
I have a Eonon Radio similar to this unit except it originally had 4.2.2 on it I recently tried to update it to 4.4.4 and mcu 2.81 which worked perfectly until restarting the car overnight. Radio booted into cannot find e:\
I then reverted back to 4.2.2 but I can get to the 4.2.2 recovery mode but every update.img I try to use only puts me into a reboot mode of the KiKat screen Maylay Mod Splash. Anyone out there can help suggest something?
I seem to have a half baked system that I can get into the recovery mode for 4.2.2. but the update.img says it cannot find it in the GPS sd card.
Click to expand...
Click to collapse
There are no Eonon radios, Eonon sell radios from several different manufacturers, the one in this thread is a Klyde - KLD.
If yours was 4.2.2./4.4.2 and MCU 2.85 then you have an MTCB unit and you need to try in the MTCB forums.
I've downloaded the rockchip create upgrade disk tool v1.4 and ran through your instructions. The HU won't boot off the SD card. Just sits there. If I remove the SD card, it immediately boots into the installed ROM. (I want to downgrade)
Hi
I tried reinstall the malaysk firmware but i rename dupdate.img as update.img and after reinstall now my device do not turn on, only show black screen like off and appear turn on nothing, i tried apply different methods of reset but nothing worked.
Help please!
Rodrizio said:
Hi
I tried reinstall the malaysk firmware but i rename dupdate.img as update.img and after reinstall now my device do not turn on, only show black screen like off and appear turn on nothing, i tried apply different methods of reset but nothing worked.
Help please!
Click to expand...
Click to collapse
Can you put it in recovery ?
typos1 said:
Can you put it in recovery ?
Click to expand...
Click to collapse
I don't know how exactly. I push the reset and power button in the sequence of first post but nothing happens. Only every time pushed the reset button the device light flashes but it's look like off
Rodrizio said:
I don't know how exactly. I push the reset and power button in the sequence of first post but nothing happens. Only every time pushed the reset button the device light flashes but it's look like off
Click to expand...
Click to collapse
Try making a bootable sdcard.
Guys your help pls! My head unit is stuck to the initial logo (Navigation System) and there seems to be nothing I can do to get into recovery to re-install the software. I have tried everything described above, no way to get into recovery with buttons, so I made and SD bootable card with various firmwares but the HU does not seem to read the card (I tried also with a USB stick, with no luck).
Is there anything else I can try to get it to work again?
My HU is a Px3 MTCE KGL 2 GB.
Thanks a lot for your help!!
Bobek82 said:
Guys your help pls! My head unit is stuck to the initial logo (Navigation System) and there seems to be nothing I can do to get into recovery to re-install the software. I have tried everything described above, no way to get into recovery with buttons, so I made and SD bootable card with various firmwares but the HU does not seem to read the card (I tried also with a USB stick, with no luck).
Is there anything else I can try to get it to work again?
My HU is a Px3 MTCE KGL 2 GB.
Thanks a lot for your help!!
Click to expand...
Click to collapse
Try @marchnz's recovery method.
typos1 said:
Try making a bootable sdcard.
Click to expand...
Click to collapse
I tried boot with a Sdcard bootable created with rockchip create upgrade disk tool (my sdcard is a 8gb size. I don´t know if the size make a issue) with the Malaysk dupdate.img file but nothing happend.
I follow the next steps.
I unplug from the back my device and insert the SD card bootable into GPS slot.
I plug again the device from the back and nothig, only the same screen black like off, I try differents combination of keys (press RES+Power ) and nothing....:crying:
It´s my device really dead? :crying:
Rodrizio said:
I tried boot with a Sdcard bootable created with rockchip create upgrade disk tool (my sdcard is a 8gb size. I don´t know if the size make a issue) with the Malaysk dupdate.img file but nothing happend.
I follow the next steps.
I unplug from the back my device and insert the SD card bootable into GPS slot.
I plug again the device from the back and nothig, only the same screen black like off, I try differents combination of keys (press RES+Power ) and nothing....:crying:
It´s my device really dead? :crying:
Click to expand...
Click to collapse
You shouldnt need to press anything, it should boot from the sdcard as soon as you turn it on. I would read @marchnz's unbricking threads if nothing its working.
Just want to know were I can find an "original" Rom for my Klyde PX5 MTCD unit.
I install Hal9k and it work like a charm but what if I have to send it back to Shenzhen?
Maybe I have to do this so before that I want to get it in original state.
Seelenwinter said:
Just want to know were I can find an "original" Rom for my Klyde PX5 MTCD unit.
I install Hal9k and it work like a charm but what if I have to send it back to Shenzhen?
Maybe I have to do this so before that I want to get it in original state.
Click to expand...
Click to collapse
Lol, no one send their unit back to China because it costs too much, its far easier and cheaper to repair it yourself, but there are factory ROMs around if you look, but I wouldnt bother looking unless you need to, cross that bridge (if and) when you come to it as they say.
Now it's a situation I really need that klyde mtcd px5 firmware.
Are there any hints or links?
Thanks ✌?
Yeah loads all over the forums.
Hello together,
have a problem with my first gen Fire TV 2014 box.
Went on vaccacion and turned everyhting off, when i came back and turned everything back on, the Fire Tv is only booting into recovery mode.
Is there a way to fix it? the box was not modified in any way, except a sideloaded kodi.
So im wondering if its possible to somehow reinstall the full-software, on a phone it would be possible using odin for samsung for example, but is there anyway to do so on a firetv? jtag, anything?
regards
Vin
Does if give you the option to wipe cache? I have not dealt with the factory recovery, but you can always wipe the cache then reboot and see what happens. Worst case wipe Data and cache (that is like a factory reset and you will have to reinstall everything).
No its just a blank Page unfortunately with the Information to wait till it reboots (it doesnt) and in case it doesnt to pull the cable, which also doesnt help.
Would love to wipe everything regardless of the Data, but cannot figure Out how to get this Option
Amazon Recovery Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm having the same issue. Chatted with amazon and tech told me this is a know issue and there is a master ticket and my info was added to the list. Someone should contact me within 3 days. I think an update probably bricked my device. What are the odds they send me a new one? Will post update.
I tried some troubleshooting prior. Was trying to adb into it but checking router, it doesn't have an ip, wireless or wired, which is what is needed to adb into it. I also put the firmware on a usb and renamed it recovery.bin but wouldn't load. Connected it to laptop via usb to usb cable. Using a usbview windows 10 debug program, it only connects when booting and on the white logo screen. So when you get that recovery message, there is no power to usb port.
Just have to now wait for them to contact me.
any news so far?
when i called the amazon support hotline (germany), they said its no known issue and there is nothing they can do, also since the warranty is over, there wont be any solution, or replacement whatsoever, very disappointing to be honest
This is exactly the same problem i have.
My FireTV 1 just boots into the colored animated logo and doesn't go any further.
From there i can get a adb shell via a usb a-a cable. But i don't know what to do at this point.
Mine Bricked Thursday during a software update. A gen 1 box. If I could get the software reload onto a USB drive, I know it would reboot. Amazon admitted they had been getting calls all night ( I called at 10:00 PM). The rep promised me a replacement (fat chance) but didn't send me anything. I tried a USB keyboard but no go.
m0r0k said:
This is exactly the same problem i have.
My FireTV 1 just boots into the colored animated logo and doesn't go any further.
From there i can get a adb shell via a usb a-a cable. But i don't know what to do at this point.
Click to expand...
Click to collapse
You could always try wiping from the shell... Cache or a factory reset, just throwing out ideas....
something like this still a possibility?
https://www.youtube.com/watch?v=IgC4iDzQ8gw
or is there a way to boot up an original amazon update via usb?
Still have a working recovery menu, so there must be something usefull to do with it, just cant select anything on the screen (see picture in previous post)
m0r0k said:
This is exactly the same problem i have.
My FireTV 1 just boots into the colored animated logo and doesn't go any further.
From there i can get a adb shell via a usb a-a cable. But i don't know what to do at this point.
Click to expand...
Click to collapse
You have a different issue. We have a white logo and the 3e error. Wish I had your problem, I could recover it.
Google how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software. Can't post urls since I'm new
---------- Post added at 11:11 PM ---------- Previous post was at 10:55 PM ----------
Vin 2 said:
something like this still a possibility?
or is there a way to boot up an original amazon update via usb?
Still have a working recovery menu, so there must be something usefull to do with it, just cant select anything on the screen (see picture in previous post)
Click to expand...
Click to collapse
Unfortunately we don't have a working recovery menu. It should have other options. Google how-to-unbrick-by-entering-recovery-mode-and-factory-reset-the-amazon-fire-tv, and you'll see the options we should have. Can't post urls, too new. They called today and scheduled someone to pick it up to have it delivered to lab for review. Was hoping they would give me the steps to access and recover it but looks like they will be doing it instead since they probably have to open it up like that youtube video you posted to access it directly. I hope they send me an updated device and just keep mine for review and testing.
Toonice007 said:
You have a different issue. We have a white logo and the 3e error. Wish I had your problem, I could recover it.
Google how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software. Can't post urls since I'm new
Click to expand...
Click to collapse
First of all, thank you. The problem is my device is unrooted.
Booting into recovery gives me the same unusable Amazon system recovery <3e> screen.
It looks like my FireTV (gen1) has the newest software, which is maybe the cause of the problem:
Code:
$ cat system/build.prop | grep fireos
ro.build.version.fireos=5.2.6.0
Is there a way to root it via adb shell?
Thanks for any hints.
m0r0k said:
First of all, thank you. The problem is my device is unrooted.
Booting into recovery gives me the same unusable Amazon system recovery <3e> screen.
It looks like my FireTV (gen1) has the newest software, which is maybe the cause of the problem:
Code:
$ cat system/build.prop | grep fireos
ro.build.version.fireos=5.2.6.0
Is there a way to root it via adb shell?
Thanks for any hints.
Click to expand...
Click to collapse
I could be wrong but I don't think you can root that version yet. Sorry I do see in the instructions you need to be rooted.
Sorry all. They had me ship them the firetv and gave me $85 promo credit on Amazon. Was hoping they would instruct me on how to fix it.
same for me, nobody was able to give a solution, was redirected to real technical support in the backoffice>no solutions
finally after many tries, amazon was ready to give a accommodating arrangement, they will replace my 2014 model, with the 2017 model thats going to be released end of october, despite the lack of warranty
but yes still its a disappointment to have working hardware, but broken software here, would have liked to continue using the old model
Looks like they realize it's an issue with the update that affects at least the first gen Fire TV. Good that they are doing the right thing. That's why I like and buy Amazon. Hopefully others see this post and get the same compensation.
I'm using the firetv 1 model too. I'm rooted and have blocked updates, thankfully. I really wonder if this update bricked all the aftv 1 models. I'm hoping for a prerooted @rbox image. This new software is really needed, because all software revisions before have the very serious bluetooth vulnerability that affects all operating systems (your device grants console access to any attacker in bluetooth range without your notice).
For me, the 2017 model is no option since i depend on the optical out.
Sorry for bumping an old thread, but I have a Fire Tv Stick 2nd Gen (not rooted) and getting the same amazon system recovery 3e as posted by OP.
Wondering if any fix was found for the same as I do not see a resolution mentioned in this thread.
rocker123 said:
Sorry for bumping an old thread, but I have a Fire Tv Stick 2nd Gen (not rooted) and getting the same amazon system recovery 3e as posted by OP.
Wondering if any fix was found for the same as I do not see a resolution mentioned in this thread.
Click to expand...
Click to collapse
You may just unlock the stick. With twrp recovery you can fix your issue.
Sus_i said:
You may just unlock the stick. With twrp recovery you can fix your issue.
Click to expand...
Click to collapse
Is there an easier way out... The steps listed for TWRP installation seem to be a bit complex..
Tried plugging in a USB keyboard to my TV, (alt+ prt sc+ I), did not work for me..
Is there a physical button inside the AFTT to do a hard reset ?
rocker123 said:
Is there an easier way out... The steps listed for TWRP installation seem to be a bit complex..
Tried plugging in a USB keyboard to my TV, (alt+ prt sc+ I), did not work for me..
Is there a physical button inside the AFTT to do a hard reset ?
Click to expand...
Click to collapse
No, there isn't any button inside
A way easier solution is to buy a new device...
I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"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"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.
You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.
My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.
To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz
Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?
paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me
Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !
Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?