Database Users

Lenovo Tab 3 8 (TB3-850M) - Hard Bricked

Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.

wxtester said:
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
Click to expand...
Click to collapse
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.

AeonFlux1603 said:
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
Click to expand...
Click to collapse
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course

wxtester said:
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
Click to expand...
Click to collapse
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.

AeonFlux1603 said:
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
Click to expand...
Click to collapse
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...

wxtester said:
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
Click to expand...
Click to collapse
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.c...-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:

I have the same issue. I dont know how but i got hard bricked completely. I was flashing rom on it and it got bricked. Now service centre guy is saying that i have to change motherboard altogether. But your post seems convincing. Please let me know the next detailed process.

i have the same issue.
one day stop working

AeonFlux1603 said:
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.cdn.ampproject.org/v/s/forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/amp/?amp_js_v=a2&amp_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&amp_ct=1551037935701&referrer=https://www.google.com&amp_tf=From %1$s&ampshare=https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
Click to expand...
Click to collapse
what is next? i have a tab 3 710f that is very dead.. hardbricked in wont boot into nothing.. black screen like its shut down

Help with adb/recovery/root for Silverstrong Android 9

Hello!
I've recently got a Silverstrong Android 9 Head Unit: https://www.aliexpress.com/item/32822937592.html?spm=a2g0s.9042311.0.0.328e4c4dWZb7Fi
Can someone help me on how to get adb access or a custom recovery (mainly for rooting purpose)?
I have to mention that I've tried connecting a notebook with adb via and USB cable (male USB type A to USB type A), but it seems nothing happens. I can tell that the unit's USB ports are working for USB sticks.
I have also tried some combination implying the reset hole present on the front, but I couldn't make it work.
Any help is appreciated! Thanks!
Edit: I have to mention that the unit packs a MediaTek MT8321M if it matters.

Just an update: I have followed the instructions provided here for rooting: https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740 . Everything went well until I tried to reboot the device. Now it is stuck in a bootloop (it passes the kernel bootlogo but it is stuck on Android bootlogo) and I really need to access its recovery. It would be my only hope to try to unbrick it. Unfortunately the only physical switch of the unit is just a reset hole on the front which will cut the power right away (tried multiple pressing combinations, none worked). I really need to enter recovery mode and I am pretty desperate, so any advice is welcome. Thanks!

I couldn't make it boot into recovery mode, but it did boot when I placed on a usb stick a file named "ZQ_MTK1B_UPDATE_HeXinDa_EN_8003_08152051.zip" and then it started to flash it automatically. After the flash completed, the unit recovered from bootloop, but now it seems there is no sound and no radio. I posted all of this just in case somebody ever will have to deal with same kind of trouble. It seems the unit is actually branded as alps ZQ8003 and I will ask the seller for some firmware/more technical info.

Hi, I have the same problem. Did you make it?

Help!! I accidentally soft-bricked (or hard-bricked) my PX6 Rk3399 Android 10 HU!

