Hey guys,
something went wrong when i flashed the MTCE 2.72 GS File, my unit is now totally black and dead, no response.
What options do i have?
Kind Regards
kaya
Recovery & Re-flash.
Cheers
The Question is how, do all of these units have an internal USB??
I do hesitate to open up the case and end up in a missing USB Port, when i played around with ADB i could only access USB1 and USB3 before i bricked the unit.
OK, i am doomed...or someone just has a clue where i might solder USB and recover with "Rockchip Assitant"? :crying::crying::crying:
Kayhan 17# said:
OK, i am doomed...or someone just has a clue where i might solder USB and recover with "Rockchip Assitant"? :crying::crying::crying:
Click to expand...
Click to collapse
See links in my signature.
I already saw your thread buddy, but i absolutely dont have a clue where those USB1 Connections are.
i could find some stuff in the front of the Board like M-USB, L-USB, R-USB and a few centimeters far away +5V USB but dont know exactly where to solder.
Oh and i dont get it why i have to lift 27 and 28 of that chip, so there is no way to hard install this for later applications?
I mean like let 27 and 28 open so i can have 3-USB Ports? AFAIK that 3rd USB is for ADB and Recovery?
Hey Guys,
i tested my px3 board on a different unit and its working, so it seems that my android system is gone. Any ideas how i may fix this?
but...the PX3 coreboard has the Android image included...if that worked on other unit....the problem is your MainBoard, not the CoreBoard
yeah, thats what i am thinking of too??
so how the hell is this one dead after firmware update?
Kayhan 17# said:
yeah, thats what i am thinking of too??
so how the hell is this one dead after firmware update?
Click to expand...
Click to collapse
Agree, sounds like your MCU is corrupt/bad. Replace the mainboard.
impossible, as the old bricked one(which was not bricked!) does work in the new radio, the new mcu of the NEW Radio does not work in my OLD radio shown in the pics above. It still has a black screen and no illumination on the buttons and behaves dead with a definitely working MCU
Kayhan 17# said:
impossible, as the old bricked one(which was not bricked!) does work in the new radio, the new mcu of the NEW Radio does not work in my OLD radio shown in the pics above. It still has a black screen and no illumination on the buttons and behaves dead with a definitely working MCU
Click to expand...
Click to collapse
Replace mainboard not som.
I found that video: https://www.youtube.com/watch?v=DkA6o2P_hTc&t=127s
It could help you...but important question is: where to find ha_256_FULL.bin ??
Hey Buddy,
i already flashed the newest file with your mtcdtool (img to bin), but you said in a different thread that it wont turn on because the bootloader is missing, i ordered another unit and will try to do a read and put it on my device to recover it.
if you could do a dump or find that file, dont hesitate to send it to me =)
Wadzio said:
I found that video: https://www.youtube.com/watch?v=DkA6o2P_hTc&t=127s
It could help you...but important question is: where to find ha_256_FULL.bin ??
Click to expand...
Click to collapse
From video, note start address. Is it possible he only flashes standard MCU file?'
Kayhan 17# said:
Hey Buddy,
i already flashed the newest file with your mtcdtool (img to bin), but you said in a different thread that it wont turn on because the bootloader is missing, i ordered another unit and will try to do a read and put it on my device to recover it.
if you could do a dump or find that file, dont hesitate to send it to me =)
Click to expand...
Click to collapse
ok....but....
What is 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"
}
For me its look like simple RS232ToUSB converter. It's wrong tool.
You should use ST-Link, for example:
and connect it to MCU pins: SYS_SWCLK, SYS_SWDIO. Some boards has special pinpad for that:
On your board I can't find it (picture is poor quality)
---------- Post added at 09:19 AM ---------- Previous post was at 09:14 AM ----------
marchnz said:
From video, note start address. Is it possible he only flashes standard MCU file?'
Click to expand...
Click to collapse
I don't think so. On video we see 0x08000000
"standard" MCU files (the ones we upload to unit 'dmcu.img') has start address 0x08004000
I have an USBtoTTL aswell and an USBtoUART:
The one in the picture is the UART-adapter and i could flash with the Flashloader-DemonstratorGUI(also from STM)
I used 0x8000 as start adress but as you stated it possibly starts at 0x8004000
I found out that i did a mistake on PIN74 and instead used PIN72 for VSS - but nevermind it worked two weeks ago and it still does =)
I wanted to post here earlier but i had exams and the new board didnt arrive yet =)
EDIT: for the other interested guys, this is what i bought years ago USBtoUART 6-pin CP2102 Adapter
Kayhan 17# said:
Hey Buddy,
i already flashed the newest file with your mtcdtool (img to bin), but you said in a different thread that it wont turn on because the bootloader is missing, i ordered another unit and will try to do a read and put it on my device to recover it.
if you could do a dump or find that file, dont hesitate to send it to me =)
Click to expand...
Click to collapse
If you have read the topic PX5 Oreo ROM you probably already know that the owner of magintolog.ru (along with the youtube channel) is @kumarai.
He has such a file. Unfortunately, on the 4PDA forum, I found such like this: (=> )
At the moment, there is an opportunity to raise dead MCU chips (MTCD and future MTCE), pull it out of any state. Unfortunately, the existing version will not be published for a number of reasons, excuse me. I can say that the MCU is almost not killed, you really have to make a mistake to kill the MCU. No one is immune from a hardware failure.
You can try to ask him, maybe something has changed since then.
Also be careful when you will try read by the BOOT0 method. This is also from him (=>):
This is excluded. You have to be an idiot manufacturer to give you the opportunity to read the chip. Moreover, when you try to read, the chip will no longer start up, it will wrap up the boot-old firmware from such read attempts.
If you read the datasheet on the protsyk, there are three levels - 0, 1, 2. If transferred to the second level, only the replacement of the protsyk. But it makes sense to change if there is protsik's firmware.
Result: If you tried to do a reading of the protsik, he is in the block, the radio tape recorder is a corpse. Transfer to mode 2
@level 2: chip readout protection, debug features (Cortex®-M0 serial wire) and boot in RAM selection disabled @
Disables the chip firmware option.
He is a professional, i dont think he is gonna give out that file :\
I prepared simple recovey image (based on KLD_V257): https://www.sendspace.com/file/wsvj55
If you want to try flash it and tell us is it works.
Related
I've got a dead bootloader. My device doesn't upgrade thru SD and not with USB. can somebody please help me because i realy don't know what to do. My device is dead for almost 3 weeks now
[edit]
Even my backup on SD doesn't load. And this happend after i downgrade the radio version of the well know greek rom
[/edit]
nobody?
Is there a solution to flash only the bootloader?
I think you need to add some more info, if anyone should have a chance to help. For example what happened when it died - how and why? What happens if you remove the battery cover, replaces it and turns on the device? Text on screen, like USB or Serial? Have you tried uploading ROM from different PCs?
The more info you provide, the more likely it is that someone recognizes your situation from own experience and can provide some help.
HBK said:
I think you need to add some more info, if anyone should have a chance to help. For example what happened when it died - how and why? What happens if you remove the battery cover, replaces it and turns on the device? Text on screen, like USB or Serial? Have you tried uploading ROM from different PCs?
The more info you provide, the more likely it is that someone recognizes your situation from own experience and can provide some help.
Click to expand...
Click to collapse
You are totaly right.
I have update my frvice with the wrong greek rom and now i have the 15 sec reboot thing.
When I startup my device he ends up the bootloader and the only way to get the device booting to windows is remove the battery cover. But the her reboots again after the 15 seconds.
In the bootloader i tried to load my backup with the SD card but nothing happens. I also tried to load a ROM with MaUpgradeUt_NoID but nothing happens. I only get empty version thing.
{
"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"
}
If i use the regular MaUpgradeUt and change the file change.bat for the xda3nbftool I get a error "error 201: get device data error".
I also tried to backup my device with the wrong ROM on it, to look at the header but nothing happens (romupdate.exe).
So my conclusion is that my bootloader is dead. Please correct me when i'm wrong but if this is the case how can i correct my bootloader.
When you unplug your Magician from the USB cable, what do you see?
If you see (with the backlight OFF) "Serial v1.00" or similar, thats a WORKING bootloader.
Make sure you have Active Sync DISABLED (right click the taskbar icon, click "Connection Settings..." the uncheck "Available by USB".
You should then plug in the USB cable and it should change to "USB v1.00" or similar.
Your PC may detect the connection as new hardware - that is a good sign that you have Active Sync disabled.
Let the New Hardware Wizard do it's thing, then re-run the upgrade setup and it should work.
If not, you've got BIG problems.
guess I'm in big trouble
The only thing i can do, is trying a different pc without ASync. On the current pc i'm working on, USB in activesync is disabled.
Are there any posibilties to reload (rebuilt, update) Bootloader.
Can somebody please help me.
The bootloader is built in as it's own ROM, and I've never seen a utility that can make it writeable. I doubt you've destroyed your bootloader, but that doesn't help you - sounds like you'll have to bite the bullet, act dumber than you are, and return it to the manufacturer for a repair - and probably pay for the privilege.
KevinL said:
The bootloader is built in as it's own ROM, and I've never seen a utility that can make it writeable. I doubt you've destroyed your bootloader, but that doesn't help you - sounds like you'll have to bite the bullet, act dumber than you are, and return it to the manufacturer for a repair - and probably pay for the privilege.
Click to expand...
Click to collapse
:shock:
But isn't it strange that if you can't destroy it, it doesn't work anymore? And isn't there somebody who had the same problem?
Before you give up, try this:
Try using another USB cable.
I have experimented many times to realise that the upgrading process does require matching with the right cable.
I noticed that in the screenshot you posted, there is no info on what the device will be upgrade to! I could be wrong, but this may well mean that your device is incompatible with the ROM you are trying to upload.
Try downloading another ROM and give it a go. The best thing would be, if you can find one made specifically for your brand, ie Qtek, I-mate or whatever, and DON'T patch it. Just let the original installer do the job...
Talents said:
Before you give up, try this:
Try using another USB cable.
I have experimented many times to realise that the upgrading process does require matching with the right cable.
Click to expand...
Click to collapse
I'm using the cable that came with my device so that can't be wrong. But i could give it a try.
HBK said:
I noticed that in the screenshot you posted, there is no info on what the device will be upgrade to! I could be wrong, but this may well mean that your device is incompatible with the ROM you are trying to upload.
Try downloading another ROM and give it a go. The best thing would be, if you can find one made specifically for your brand, ie Qtek, I-mate or whatever, and DON'T patch it. Just let the original installer do the job...
Click to expand...
Click to collapse
There isn't a orignal rom fot the dutch T-mobile MDA. And if you use a original installer, it uses ActiveSync. And i can't boot windows because it restarts after 15 seconds so I can't use ActiveSync.
Why can't you use an original ROM updater, if you have the Greek resetting ROM installed? I believe a lot of us has done so without any problems, including me. I don't remember precisely what I did, but it was no problem whatsoever. Most likely I just entered bootloader mode first, to keep the Magician from resetting...
HBK said:
Why can't you use an original ROM updater, if you have the Greek resetting ROM installed? I believe a lot of us has done so without any problems, including me. I don't remember precisely what I did, but it was no problem whatsoever. Most likely I just entered bootloader mode first, to keep the Magician from resetting...
Click to expand...
Click to collapse
I really tried everything but without any results. I realy don't know why i can't use the original ROM updater.
I have the similar problem, but mine one doesnt even start windows. It always go into the bootloader mode and stays there. I try upgrading it, but it gives me communication errors.
Do this
This is what you do.
Disconnect your JAm from USB
Go from your PC , ACTIVESYNC > FILE > CONNECTION SETTINGS > remove the check mark for ALLOW USB CONNECTION TO THIS DESKTOP COMPUTER
Now connect your JAM to your PC again via USB, this time active sync should not start since you have disabled USB
Now double click on the installer file of the original ROM and you should be good to go
After Reset , enable USB ,
Go from your PC , ACTIVESYNC > FILE > CONNECTION SETTINGS > Put a check mark for ALLOW USB CONNECTION TO THIS DESKTOP COMPUTER
MDA dead
I have tried.... it's not responsing as it should be.
Hi friend, i have found this good china phone. Have android 2.2, wifi, gps and tv
Is a dualsim
The russian site have release firmware cooked rom... You can test ?
http://forum.china-iphone.ru/viewtopic.php?f=31&t=9519
After can download this document for create a data cable for this telephone...
http://depositfiles.com/en/files/0jnvipl4e
1 upgrade can download at this link:
http://sendfile.su/219002
cost 130$ star studyyyyyy
{
"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"
}
Hello!
Good links. I tried to read the all 18 pages translated by google, but the translation is not very good.
Could you speak russian?
Must I have such a cable to adjust the IMEI after updating?
On my A3000 version (dual sim android 2.2) the GPS is not working and the other forum explains that this could be solved by a new firmware version...
I speak russian.
those ROM has two problems: GPS Doens't work and Market application defective.
Flashing this ROM might be a huge mistake (IMHO)
Let's wait and see
hi friend, u have found other russian Rom work with a3000 ? Pls send link. Thanks
The A3000 i recently bought has no GPS chip in it, the battery does not charge, and the resistive touchscreen has a large dead spot on it. It seems there are several hundred versions of the A3000 and I doubt the ROMs from one will work on the other because the hardware varies so much.
i have buy this model A3000. Arrive today. The firmware version is
e1000_pxht2 2011/0/22
is rooted ;-)
i think is last firmware found on this forum.... try upgrade your telephone at this firmware.
the post forum
http://www.forum.china-iphone.ru/viewtopic.php?f=31&p=258161
i think is it for download: http://us.ua/160472/
for buy cable flash is need buy on this link...
http://item.taobao.com/item.htm?id=8591547110
Do you know who is the phone manufacturer? because I want to ask them if they can provide me the MTK 6516 processor kernel driver. Thanks,
blassmegod said:
Do you know who is the phone manufacturer? because I want to ask them if they can provide me the MTK 6516 processor kernel driver. Thanks,
Click to expand...
Click to collapse
sz pxht inc
Search for "burebista | 8 Mar 14:51 how to decompile a linux kernel zImage" in Google.
fabio84 said:
i have buy this model A3000. Arrive today. The firmware version is
e1000_pxht2 2011/0/22
is rooted ;-)
i think is last firmware found on this forum.... try upgrade your telephone at this firmware.
the post forum
i think is it for download:
Click to expand...
Click to collapse
Hi i'm new of the forum and this is the first time i've to Flash so many files ! xD Could someone help me ?
xD
I've bought this phone and this is the only post i found talking about the rom of the phone !
Could someone link me a guide ?
Which program i have to use to backup the whole ?
I've downloaded universal androot but still i've not acces to recovery mode bootstrap !
I Suppose i've to use SPMultiPortFlashDownloadProject to flash gps_DA.bin and MTK_AllInOne_DA.bin right ?
how can i backup those ?
.... So ... =D i'm a little noob ! the only firmware i've flahed are the one of my graphic cards and the one of my DVD-Writer !
So i need a little help
Thanks
darthtony said:
Hi i'm new of the forum and this is the first time i've to Flash so many files ! xD Could someone help me ?
xD
Click to expand...
Click to collapse
Hi!
To root the phone use z4root (permanent root. temporary root doesn't work!). Also install TitaniumBackup and backup all applications from phone (WARNING! It is NOT full backup!)
There are good thread at russian forum for flashing this phone, ROMs for it and related problems/bugs. -- http://forum.china-iphone.ru/viewtopic.php?f=31&t=9519&start=760
If you do not understand Russian and translate.google.com cannot help you, I may provide some essential information from there soon.
First of all, perform full backup of your phone! Otherwise you can lost IMEIs after reflashing OR restoring to initial settings.
For FULL backup of your phone use this manual -- http://forum.china-iphone.ru/viewtopic.php?uid=76043&f=31&t=11788&start=0 See text under "Сливаем прошивку" spoiler there.
Backup also content of /nvram forder from phone.
I also recommend you perform backup of all files from phone using tar utility.
Tar you can get there -- http://groomws.info/index.php?title=AndroidNativeBinaries
Copy tar binary to sd-card.
Commands for tar backup:
Code:
su
cat /mnt/sdcard/tar > /data/tar
chmod 0755 /data/tar
/data/tar -cvpf "/mnt/sdcard/rootfs.tar" --same-permissions --same-owner --verify --exclude="/mnt/sdcard/" --exclude="/sys/power/wait_for_fb_wake" -C "/" "./"
Ok !
thank you so much !
No i don't speak russian either chinese !
I'll try in an hour !
@darthtony
Plase use the "Tanks" button next time!
Sorry,
but i've not understood
i need of two different cable?
No. You will need stock cable from phone's kit only.
And what step(s) exactly do you not understand?
i had understood that to flash my phone i need this cable :
item.taobao.com/item.htm?id=8591547110
And i'm searching one !
SP update can't find the com port with the standard cable !
So i'm stucked !
Another thing ! i made the backup with YAFF2 ! it was the only thing i've to do , wasn't it ?
i've also backuped the nvram directory !
Isn't there a way to make the backup with SP update ?
for the rest i hope it is simple !
I install the modem driver when i plug the phone to the PC, then using "SP update" i set the port and the speed , i set the file MT6516_Android_scatter.txt from the rom zip
and if it works ... it works ! xD
another question : would this resolve the GPS problem ?
darthtony said:
i had understood that to flash my phone i need this cable :
item.taobao.com/item.htm?id=8591547110
Click to expand...
Click to collapse
No! For flashing your phone you DO NOT need flashing cable! "Flashing" cable are used for restoring IMEIs if you did not backup /nvram directory from your phone.
For flashing your phone you can use attached bundle of software and instructions. -- http://us.ua/199217/
This manual explain recovery.img flashing process. For full flashing -- select all .img files from ROM archive (except preloader.img, if it exists).
Archived .DOС-file is in russian, but instructions, contained in it, are simple, so you can use translate.google.com for translation.
If you cannot understand some steps, ask here.
There are also needed modem drivers in this archive. Power off phone, then connect it (powered OFF!) to the computer via usual USB cable. MTK USB modem device will appear FOR 5 SECONDS. After this timeout it will disappear.
You should manually locate folder with this driver in "New Hardware Found" wizard in these 5 seconds and install this driver. Otherwise SP Flash Tool will not found your phone.
Specifying a COM-port number in SP Tool is NOT needed, this program will find phone automatically.
darthtony said:
another question : would this resolve the GPS problem ?
Click to expand...
Click to collapse
In newest batches of A3000 phones GPS chip is physically absent.
You can check it presence in Factory mode.
Power off phone. Press one of side volume buttons (check each of it, I do not remember exactly) and power button. "Factory mode" text will appear. Then you can go to the underlying menu - GPS test. If you will get "-8" test result -- there is no GPS chip in your phone. If test will pass -- there are no hardware problems with GPS in your phone.
In newest batches of A3000 phones GPS chip is physically absent.
You can check it presence in Factory mode.
Power off phone. Press one of side volume buttons (check each of it, I do not remember exactly) and power button. "Factory mode" text will appear. Then you can go to the underlying menu - GPS test. If you will get "-8" test result -- there is no GPS chip in your phone. If test will pass -- there are no hardware problems with GPS in your phone.
Click to expand...
Click to collapse
I made the test and it failed !
But if i open google navigator it shows my position !
Also installing another 2 navigator it founds my position ! So i thought that it was a software problem !
Disconnect from WiFi and Bluetooth, pull out both SIM cards and launch your navigation software again.
If it will show your location correctly, it is GPS. Otherwise base-station-based location were used.
You can also use GpsTest software from Android Market.
I disconnected from everything but i forgot that i've only google maps navigator in this time so i've put on WI-fi connection to download the map and then i'm gone where the Wi-fi signal is off !
It indicates my right position !
I've a home wi-fi to connect pc between floors ....
It is enough ?
OK so I bought the Quad Core version non DVD version and here are the pictures. Right now I am using my bench power supply to power the unit.
{
"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"
}
Tried Airplay with iphone 6 after installing airpin, it works fine
Then I wanted to root it, used a few methods. Firstly I tried RootMaster 2.1.1 and framaroot, no go it does not root it. Then, use kingroot, unsucessful and reboot by itself. Lastly baidu root does seems to work properly.
I am at my wits end, how can I successfully root this unit? :crying:
help pls.....
Other methods of rooting anyone?
Alphas said:
Other methods of rooting anyone?
Click to expand...
Click to collapse
Try this method for rooting RK3188 based tablets...
http://www.slatedroid.com/topic/88850-rooting-rk3188-tablets/
There is no USB cable that I can connect from the unit to the PC, unless the USB cable for the flash drive can be used to connect to PC?
Alphas said:
Then I wanted to root it, used a few methods. Firstly I tried RootMaster 2.1.1 and framaroot, no go it does not root it. Then, use kingroot, unsucessful and reboot by itself. Lastly baidu root does seems to work properly.
I am at my wits end, how can I successfully root this unit? :crying:
Click to expand...
Click to collapse
This thread has a lot of good information about these head units:
http://forum.xda-developers.com/showthread.php?t=2660662
The suggestion is to use a pre-rooted kit kat rom that matches your processor and screen resolution.
JPS11 said:
This thread has a lot of good information about these head units:
http://forum.xda-developers.com/showthread.php?t=2660662
The suggestion is to use a pre-rooted kit kat rom that matches your processor and screen resolution.
Click to expand...
Click to collapse
I read the thread but the method of rooting is not possible with this unit.
Alphas said:
I read the thread but the method of rooting is not possible with this unit.
Click to expand...
Click to collapse
From page 1 of the link:
Rooting only works for Android 4.2.2. If you want to root 4.4.x you need to take apart update.img and inject SuperUser app (this is only for experts as @coudu, @Malaysk, @dsa8310 ). The alternative is to install a 4.4.x pre-rooted image and you do not have to do anything.
My understanding is that the usual way of rooting does not work for Android 4.4.4. Unless you know how (I do not) to inject SuperUser into the rom, you should find a pre-rooted rom to install and then the device will be rooted. Since the quad core are new, I am having a hard time finding a quad core, 1024x600 rom for you. I do not know if a dual core, 800x480 rom would work.
I am not sure of your screen resolution.
There is a quad core 800x480 rom on the repository link on the first page.
I haven't found a quad core 1024x600 rom.
I am looking at the rooted rom, the MCU MTCB-JY-v2.11 from lightinthebox is an older version of MCU from this unit, they are the same OEM.The resolution of this unit is 800x480, the problem is how should I change the rom when there is no reset button, no USB to connect to PC?
Alphas said:
I am looking at the rooted rom, the MCU MTCB-JY-v2.11 from lightinthebox is an older version of MCU from this unit, they are the same OEM.The resolution of this unit is 800x480, the problem is how should I change the rom when there is no reset button, no USB to connect to PC?
Click to expand...
Click to collapse
Interesting, no way to boot into recovery? Not mentioned in the manual?
Maybe send the seller an email?
Another thought is that one of the rear USB ports may be an OTG port which means you could use a USB A to USB A cable to plug into your computer?
It actually looks very similar to the unit I ordered recently except mines only dual core and has some physical buttons on the front. The back looks identical. Mine looks to have a reset button though so hopefully shouldn't be too hard to flash.
My version comes without the DVD loader, otherwise it is the exact same unit. I posted the message to them, hopefully they can instruct me on how to reset it.
They posted the updated MCU and update.img on the website. http://www.carjoying.com/Joying-blog/12.html . But I am still waiting for them to show how to reset it. The MCU version v 2.49 is newer than HuiFei MCU in the repository, , so you guys can try to download it too.
Finally got inside the bootloader, wow this unit does not have physical buttons, so they have two buttons holes for reset/move down and select!
Now that there is a update.img and mcu.img, what should I do to root this?
If your joying head unit android resolution is 800*480 and want to latest upgrade your stereo version is 4.4.4 kitkat like universal toyata android car stereo, please download the update file April,11,2015 in the link https://mega.co.nz/#!3s0QURxS!3icY8M03kqLgQwISOlZNbh7aJ_uSGArcFD83JRqvvGg
Alphas said:
Finally got inside the bootloader, wow this unit does not have physical buttons, so they have two buttons holes for reset/move down and select!
Now that there is a update.img and mcu.img, what should I do to root this?
If your joying head unit android resolution is 800*480 and want to latest upgrade your stereo version is 4.4.4 kitkat like universal toyata android car stereo, please download the update file April,11,2015 in the link https://mega.co.nz/#!3s0QURxS!3icY8M03kqLgQwISOlZNbh7aJ_uSGArcFD83JRqvvGg
Click to expand...
Click to collapse
glad you found it.
There is a video of a similar unit here showing how to reset.
https://www.youtube.com/watch?v=30bUAbxAR9I
Unfortunately the reset button is position at another location, it is not exactly the same as the unit I had.
I am posting the high resolution images of the inside of the unit.
Any idea how to do a backup without root access, I want to save the data in case of a bricked unit?
dsa8310 said:
Yes, and vice-versa.
But for now only KLD 800x480 rk3188 images are available.
Click to expand...
Click to collapse
I just do not want to brick it, to be sure there are two img files in the sd card.
update.img from quad-core rk3188 image, KLD, is in post #11499.
and mcu.img from http://www.carjoying.com/Joying-blog/12.html
reboot and update the img from sd right?
Since I do not have root access I cannot backup the system files.
Thanks.
You do not need to update the MCU. You already have the same version.
The firmware from DSA8310 is correct.
JPS11 said:
You do not need to update the MCU. You already have the same version.
The firmware from DSA8310 is correct.
Click to expand...
Click to collapse
I got this rooted finally, you guys are a great help. One question, will the rooted image from joying quad core be uploaded too? I kinda like the interface from Joying rom better than KLD version.
Greetings from Portugal,
I need your help because I probably messed up.
I have an Android Unit on my Mini Cooper. It's from ERISIN (At least the software was, because the booting logo used to be from Erisin).
{
"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 unit has USB and two microSD slots (one is the GPS slot)
Here are the specs from my unit (I took before messing up):
The background story - I contacted ERISIN asking them for a new MCU firmware and ROM, because mine was from 2016. They sent me the files (They sent me an MTCE LM firmware - even though mine was KGL and they also sent an Android 10 ZIP file). I'm a new to this kind of android "programming" so, naive of me, I tried to install it.
In the settings I was able to upgrade the MCU firmware. But unable to to the same with the ZIP file. So I tried from the android recovery - boot from USB and Erase All. The recovery was able to read the MCU file in the usb but not the ZIP. Then I probably ended up recovering from backup (or something like that) because I ended up with a version of the software which did not have working driving wheel buttons nor the front physical buttons. I PANICKED :laugh:
I then got the "yandex disc" version of a KGL MTCD version (similar to the one I had before flashing) and also downloaded the update.img of android 5.1 for PX3 KGL (rk3188, my rockchip) - I wanted to get as stock as I could.
Long story short - I'm stuck with recovering, something went wrong because I get the loop on the lollipop booting screen and wont pass from there.
On Recovering, the GPS microSD is not mounting (and I know It's advised to flash from that slot). The USB is working (I can flash the MCU version from USB but the ROM image gets errors every time I try to flash it.
What I've tried:
- Format microSD in Fat32, ExFat, NTFS to see if the GPS Slot would recognise it. Didn't succeed. Tried with a 1GB and a 4GB card.
- Tried to make a "Boot" SD and USB with "Rockchip Create Upgrade Disk Tool" Software (Following Malaysk posts), but both didn't work.
- Tried to disconnect battery from car, inserting MicroSD in GPS slot and then connect the battery to check if the unit would recognize it.
The ROM update from USB always starts, but after 30 seconds it gives me a bunch of errors (cant mount cache... cant open cache... block device required... and some rknand errors.
The Malaysk ROM is named dupdate.img Should I try to rename it to update.img ? Would that work?
Please help. And thanks in advance.
I leave you the errors:
Your unit isn't [Android Auto] but the good news is that it is a well known [MTCD] type, as seen from the MCU type code.
Ive requested mods move your question to the MTCD Q&a, but as a suggestion, take a little time to read the forums then post. There's a wealth of info, and your issue can be found in the forums.
marchnz said:
Your unit isn't [Android Auto] but the good news is that it is a well known [MTCD] type, as seen from the MCU type code.
Ive requested mods move your question to the MTCD Q&a, but as a suggestion, take a little time to read the forums then post. There's a wealth of info, and your issue can be found in the forums.
Click to expand...
Click to collapse
Thanks in advance. Yes, I did find some post - even 1 or 2 related to KGL version and similar error codes as mine - that's how I started trying some of the solutions I mentioned. Unfortunately it has not worked so far.
Maybe if I try to flash the ROM with RK Batch tool I can get it to work? I'm afraid that with the error codes I have maybe the unit is beyond salvation.
amc90 said:
Thanks in advance. Yes, I did find some post - even 1 or 2 related to KGL version and similar error codes as mine - that's how I started trying some of the solutions I mentioned. Unfortunately it has not worked so far.
Maybe if I try to flash the ROM with RK Batch tool I can get it to work? I'm afraid that with the error codes I have maybe the unit is beyond salvation.
Click to expand...
Click to collapse
Wipe storage first? Put it this way, never had a single SOM that was unrecoverable. Becareful upgrading to Android, does your BT support it.
Just tried to connect the unit with my PC to use with RK Batch tool.. but the PC doesnt recognize the Unit (yes, I've already used the RK Driver Assistant, and it tells me it succeeded to install drivers).. Even so, RK Batch tool does not recognize it. But 2 USBs appeared in "other device" in windows device manager (dont know if it is the unit being recognized, but it's strange that it lists 2 devices there) .
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Don't switch slots unless you know Slot B is filled!
Instructions
fastboot boot RECOVERY.img
Downloads
https://1pwn.ixmoe.com/android/osaka/twrp-3.6.2_12.1-BETA-V1.img
Contributors
@Electimon, @sosthenisRR
Version Information
SourceCode: https://github.com/TeamWin
Version Information
Status: Beta | If touch doesn't appear to work please turn screen off and back on, thank you!
Release Date: November 12 2021
Last Updated: 9/124/2022
2/2/2022:
Fixed bootctrl and micro sd support
6/14/2022:
Merged 3.6.2 sources
9/24/2022:
Rebase on Android 12
Xt2131-1 and recovery log
Love seeing progress. Can't wait to get started..
For ext SD card storage on xt2131-1 boost mobile. In the recovery it is set to mmcblk0p1 mmcblk0 unfortunately.
Just picked this phone up on the cheap and I'm looking forward to hopefully seeing the development scene grow!
xStealth said:
Just picked this phone up on the cheap and I'm looking forward to hopefully seeing the development scene grow!
Click to expand...
Click to collapse
Don't worry, 2 roms are on the way, I hope you guys like Android 12
Electimon said:
Don't worry, 2 roms are on the way, I hope you guys like Android 12
Click to expand...
Click to collapse
Best news I've heard in a while! Good luck with your development! Looking forward to giving them a try!
Im on Metro-pcs phone was an amazon unlocked phone i can confirm sd mounted on mmcblk1p1 and mmcblk1
i changed in the twrp flags on the recovery and now i can access my sd card in twrp
{Mod edit: Quotation fixed}
@androidpimpz Please correct the quote in your reply. I shouldn't be quoted if you're adding to what I wrote. Sorry. Thanks.
androidpimpz said:
Im on Metro-pcs phone was an amazon unlocked phone i can confirm sd mounted on mmcblk1p1 and mmcblk1
i changed in the twrp flags on the recovery and now i can access my sd card in twrp
{Mod edit: Quotation fixed}
Click to expand...
Click to collapse
@androidpimpz
I've edited your above posted and fixed the quotation. I grant you the benefit of doubt that you intended to correctly quote and just misplaced your first sentence. In future, please be more careful when you quote somebody in order not to falsify information and not to show disrespect to the author you quoted!
sosthenisRR said:
Please correct the quote in your reply.
Click to expand...
Click to collapse
This has been accomplished.
Regards
Oswald Boelcke
Senior Moderator
This is my next phone ill be getting next week.
Does this twrp work on the US model Moto g 5g?
Edit saw a previous metro pcs user say it did..
thanks..
sorry i didnt mean any harm. and thanks for understanding.
during testing of this twrp i ran into a problem. i didnt realize i had changed slots to slot B and now my stylus 5g is stuck on black screen with no fastboot and no adb. all is on the phone is a white light that blinks when i hold power and vol-. i cannot connect to my pc with any cable ive tried. i have also tried different button combos to try to boot edl mode. i have a edl cable as well which did not work. if anybody would be able to help me i would greatly appreciate it. i have blank flash file. just cant go into edl.
I told you slot switching doesn't work.... Hold volume down and power then connect to PC, it will show up as qdloader
i apologize. i have tried using button combos but the only thing that happens is a white light blinks once per "combo". might you know where the pinouts are located to force qdl mode? i am aware that would need to open the phone up but thats not the problem. i cant seem to find a diagram to show the pinout locations. again i do apologize and thank you for your time.
sosthenisRR said:
i apologize. i have tried using button combos but the only thing that happens is a white light blinks once per "combo". might you know where the pinouts are located to force qdl mode? i am aware that would need to open the phone up but thats not the problem. i cant seem to find a diagram to show the pinout locations. again i do apologize and thank you for your time.
Click to expand...
Click to collapse
check your telegram dms
I'm also having the same problem as sosthenisRR...
Removed download link because people can't read that slot switching is broken and still decide they want to try it...
Electimon said:
Don't worry, 2 roms are on the way, I hope you guys like Android 12
Click to expand...
Click to collapse
How is the ROM development coming..no rush just curious. And has anybody tried putting a custom boot animation/logo I ended up having to 911 my phone after flashing a file thru twrp