Hello, I bought be Z80 Smartwatch. I made some mistake and broke firmware. Somebody, who has this watch, could you upload firmware for them. I will be real grateful.
And how do you think will it be created? This watch does neither have USB connector, nor TF-Card slot.
gloover said:
And how do you think will it be created? This watch does neither have USB connector, nor TF-Card slot.
Click to expand...
Click to collapse
It is easy, you need just flash tool. It has usb connector.
finally anyone would like to share ? thanks.in advance
vlad12345611 said:
It is easy, you need just flash tool. It has usb connector.
Click to expand...
Click to collapse
I opened the watch - there is definitely no usb port or card slot (seen neither outside nor inside the watch). You also cannot switch "bluetooth-debugging" in the develepors menue. Its impossible to establish an adb connection and make a firmware dump.
BTW: flash tool needs a physical connection (usb) to make his job.
gloover said:
I opened the watch - there is definitely no usb port or card slot (seen neither outside nor inside the watch). You also cannot switch "bluetooth-debugging" in the develepors menue. Its impossible to establish an adb connection and make a firmware dump.
BTW: flash tool needs a physical connection (usb) to make his job.
Click to expand...
Click to collapse
Yep, but you could use standard cable for charging as usb cable. It works fine for charging and flashing
vlad12345611 said:
Yep, but you could use standard cable for charging as usb cable. It works fine for charging and flashing
Click to expand...
Click to collapse
Dude, you've right! I thought this is the charging adapter only, thx for the info. I've to install some drivers, then I'l try to dump the rom this week.
Any success at installing watch faces ?
gloover said:
Dude, you've right! I thought this is the charging adapter only, thx for the info. I've to install some drivers, then I'l try to dump the rom this week.
Click to expand...
Click to collapse
Nice! You will save me, becouse my watch has still broken(( I am waiting for firmware, thanks
vlad12345611 said:
Nice! You will save me, becouse my watch has still broken(( I am waiting for firmware, thanks
Click to expand...
Click to collapse
I've tried to make a dump yesterday, it seems to be harder then Ithought. MTK Droid Tools doesnt recognize the watch, even though all necessary drivers are correctly installed (have tried on severals systems with Mediatek ADB driver and also with universal ADB driver + PDA-Net). It seems to have a problem detecting MTK6580 chipset.
The adb console works fine, so its helpfull to make an app and data backup, but not the whole stock rom.
Any other idea how to dump a whole stock ROM except of rooting the watch and using MTK Droid Tools?
gloover said:
I've tried to make a dump yesterday, it seems to be harder then Ithought. MTK Droid Tools doesnt recognize the watch, even though all necessary drivers are correctly installed (have tried on severals systems with Mediatek ADB driver and also with universal ADB driver + PDA-Net). It seems to have a problem detecting MTK6580 chipset.
The adb console works fine, so its helpfull to make an app and data backup, but not the whole stock rom.
Any other idea how to dump a whole stock ROM except of rooting the watch and using MTK Droid Tools?
Click to expand...
Click to collapse
It is faster to make root and use MTK Droid Tools. I rooted my Z80 with KingRoot and it was fine.
vlad12345611 said:
It is faster to make root and use MTK Droid Tools. I rooted my Z80 with KingRoot and it was fine.
Click to expand...
Click to collapse
How did you brick you watch? The reason for this is not the rooting, is it? I want to avaid the rooting.
BTW: MTK droid tools should detect the device even if its not rooted. Its realy seems to have some problems with droid tools and 6580 chipset. Could you recognized your watch by Droid Tools before its bricks?
gloover said:
How did you brick you watch? The reason for this is not the rooting, is it? I want to avaid the rooting.
BTW: MTK droid tools should detect the device even if its not rooted. Its realy seems to have some problems with droid tools and 6580 chipset. Could you recognized your watch by Droid Tools before its bricks?
Click to expand...
Click to collapse
I don't try. My watch was bricked becouse I changed system apps and tried to change watch faces. After rooting everything was fine.
gloover said:
How did you brick you watch? The reason for this is not the rooting, is it? I want to avaid the rooting.
BTW: MTK droid tools should detect the device even if its not rooted. Its realy seems to have some problems with droid tools and 6580 chipset. Could you recognized your watch by Droid Tools before its bricks?
Click to expand...
Click to collapse
Actually, main point was that, I set new bootlogo and after that watch just showed bootlogo and without loading. So, then I tried to flash them, using firmware from another, similar Smartwatch, but it was not successful(
So, now I've rooted the watch, but MTK Droid Tools cannot detect it. For making a dump witch flash tool I need a working scatter file. That is wheremy knowledge stops. Any suggestion how to make a dump in easier way. As I already said, MTK Droid Tools isnt working.
gloover said:
So, now I've rooted the watch, but MTK Droid Tools cannot detect it. For making a dump witch flash tool I need a working scatter file. That is wheremy knowledge stops. Any suggestion how to make a dump in easier way. As I already said, MTK Droid Tools isnt working.
Click to expand...
Click to collapse
Have you try to ftake it from another similar watch with the same processors?
There is instructions, how to make scatter file
https://androidmtk.com/create-scatter-file-for-mtk-devices
https://forum.hovatek.com/thread-87.html
You could also try to google "how to make scatter MTK 6580" and you will find more links, video and instructions.
rose5hill said:
finally anyone would like to share ? thanks.in advance
Click to expand...
Click to collapse
gloover said:
So, now I've rooted the watch, but MTK Droid Tools cannot detect it. For making a dump witch flash tool I need a working scatter file. That is wheremy knowledge stops. Any suggestion how to make a dump in easier way. As I already said, MTK Droid Tools isnt working.
Click to expand...
Click to collapse
Hey, how is going with firmware?
MT6580_Android_scatter.txt
https://drive.google.com/open?id=0Bwl4RzMY5XyWcnduU0ZkUFVPS2s
This is supposed to be a proper scatter for this device.
Unfortunately what MTK Droid Tools generates is a total trash.
Therefore this one is based on a scatter file from another 6580 device with partitions adjusted according to /proc/partinfo.
For me SPFT doesn't want to start a readback indicating a 2005 error.
May be someone else will be more lucky.
---------- Post added at 12:36 PM ---------- Previous post was at 12:24 PM ----------
gloover said:
So, now I've rooted the watch, but MTK Droid Tools cannot detect it. For making a dump witch flash tool I need a working scatter file. That is wheremy knowledge stops. Any suggestion how to make a dump in easier way. As I already said, MTK Droid Tools isnt working.
Click to expand...
Click to collapse
MTK Droid Tools indeed detect the watch. But one needs to update bundled adb to more recent (but not latest) version. Version 1.0.32 from platform-tools 22.0 seems to be the last one to work.
But as I've already said the generated scatter file has very little to do with reality. And it is unlikely that backup functionality would work.
@ Vertigo: the scatter file you've linked is for "zeblaze blitz" - it has a "really" android 5.1 not the trash like those installed on Z80 and it also have another partition system. I've already tried to adapt this scatter file some days ago, using the partition system of Z80 - without any success. The adapted scatter file could not be read by Flashtool 5.15.16 Here is what I receives with adb:
Code:
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00001800 "proinfo"
emmc_p2: 00001c00 00002800 "nvram"
emmc_p3: 00004400 00005000 "protect1"
emmc_p4: 00009400 00005000 "protect2"
emmc_p5: 0000e400 00000200 "seccfg"
emmc_p6: 0000e600 00000300 "lk"
emmc_p7: 0000e900 00008000 "boot"
emmc_p8: 00016900 00008000 "recovery"
emmc_p9: 0001e900 00000400 "para"
emmc_p10: 0001ed00 00004000 "logo"
emmc_p11: 00022d00 00005000 "expdb"
emmc_p12: 00027d00 00000800 "frp"
emmc_p13: 00028500 00010000 "nvdata"
emmc_p14: 00038500 00013b00 "metadata"
emmc_p15: 0004c000 00001000 "oemkeystore"
emmc_p16: 0004d000 00003000 "secro"
emmc_p17: 00050000 00004000 "keystore"
emmc_p18: 00054000 00190000 "system"
emmc_p19: 001e4000 00080000 "cache"
emmc_p20: 00264000 004dbc00 "userdata"
emmc_p21: 0073fc00 00008000 "flashinfo"
First crazy thing: the bootloader is not listed, even if it is unlocked in the develepors settings.
Generally, as you can see, the partition offsets deviates from Zeblaze smartwatch scatter file.
Using MTK_Rom_Studio to generate a scatter file from generated firmware.info is also a crap.
I've tried every conceivable possibility and spend nearly 2 weeks of time - now I'm ran out of ideas.
@vlad: how did you root your watch? Running the kingroot.apk on your smartwatch or from your computer connecting the watch?
Sucks that you spent a lot without success(
As I remember, I rooted through kingroot on my laptop
Related
Hello,
My N4 is soft-bricked. Well, hopefully that's all it is.
I want to sideload a ROM onto it, via Mac OS X 10.9.3
I have found plenty of instructions on how to do that with a Mac.
But I can't get ADB or fastboot to see the device.
When I go to the system information on this Mac and looked at the USB devices, I see the Nexus there... along with its serial number, etc. But in Terminal I get a device not found error in ADB and nothing at all in fastboot.
It is my understanding I don't need to install any special drivers on Mac for it to detect the device. Is that correct?
If not, does any one have any suggestions on how I might get this device connected properly?
Thank you...
With further research, I have made some progress. I found this: http://stackoverflow.com/a/7169048
It says:
Also, if that does not work, check to see if the device shows up under USB in the System Profiler (included in OS X). If it is showing up there, but not in ADB, try adding the USB Vendor ID of the phone to ~/.android/adb_usb.ini
This file can be created if it does not already exist. The Vendor ID of the Nexus S is 0x18d1. Please make sure the last line of the file is a Vendor ID, do not leave a blank line at the end.
Click to expand...
Click to collapse
After doing that, I can now see my N4 listed. Well, at least it does when I am in recovery mode.
Now I shall see if I can make some progress with pushing a ROM to this thing (I am new to all this, so I'll see how this goes...)
Can you get to the bootloader screen? Only there fastboot will work.
Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk
coolqf said:
Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Thanks. I have a VM on this Mac... so i'll try doing this through that.
AndroidWelcome said:
Thanks. I have a VM on this Mac... so i'll try doing this through that.
Click to expand...
Click to collapse
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3
Thanks
coolqf said:
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3
Click to expand...
Click to collapse
Sorry I never replied. Thank you. I got it sorted. Nice to have my N4 up and running again.
Good day DeV's i am making this thread to request stock dump of bootloader for our grand 2
microchip88 said:
Good day DeV's i am making this thread to request stock dump of bootloader for our grand 2
Click to expand...
Click to collapse
you dont have this device? if you have you can get it on your own..
My device is brick thats why im asking developers here to help me get bootloader dump to create debrick file for my grand 2.
Sent from my Nexus 7 using XDA Premium 4 mobile app
microchip88 said:
Good day DeV's i am making this thread to request stock dump of bootloader for our grand 2
Click to expand...
Click to collapse
SM-G7102( Grand 2) SDCARD Un-Bricker Files
http://www.4shared.com/file/xaasWKQc...02XXUANE2.html
This file is ready
It is through the program ATF
Copy it to your memory card and try
drrami75 said:
SM-G7102( Grand 2) SDCARD Un-Bricker Files
http://www.4shared.com/file/xaasWKQc...02XXUANE2.html
This file is ready
It is through the program ATF
Copy it to your memory card and try
Click to expand...
Click to collapse
man your link is not working.....
junaid992 said:
man your link is not working.....
Click to expand...
Click to collapse
this link:
http://www.4shared.com/file/xaasWKQcce/SM-G7102_43_8GB_G7102XXUANE2.html
Now its working....btw how do I use this file plz elaborate stepwise....
Sent from my CT-1 using xda premium
junaid992 said:
Now its working....btw how do I use this file plz elaborate stepwise....
Sent from my CT-1 using xda premium
Click to expand...
Click to collapse
Atf Side:
- only select SDC,
- Insert micro sd (just formatted fat 32), in M.sd reader of BIG atf or adaptor
- select you .img file
- click in "write" button, wait and when ready get out,
-------------------------------
Phone side:
1) insert Micro sd in slot of Samsung, wait a little, (5 min.s),
2) connect any Uart Cable of BOX samsung or if have the "JIG UNBRICK" in Usb port of the Samsung and waith that enter in D.Mode,
3) Download and insert Full Flash pack whith Single file, Csc.. Phone..Pda + Mx-Pit file, (this is important), in Odin or if you want, can use any Samsung BOX, (i use Odin), wait when is ready and click START,
4) Now in you phone will be write Full Fw and will be ready for use,
ISSUES:
a) in D.Mode you have Product NULL, any model showing,
b) phone know message like: "efs impossible mount itc.."
c) after too much time phone Not enter in D.Mode whith JIG UNBRICK or UART CABLE,
SOLUTION:
a1) can be that you eMMc is damaged and have need replace it, this method work only if is Sw problem no work whith HW problem, replace you eMMc,
b1) easy solve this, search and Finf FULL EFS for you model and write it whith Odin or Box Samsung that support it, (i use Odin), wait end process and you phone is alive and working,
c1) in this case, ceck: 1) if you have download and used correct sdc .img file,
2) if you have used right "size" of micro sd card" ad file .img is not wrote for half, remember that for I9300/N7100/I9500 you can use also 2gb of Msc, (for sure use 4gb), 3) reformat Msc and write other time sdc .img file and repeat full procedure, 4) to be shure that UART cable or JIG Unbrick is working, Test whith other phone, from power off connect Uart or JIG and wait 3/5 sec.s if phone goes in D.Mode, if NO, then change Uart cable or Repair Jig, never you phone damaged can enter in D.Mode if you use wrong Uart Cable or Jig Unbrick not working!!!!
If you device NOT respond for nothingh after all these steps, please ceck you HW problem, short circuit, Power ic, Usb connector itc... shure you device have other type of problems....
Best regards
How can I unlocked the bootloader so that I can installed custom rom.
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Here are the photos
njking25 said:
Here are the photos
Click to expand...
Click to collapse
njking25 said:
So after flashing the new lollipop update I found myself stuck in a bootloop unable to get into the android operating system at all. I used flashboot and the intel flash tool to try and restore to an older ROM. It forze at 91% with an "error:unable to mount /data" I then used the root tool to try and sideload and install the update.zip from adb shell. No luck. When I rebooted I got to a strange efi menu. Looked around, and it gives me the option to install with with windows?
Anyone have any ideas. I'm waiting for radio shack to open, its the only local place that sells USB otg cables locally.
Click to expand...
Click to collapse
That is something interesting. It is asking which os to boot to, not install.
I'd like to know how you got into the bios? I am looking for a way to install Linux....
Sent from my YOGA Tablet 2-1050F using Tapatalk
njking25 said:
Here are the photos
Click to expand...
Click to collapse
Did you get this figured out?
I can see "fast boot" enabled. Have You tried to switch it off? any other menu is displayed?
Have You tried to "power+vol down" on it?
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
zach181 said:
I've tried a few ways to get into the BIOS shown... all failed.
Maybe the only way to trigger the BIOS to show is to fully wipe/format the internal storage so the BIOS can't pick up droidboot or anything else. Quite risky though if it isn't the way.
I'm in no way telling anyone to do this and I have not tried it myself. I'd be curious to hear from any advanced users if they have ever completely wiped the internal memory and what options would be available to restore if things did go wrong.
Click to expand...
Click to collapse
This guy seems to have stumbled on it also. I flashed the stock kk firmware and I am trying to do it but can't get Lollipop update to work. But it won't boot after it fails so I am reflashing KK again.
http://forum.xda-developers.com/showpost.php?p=60490907&postcount=578
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
zach181 said:
Thanks for the link workdowg,
I'm still trying to work out how they did it. Could do with a step by step and whatever files needed uploaded and linked to. Also the bit about not using windows startup programs.
Click to expand...
Click to collapse
If you try it do let me know. I need to get into the bios to get started on a dual boot to Linux on this bad boy...
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
So... conclusion. we have to damage firmware to boot efi...
If we could swap img file before upload to tab (during this 25 second wait) we could make windows installation possible. Am i right?
zach181 said:
I will let you know.
I just asked for the OP to clarify a few things before I go ahead. I may try Linux first with Windows 8/10 being the final install.
Click to expand...
Click to collapse
@social-design-concepts suggested we should try to change the boot order using efibootmgr. I've been communicating with him. Here is the post in the Venue thread... http://forum.xda-developers.com/show...postcount=2083
Links giving 404
zach181 said:
Links giving 404
Click to expand...
Click to collapse
here it is again... http://forum.xda-developers.com/showpost.php?p=61108700&postcount=2083 it got truncated.
Thanks workdowg.
It seems it's not as clear cut as first thought. Mind you, I didn't expect it to be. I did try a HP keyboard with OTG in Android and that got picked up ok (No lights on keyboard)
I'm a bit in the same mind as Social-Design. I'd rather have a definite way to restore Android from a totally blank internal drive before I have a go. Just up to page 214 in the thread so it may be covered later.
UEFI soft brick?
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Yosha1 said:
Hi guys,
I accidentely tried to use the firmware on my 1050 as described in this thread. I can indeed load the UEFI BIOS with all its settings (even though most don't do anything). But unfortunately, I cannot load any OS. I always get the error "EFI Harddrive failed" - meaning it cannot boot fomr hardrive.
I have used an externally powered USB-HUB with mouse, keyboard and USB-Stick and connected to the 1050 via OTG-cable. If the stick is bootabnle with GPT x64 then it will boot from that stick. All 64bit windows versions that I tried failed to install with "ACPI_BIOS_ERROR". 32bit windows would not start, because the GPT is 32bit and the BIOS does not recognise it.
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Unfortunately, I am running a bit out of ideas of what to do in order to get a normal system (or firmware) back. ADB-drivers obviously don't work (the Intel SoC driver is installed as well), so I cannot use the Phone Flash Tool.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You can get it to boot from USB? Get someone with to use tethered twrp and get a backup of the esp and fastboot partitions.
I have 2 things you can try if the goal is getting back to booting stock Android.
Yosha1 said:
The best success I had so far was to copy a ISO from android-x86 on the usb stick. It will boot in live-mode from the USB. Not so suprisignly, mouse and keyboard are working, touch isn't. WiFI is working and the SD card is detected. I tried to install this version of android on the harddrive which works, but it installs the EFI GRUB bootloader which is not recognised by the BIOS.
I can also access the UEFI shell.
Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
Have You tried booting any x64 linux iso from flash drive?
dreamnewbie said:
Have You tried booting any x64 linux iso from flash drive?
Click to expand...
Click to collapse
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Yosha1 said:
Thank you for your fast reply.
I just tried that with an Ubuntu Desktop Distro. It boots up from teh USB drive, keyboard and mouse are present. Wifi, sound, touch don't work but I can see the internal Harddrive and the sdcard in the file exsplorer.
Click to expand...
Click to collapse
extract and dd this to a usb drive and see if it is able to boot it View attachment 3415895 if it successfully boots replace the fastboot.img thats on the thumbrive with one for your devices and see if it boots. if your fastboot.img is named droidboot.img rename it to fastboot.img.
If you can successfully get your devices droidboot/fastboot.img to load you can then disconnect the usb-otg cable and reconnect it to your PC and use the phone flash tools to restore your device completely.
Hello everyone! Thank you for taking the time to read my post, this is my first post, so please forgive me if I make any mistakes.
The PreLoader Driver for me is not working, at all. I run Windows 8.1.
Now, I've read to install it this way and that, and if you have a yellow exclamation point under device manager, I should be ok.
To run flashtools to make a backup of my firmware, I need a scatter file and the software doesn't allow you to do much of anything unless you select this file.
Fine, so I need to make my own scatter file, so I have the MTK Droid tools to make my scatter file.
Because my drivers don't work, I can't my scatter file and I cannot continue forward with this.
MTK Modem, Debug and Port drivers are all installed and fine and working correctly.
The Preloader and DA USB VCOM port drivers do not work for me.
Can anyone offer some kind of guidance? Suggestions? Driver issues you had and got working?
If I can get my firmware backed up I'll be more than happy to share and try to help tweak and such!
Thanks again for your help!
Anyone? Someone?
Please does anyone have the stock ROM file for apro q18 smart watch
Same problems too
Jobe5150 said:
Hello everyone! Thank you for taking the time to read my post, this is my first post, so please forgive me if I make any mistakes.
The PreLoader Driver for me is not working, at all. I run Windows 8.1.
Now, I've read to install it this way and that, and if you have a yellow exclamation point under device manager, I should be ok.
To run flashtools to make a backup of my firmware, I need a scatter file and the software doesn't allow you to do much of anything unless you select this file.
Fine, so I need to make my own scatter file, so I have the MTK Droid tools to make my scatter file.
Because my drivers don't work, I can't my scatter file and I cannot continue forward with this.
MTK Modem, Debug and Port drivers are all installed and fine and working correctly.
The Preloader and DA USB VCOM port drivers do not work for me.
Can anyone offer some kind of guidance? Suggestions? Driver issues you had and got working?
If I can get my firmware backed up I'll be more than happy to share and try to help tweak and such!
Thanks again for your help!
Click to expand...
Click to collapse
I'm having the same issues too
ROM / Firmware/ Brick Recovery for 7" Android Head Unit AC8227l YT9217 YT9218 1/16GB
Thanks everyone who contributed in my effort to fix my bricked device. Here is all that I have found useful in successfully reviving my device.
The files shared here are the ones that worked on my unit (see specs and pictures below) If your device is different, it may or may not work.
If the device has dedicated radio chip inside, the Firmware number will show as YT9218, if no radio chip, then it will show as YT9217
Note: if your device is not bricked, Make a full backup before trying another firmware.
I hope it helps. (donations are always welcome )
Memory dump:
firmware 20181222 HiFi: (Link) (thanks mazepa2000) (May 2019 update below)
Rooted TWRP firmware 20190523 HiFi: (Link)
Preloader (Boot_1) from other Similar Firmwares: (Link) <- Click again if it doesn't lead to the relevant post.
Download the one similar to your device's version.
Firmware via flash tool: Rooted TWRP 20190523 (Link) Thanks Maxkir
(You may need to remap side touch buttons in Factory settings (code 8888) -> Touch settings -> Click start -> Name of the button -> The button itself ->Repeat for all the buttons -> close -> ok).
Firmware for YT9213 Device: (Link) (Thanks pajurpl)
Update / Upgrade Files USB flash drive:
Firmware 20190522 HiFi: (Link) (Thanks foxgiggle , iSevenAuto)
Firmware 20190906: (Link)
MCU 3.1 (Link)(Thanks foxgiggle )
MCU 2.8 (Link) (Thanks lemmon and foxgiggle)
I hope it helps. (donations are always welcome )
Memory Dump Procedure via flashtool:
(Memory dump is only needed if you need full recovery from a backup. Otherwise you may only need to do the next part.)
Download and install MTK drivers. (Link)
Load scatter file and preloader (Link) in spflashtool. Press Ctrl Alt V , then go to Window and select "write memory". In file path select "user", in begin address put 0x0, In Region select the partition named "EMMC_USER". Hit Write memory. After that plug in the usb cable (connected to usb1 port). If the device is not detected, you need to power it on. If still not detected then you might need to short the two test points (see picture) (without power this time) and then plug in the usb cable. Remove the short when write process starts. Check if the issue is fixed. If its not fixed, then do the same to write boot2 and boot1 partitions as well. You may need to download Boot_1 specific to your original firmware from the link above.
Uploading Firmware (full or parts) via flashtool:
If you are uploading the firmware available in parts, you only need to upload "BOOTIMG" and "ANDROID" (SYSTEM).
You may also need to flash "RECOVERY". Remember to uncheck the preloader. Here is a nice instructions file. (Link) (thanks Maxkir)
There is more info and firmwares to chose from at 4pda forum.
Update / Upgrade Procedure via USB flash drive:
Copy the zip file (do not extract) to usb drive or microSD card, (formatted by SD Card Formatter). Connect to usb port 1 or 2. Go to Car Settings, System info. Click Android Upgrade.
--OR--
Extract the zip into a folder named XYAUTOUPG into the flash drive or microSD card, connect to usb port 1 or 2 and then reboot. Upgrade should start automatically. You might need to try with different USB drives or sd cards. For some reason this only works with certain usb and cards.
I hope it helps. (donations are always welcome )
MCU Upgrade Procedure via USB flash drive:
Extract the mcu file into flash drive or microSD card. Connect to usb port 1 or 2. Go into system info and update mcu.
Make a Full Backup/Memory Dump:
Open SPFlashtool, Select Memory Test Tab, Select only RAM Test (uncheck the rest), push start, and connect the unit. Save the information appeared, in a text file for later. (Read above "Memory dump procedure" for the usb connection setup).
Now go to ReadBack Tab, Double click on empty space next to tick mark, Select a folder where you want to store the dump file, and Type a name for the dump file you are going to creat, (ie. Boot_1, Boot_2, USER). Click Save. In next window "Readback block start address", select the region you want to make backup of (ie. EMMC_BOOT_1, EMMC_BOOT_2, EMMC_USER).
Start address is 0x0000000000000000
Length copy and paste from the text file you created earlier.
typically for Boot_1 and 2 the length is 0x0000000000400000
and for USER (16GB models) the length is 0x00000003a8000000
Click OK.
Now click on Readback and then connect the unit via usb cable. and Read process will start.
Do the same to make backup of all three partions. USER will take long time because its the largest partition.
RDS FM Radio:
Radio app with fixed RDS, channel names on buttons and HiFi: (Link) (thanks sjguk)
Copy to FMRadio directory /system/priv-app/FMRadio, rename to FMRadio.apk and change permission 764. (or 755 ?).
Channel name Editor: (Link) (thanks mclaught)
install as normal. You may need to install GalaPublicResources. Click top right dots.
I hope it helps. (donations are always welcome )
Multi Window Mode:
Go to root folder, look for build.prop. Open in text editor. Change the line ro.build.type=user to ro.build.type=userdebug.
If no such line is there, then simply add the line at the end. Save and exit. Go to Android settings, Developer options, look for multi window mode and enable it. Swipe down from the top of the window, Click on recent apps tile. You'll see the new multi window option there.
Subwoofer output Pin:
The default AUX_out pins are for mid range audio and is controlled by Mid slider in the mixer. The subwoofer output is on another pin (See Picture).
it is easy to remove one of the AUX_out pin and install it at the Sub output. this pin is controlled by Subw slider in the audio mixer.
Launchers UI1, UI2, UI4, UI5 (Link) (Thanks Maxkir)
Boot animation: (Resolution is 1024x600)
eg. (Link)
The animation preview didn't work for me, but I installed it anyway and it worked fine.
OBD Dongle Bluetooth Setting:
Open Bluetooth app, Click on settings, tap on the pin code "0000" and type in "1234" instead. Save settings.
Now search and connect the OBD dongle normally.
I hope it helps. (donations are always welcome )
Unit Specs:
motherboard marking YT9217 VER1.5 XY AUTO also 9218 VER2.4 XY AUTO near the antenna
Model no 8227L_demo android 8.1
Android YT9217C_00005_V003_20191402_HIFI
Kernel 3.18.22
DDR 1GB FLASH 16GB
CPU A7 1.3GHzx4
Amplifier AC7315 mos bile duct 45Wx4
AutoChip ARM AC8227L
Mediatek MT6323LGA
Kingston EMMC 16G
Im looking for the same ROM. Let me know if you find some info. Also Im looking for the AirRadio App. so I can use a Launcher.
Thanks
viktorsaari said:
the link takes me to the main page. and then its like finding needle in a haystack.
Click to expand...
Click to collapse
All relevant info about ROMs and flashing you can find in top header of this russian forum.
Look at the spoilers in the gray header layer and use Google translate to understand what is written there.
There are 3 ROM versions for the 8227L based head units. I downloaded and installed the oldest of the 3 (rooted and TWRP IMG included). Copy all files from the RAR to a flashdrive in root folder.
Turn off the head unit.
Connect the flashdrive to USB 1 slot of the head unit.
Turn on the the head unit.
The install process starts immediately after turning on.
It takes about 10 minutes.
When install process is ready, turn off the head unit.
Detach the flashdrive.
Turn on the head unit and it will boot with factory settings like a new device....
Note that there are also ROMs for flashing wit MTC flash tool downloadable.
But the versions for installing from USB sticks ( po russki - dla flashky) are more comfortable to install and I don't own a Windows pc. So this variant was my favorite method...
Regards and good luck...
Edit: if your unRAR program asks for a password for unpacking the RAR file, then use Eazy unRAR app from Playstore on your Android device - it ignores password lock in RAR file ...
Edit2: the 5th gray spoiler in the top header of the Russian forum hosts the links to the ROM RAR files...
The USB flash drive method didn't work for me, Device doesn't detect USB while booting up. I tried everything, connecting the test points, pushing reset button etc. to no avail.
SP flash tool does seem to work, I have tried uploading several available roms, only these three uploaded successfully,
full_8227L_demo-userdebug 6.0 MRA58K 1534513814 test-keys
Заводская прошивка под флештул от 09.11.2018 UI1 с переводом
20181224 TWRP ROOT перевод и эквалайзер от ноябрьской
but didn't turn on the device. Device turns on but I get a black (backlit) screen. What else is there to try?
bitstra said:
All relevant info about ROMs and flashing you can find in top header of this russian forum.
Look at the spoilers in the gray header layer and use Google translate to understand what is written there.
There are 3 ROM versions for the 8227L based head units. I downloaded and installed the oldest of the 3 (rooted and TWRP IMG included). Copy all files from the RAR to a flashdrive in root folder.
Turn off the head unit.
Connect the flashdrive to USB 1 slot of the head unit.
Turn on the the head unit.
The install process starts immediately after turning on.
It takes about 10 minutes.
When install process is ready, turn off the head unit.
Detach the flashdrive.
Turn on the head unit and it will boot with factory settings like a new device....
Note that there are also ROMs for flashing wit MTC flash tool downloadable.
But the versions for installing from USB sticks ( po russki - dla flashky) are more comfortable to install and I don't own a Windows pc. So this variant was my favorite method...
Regards and good luck...
Edit: if your unRAR program asks for a password for unpacking the RAR file, then use Eazy unRAR app from Playstore on your Android device - it ignores password lock in RAR file ...
Edit2: the 5th gray spoiler in the top header of the Russian forum hosts the links to the ROM RAR files...
Click to expand...
Click to collapse
No idea, what else you can try
If you can connect a PC to headunit and flashed a ROM with TWRP, may be you can use adb reboot recovery and clear data and cache via TWRP?
Hope you find a solution to boot your HU...
viktorsaari said:
The USB flash drive method didn't work for me, Device doesn't detect USB while booting up. I tried everything, connecting the test points, pushing reset button etc. to no avail.
SP flash tool does seem to work, I have tried uploading several available roms, only these three uploaded successfully,
full_8227L_demo-userdebug 6.0 MRA58K 1534513814 test-keys
Заводская прошивка под флештул от 09.11.2018 UI1 с переводом
20181224 TWRP ROOT перевод и эквалайзер от ноябрьской
but didn't turn on the device. Device turns on but I get a black (backlit) screen. What else is there to try?
Click to expand...
Click to collapse
No luck with adb either.
seems like my only option is if I could get the exact ROM for this device and flash it. The seller was less than helpful, so Aliexpress refunded me in full.
bitstra said:
No idea, what else you can try
If you can connect a PC to headunit and flashed a ROM with TWRP, may be you can use adb reboot recovery and clear data and cache via TWRP?
Hope you find a solution to boot your HU...
Click to expand...
Click to collapse
Received firmware files from seller, but its probably the update files, not the complete firmware. Unable to flash it via sp flash tool. (copy and paste the whole link until the .zip part)
http://download.seicane.com/doc/80/H5 Android 8.1 updated file.zip
Any ideas ???? my device is a brick at the moment, and doesn't recognise usb flash drive for updating.
Fixed.:victory:
Check the first post for detail.
So you flashed via sd card or flashtool?
viktorsaari said:
Fixed.:victory:
Click to expand...
Click to collapse
Hi How did you manage to fix it I have the same problem?
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
viktorsaari said:
Received firmware files from seller, but its probably the update files, not the complete firmware.
http://download.seicane.com/doc/80/H5 Android 8.1 updated file.zip
Any ideas ???? my device is a brick at the moment, and doesn't recognise usb flash drive for updating.
Click to expand...
Click to collapse
The link is dead!
SP Flash tool.
ric69 said:
So you flashed via sd card or flashtool?
Click to expand...
Click to collapse
Thanks but flashtool is impossible to me as I don't have any USB recognition on my pc
Please see the original post, I added the things I did to fix it.
the link is not dead, copy and paste complete until the .zip part
anyway this zip file didn't help.
Check the first post for helpful material.
coffer said:
Hi How did you manage to fix it I have the same problem?
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
The link is dead!
Click to expand...
Click to collapse
ric69 said:
Thanks but flashtool is impossible to me as I don't have any USB recognition on my pc
Click to expand...
Click to collapse
Did you get your connection to the PC yet?
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
viktorsaari said:
Please see the original post, I added the things I did to fix it.
the link is not dead, copy and paste complete until the .zip part
anyway this zip file didn't help.
Check the first post for helpful material.
Click to expand...
Click to collapse
Thanks for that, wow the memory dump is massive more than 4Gb! Did you use format and download or just download in the Flash tool? Do you know the files the scatter file took from the memory dump? So, you didn't use any files from the first download where you took the scatter file from? I'm still having a problem connecting to my PC may have to use the hardware forced (testpoint) method!
You need usb male to male cable, attach it to usb1 on the device. but not yet connect to pc. Run the sp flash tool. and select the correct scatter file. Then run which ever function you need. after that connect the usb cable to pc while connecting these two test points (picture) with a small piece of wire to each other. After it is recognised and operation starts, you can release the jumper wire.
ric69 said:
Thanks but flashtool is impossible to me as I don't have any USB recognition on my pc
Click to expand...
Click to collapse
viktorsaari said:
You need usb male to male cable, attach it to usb1 on the device. but not yet connect to pc. Run the sp flash tool. and select the correct scatter file. Then run which ever function you need. after that connect the usb cable to pc while connecting these two test points (picture) with a small piece of wire to each other. After it is recognised and operation starts, you can release the jumper wire.
View attachment 4769616
Click to expand...
Click to collapse
Thanks, when I use the scatter file from the first download and put it with the files in the second download it only picks up the preloader file nothing else?
Hi, Scatter file is only needed to make sp flash tool recognise the partition table on the device. no need to download anything via scatter file. press Ctrl Alt V , then go to Window and select "write memory". Set start address to 0x00 Use this to write Boot_1 , Boot_2 and User, to EMMC_Boot_1, EMMC_Boot_2 and EMMC_User respectivly. thats it.
I hope it helps.
Thanks for that, wow the memory dump is massive more than 4Gb! Did you use format and download or just download in the Flash tool? Do you know the files the scatter file took from the memory dump? So, you didn't use any files from the first download where you took the scatter file from? I'm still having a problem connecting to my PC may have to use the hardware forced (testpoint) method!
Click to expand...
Click to collapse
Hi, yes, I fixed it. Check the first post for details.
NicoApple said:
Im looking for the same ROM. Let me know if you find some info. Also Im looking for the AirRadio App. so I can use a Launcher.
Thanks
Click to expand...
Click to collapse
Thanks but for most of us , we don't have any USB recognition to pc (or android devices) there is any sounds when plug
ric69 said:
Thanks but for most of us , we don't have any USB recognition to pc (or android devices) there is any sounds when plug
Click to expand...
Click to collapse
have you tried the test point method yet, I will try it tomorrow or Monday?