Develop Bugs

[Q] help! kindle fire bricked

ok here is how it went.... i had installed cm 10 android 4.1 rom and also flashed change_to_nexus.zip. While flashing, i chose the wrong rom to flash which was my backup for stock software for kindle fire. i then installed my back up cm 10 rom. i later found out that i had deleted twrp and fff when i had flashed my stock software then cm 10... after a week of trying to find out how to get trwp.. no results.. i got frustrated and started deleting random files and one was the systems file. (dont ask why) thi forced close everything, making me reboot. from there it boots up in regular kindle fire logo, quicky flashes a whit light, then goes to a backlit screen. i drained the battery and stuff like that but no help. i try to reinstall twrp with kfu but it doesnt reconize my kindle fire. i go to devmanager and it shows up as a disk drive, amazon file-cd gadget usb device. i got to devices and printers it shows up as android. nothing reconizes my kindle fire. im only 13... dont want my parents to know cause theyll get mad. any help would be well appriciated.
thanks,
gboy

pics
i attached some pictures

You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547

hmmm
kinfauns said:
You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
well i im 13 so i cant get the factory cable without my parents knowing... and i have tried to open the back... its super hard.. can u tell me how to open the back without scratching it.

walkthrough
kinfauns said:
You have a device with a broken system booting with the stock bootloader. You'll need to get it to boot into fastboot mode to fix it. There's a remote chance you'd be able to change bootmodes through adb shell, but I doubt it. The only likely way you will get this fixed is by either utilizing a factory cable or opening up the back of the case. The following will spell out the details...
http://forum.xda-developers.com/showthread.php?t=1668159
If any part of that is confusing to you, you need to read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
could u give me a walkthrough how i would use command prompt and adb shell to unbrick.... please make so i can understand. thanks. i'm pretty sure i have everything downloaded that i need. also is there any chance i could fix the driver to one that kfu would reconize?

http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.

?
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.
Click to expand...
Click to collapse
sorry for my stupidity.. still dont understand what im supposed to be reading from the link you gave me.

Sorry, I keep forgetting Tapatalk is a little different from the webpage.
http://forum.xda-developers.com/showthread.php?t=1869297&page=9

83
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=31141110
Start at post #83 and read on.
Click to expand...
Click to collapse
when u say 83 and on.. u mean 83-1 or 83 up?

Why would you read from #83 going backwards?
{
"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"
}

soupmagnet said:
Why would you read from #83 going backwards?
Click to expand...
Click to collapse
ok ill do the back cover way.. can u give me info or post how to open the back besides using something sharp... bcause it scratching my kindle

Plastic tools are by far the best even a really stiff guitar pick will work just don't go all the way with it rather take several careful passes around the device...of course you are just removing the back cover http://m.youtube.com/#/watch?v=MGLn1TVAITQ&desktop_uri=/watch?v=MGLn1TVAITQ

firekit
ok so i guess i gotta download it to fix it if im gonna do it the back cover way. instructions on taking the backcover... without scratching...?

yay
yay got it opened... now wht???

try
when i try to download the ubuntu.. it gets corrupted at the end. i also dont know wht to do now with the back cover pryed open.

http://forum.xda-developers.com/showthread.php?t=1869297&page=9
Start at post #83 and read on.

ubuntu keeps getting corrupted on 32 and 64...

There isn't much we can do about that. That's a problem with your computer or your flash drive.

lol.. didnt have enough space on my flash drive... lets try agian...

If your not going this route you should be its all set up
Here try this iso http://db.tt/KDNzyCTP
Instructions:
1. Download this http://www.pendrivelinux.com/ use universal usb installer
2. Download iso
3. Preformat usb in windows
4. Select try unlisted Linux iso from the very bottom of dropdown in universal usb installer
5. Select iso
6. Select usb drive letter
7. Tick format
8. Create
9. Eject safely and remove
10. Shut down computer
11. Insert and power on computer
12. Select boot from usb and use..
different build but thread found here http://forum.xda-developers.com/showthread.php?t=1882565

Guide how to unlock bricked MCU units

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

Android tablet, how to disable kiosk mode or install new firmware

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?

Zenwatch (WI500Q) firmware needed...

