Hi Everybody,
I recently buy a isudaar aa01 for audi a3 with lollipop. Today i try rooting and... nothing is working anymore. When i turn on the radio starts pooping up messages like "android service has stop working" ecc. :crying:
I entered recovery mode and done wipe data/cache but nothing changed. Can anyone please send me the backup/factory image to restore the operating system, or tell me a way to restore the radio? Please. :crying:
Thank you very much
First ... can you give us more information about your unit?
An image of device information could help
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
First ... can you give us more information about your unit?
An image of device information could help
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
Hi Ikerg, thank you very much for your help.
Id like to, but i can't do anything once the radio is turned on, i can just press "ok" on the pop ups that continuosly appear.
I can tell you that it is a rockchip Rk3188.
Here is the link of the product description (not so accurate) where i bought it: https://it.aliexpress.com/item/Andr...4.html?detailNewVersion=&categoryId=200000302
A friend of mine has an identical radio, except for the os since his radio runs android 4.4.4, maybe a screen of his device info might be usefull?
Thank you again
If your radio is the one of the publication...it is a mtcd.
Go to the mtcd thread and download the last ROM.
All mtcd have roms compatible...but not the mcu.
So..if you download from any mtcd source ROm....just be sure you only upgrade the dupdate.img file and NOT dmcu.img one
http://forum.xda-developers.com/showthread.php?t=3366561
You will have to enter into recovery mode and update the ROM.only (dupdate.img)
https://mega.nz/#!44dSiLRY!aqFq_hYLENSiwtel8bhXY24EzQLH1quzgU0VdgXfKME
But check first if your headunit is MTCD. There are other rk3188 units MTCB and MTCC which roms are not compatible
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
If your radio is the one of the publication...it is a mtcd.
Go to the mtcd thread and download the last ROM.
All mtcd have roms compatible...but not the mcu.
So..if you download from any mtcd source ROm....just be sure you only upgrade the dupdate.img file and NOT dmcu.img one
http://forum.xda-developers.com/showthread.php?t=3366561
You will have to enter into recovery mode and update the ROM.only (dupdate.img)
https://mega.nz/#!44dSiLRY!aqFq_hYLENSiwtel8bhXY24EzQLH1quzgU0VdgXfKME
But check first if your headunit is MTCD. There are other rk3188 units MTCB and MTCC which roms are not compatible
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
Hi Ikerg, thank you again.
I totally believe my radio is MTCB model, and i downloaded and pasted the corresponding update.img file into the sd card.
Now my problem is that i can't start the recovery mode, i've tried for over an hour. Could you help me again?
Thanks
First of all don't use the link I provided (as it is for mtcd).
If you cant enter into recovery you shall force to update from sdcard as follows:
http://forum.xda-developers.com/showthread.php?p=67184851
Enviado desde mi D6603 mediante Tapatalk
Thank you Ikerg;
does this step "8) Completely disable power radio. That is, even disable BAT wire (yellow), not to mention the ACC (red). It is best to simply pull the main connector on the rear panel."
mean that i have to take the autoradio outside from its lodging in the car?
thanks again
Sorry @Dek_92....you should ask on that thread...i just put on the direction to follow...I never had to use that method
But my sense tells me that you shall ensure the radio will.boot from cold.
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
Sorry @Dek_92....you should ask on that thread...i just put on the direction to follow...I never had to use that method
But my sense tells me that you shall ensure the radio will.boot from cold.
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
Again thank you @ikerg. Now, i've been enable to enter recovery mode, i tried to install a ROM for MTCB, but radio abort the installation stating that or the image is missing or it is broken or it is not compatible. i tried with Malysk ROM for MTCB. Can you tell me what should I try next?
Thank again
I don't know how to help you....please use the corresponding thread for MTCB on order people could help you
Enviado desde mi D6603 mediante Tapatalk
Related
Hi There,
Yesterday i've received the notification of update 24.211.11.en.EU for my moto Xplay. Problem i had a TWRP Recovery, so i made the manip to come back to a stock recovery... with success, i think, fastboot tell me "okay". But the install stop with message "error" ... help ...
you can install by RDS Lite firmware factory.
Enviado desde mi XT1635-02 mediante Tapatalk
Does anyone have information about how to rebrand this tablet? Or root, change ROM... Anything? There is nothing on the internet
Enviado desde mi VTR-L29 mediante Tapatalk
+1 also very interessed , found nothing too on the internet. I managed to unlock it that's all
pitapart said:
+1 also very interessed , found nothing too on the internet. I managed to unlock it that's all
Click to expand...
Click to collapse
What do you mean by unlock? The carrier network? My model is only wifi.
Enviado desde mi VTR-L29 mediante Tapatalk
I meant Bootloader unlock. My model is WIFI only too
I wanted to ask, could you give list of languages available in default firmware on BAH-W09 tablet? I thought about buying it from china, but I'm not sure what languages are available there. I'm interested in English and Russian.
Hello,
I'am also interested. I'm trying to rebrand from c100 to c233. I followed the guide from ministryofsolutions.com for btv-dl09 and managed to unlock my boot loader using DC unlocker (even though the reading the bootloader code isn't listed in the mediapad m3 lite 10, it still works). Then I installed twrp by using an img for bah-w09 on twrp builder. However, TWRP doesn't give me the option to backup the oeminfo partition. nor can I find an oeminfo for bah-w09c233 xD.
I hope this can help someone, and that we can find a solution xD
Can anybody help me. I have a Head Unit made by Rupse. It is sold by Witson Model Number W2-222. I have been unable to recover this unit after flash attempt. It is a PX5 FYT 6026 Core Board on a S200 main board. Is there anybody that can help me recover it. See pics below.
h**ps://photos.app.goo.gl/C1YaYLiC7WLASAK17
Hi, can you enter on recovery or the unit is completely dead?
Enviado do meu ASUS_Z01RD através do Tapatalk
serpa1982 said:
Hi, can you enter on recovery or the unit is completely dead?
Enviado do meu ASUS_Z01RD através do Tapatalk
Click to expand...
Click to collapse
The unit does not have a recovery. I was never able to enter recovery mode. The unit gets power but nothing boots.
Maybe it works:
I also have a CPU Cortex-A53 PX5
Use the PX5 Upgrade-Tool and make a Boot-Stick with your original Firmware
https://forum.xda-developers.com/an...oying-qd-saved-rooting-supersu-brick-t3903302
Scheitig said:
Maybe it works:
I also have a CPU Cortex-A53 PX5
Use the PX5 Upgrade-Tool and make a Boot-Stick with your original Firmware
https://forum.xda-developers.com/an...oying-qd-saved-rooting-supersu-brick-t3903302
Click to expand...
Click to collapse
The Firmware they sent met does not have an sdupdate.img file. Also no Demo folder.
Any other ideas?
unfortunately i managed to do a stupid mistache, i upgraded the system to android 9 but it does not work on normal parameters so i tried to update the MCU and i think that was my stupidity, now is showing an weird screen in chinese everytime when i have an card on GPS slot. Now the system doesnt work properly anymore.
So i need an little bite of help from you guys.
PX5 MTCE_KLD_V 3.06.1 OCTACORE CORTEX [email protected] 3940MB From Pumkin
Pyconehd said:
unfortunately i managed to do a stupid mistache, i upgraded the system to android 9 but it does not work on normal parameters so i tried to update the MCU and i think that was my stupidity, now is showing an weird screen in chinese everytime when i have an card on GPS slot. Now the system doesnt work properly anymore.
So i need an little bite of help from you guys.
PX5 MTCE_KLD_V 3.06.1 OCTACORE CORTEX [email protected] 3940MB From Pumkin
Click to expand...
Click to collapse
How did you try to upgrade to android 9?
Did you upgrade your recovery first?
Enviado desde mi SM-G975F mediante Tapatalk
ikerg said:
How did you try to upgrade to android 9?
Did you upgrade your recovery first?
Enviado desde mi SM-G975F mediante Tapatalk
Click to expand...
Click to collapse
The upgrade was just fine but i was stupid enough to use one of the MTCE from an long list and now instead of MTCE_KLD_V 3.06.1 is an MTCE-KLD-3.01ss+by+cs-x(that was probably that my mistake), no lights on butons when i,m turning on the car lights.
I have an android head unit with 7.1.2 and i want tu upgrde to newer android.
In android when I go to system update and press it, nothing happens.
when I connect wire key_1 to ground as a manufacturer sais, y press reset button and apears updating, but in a second sais update end and dont load any files, then the update dont run
what its the problem? I need to be root? i tryed with a lot of updates files, extrac their in the root of sdcard....
Procesor type ultraOcta-T8
android 7.1.2
MCU 5.3.19-11-13-453101-1711011
version sistema V9.2.2_20171101.151913_KED7
banda base MF110
Help me please!!!
thanks
So the name of the files need to match the ones for android 7 then the system will see them when you press the update button in the settings
CrypticVorttex said:
So the name of the files need to match the ones for android 7 then the system will see them when you press the update button in the settings
Click to expand...
Click to collapse
the names of the files in V9.2.2_20171101.151913_KED7 are:
b1604ca8-7757-11e7-906d-3390eed0c0c2
b278023e-7757-11e7-bb3a-07933d230b22.0
b278023e-7757-11e7-bb3a-07933d230b22.1
b278023e-7757-11e7-bb3a-07933d230b22.2
but the names in the update file V9.3.1_20180619.172554_KED1-i140 are:
21a4f59a-0a56-11e8-91c9-971a30d57911
22e42020-0a56-11e8-abef-631acfb3beab.0
22e42020-0a56-11e8-abef-631acfb3beab.1
22e42020-0a56-11e8-abef-631acfb3beab.2
2516e792-0a56-11e8-8f93-f3371fae028e
there are one file more in update, waht names are the correct?
Can I rename V9.3.1_20180619.172554_KED1-i140 file to update.zip and try?
Update.zip will not work , they wont update from a zip file from within the system (I don't think)
I think you should update your current firmware to a v9.2.2 2018 and go from there, I think that firmware has the correct number of files which will help in changing the names ?
CrypticVorttex said:
Update.zip will not work , they wont update from a zip file from within the system (I don't think)
I think you should update your current firmware to a v9.2.2 2018 and go from there, I think that firmware has the correct number of files which will help in changing the names [emoji106]
Click to expand...
Click to collapse
I'll try it
Enviado desde mi ALP-L09 mediante Tapatalk
rob_ertin said:
I'll try it
Enviado desde mi ALP-L09 mediante Tapatalk
Click to expand...
Click to collapse
well I can update to last android 7.1.2 ---> V9.2.2_20180827.165435_KED1-i145.
I now try to update to the first android 8.1 ---> V9.3.1_20181203.171342_KED15-i145.rar
and tell you...
editing: FAIL!!!! not update to V9.3.1_20181203.171342_KED15-i145.rar
in your opinion with update must I try?
i must to update with phoenixsuite?
Help please!
Enviado desde mi ALP-L09 mediante Tapatalk
Well I finally update it with phonesuit!
Enviado desde mi ALP-L09 mediante Tapatalk