First of all, thank you so much all for any help!! It's my first time posting in the forum which I think speaks to my desperation state right now:crying:, so anything is greatly appreciated!
I bought an Android 10 unit with the PX6 Rk3399 processor, but it had some bloatware that I wanted to get rid of (mainly a knock-off android auto that started when I plugged my phone in even after disabling the app and it got pretty annoying). I decided to root the unit, but it wouldn't stay rooted after restart. I then decided to let SuperSU update the SU binaries despite knowing that something could go wrong, and of course the unit went straight into bootloop!
I then accessed Recovery mode by long pressing the power button (waiting for the unit to flash 5 times) then releasing and pressing again (don't ask me how I found this out). It had an option to flash updates, so I tried flashing the Kal9k Android 9 ROM, with no luck (kept getting error 1001). Then I found a firmware in update.zip form for a similar radio, with my processor and ram and etc from sygav, so I decided to flash that one using the update option on recovery. No luck though, as it was still stuck on boolook with a ford logo (as if the original system partition wasn't flashed and was still there). I couldn't access adb from recovery to see if I could delete the SU folder (if I plugged a USB cable on recovery, the computer didn't seem to see anything), so I booted into bootloader from recovery. Which by the way, was a black screen but did get picked up through USB by windows.
After tinkering with drivers for hours, I don't know how, but my unit got connected and recognized by fastboot. But in trying to erase the system partition, there was no way for system to be found. Every other partition (i.e. cache) could be erased but not system. I also couldn't flash the firmware I found because it being an update.zip, it didn't have a system.img (but it did have an image for everything else, such as boot, recovery, etc).
So I decided to flash a firmware from a guy on the internet that had a soft brick, and I flashall'd it. Now I'm starting to think this guy's firmware was for another completely different system (oh and by the way, System.img failed to flash as it couldn't find the partition, but it really was the only firmware I could find that had a system.img, so since I was completely desperate I stupidly went for it).
Now I can no longer boot into recovery, and I might be booting straight into bootloader mode, but I am not that sure. After I do the trick with the lights flashing and all, the device gets picked up by my computer, but as an unknown device:
{
"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"
}
I manually update it's drivers with the downloaded bootloader drivers from the android sdk (google USB drivers) and it gets detected as a Kedacom USB device, not an Android Device, so no fastboot:
Then if I disconnect it and connect it again, it shows up as an unrecognizable USB device or something like that.
It seems like the same problem I had when I first connected to bootloader, but I don't even know what I did to fix that . I think I might have rebooted into recovery, and then from there booted into bootloader, and somehow my computer then had Android drivers available for install and I manually installed them and it worked? Maybe? I really have no idea, but I can't try that because I can't get to recovery.
I have an update.zip with what I think is the closest firmware to what my radio had originally, an Android 10 PX6 firmware, from which I was planning to install the boot, bootloader and recovery if I had access to fastboot (which I really don't know how to make windows see that it might be a bootloader device), however, since I don't have a system.img to flash and bootloader doesn't even find the system partition, I don't even know where I would go from there.
What do you guys think I should do? What are my options? Did I just hard brick my unit? I wouldn't think so because windows detects "something" even if it can't assign it the driver. But if it is hard bricked, I am not scared to open it up and to do whatever I have to do, if just am really unsure on what to do and how to do it!
Again, any help is highly appreciated! And thank you so much in advance!:fingers-crossed:
SOLUTION:
Alright, this was a ride! It took me about two weeks to find the solution. No matter what I flashed from the recovery, the unit would still be on bootloop, but the last thing I flashed was an update.zip I found on the internet from some guy, and that made my unit completely hard bricked and irrecoverable (no access to recovery). So here's what I did.
Apparently, reading around Rocketchips (PX3,PX5,PX6) have like a "if everything else fails" kind of mode, for stupid people like me, called MASKROM Mode. It's the last resort mode that lets you flash something on the unit when everything fails. That mode is not flashable (you can't mess it up). It's kind of like if a computer had an integrated last resort in case you mess up and break the BIOS.
To get to it though, it is kind of complicated. You need to get to the PX6/5/3 board, which is basically the heart of your radio. So start unscrewing!
The board will look something like this one:
https://sc01.alicdn.com/kf/HTB1f6tCE.R1BeNjy0Fmq6z0wVXaC.jpg
Where the top part is a heatsink that you might also have to remove. PX5s and PX3s may not look exactly like so, but look for something of more or less the same characteristics and form factor, you'll know when you see it.
Go ahead and remove the board from the unit VERY CAREFULLY (the female pin sockets break VERY VERY EASILY from what I've heard, so be very careful).
Next, we will need to connect the PX6/5/3 to the computer through USB. For that, we will have to make a custom cable. Here's the link to the forum where they explain how to make that cable in detail: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Shoutout to @marchnz , he's a genius and without his help I certainly would have wasted my $400 I spent on the headunit.
So long story short, take a USB to something cable (the ones for your phone, for instance), strip it, and solder some resistances to it in the EXACT SAME WAY as in the pictures in the first post of the forum.
Now, connect the cable in the same way as the pictures if you have a PX5 or PX3.
IF YOU HAVE A PX6 find out which pins to connect in PAGE 2 of https://forum.xda-developers.com/an...s-development/px6-maskrom-mode-t3989407/page2 , in the pictures of a post by @oton .
Now download Androidtool here: https://github.com/rockchip-linux/tools/blob/rk3399/windows/AndroidTool_Release_v2.52.zip . This is the software that is going to let us access the mode I was talking about earlier.
Once you have it install, restart and plug in your USB end of the cable. Open the device manager on windows. If you see an Unrecognized device pop up, or a malfunctioning USB, you will need to install the drivers. Here's the link to where you can find an autoinstaller: https://github.com/rockchip-linux/tools .
If, after all, you still are having issues with the drivers, you'll need to install them manually. So right-click on the unrecognized device, update driver, browse my computer, let me pick, Have Disk, and then you find the drivers that we just downloaded (unzip them, of course). Choose the driver, and close and re-open Androidtool.
If you see Maskrom device detected on the bottom, you're all set! If you see recovery device detected, you'll have to put it on Maskrom, for good measure. It might work on recovery, but I'd put it in maskrom mode anyway. To do that, you'll have to disconnect the usb from the computer (while the other end with the cables is still hooked to the board), short two pins on the other side of the board (where the heatsink was) (for a PX6, you can find out which ones here https://forum.xda-developers.com/showpost.php?p=80641439&postcount=435) (for a PX5, I belive it will be on the thumbnails of the first post here: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892) (if you can't figure out which ones, google search for pins to put your unit in maskrom). While you are shorting those pins (maybe with some metallic tweezers), plug in the usb, stop shorting the pins, and the unit should show up in maskrom.
Now dowload an update.img from the following repository: https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/YB . If it tells you to download something, just click on the file until you get to the .rar screen and click on the download arrow on the top right of the screen.
Important: FOR MY UNIT, I HAD TO DOWNLOAD MANY UPDATE.IMG BEFORE 1 WORKED. ONLY ANDROID 8.1 WORKED FOR ME, SO KEEP TRYING! YOU'RE ALMOST THERE!
ALSO, DO NOT DOWNLOAD ANY OTGs (update.zip), ONLY DOWNLOAD IMAGES (update.img).
Now go to upgrade firmware on Androidtool, click on firmware, choose the update.img you downloaded, and start flashing it!
You'll get a progress readout on the right side, and you'll know when its done. Now it's time to put everything back together and hook up the unit and see if it worked. If it didn't or if it's in bootlooop, download another image from the repository and try again. The only one that worked for me was android 8.1.
Okay, so now everything worked and you got your Head Unit back! But what if you had to downgrade android for it?
Here's how to bring it back to its former glory:
From where I stood (android 8.1), the android 8.1 recovery wouldn't allow for android 9 or android 10 flashing. And I found some info on how to flash PX5s recoveries, but nothing on PX6, so I went to Hal9k's website and purchased his modinstaller 2 and followed instructions. Through there, you'll have the chance to update to android 9 or 10 (up to you), by running his apk that will install a new recovery on your machine, and then flashing any update.zip you want. In my case, I decided to also go for his ROM, because of the features it offered. The whole process was 10 bucks but I think it was completely worth it (honest opinion, not sponsored). You can also opt for installing and Android 10 ROM, as I had at the beginning, but I've heard they're pretty unstable.
So that's all! Not an easy project, but at the end you'll have your unit back and running!

I'm guessing you've seen this rom thread? There's a link to the stock stm firmware in the thread, if that's what you have.
https://forum.xda-developers.com/an...rom-malaysk-rom-px6-mcu-stm32-rk3399-t4111653
When mine was stuck on the black screen, I had to short 2 pins out on the board which entered recovery mode. I then managed to get it working from there. I can post a photo of which pins if it's any use to you?

skipraider said:
I'm guessing you've seen this rom thread? There's a link to the stock stm firmware in the thread, if that's what you have.
https://forum.xda-developers.com/an...rom-malaysk-rom-px6-mcu-stm32-rk3399-t4111653
When mine was stuck on the black screen, I had to short 2 pins out on the board which entered recovery mode. I then managed to get it working from there. I can post a photo of which pins if it's any use to you?
Click to expand...
Click to collapse
Hi! I saw that ROM, but when I went to download it it still gives me an update.zip file with all the recovery.img, boot.img bootloader.img but no system.img. I guess I could boot it to recovery and apply the update there, but I think my recovery is also gone :/
Regarding what you said though, are you talking about the maskrom mode? or something like that? Or do those pins just take you into recovery? I could try it but I don't know if Recovery will even work :/
And if they put the radio in maskrom, where do you go from there?? And sure! A picture would be more than greatly appreciated!!
Thank you so much for all your help!!!

To be honest with I'm not sure if it is the maskrom mode, I'm no expert with these things.
All I was getting out of mine was a black screen, but shorting these pins out and powering it up entered a recovery mode each time. Might be worth a try.

skipraider said:
To be honest with I'm not sure if it is the maskrom mode, I'm no expert with these things.
All I was getting out of mine was a black screen, but shorting these pins out and powering it up entered a recovery mode each time. Might be worth a try.
Click to expand...
Click to collapse
My board looks different from that one and I can't seem to find any pins that look like could be shorted :/
I'm at the point where I can flash update.img into the board with my computer (through connecting pins to some USB cable), but I cannot find any full OTG flash for my PX6!
Any ideas? This might be too much to ask but is there any chance you could provide me with a full otg backup of yours to flash on mine maybe?

alfondehesa said:
My board looks different from that one and I can't seem to find any pins that look like could be shorted :/
I'm at the point where I can flash update.img into the board with my computer (through connecting pins to some USB cable), but I cannot find any full OTG flash for my PX6!
Any ideas? This might be too much to ask but is there any chance you could provide me with a full otg backup of yours to flash on mine maybe?
Click to expand...
Click to collapse
Hi,
I have no idea how to do that, and the unit is back in the car now. I ended up keeping the stock rom to be on the safe side! Sorry.

I'm stuck in bootloop on Android 10 PX6 MTCE, headset has no HW buttons only a reset button, can't seem to access recovery.
What step should I try first? I am a total noob and don't own a soldering iron.
Paperclip and recovery?
Update.zip won't flash before rom boot will it.
If all else fails can someone post me a USB OTG?
I only started messing as Malaysk rom had no software volume change for me. Xposed install then reboot looks like a bootloop. Was my Christmas present as well

Hello My Threecar device crashed.
I could not connect to the port in the picture.
The computer does not see the device at all. Does not detect.
Red square. I shorted the feet and the computer never detected it
How can I do PC device detection

Hi, What kind of connector are you using ? can you send a link for that connector or give the connector name ?

radskin said:
Hi, What kind of connector are you using ? can you send a link for that connector or give the connector name ?
Click to expand...
Click to collapse
Hi.
JST-SH 1.0 mm 4 pin Connector

bicer79 said:
Hi.
JST-SH 1.0 mm 4 pin Connector
Click to expand...
Click to collapse
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.

Sorry mate.
I confused it with another device
jst 1.25 connector 4p female

if you want i can pay you

radskin said:
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.
Click to expand...
Click to collapse
radskin said:
I have bought the JST-SH 1.0 mm 4 pin connector and the connector is to small.
Click to expand...
Click to collapse

bicer79 said:
if you want i can pay you
Click to expand...
Click to collapse
Tanks for the offer, but I work at a company that sells this type of material. I ill look for the right type of connector.

radskin said:
Tanks for the offer, but I work at a company that sells this type of material. I ill look for the right type of connector.
Click to expand...
Click to collapse
This is the correct connector
JST 1.25 mm connector 4 pin female

Hi,
I have same board like skipraider, when I short these two pins there is no results. Should I connect board to PC by USB cable. My radio is freezing on black screen after car logo. It happend after updating software and it was take very long time on erasing part so then I restarted radio and it never woke up If I should connect to PC by USB using 4 pin connector has someone pinout description of this connector. Where is Ground, 5V+ , DP+ and DP-?

welcome
Sorry, I don't know English, but I translate from Google. I have a problem. I updated the screen and an error occurred. And because a black screen appears after the logo appears. I can not enter the recovery recovery. The computer refuses to recognize the screen. There is someone who said it must be a 6pin. How do I get the cable that holds the 6 pin. Or is there a way to revive?

[ROM][PX6][STM32][9.0] Malaysk ROM for PX6 MCU STM32 RK3399 with Android 9
Only for devices processor Rockchip PX6, MCU - STM32. Mod Pie 9.0 Android PX6 STM32 RK3399 Not suitable for those who have a real 10 android installed. Install the Device Info HW application in Google Market and look at the API level. 28 API - 9...
forum.xda-developers.com
Examine this topic. Here is how to recover bricked device.
jst 1.25 connector 4p required

[Recovery access] Jitu QF001 / Roco K706 - Hizpo / Ossuret S4 - S8 (UIS 7862) Headunits (no FYT)

Hi all,
this is a dedicated thread for gaining access to the recovery on the QF001 head units. All other infos and general discussions are posted here: https://forum.xda-developers.com/t/...d-units-with-uis-7862s-not-fyt-based.4525675/
What we have got so far:
the whole firmware as flashable zip file
adb access with root user via wireless on port 9876
reboot bootloader brings up a screen which says "fastboot mode" but thats worthless without a working usb connection
reboot recovery boots for a second into a kind of recovery screen and than automatically reboots into normal mode
What i have tried myself so far:
flashing the device with a self cooked firmware (SuperR) with integrated magisk recovery. The device went into flash mode but did not accept the file due to signature issues
several method to push the reset button to get into recovery. no success...
Every info is very wellcome. Happy trying to all!
Cheers

I tried this. It didn't work but I'm not sure I was doing it right.
There is a link to a text file with instruction in the YouTube comments.

Rebooting into recovery from system shows this briefly, then boots back into the system.

I found something interesting. It's from the FYT device, but it's done very similarly with us.
Maybe it would be possible to make Usb Otg working
Motherboard on photo - our device

Vėžys said:
I found something interesting. It's from the FYT device, but it's done very similarly with us.
Maybe it would be possible to make Usb Otg working
Click to expand...
Click to collapse
Can you please link the post on the FYT device that talks more about USB OTG capability?

It's from the 4Pda forum, it's on Russian language
Головные устройства Unisoc на процессоре UIS7862 / SC9863a (UIS8581A) Android 10 - 4PDA
Головные устройства Unisoc на процессоре UIS7862 / SC9863a (UIS8581A) Android 10, [Головное устройство][Автомагнитола][Android]
4pda.to

Hello, people. I have good news for the owners of bricks: my seller kindly provided me with the tools to repair a device with a damaged operating system - a flasher and the necessary files for the S8 1024x600. Download all the contents of the folder and sort it out. I don't have time yet. Good luck!
Восстановление_кирпича-S8_1024х600 - Google Drive
drive.google.com

Great, everything works. A big thank you. Finally unbrick my device

And-S said:
Hello, people. I have good news for the owners of bricks: my seller kindly provided me with the tools to repair a device with a damaged operating system - a flasher and the necessary files for the S8 1024x600. Download all the contents of the folder and sort it out. I don't have time yet. Good luck!
Восстановление_кирпича-S8_1024х600 - Google Drive
drive.google.com
Click to expand...
Click to collapse
Looks like we have at minimum an USB driver now to connect the HU to pc... looks like it is included in the package for recovery tool...

Is there anyway to get into recovery mode if I'm stuck at the boot logo?

super_paws said:
Is there anyway to get into recovery mode if I'm stuck at the boot logo?
Click to expand...
Click to collapse
Not directly but there is a software solution mentioned in the other thread. Someone could revive his head unit with that software.

Thanks to everyone that helped! I have a working unit again!
Figured I'd write a few things here to help anyone else that might have a bricked device.
My device had a corrupt build.prop, so it was not able to boot the system partition at all. On the screen, it was stuck on the initial boot logo screen with the "Powered by Android" logo.
1) Download the above posted package for 2 assets: a) PAC file containing the stock firmware, and b) drivers for the SPD interface of the device
2) For a non-4G device which I had, I went to spdflashtool.com to download the Research Tool. This will allow you to flash firmware onto a non-4G device.
3) Ensure you have enough disk space (~3-4GB) on the same partition as the Research Tool app.
4) Open Research Tool and load the PAC file.
5) Follow the .doc file in the posted package for wiring up the USB interface to the SPD interface. Essentially, you are connecting USB to the 8-pin header on the device, and accessing data via the UART pins. Pin 1 on the 10-pin connector needs to be grounded in order to get the device into the mode for flashing.
6) Press start on Research Tool, and once completed, you should have a freshly flashed device

