Hi all,
So I managed to successfully root and dump various bits of firmware etc over the past few weeks and generally had no issues(apart from the LED front panel lights not working(did at first), which is the main reason I was trying to rectify) - I have flashed from USB using a .bin also dumped preloader and rom etc via a scatter file using SP Tools after finding a rom entitled 8277L in the filenames, this worked perfectly(but still without the LEDS's) - Link to bought device(a cheap chinese one) - https://www.ebay.co.uk/itm/Single-O...e=STRK:MEBIDX:IT&_trksid=p2060353.m2749.l2649
Main issue: Now I have bricked it - I selected the format all part in SP-Tools thinking it would allow me to flash from fresh to stop the stock and TWRP recovery from timing out(I successfully ported TWRP over, but after about 30-40 seconds it was rebooting the device, bizarre!) - When the head unit is powered on it turns on the display but that is all, just a light black screen. I've tried recovering again via USB and SP tools but I think I'm almost out of luck. SP Tools doesn't read from the device or detect it, and yes I have the correct drivers installed under Windows. No screen swiped or button presses help in getting into any bootloader or update mode.
I am really hoping, anyone could help identify the UART pins on the board - yes I've now taken it all apart - in the hope I can flash a bootloader image which I guess is what is now wrong and has been erased??
I've really been digging into this and researching on Russian websites and getting lot's of interesting information including from XDA thankfully, but not this issue. I have included some pretty much hi res images, some are dark but I have redone some, everything is readable but I've googled and googled for model/part/serial numbers etc and have had no results that helped to indentify where I could potentially find the UART connection.
If anyone has the same unit or similar it would be great to share the knowledge so perhaps we can help bring the info together and help other debrick this device if there are any!
Many thanks, for anyone who cares take a look!
https://imgur.com/a/8Qz8ESP - all high res images
Same problem
I am facing the exact same issue.. Have you figured out any solution to your problem mate? Any help would be appreciated.
Related
Hello,
This is my first post on this forum so hello everyone! This forum has helped me numerous times with various devices, it is a valuable source of information and the people here seem very helpful. I have searched but cant find a thread relating to my current issue so I decided to start a thread and hopefully get some answers.
Ill try to keep this short while still providing enough information, first things first my device is a D802T 32GB model. Timeline of steps ive taken are as follows.
-Running Ressurection Remix ROM
-Downloaded ROM update and flashed with TWRP
-Device would get to "Upgrading Apps" step then restart half way through, back to upgrading app, restart again and so on
-Flashed stock ROM with LG Flash tool 2014, Froze at 49%
-Tried again to flash Stock ROM, this time it froze at 10%
-This caused the phone to loose Download mode & Recovery.... HARD BRICKED
-Phone would show as Qualcomm HS-USB 9006 in device manager
-Used Ubuntu to flash Partitions
-Must have flashed wrong partitions, after I flashed them the phone seemed to be 100% bricked with no signs of life at all
-Managed to jump pins on chip inside phone to get it into Qualcomm HS-USB 9008 mode
-Downloaded BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0 TOT File and extracted partitons
-Used BoardDiag to re flash Partitions I extracted from TOT file above
-Phone now seems 100% fixed except for one issue NO DISPLAY!
The phone boots, I hear the boot sound, the touch screen works as it should but I have no display whatsoever not even a black screen. My question is can flashing partitions cause you to loose display but the phone still boot and retain digitizer function?
I repair phones for a bit of extra money on the side so I know what im doing but I wanted another opinion or two before I go ordering parts. Does this sound like I may have damaged something while jumping the pins or could it be the partitions I flashed? Also if I have damaged something how can I tell if its the screen or if I damaged the charge port flex as this carry's the display signal. Keep in mind everything else works on that lower board such as the USB port etc. It seems a massive coincidence I loose display after flashing partitions but then again I was fiddling with the insides but I have done that many many times before so what are peoples thoughts on this?
I appreciate anyone who takes the time to help
42 views and no one has any ideas at all?
Sorry m8.....the last time i had 9006 brick i flashed correct partitions and got my phone working through TOT.......
You could try a new flex cable or even a new screen to diagnose whether its a hardware problem, black screen usually indicates damaged LCD connector pins on LCD panel or flex cable.
Also having "white tv noise" indicates a damaged flex cable.
Next time you have 9006, use this! https://www.youtube.com/watch?v=_d5b_osUTug
You don't need Ubuntu and you have less chance of super bricking.
Hey mate thanks for replying,
I did try that method but kept getting an error (something about cannot find file specified) so I just went the Ubuntu method. I did plan on just ordering a new screen but wanted to be a bit more certain of the issue first. I wish I had of kept my old damaged screens so I could fit one to determine if the screen really is the issue.
I didn't need to touch the bottom part where the LCD flex cables plug onto the board but stranger things have happened, unfortunately the G2 doesn't seem to be very popular in my area as I dont know anyone else that has one that I could possibly put my motherboard in to know for sure its the screen.
I might completely disassemble it and inspect it under a magnifier to make sure I haven't knocked any resistors or anything off the board, ill probably end up just ordering a screen as it seems the only way to know.
Thanks for your help
Has anyone any idea on how to get out of this situation. Device totally unresponsive, screen is black blank and displays nothing irrespective of button press combinations, including EDL. Not that its of any consequence now but this was achieved by my flashing a data file onto and overwriting the "aboot protected partition"
Device cannot be switched "on" and therefore is not recognized by windows device manager. Windows has all drivers installed i.e. ZTE - Qualcomm - Qualcomm EDL, although this is rather a moot point considering the device won't switch on.
The following files are still alive both on my device external SD card and in a windows "C:" folder --- B20 file, B27 file, B29 file, B15 file, plus a TWRP backup. To repeat myself all and every button combination has been used to no effect.
I rather much doubt that I shall get an answer to this question but has anyone any idea as to how I can get in the position where I can flash any of the above files?
Attempt to put it in edl mode I believe there is an unbrick guide somewhere around here. Aboot is related to bootloader so your phone is bricked.
Do you hear any sound from the PC when you connect the phone? This is particularly important because with the "wrong" driver enabled your device may not show in Device Manager, but it most likely, may have booted into EDL mode. Please check this and post back. If there's a sound on connect, there is hope. Nothing ZaDig and the new unbrick guide can't help you fix. I was in a similar hopeless situation a few weeks back but I resolved it with the help of the unbrick guide.
@george241312 ... @KwesiJnr ... I appreciate your answers and thank you for bothering to reply.
george ... Sad to say I was fully aware of what I was doing when I overwrote the "aboot" partition and anticipated ending up in something like my present situation. I have one final line of help to try before giving up all together.
Kwesi ... The only sound my device made was agonizing screams as I totally bricked it.
THANK YOU ALL BUT NO MORE REPLIES IF YOU PLEASE - CONSIDER THIS MATTER CLOSED ..... The device is dead due to my own stupidity and I will just live with that.
Try connecting the phone to another computer or wall charger ?
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?
Hi all, a need help. After an unsuccessful update, I received a bootloop. There are no physical buttons on the device. Found instructions for recovery through ANDROID TOOL. I connected it to the computer in maskrom mode, but I can’t find the firmware that needs to be uploaded in order for the device to work. Share a dump that suits me or give instructions on how I can restore the device.
They're all there in the MTCD forums.
Thanks for the answer, but all I found is different ota update.zip. And my device is loaded only in maskrom mode.
That's why I'm looking for a full recovery version.
Hi, you have to use the IMG file that contains the recovery and then update normally via OTA. For example, the IMG is:
CHS2_RK3399_10.0_IMG(20200424)
HCT7_rk3399_10.0_IMG(20200415)
OLS_rk3399_10.0_IMG(20201012)
Яндекс
Найдётся всё
disk.yandex.ru
I recommend reading this thread, you will find answers to your questions here:
[MTCD/E] Android 10 upgrade using official Free tools
To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads. First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported...
forum.xda-developers.com
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
s.danyliak said:
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
Click to expand...
Click to collapse
Erase first
I did, first cleared, reboot and firmware. The result is the same I read a lot of documentation, they wrote that there may not be enough power, but the power supply is 5A.
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
s.danyliak said:
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
Click to expand...
Click to collapse
I had the same problem I bricked my headunit (rk3399 PX6 Android 10) trying to recover root after updating magisk to 25.1 went into maskrom mode but device lost connection to my PC and flash fails at different percentage.
Cause ended up being the adapter i was using to power the device I used 12v 2A adapter
After switching to 12v 10A adapter it finished flashing. BUT make sure the chip has cooling like a heatsink or it will overheat during flash.
I changed the power supply to 10A. Installed cooling. The result is the same. The device reboots even if nothing is done.
Have you tested another USB cable? @s.danyliak
I have tried two different cables. But I connect via usb which is from the device kit and also the usb a - usb a cable is possible in this problem. There are also only 4 contacts, and for otg you need 5. I did not find information on the board I attached the photo.
Does anyone have any ideas ?
Ask seller for schematic and share here for feedback
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
s.danyliak said:
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
Click to expand...
Click to collapse
Short the two pads while powering on. Lift short after powering on
I tried, I can no longer enter maskrom with this method
Hi Folks,
I'm having RK3288 Board it was working fine until I decided to do an OS upgrade. Accidentally ROM didn't install correctly and now the device is nearly bricked.
I'm searching the web for the past 2 months to try any method which can help me to return the board to a working state.
The issue I tried to Install a new untested ROM over a working ROM and the device isn't booting UP, whenever I'm trying to boot nothing happens also RK Android Tool isn't able to detect the device. The issue is pretty big as I'm left with more than 20 unused boards.
Could you please suggest how to enter eMMC or EDL mode? Attaching a Snap of my Board.
HI ,
you can short the Pins 7/8 , right side , count from triangle in IMG .....402.jpg , for more Infos search on Freaktab ,
greetings / gefattern
Hi,
i have a similar Problem with a rk3288 based Chip.
I tried to do a firmware update, but it ends with an error. Now the RKDevTool only shows "No Devices found".
Can anybody give me a hint, how to solve this? The board seems to be powered, because the Power LED lights green.
Please look a the photo attached
thank you very much
A128/A139 said:
Hi,
i have a similar Problem with a rk3288 based Chip.
I tried to do a firmware update, but it ends with an error. Now the RKDevTool only shows "No Devices found".
Can anybody give me a hint, how to solve this? The board seems to be powered, because the Power LED lights green.
Please look a the photo attached
thank you very much
Click to expand...
Click to collapse
Please share pic from the back of the port also. don't attach PDF file make it JPG
dbzdivik said:
Please share pic from the back of the port also. don't attach PDF file make it JPG
Click to expand...
Click to collapse
Hi,
here are the pics. Many thanks
Has nobody any idea?