Hey all.
It seems like this section of the forum hasn't seen any visitors for some time, not surprising given the age of the original Zenwatch. However, I am posting this on the slim chance that someone with one of these watches might see it and help a brother out.
My Zenwatch was bricked years ago following a corrupted OTA update, and hasn't seen the light of day since. Recently though I found the watch, charged it up, and gave it another go. The stock firmware was still crashing constantly leaving the watch unusable, but I managed to install the Asteroid OS on the watch and now it works, albeit in a very limited fashion compared to the official software.
Now that I know that the watch itself is OK, and it just needs the stock firmware to be installed, I turn to you. Asus were unable to help me, as they no longer have access to the original firmware (or more likely, they're unwilling to share them with an end user), I am hoping that someone on this forum still possesses one of these watches and can create and share a backup of the OS, as it now appears that this is pretty much my last chance of getting my watch working properly again.
So, any retro watch owners left in this corner of the t'interweb?

Hi! I have this watch with stock firmware. Tell how to do the backup or send manual and I'll do it.

{
"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"
}

helloworld1337 you might be about to make a lot of people very happy!
I'm not sure how to extract the firmware from the watch, I'll have to do a little research in to that, but I don't think it's a particularly complicated procedure. Give me a little time and I'll get back to you as soon as I can.
Thanks again!

OK, I think I understand how to do this now, but as with any image copying / rooting process, only proceed if you are happy to do so, there is always the slim chance that rooting a watch can have undesired effects, but mine rooted without any issues. So, here we go...
Files that you will need...
KingRoot - https://kingroot-pc.en.uptodown.com/windows/download
ADB & Fastboot - https://developer.android.com/studio/releases/platform-tools
ADB Explorer - Can be found in the Microsoft Store. It only gets a 1* rating but we only need it to look for files and delete created images once we're done with them.
Next, connect your watch to your PC via the charging dock and a suitable USB cable. Now comes the technical stuff which I hope I have understood correctly...
1) Enable developer mode on your Zen watch. You do this by going to settings/about and tapping on the version number 7 times. This should enable the developer options, one of which should be to enable USB debugging (I can't tell exactly where this option is as my watch is running Asteroid OS, but it should be in there somewhere).
2) Extract the ADB tools to a known folder. Open a command prompt in that folder. Type the command "Fastboot oem unlock". This should unlock the bootloader on your watch.
3) Install and run KingRoot, this will root your watch granting you access to all the files on it. Again, this step is done at your own risk, I did it with mine and it worked perfectly, but it would be remiss of me to not give a warning at least. It takes a little while to complete so be patient.
4) Open ADB Explorer and hopefully your watch will be listed in the left-hand panel in the devices list. If it is, click on it and then click the browse button, this should display all of the accessible directories. In my case I see "Internal storage" and "Root", open "Root".
5) At this point we are looking for a folder that contains all of the partitions listed by name. On my watch it is in /dev/disk/by-partlabel, but again, I'm running Asteroid OS. Another possibility is /dev/block/platform/dw_mmc/by-name, but have a browse around the dev folder and subfolders, somewhere in there should be folder with lots of files, some named "boot" "recovery" and "system". Make a note of the path to these files.
6) In the command prompt type "ADB shell", the cursor should change to a # symbol (the first time you do this, type "mkdir images", this will create an images folder on your watch that'll just make things a little easier to navigate in the next steps, you only have to run this command once).
7) Type "dd if=/dev/disk/by-partlabel/boot of=/images/boot.img" but change the "/dev/disk/by-partlabel/boot" to match the path that you found on your watch earlier. If successful this will create a "boot.img" file in the /images/ directory. This can take a while depending on the size of the partition, just give it some time and it will eventually go back to the # prompt (boot and recovery are about 16mb, system is about 500mb so takes longer).
8) Type "Exit" which should return you to a normal command prompt. Now type "ADB pull /images/boot.img", this will copy the boot.img file to your PC (into the same folder as the ADB command file).
9) Use the ADB Explorer program to go to the /images/ folder on your watch and delete the boot.img file, it'll just free up space for more images.
10) Repeat steps 6-9 for the "recovery" and "system" partitions, naming the created image files recovery.img and system.img respectively. Don't forget to delete them off your watch after you have copied them to your PC as the system one takes up quite a bit of space.
11) Take the three image files (boot.img, recovery.img and system.img) and upload them to a sharing site of your choice, then let me know the links to them.
I have tested the above steps with my Zenwatch and have successfully extracted and then re-flashed the images. With luck, and the images you produce, this will allow me to re-flash my watch back to factory standard, then I'll see if there's somewhere where I can host them permanently for anyone else that may need them, as I suspect that I am not the only one looking for them.
Fingers crossed!

Hi!
I got problems with ROOTing.
Tried Kingroot, kingoroot - failed at exploiting. Also looked for TWRP, but all links dead.
ED: Failed means that process went to the end without results.

Yeah I've not been able to find TWRP anywhere either. It's gone midnight now and I'm turning in but I'll see what I can find tomorrow. Bear with me, we're almost there.

Just to check, have you done these steps?
On your watch, head to Menu->Settings->About and tap on Build number for 7-8 times until it says you are a developer. When it does, the developer menu should be unlocked on your watch.
Head to Menu->Settings->Developer options and enable ADB debugging. Without this, your computer will not be able to communicate with your watch.