Hi, I have the same problem being stuck on Powered by Android logo.
I tried this technique without any success, I have a S3, 4G+Wifi version. Any idea how to solve this problem ? Thanks !
super_paws said:
Thanks to everyone that helped! I have a working unit again!
Figured I'd write a few things here to help anyone else that might have a bricked device.
My device had a corrupt build.prop, so it was not able to boot the system partition at all. On the screen, it was stuck on the initial boot logo screen with the "Powered by Android" logo.
1) Download the above posted package for 2 assets: a) PAC file containing the stock firmware, and b) drivers for the SPD interface of the device
2) For a non-4G device which I had, I went to spdflashtool.com to download the Research Tool. This will allow you to flash firmware onto a non-4G device.
3) Ensure you have enough disk space (~3-4GB) on the same partition as the Research Tool app.
4) Open Research Tool and load the PAC file.
5) Follow the .doc file in the posted package for wiring up the USB interface to the SPD interface. Essentially, you are connecting USB to the 8-pin header on the device, and accessing data via the UART pins. Pin 1 on the 10-pin connector needs to be grounded in order to get the device into the mode for flashing.
6) Press start on Research Tool, and once completed, you should have a freshly flashed device
Click to expand...
Click to collapse

there is a complete instruction.
You're doing something wrong.
Write what and how you do

