Related
Hi folks.
A lotta people damage it´s Motorola TN20 and TN30 GPS by trying to put maps and software inside of it.
I am trying to make these unit to reborn.
I tried to reload firmware but at the process looks like it need to have it´s flash fully formatted and empty because the first part (load WinCE) seems to work, but the second on (load Application) fails.
Can someone give me a tip?
WC
basically my motorola atrix doesn't work any more!!
the bit of the screen which is meant to be used to access the buttons bellow, work as though you are pressing the bottom of the visible screen!!
EVERYTHING is shifted down! if i want to press something, i have to press the area 1cm bellow the location!
I suspect it is cause by me formatting every single folder on the internal storage using clockwork recovery...
i have tried installing the original Rom using RSD, i have tried everything!!!
ANY HELP PLEASE?
the device is a piece of garbage now!
i saw that NO ONE else has reported this issue anywhere on the net!!
it can't be a hardware problem cause it was working before i formatted all of those folders! including the ones with the 3 character names... can't remember the names... but basically i formatted everything...
this is a common problem when you format / partition the internal memory. it screws up your PDS partition, which i hope you backed up. search a little more, there are lots of topics on this in the dev forum and I believe there MAY be a solution but i don't remember.
Just found a couple of threads...
I didn't back it up... does this mean that my Motorola atrix is practically worthless now? :s
Solution
http://forum.xda-developers.com/showthread.php?t=1131649
this apparently is supposed to work... will try it in a bit.
but still, you won't get the original mac address and bluetooth number and the rest...
:/ sad times... there must be someway to acquire the original values?!?!
benedict.s said:
http://forum.xda-developers.com/showthread.php?t=1131649
this apparently is supposed to work... will try it in a bit.
but still, you won't get the original mac address and bluetooth number and the rest...
:/ sad times... there must be someway to acquire the original values?!?!
Click to expand...
Click to collapse
i'm not sure there are, as those values were never meant to be cleared out.
can ask why you decided to format every folder in the memory?
dLo GSR said:
i'm not sure there are, as those values were never meant to be cleared out.
can ask why you decided to format every folder in the memory?
Click to expand...
Click to collapse
Well, if you look in the post i linked to, it is an image that i pushed into the partition...
it's working now at least!
I do have my mac address and IMEI, do you know how i can edit that image file to put my own values in it? i have no clue as to how the image can be edited.... :/
the reason i did that was because i had an HTC HD2 before. it originally comes with windows, and so when you installed Android, it had a horrible process... in that process, the MAGLDR and CWR as they were called, did not erase every folder in the phone's main memory... so i had gotten used to formatting them individually in that phone.. that's why i did it on the Atrix...
also, in the HD2 they were folders not partitions... so basically, i wasn't familiar with the exact core of Motorola android devices...
there must be a way to put in my own hardware details into the PDS image file?
benedict.s said:
Well, if you look in the post i linked to, it is an image that i pushed into the partition...
it's working now at least!
I do have my mac address and IMEI, do you know how i can edit that image file to put my own values in it? i have no clue as to how the image can be edited.... :/
the reason i did that was because i had an HTC HD2 before. it originally comes with windows, and so when you installed Android, it had a horrible process... in that process, the MAGLDR and CWR as they were called, did not erase every folder in the phone's main memory... so i had gotten used to formatting them individually in that phone.. that's why i did it on the Atrix...
also, in the HD2 they were folders not partitions... so basically, i wasn't familiar with the exact core of Motorola android devices...
there must be a way to put in my own hardware details into the PDS image file?
Click to expand...
Click to collapse
well, that's a little over my head, but i know some of the devs would be able to help you if you PMed them maybe.
coolios...
know anyone in particular?
Hello I need help, by mistake I flashed SP_Flash_Tool a version that in the end was incompatible with my AC8227 YT9216B with what remained brick.
I am trying to recover it with versions that download YT9217 and YT9218 but it is known that they are very different from the version that I had the YT9216B_00002_v004_20190530 and by means of USB bridging the test point close to negative but even though the program SP_Flash_Tool- 5.1916 always ends with failure 4032 or 5054 both related to the DMRAM.
There would be someone in the forum that could help me indicating where to find the link to download my ROM? I have already reviewed the month of 400 pages of the 4PDA forum and I did not find it.
I believe this (Link) is the version you are looking for. Its a memory dump. If you need help flashing it, follow the instruction here. Error 4032 means you are not using correct scatter file. and 5054 means there is not correct preloader file to go with the scatter. You can try the one I have shared, or copy the 2 files from other similar firmwares offered at 4pda
I hope it helps.
lmmerono said:
Hello I need help, by mistake I flashed SP_Flash_Tool a version that in the end was incompatible with my AC8227 YT9216B with what remained brick.
I am trying to recover it with versions that download YT9217 and YT9218 but it is known that they are very different from the version that I had the YT9216B_00002_v004_20190530 and by means of USB bridging the test point close to negative but even though the program SP_Flash_Tool- 5.1916 always ends with failure 4032 or 5054 both related to the DMRAM.
There would be someone in the forum that could help me indicating where to find the link to download my ROM? I have already reviewed the month of 400 pages of the 4PDA forum and I did not find it.
Click to expand...
Click to collapse
viktorsaari said:
I believe this (Link) is the version you are looking for. Its a memory dump. If you need help flashing it, follow the instruction here. Error 4032 means you are not using correct scatter file. and 5054 means there is not correct preloader file to go with the scatter. You can try the one I have shared, or copy the 2 files from other similar firmwares offered at 4pda
I hope it helps.
Click to expand...
Click to collapse
Thank you very much for your help, I will try it immediately to see if with a little luck and your copy of the firmware convinces my computer and starts once and for all, although I do not have too much hope, but anyway, we will try achieve.:good
Nothing, still the same, error 4032 put it as you put it.
Connected to a 12V source the screen starts in a blue color and there is no change unless the reset button is pressed, I don't know if that can indicate any other fault such as that the MCU memory had been erased or corrupted and that is why he does not stop doing anything but the question is that following the procedure for the use of the "test point" step by step always cindependently of using a flash tool or another, of using different scatter files or firm YT9216 / 17/18, B, Whatever the question is, always, always the blissful error 4032 above all.
I don't know what to do, any suggestion is accepted even if it is to use a hammer as a tool.
did you try the scatter and preloader from my post?
viktorsaari said:
did you try the scatter and preloader from my post?
Click to expand...
Click to collapse
yes both and in different ports of the PC (windows10)
the error you have described is only the wrong scatter and preloader file. its only a matter of finding the correct one. I also found the scatter that worked from a different firmware(the firmware didnt work but only the scatter did) , and installed different firmware. It might be possible for you to extract original scatter from the device using MTK droid tools.
lmmerono said:
yes both and in different ports of the PC (windows10)
Click to expand...
Click to collapse
viktorsaari said:
the error you have described is only the wrong scatter and preloader file. its only a matter of finding the correct one. I also found the scatter that worked from a different firmware(the firmware didnt work but only the scatter did) , and installed different firmware. It might be possible for you to extract original scatter from the device using MTK droid tools.
Click to expand...
Click to collapse
Thanks, I found about 20 scatter files between AC8227_Android_scatter and MT3367_Android_scatter, I have about 10 preloader_8227l_demo_ (Preloader) and another 15 different SP_Flash_Too.
I will have to arm myself with patience and try different combinations (so far I have tried more than 50 with the same result, the always present ERROR (4032).
We'll see if I get it or give up before, the ideal is that somewhere the files were found together and that they were already successfully tested but that would be daydreaming.:crying:
Another possible solution would be to enter the way that I would recognize a USB Flash drive with an XYAUTOUPG file or whatever I had tried with it but since this brick after pressing the reset it still does not know.
wow, I'm impressed by your patience
I also downloaded many files from the Russian forum. One of the problems I faced is if the folder name contains some Russian characters, the flashtool gives similar errors. Also some suggested, removing first 4 lines from the scatter file helps in some cases.
I remember I also had disappointments first. Many times I packed everything up and put in storage, but then brought it back for further testing. and one day I got lucky. Hopefully you too will fix it soon.
lmmerono said:
Thanks, I found about 20 scatter files between AC8227_Android_scatter and MT3367_Android_scatter, I have about 10 preloader_8227l_demo_ (Preloader) and another 15 different SP_Flash_Too.
I will have to arm myself with patience and try different combinations (so far I have tried more than 50 with the same result, the always present ERROR (4032).
We'll see if I get it or give up before, the ideal is that somewhere the files were found together and that they were already successfully tested but that would be daydreaming.:crying:
Another possible solution would be to enter the way that I would recognize a USB Flash drive with an XYAUTOUPG file or whatever I had tried with it but since this brick after pressing the reset it still does not know.
Click to expand...
Click to collapse
viktorsaari said:
wow, I'm impressed by your patience
I also downloaded many files from the Russian forum. One of the problems I faced is if the folder name contains some Russian characters, the flashtool gives similar errors. Also some suggested, removing first 4 lines from the scatter file helps in some cases.
I remember I also had disappointments first. Many times I packed everything up and put in storage, but then brought it back for further testing. and one day I got lucky. Hopefully you too will fix it soon.
Click to expand...
Click to collapse
Thanks for your help but I don't get results on the other hand, the test point disappeared from using it so much, it was deleted and since the processor does not have the pins in the air it can no longer even be tried.
I do not know if there is another test point or one that could help for the purpose that is sought and is: to start this brick.
On the main board, from where there would be a SIM socket, there is a connector that could appear to be a USB socket to be used by the Technical Service in the commissioning of the newly assembled ones.
Anyway, I just want to be able to recover my radio.
Thanks for your help.
Hello my friend I hope you upload the file again, YT9216B_00002_v004_20190530 * Thank
viktorsaari said:
I believe this (Link) is the version you are looking for. Its a memory dump. If you need help flashing it, follow the instruction here. Error 4032 means you are not using correct scatter file. and 5054 means there is not correct preloader file to go with the scatter. You can try the one I have shared, or copy the 2 files from other similar firmwares offered at 4pda
I hope it helps.
Click to expand...
Click to collapse
Hello my friend
I hope you upload the file again,
YT9216B_00002_v004_20190530
* Thank you
imr088888 said:
Hello my friend
I hope you upload the file again,
YT9216B_00002_v004_20190530
* Thank you
Click to expand...
Click to collapse
Not exactly the same date but this will work. Just a newer update with root and TWRP
Firmware YT9216B_00002_V004_20190826 (UI1) ROOT, TWRP, translation. (1/16)
https://drive.google.com/file/d/132kkj5neExIr9UufZIgAqeEu67JSVtu3/view
Hi my friend, I could not update, I put the update in usb and the update did not show me, is there a certain way to install?
Hi there I exausted the whole xda and russian forum for something that can work..
exausted different forums.... and tryd a lot of firmware and methods...
I did about the same I am afraid.... no backup and now black screen on startup and no connection to usb no more......
yesterday it still connected to my laptop....you could hear it connect in windows but i couldnt get anything to load on it... all sorts of errors in Flash tool....
eventually i I Did manage to download the preloader onto ny headunit from firmware I found in this post....
I found out that I had to use this order: I would connect my usb... click download in Flashtool then it starts... and I switch on the power of my head unit.... and it completed the upload of the preloader..... So i finally thought Yessssss now install the rest of the firmware.... but after this I had no connection with my head unit... it doesnt find it anymore trough USB.....
but after that I installed that preloader file... I can no longer get any connection no more to my hu....
please help me out.... I also did read some stuff that you need to connect or push 3 spots togheter on youre pcb...?? does anyone got more information or a clear foto of wich and how I connect these 3 spots?
Or maybe now a way I can unbrick my device or have correct software for me??
Ive been trying to fix it 4 3 days in a row now... but I am about to go insane
System information I found in factory settings when the unit was still stock and untouched:
YT9216B_00002_V004_20190708
kenel: 3.18.22
Flash:16G
CPU:A7 1.3 GHz x 4
Display 1024 * 600
MCU1: HW8227L-3.3-SW0-3.1
Inide when i open it op the sticker on the connectors on the pcb tells me:
YT9216B Vo.1 16C
A.005-YT9216B004
20200214
And here is the information of the store i bought it from in the original advertisement:
Specifications on website:
● System:Andriod 8.1
● Model:SU 9701
● Radio Chip:QN8035
● Software:8227L
● Type:Android navigation MP5
● Size:7 Inch
● Bluetooth:Bluetooth 4.0
● Resolution:1024*600
● Audio Amplifier:TDA7388
● Voltage:12V
● Power Output:60W
● Memory:1G+16G
● Audio format:MP3/WMA/WA/OGG/FLAC/APE
● Video format:RM/RMVB/MP4/FLV/MKV/3GP/AVIASF/SWFMP1
● Image foramt:JPG
● FM Range:FM 87.5~108MHz
● Operating temperature:-10℃ ~ +60℃
● USB Interface:USB 2.0
● Product Size:188mm*58mm*165mm
● Weight:1922g
● Button: Physical button/Reset button
● Factory password:1111
My apologies for my bad English (not my native language).
Hope you guys can help me unroot it...
martinique78 said:
Not exactly the same date but this will work. Just a newer update with root and TWRP
Firmware YT9216B_00002_V004_20190826 (UI1) ROOT, TWRP, translation. (1/16)
https://drive.google.com/file/d/132kkj5neExIr9UufZIgAqeEu67JSVtu3/view
Click to expand...
Click to collapse
I have this radio version and I can't update it. I tried USB update with a flash pen USB and gave me an error. I tried with SP flash and gave me error 4032 with the test points method... I don't know what can I do more.
DFC said:
I have this radio version and I can't update it. I tried USB update with a flash pen USB and gave me an error. I tried with SP flash and gave me error 4032 with the test points method... I don't know what can I do more.
Click to expand...
Click to collapse
I gave up on this junk radio a while ago...worked for a few days then it just went blank and got really hot so i pulled it out. Now it sits in a box in pieces.
My radio looks like a PODOFO, It's a YT9216B_00002_v004_20190826 firmware but aida64 show yt9218B.
I tried some methods, nothing worked. I tried to update via Android update, flash with USB with SP flash, flash with USB pen and sd card, without success .I decided to try again. Can someone help me, and on first place tell me what is the correct firmware for this device? And a full tutorial step by step (without shortcuts)? or some tip that can help me?
yt9216b
hello can you help me please me send new rom
thank you
YT9216B?
morio005 said:
hello can you help me please me send new rom
thank you
Click to expand...
Click to collapse
Hi, I wanted to know if this version of the radio was updated? Thank you
Renstaman said:
Hi there I exausted the whole xda and russian forum for something that can work..
exausted different forums.... and tryd a lot of firmware and methods...
I did about the same I am afraid.... no backup and now black screen on startup and no connection to usb no more......
yesterday it still connected to my laptop....you could hear it connect in windows but i couldnt get anything to load on it... all sorts of errors in Flash tool....
eventually i I Did manage to download the preloader onto ny headunit from firmware I found in this post....
I found out that I had to use this order: I would connect my usb... click download in Flashtool then it starts... and I switch on the power of my head unit.... and it completed the upload of the preloader..... So i finally thought Yessssss now install the rest of the firmware.... but after this I had no connection with my head unit... it doesnt find it anymore trough USB.....
but after that I installed that preloader file... I can no longer get any connection no more to my hu....
please help me out.... I also did read some stuff that you need to connect or push 3 spots togheter on youre pcb...?? does anyone got more information or a clear foto of wich and how I connect these 3 spots?
Or maybe now a way I can unbrick my device or have correct software for me??
Ive been trying to fix it 4 3 days in a row now... but I am about to go insane
System information I found in factory settings when the unit was still stock and untouched:
YT9216B_00002_V004_20190708
kenel: 3.18.22
Flash:16G
CPU:A7 1.3 GHz x 4
Display 1024 * 600
MCU1: HW8227L-3.3-SW0-3.1
Inide when i open it op the sticker on the connectors on the pcb tells me:
YT9216B Vo.1 16C
A.005-YT9216B004
20200214
And here is the information of the store i bought it from in the original advertisement:
Specifications on website:
● System:Andriod 8.1
● Model:SU 9701
● Radio Chip:QN8035
● Software:8227L
● Type:Android navigation MP5
● Size:7 Inch
● Bluetooth:Bluetooth 4.0
● Resolution:1024*600
● Audio Amplifier:TDA7388
● Voltage:12V
● Power Output:60W
● Memory:1G+16G
● Audio format:MP3/WMA/WA/OGG/FLAC/APE
● Video format:RM/RMVB/MP4/FLV/MKV/3GP/AVIASF/SWFMP1
● Image foramt:JPG
● FM Range:FM 87.5~108MHz
● Operating temperature:-10℃ ~ +60℃
● USB Interface:USB 2.0
● Product Size:188mm*58mm*165mm
● Weight:1922g
● Button: Physical button/Reset button
● Factory password:1111
My apologies for my bad English (not my native language).
Hope you guys can help me unroot it...
Click to expand...
Click to collapse
Hello, Did you solve issue?
I'm facing same issue. My android radio is the same of yours.
Hello folks,
I ran into a poblem with my old Samsung Galaxy Grand Prime Plus. 3 years ago I was messing up with the phone and I ran into an invalid IMEI problem. As I was a real newbie, I brought it straight to a friend of a friend of a friend who had a phone shop, and he fixed it for me.
Everything OK until last week, when I suddenly realized that probably the guy had flashed the wrong IMEI to it, mistyping 2 numbers of one of the two IMEIs.
Currently, I then have a perfectly working phone, but the IMEI is incorrect and I need to fix it.
I don't have the box anymore, but luckilly the numbers under the battery are perfectly clear and readable, although this is quite an old device.
As the shop of the guy who did the work is long gone, I started to look around for instruction on how to deal with the problem, and I followed all the possible tutorials, but apparently I'm not able to fix the issue.
I just know it can be done, as this was done to the very same phone in the past, creating the problem. I just do not happen to know how he did...
Here's what I tried so far:
1. APP: Mobileuncle Tools
Whenever I tap onto "IMEI Backup Restore (MTK)" I get an error message that says "No support".
2. APP: MTK engineering mode
I open the app, and whenever I tap onto "MTK Settings" I get an error message that says: "Cannot find EngineerMode App - Mediatek chipset is mandatory and stock ROM must be installed".
I tried both Mobileuncle Tools and MTK Engineering mode with 3 different ROMs downloaded from different sources, before and after rooting the device with Super SU, but to no avail.
3. With any xposed module
This could be a solution... but not a real one.
At least according to all the documentation I found (also here on the forum), any xposed module like "IMEI Changer", "chamaleon", "device changer", "hijack suite free" etc only mask the IMEI in front of other apps, but do not really change the IMEI of the phone.
So basically I would still have a phone with an illegal IMEI on it.
Not ideal: this is not what I am looking for.
4. IMEI Maker and IMEI Repair
I followed the tutorial I found here:
https://forum.xda-developers.com/showthread.php?t=2399037
I encounter no errors at all, and TWRP shows a clean log, nothing seems to be wrong. But after flashing the new IMEI, nothing changes: with *#06# I can still see the wrong IMEI there.
The file in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 just remains the same, dating 2016, and does not get replaced by the new one.
I tried to replace the file manually, using ROM Toolbox Lite. At the beginning I could not delete the original MP0B_001 file, even after changin permissions to 775. It kept saying "File deleted" but the file remained there.
I then installed BusyBox Free, and it did the trick: now using ROM Toolbox Lite I definitely can delete the MP0B_001 file. The problem is that the original file keeps coming back again and again, after every reboot.
Nevermind if I place the new MP0B_001 file in the folder copying and pasting it or flashing it with TWRP, it will get overwritten by the old file with the wrong IMEI.
5. Flashing a Combination ROM
I didn't find a specific tutorial for this one, but I just tried to flash the combination ROM and see whether I could get any luck touching things in there.
No luck!
6. With SN write tool (windows software)
Here the big problem is, I can't find the BP file anywhere.
No AP_BP_database seems to contain the BP file for the MT6737T (that is the chipset of the G532F). As I am writing, I am thinking about trying to use a different BP file, from a different chipset. This will probably won't work, but after trying all of these, I mean, why not...
I also tried to look for the BP file into the folder /system/etc/mddb/ , as advised here: https://forum.hovatek.com/thread-11609.html . I looked for ir with any of the 3 different stock ROMs I tried to install. Yet again, absolutely nooooo luck here.
7. MTK Droid Root & Tools (windows software)
This won't even connect to the phone. That is, whenever I connect the phone to the PC, I get the following errors:
" --- Estructura de ROM desconocida, no se puede hacer backup ! "
That would be something like: "Unknown ROM structure, cannot perform backup"
The device gets recognized (hardware, model, build number...), so it should be a problem of drivers, cable or USB port. Also because I used the same setup to install all the stock ROM, TWRP, Super SU etc...
---------------------------
And here I am. After one week of try and fail, getting tired of all this!
I'm surprised on how persistent that wrong IMEI is, as I can't get rid of it in any way.
Do you have ANY kind of idea of what can I do?
As the points 1, 2, 4, 6 and 7 are specifically advised for MTK chipset. I'm starting to doubt that this is an MTK chipset altogether!!!
Thanks for your help
Peter
Update:
I tried with NCK Dongle AndroidMTK 2.5.6.2
Still no success (phone apparently not supported).
Do not blindly flash this device without knowing what you are doing. While the device is hard to brick in general, it is very easy for someone new to brick it by flashing the wrong partitions.
I will write a generalized tutorial that will cover the basics and hopefully make everyone feel better about flashing the device. At first I was skeptical but after understanding everything, I have to say it really isn't that bad, and I am here doing all the leg work for these fake 2gb (its really 1gb ram) and 16gb hdd
OK I am goin gto try and put all of this information in one place because these units say android 10 or 10.1 but in reality cpu-z they are android 9 with api of 27 (will double check to be sure. This unit says it is 2gb ram but it is indeed 1024 MB (q GB). I am not sure if the other custom firmwares dumps from 1gb yt9213aj models will work without problems on these yt9213aj units that say 2gb.
In order to try anything you need to first make a scatter file for your unit. I messaged the manufacture of my unit for a firmware and they sent it. I unzipped it and looked at the scatter file and it is of a different formatting than one that comes from mtk droid tool.
So, mtk droid tool doesn't work with OS versions 9 or higher. It is the problem of adb. But we can follow this guide https://forum.xda-developers.com/t/...not-revealed-error-in-mtkdroid-tools.3582571/ and get it to work.
Once you have your device connected and recognized in droid tools you should first create the scatter file, as this is the most important step to do a full readback in SP flash tools.
Once you have a backup, you are in the clear for the most part. I am still trying to figure out how to backup preloader and etc if possible.
Now you will also need to connect some kind of wire or some small buttons taken from something disassembled. Just something that you can use as a mock button because there is no hardware button on the device for up/down and OK and you cannot use the touch buttons. So you need to short these traces while in recovery in order to get further/
The main point of this thread is to update the existing ones and to add tools and stuff nmeeded in one location because it has taken me over 5 days to search for all fo this, and I am still not done, so lets make it a little easier on the new comers because the last thing we want to do is brick each others devices by using old outdated guides that don't fully work.
Flow chart of process: install mtk droid tools and sp flash tools ->enable oem debugging and oem unlock on device -> follow guide to get mtk droid tools to work -> get scatter file using mtk droid tools -> make a full readback in sp flash tools -> solder wires/buttons onto test points -> boot to fastboot and unlock bootloader -> fastboot flash recovery <image name> -> boot into recovery and install root and/or custom firmware.
Anyone more skilled knows any better?
This post is a WIP and will be updated periodically as I source information. The main idea behind this post is to bring all resources for yt9213aj in one spot. There is plenty of information, its just very hard to navigate especially for someone new to flashing these devices, and even worse to someone who has never flashed any device
OK after trying what seems like 300 twrp's I finally found one that does work with this device. I thin kthe main difference here is that the board is a new revision and some arch changes caused older version that were ported to not work. This one booted right into it but was in russian, which is easily fixable within the twrp gui.
I will add all of these files to the op when I have collected everything.
I do not think that this version board I have has hifi? Maybe I am mistaken? I have an audio glitch at 19-20 when playing music, the sound will get louder and sound good for a fraction of a second then return to sounding ****ty. So I will look into this more. What sucks is that there are so many of the same **** that doesn't work for this model so its like... I would rather garggle gasoline than have to sift through forums that were translated on the fly
Anyway here is the twrp for this particular device - https://www.dropbox.com/s/vogg7854a7ln2zu/twrp-9213aj.img?dl=0
EDIT: also you can boot to fastboot (adb reboot bootloader) and use fastboot getvar all to get factory partition sizes that's needed to create scatter file (you will need to use a hex calculator to create it, or wait for me to upload my scatter file once I have it done). You need to be making dumps in sp flash tool way before you are ever writing anything. Make plenty of readbacks and get to know how to read it before you write anything. Blindly flashing is not what you really want to do lol
Mtk drivers for pc
to install, you will need to disable signature verification and I had to turn on test signing as well
I have successfully rooted this thing. I did encounter something kind of strange though. When I patched the boot.img I had from the device and the one I got in ota update and patched with magisk. When I booted and checked the root with magisk it said there was an unsupported root using su already. It did this for both boot.imgs.
Anyone ever heard of this on stock firmwares? I am able to grant root permissions to busybox and etc so it seems to be working OK. Maybe the root that is there is the chinese root for backdoor tracking and surveillance xD
Wonder how to see what unsupported su commands are being sent?
EDIT: i also took a lot of pictures of the board. It is yt9213aj v1.2 board. I will update the original post in the few days with everything needed for this model including testpoints etc. The test points are a little different but its pretty much the same. The only two you need in the end are the two bigger ones (for unlocking bootloader) then your set. You could drill some holes and run wire down to the trace and put some hardware buttons for the mcu to use to select things in fastboot and official recovery.
There is also another port/connector on this thing above the touch sensor board. I think we could buy a ribbon cable to connect here and run it to another board with hardware button. Actually I think the connector is for hardware buttons specifically but I don't know for sure. Must do more research
These things have are rooted from the factory. When I try to use magisk it says there is another unsupported su. The Unsu.zip floating around cures that. Then you can install magisk.
Also another thing about these things being prerooted... I think you can dump and flash without any extra sp flash tools or mtkdroid. I was dumping the partitions using adb pull function. Adb pull /dev/block/platform/soc/11230000.mmc/by-name/<insert partition name here>"
And
"/dev/block/mmcblk0pxx" where xx is the specific partition to read/write to.
I had got a scatter.txt in the ota update I obtained from the manufacturer which had all the partition layouts. I used this and a log from a failed supersu.zip install to create a scatter.txt for this particular device. The supersu log can be obtained by trying to flash the supersu zip in recovery, then in adg just pull the log file adb shell cat /tmp/recovery.log. Once you have this, you will have to use brain.exe to make your own scatter for sp flash tools.
All in all its pretty easy to actually root the device, and they are actually rooted from the factory, most likely for some functions within the os to work (like surveillance and spying xD) but that can easily be removed with the unsu.zip then install magisk.
I will be writing up a guide for this specific model in a few more days. If you read this thanks for listening to the rumbling of a mad man
Just discovered another problem. When I try to edit anything in /system it says its read only. Mounting is or remounting it shows as successful with no errors, but something is blocking it from mounting as system. I am trying to rename this audio_effects.conf and it willnt let me. I think it might be some proprietary code in the kernel designed to block mounting or remounting of certain or all partitions.
I think that a lot of them are software locked, like the fader and balance and volume level. Notice how some of these have glitches when turning the volume up and down. I think that there is some code that disables some functions of higher end units, depending on the model. If you buy a cheaper 100 dollar head unit, maybe it is indeed just software locked down.
I know for fact the amp chip in my head unit, YD7388, sec sheet says 4 channel. But my device is only 2 channel, no fader. Also the spec sheet says it needs no output capacitor but mine has one I think (there is a huge capacitor soldered next to the chip. I have some pics of the board and test points and chip markers etc. Once I have everythign ready I will make a nice guide
Wow I think I found the reason this thing outputs as 2 channel on 4 speakers. I need someone with a real 4 channel version to message me so I can get a few files for comparison. If this is the case, a simple magisk module would fix the fixed 2 channel problem we have. In the audio_policy_configuration.xml they have all output set as
XML:
<devicePort tagName="FM Tuner Out" type="AUDIO_DEVICE_OUT_FM" role="sink">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="44100" channelMasks="AUDIO_CHANNEL_OUT_STEREO"/>
</devicePort>
I wonder if you set AUDIO_CHANNEL_OUT_STEREO to multichannel or maybe like "AUDIO_CHANNEL_OUT_QUAD " as described in the official android docs say, I wonder if that would enable true 4 channel (or 5.1)?
If someone who has a 4 real 4 channel stereo and it is around the model of yt9213aj, then send me a message so we can collaborate. If you are not rooted do not worry I will help you