Yeah sure. I also went to the fastboot mode by swiping from right top corner to left bottom at boot, or sth like that and enabled bootloader by oem unlock. Kingroot has problem with rooting because device is unsupported. It tries many root strategies but all of them are unsuccessfull. It's Marshmallow 6.0.1 - m1d65s build.

We could try Kingo Root, an ironically close name to the other app, but beggars can't be choosers at the moment.
Kingo Root, the king root android app for free.
Kingo Root is #1 one click root solution so easy to use. Take your android phone by your control! You will love this feeling - the freedom.
www.kingoapp.com
I tried it on my watch and phone but they're already rooted so the process didn't succeed (obviously), but it could be worth a try.

As I mentioned before I tried both with no success.

Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.

As I mentioned before I tried both with no success.
Click to expand...
Click to collapse
Ah, that's my bad, I misread your reply, I didn't realise that you had already tried that one.
Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.
Click to expand...
Click to collapse
Damn man, that is exceedingly generous of you! If you're sure that you're happy to do that then I am more than willing to cover the cost of postage. I'll PM you my details and we can get something arranged, you are an absolute legend sir.

Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.

helloworld1337 said:
Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.
Click to expand...
Click to collapse
I absolutely will do that, and thank you again, in these days of doom and gloom you have absolutely rekindled my faith in humanity .

For anyone following this thread, the stock firmware files are now available HERE.

Howdy! Nice to see you done the work
BR

helloworld1337 said:
Howdy! Nice to see you done the work
BR
Click to expand...
Click to collapse
Hi BR.
Yup, I eventually managed to work out a somewhat unconventional way to access the storage on the watch, something which I would not have been able to do without your generous donation. I also apologise for not letting you know that it arrived safely, that was an oversight on my part I think caused in part by the dejection that set in from repeatedly failing to root the damn thing .
However, between us we have succeeded in creating the firmware files, and are now able to offer them up to anyone that needs them. I'd call that a job well done .

Question is it possible to backup my phone with my current issue?

i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone

testask123 said:
i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone
Click to expand...
Click to collapse
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.

TechnoSparks said:
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.
Click to expand...
Click to collapse
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?

testask123 said:
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?
Click to expand...
Click to collapse
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?

TechnoSparks said:
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?
Click to expand...
Click to collapse
bootloader is not unlocked

testask123 said:
bootloader is not unlocked
Click to expand...
Click to collapse
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
edit: also because i totally forgot that unlocking the BL will definitely wipe the device, which defeats the purpose of this thread!

TechnoSparks said:
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
Click to expand...
Click to collapse
is there no trustworthy program that could back it up?

testask123 said:
is there no trustworthy program that could back it up?
Click to expand...
Click to collapse
With what i knew so far with [AOSP] Android, no, because there needs to be a user confirmation on the screen. I suppose maybe Xiaomi have some proper backup tools? (I guess)

Oh yeah, maybe an external display could work. Please wait while I try to gather some limited information

After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?

Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
Could you go into details as to how to modify boot.img to enable adb?
I tried searching a bit but nothing came up

It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.

Renate said:
It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.
Click to expand...
Click to collapse
Ahhh I see , but why boot.img? It's rather difficult to modify for you gotta unpack ramdisk and all? ( I tried doing this long time ago but got stuck on how to repack properly x: )
System.img / vendor.img should be better targets for u can unsparse them ( make rw ) on PC and easily edit .prop files
It's a rly good idea

It's easier to pack something if you never unpack it.
imgutil.exe in my sig lets you modify boot images without taking it all apart.
Warning: Android moves on and many busy bees are working to make our lives more difficult.
If you have problem with imgutil.exe contact me about it.
Code:
C:\>imgutil.exe /v /x boot.img prop.default
C:\>my-fave-editor.exe prop.default
C:\>imgutil.exe /v /r boot.img prop.default
Just don't use some ignorant Windows editor like "Notepad" that uses \r\n.
I like Notepad++.
Also, with a boot image you can try booting it without flashing it.

TechnoSparks said:
After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?
Click to expand...
Click to collapse
it's hard to tell, maybe i should try to see if i can pull it of, but don't know the exact position of the usb setting in the dropmenu.
if someone could provide some screenshot, it might give me an idea where to tap.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
i remember turning on wifi debugging, but dont know if that's still the case or even useful

testask123 said:
i remember turning on wifi debugging, but dont know if that's still the case or even useful
Click to expand...
Click to collapse
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)

Renate said:
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)
Click to expand...
Click to collapse
the ip from the phone?
sorry i'm not so knowledgeable about these things and wanted to make sure

{
"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"
}
Yeah, the IP of your phone.
If you're on your own router you can log in and see if your phone is there and what IP.
Now you know that my cheap Walmart tablet is on (local) IP 192.168.1.4