[Guide] Dasaita px6 MTCE_HA update/upgrade Android 10 to Android 11

After spending 2 days on the forums and softbricking my device for several times, here's my 2 cents about on how to do the upgrade from Andorid 10 to Android 11 or even to downgrade ... on the HA units from Dasaita.
First of all, a small disclaimer:
This worked for me, it might not work for you.
You might end up in bootloop, blackscreen, softbrick, be aware of this risk
My device is a Dasaita Max11, I wanted to downgrade to A10, in order to get Magisk and Hal9k v5 mod installed.
After purchasing modinstaller 3pro, and trying to install Andorid10 I ended up in a blackscreen. Hopefully @Hal9k_ will be able to fix this in his further releases.
Remember, this was ONLY tested and worked on a MTCE_HA device. A rather new model sold by Dasaita last december. If you have a HTC or other device this has no or litlle importance to you, since the images atached are ONLY for HA devices. Also, if you have an older Dasaita model, it might not work as described bellow:
What you'll need:
- a USB A to USB A cable (as short as possible)
- the purple usb plug cable (labeled carplay/android auto) that comes out of the back of de divice (this is the only one that recognized my device in bootloader mode. Feel free to try the others, in function of what configuration your device might have.
- driver assistant (see google drive link)
- flash tool (see google drive link)
- full system image of Android 11 or 10 regarding what you want.
- a pin or paperclip to push the reset button.
The procedure is rather simple:
1. Download and install the driver assistant (google drive link at the end), run it to install the drivers on your windows machine
2. Unpack rkdevtool and run the exe (google drive link at the end). At this point the program will display a huge message in the bottom part saying: "no devices found". That's good.
3. Connect the Usb cable to the HU and to the PC, while the device is turned off (like no power, not in sleep mode)
4. Push the reset button and keep it pushed. While doing this turn on the device. At this point if everything is setup correctly you should hear a notification sound from windows and RKDevTool should say: "Found one bootloader device".
4a) If you only hear the notification and the device is not found in boot loader mode by RKDevTool, check Device Manager and try to reinstall the drivers / install other drivers, try another USB port. (at this point, the usbA to usbA might be to long if the device manager shows: unrecognized device)
4b) If you hear no sound, RKDevTool still shows no devices: Turn off the HU, (really of, no power). After 10-30 seconds turn it on, while it is on, press the reset button and keep it pressed (even after side leds flashing) until the device enters bootloader mode and it is recognized by the RKDevTool.
4c) If none of the above work, switch the usb port on the HU, or try another combination of reset pushing (like trying to enter recovery)
4d) If the PC won't recognize the device in bootloader mode, it might be a situation in which the device is not capable of this, and you might need to take it apart and use the direct SOM flash method ... search the forums.
During step 4 the HU display should remain black, so the only indication of being in bootloader mode and connected to the PC, is the windows notification sound and the messege displayed by RkDevTool.
5)With the device in bootloader mode, connected to the PC, in RKDevTool go to the tab that says: Upgrade firmware. Click on the line(empty rectangle) that says firmware and browse for the desired android img. (10 or 11). See drive link. Attention: the zips from the drive MUST be unpacked and the update.img must be loaded in RkDevTool.
6)After selecting the desired update.img, click on the ERASE FLASH button, wait until the process completes. If everything goes well, the device should reboot in maskrom mode.
7)After the device enters maskrom mode, RkDevTool shoul display the message: "Found one MASKROM device". At this point, just click the UPGRADE button. The new android is flashed on the HU. When the process is finished the HU reboots ITSELF. If that doesn't happen after 1-2max, cut the power and power on.
It should boot in the new android.
Final thoughts after 2 days of thinkering:
This worked for me to downgrade from 11 to 10, and also to upgrade from 10 to 11. Be aware it might NOT work for you!
In theory, if one can get the device in bootloader mode it should work also to upgrade from andoid 9 to 10. This is just a theory and I did not test it.
The advantages of Android 10 over 11 are (for me):
- root access via Magisk (for the time being I could not root 11 with any of the tutorials found online)
- less crap and restrictions imposed by the growing Google censorship..
- the possibility to install the Hal9k v5 mod, one of the greatest and customizable mods ever made for MTCD/MTCE devices.
- using both 11 and 10 I could very certainly tell you, that (from my point of view), 11 has no advantages over 10, nor in stability nor in sharpness.
The images from the google drive are vivid for android 10 and max for android 11. Again, this are FULL images, not just OTA. I put them here after endless hours of searching the net. I respectfully thank to those that took the time to upload them on xda and dasaita forums.
Once you install the base 10 or eleven you can easily switch from vivid to max via update.zip flashed from an usbstick.
Also: there are many tutorials that involve a sdcard, sdcardtool and different combinations of zip images. I tested them ALL using the side sd card slot of the device. NONE OF THEM worked for me. I found the OTG flash method to be the fastest and most reliable, once I figured out how to connect de HU to my pc in bootloader mode.
PX6 MTCE_HA Android 10 full image, Android 11 full image, RkDevTool, Driver Assistant link: https://drive.google.com/drive/folders/1eigYrCKl8Z34KQxBoX3Q91Foy2K15CGm?usp=share_link

Nice! Do you perhaps know where to find the files for other headunits? I have a MTCE_HT and have no idea where to look!