Related
Here are my notes regarding the Eonon GA6164F and recovering from a black screen, cant boot, cant get into recovery.
Thanks to all the members and information on this site who i was able to piece together to come up with this solution.
I still dont know if my assumptions are totally correct, (please comment if i need to learn more) .
--
Back Story : My device was shipped with a Dec 2016 Android 5.1.1 build, and my steering wheel keys on my Camry were not all working.
Skip track and Back track were doing the same action, I tried re-learning/mapping in "WheelKeys Study" but nothing fixed it.
I resorted to using Vol - + for volume, Skip forward = skip track, MODE button (underneth) as = skip back.
I contacted Eonon about this, and they gave me a new Android build to try, update.img.
I wasnt able to update using the Settings - About - Software Update. (Error finding file).
I wasnt able to update using the standard recovery options (RES button, power etc.)
I did notice it was looking for dupdate.img.
I renamed my update.img file to dupdate.img and it was able to install via the Settings - About - Software Update.
The device rebooted , installed, then nothing... just a black screen.
I couldnt get any display up no matter what i tried.
After 24 hours or so of testing/trailing etc. I did manage to get it back working.
Im certain it was a bad update file because once i had it working again, i re-applied the update file i was supplied and sure enough, it broke it again.
These are my notes on how i recovered it.
--
Reboot into recovery on a healthy device
----------------
Hold RES
Press Power
Release RES (while still holding power)
Let go of power 1-2 secs after
Should reboot into recovery
---
Boot into recovery and restoring on a un-healthy device
----------------------
If cant boot into recovery
Download a Malaysk android build file (you may need to sign up to the hosting server site, and then add to downloads, then you can download to your computer from there)
Create bootable SD card using 'rockchip create upgrade disk tool v1.4'
(Run .exe as admin, dont check 'SD Boot', just leave 'Upgrade Firmware'
(If you cant see your USB drive, check that you have right clicked-Run as Admin in windows on the .exe)
Select Malaysk MTCD dupdate.img file
First post has download links
https://forum.xda-developers.com/android-auto/mtcd-discussion-questions-development/rom-malaysk-roms-mtcd-device-t3385309
Fully power off device (unplug from the back/or remove neg battery from car).
Insert new-bootable SD card into GPS slot
Plug device back in (or reconnect neg. battery cable to car)
- Device will boot into recovery and complain about no update file (thats fine) the Bootable SD card is just to get you into recovery.
{
"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"
}
Once in recovery, remove the GPS slot SD card and plug in a USB stick with an update.img
(my machine was looking for dupdate.img so i had to rename it).
Press power button to skip down the settings
Hold power button to select an option
Select 'Update system/mcu image from usb and clear all'
<processing>
Device reboots
Toyota logo shows (never progresses)
Press RES
Device reboots
Toyota logo shows
Android is starting (optimizing app XX of XX)
Malaysk recomends once the build is installed, to reboot into recovery once again using the normal method of buttons (RES + Power etc.) and 'wipe all data/factory and cache reset'
--
Now i am running a 10.8 build, because i was having trouble with the Google services on the latest, and i need to learn more about the 11.4 build and the MicroG stuff that replaces the Google services.
I am still suffering from the steering wheel controls issue, but at this point... i dont care...
I found i am getting a lot of "unable to read file" from the m4a files i have on my SD or USB card/stick and i need to learn more about how to get the steering wheel controls to action "other" music apps, i believe this is to do with the MTCD-Keys stuff, but going from what seemed like a dead device to this point, i want to wait a while before i start playing with it again.
I have added pictures in the thread, but they are linked to a photobucket, so i have also added them as attachments in case that photobucket account ever goes down.
Eonon Issue HELP!!!!
I have a Eonon Radio similar to this unit except it originally had 4.2.2 on it I recently tried to update it to 4.4.4 and mcu 2.81 which worked perfectly until restarting the car overnight. Radio booted into cannot find e:\
I then reverted back to 4.2.2 but I can get to the 4.2.2 recovery mode but every update.img I try to use only puts me into a reboot mode of the KiKat screen Maylay Mod Splash. Anyone out there can help suggest something?
I seem to have a half baked system that I can get into the recovery mode for 4.2.2. but the update.img says it cannot find it in the GPS sd card.
rogerradio said:
I have a Eonon Radio similar to this unit except it originally had 4.2.2 on it I recently tried to update it to 4.4.4 and mcu 2.81 which worked perfectly until restarting the car overnight. Radio booted into cannot find e:\
I then reverted back to 4.2.2 but I can get to the 4.2.2 recovery mode but every update.img I try to use only puts me into a reboot mode of the KiKat screen Maylay Mod Splash. Anyone out there can help suggest something?
I seem to have a half baked system that I can get into the recovery mode for 4.2.2. but the update.img says it cannot find it in the GPS sd card.
Click to expand...
Click to collapse
There are no Eonon radios, Eonon sell radios from several different manufacturers, the one in this thread is a Klyde - KLD.
If yours was 4.2.2./4.4.2 and MCU 2.85 then you have an MTCB unit and you need to try in the MTCB forums.
I've downloaded the rockchip create upgrade disk tool v1.4 and ran through your instructions. The HU won't boot off the SD card. Just sits there. If I remove the SD card, it immediately boots into the installed ROM. (I want to downgrade)
Hi
I tried reinstall the malaysk firmware but i rename dupdate.img as update.img and after reinstall now my device do not turn on, only show black screen like off and appear turn on nothing, i tried apply different methods of reset but nothing worked.
Help please!
Rodrizio said:
Hi
I tried reinstall the malaysk firmware but i rename dupdate.img as update.img and after reinstall now my device do not turn on, only show black screen like off and appear turn on nothing, i tried apply different methods of reset but nothing worked.
Help please!
Click to expand...
Click to collapse
Can you put it in recovery ?
typos1 said:
Can you put it in recovery ?
Click to expand...
Click to collapse
I don't know how exactly. I push the reset and power button in the sequence of first post but nothing happens. Only every time pushed the reset button the device light flashes but it's look like off
Rodrizio said:
I don't know how exactly. I push the reset and power button in the sequence of first post but nothing happens. Only every time pushed the reset button the device light flashes but it's look like off
Click to expand...
Click to collapse
Try making a bootable sdcard.
Guys your help pls! My head unit is stuck to the initial logo (Navigation System) and there seems to be nothing I can do to get into recovery to re-install the software. I have tried everything described above, no way to get into recovery with buttons, so I made and SD bootable card with various firmwares but the HU does not seem to read the card (I tried also with a USB stick, with no luck).
Is there anything else I can try to get it to work again?
My HU is a Px3 MTCE KGL 2 GB.
Thanks a lot for your help!!
Bobek82 said:
Guys your help pls! My head unit is stuck to the initial logo (Navigation System) and there seems to be nothing I can do to get into recovery to re-install the software. I have tried everything described above, no way to get into recovery with buttons, so I made and SD bootable card with various firmwares but the HU does not seem to read the card (I tried also with a USB stick, with no luck).
Is there anything else I can try to get it to work again?
My HU is a Px3 MTCE KGL 2 GB.
Thanks a lot for your help!!
Click to expand...
Click to collapse
Try @marchnz's recovery method.
typos1 said:
Try making a bootable sdcard.
Click to expand...
Click to collapse
I tried boot with a Sdcard bootable created with rockchip create upgrade disk tool (my sdcard is a 8gb size. I don´t know if the size make a issue) with the Malaysk dupdate.img file but nothing happend.
I follow the next steps.
I unplug from the back my device and insert the SD card bootable into GPS slot.
I plug again the device from the back and nothig, only the same screen black like off, I try differents combination of keys (press RES+Power ) and nothing....:crying:
It´s my device really dead? :crying:
Rodrizio said:
I tried boot with a Sdcard bootable created with rockchip create upgrade disk tool (my sdcard is a 8gb size. I don´t know if the size make a issue) with the Malaysk dupdate.img file but nothing happend.
I follow the next steps.
I unplug from the back my device and insert the SD card bootable into GPS slot.
I plug again the device from the back and nothig, only the same screen black like off, I try differents combination of keys (press RES+Power ) and nothing....:crying:
It´s my device really dead? :crying:
Click to expand...
Click to collapse
You shouldnt need to press anything, it should boot from the sdcard as soon as you turn it on. I would read @marchnz's unbricking threads if nothing its working.
Just want to know were I can find an "original" Rom for my Klyde PX5 MTCD unit.
I install Hal9k and it work like a charm but what if I have to send it back to Shenzhen?
Maybe I have to do this so before that I want to get it in original state.
Seelenwinter said:
Just want to know were I can find an "original" Rom for my Klyde PX5 MTCD unit.
I install Hal9k and it work like a charm but what if I have to send it back to Shenzhen?
Maybe I have to do this so before that I want to get it in original state.
Click to expand...
Click to collapse
Lol, no one send their unit back to China because it costs too much, its far easier and cheaper to repair it yourself, but there are factory ROMs around if you look, but I wouldnt bother looking unless you need to, cross that bridge (if and) when you come to it as they say.
Now it's a situation I really need that klyde mtcd px5 firmware.
Are there any hints or links?
Thanks ✌?
Yeah loads all over the forums.
Hi all!
Some days ago I urooted my TV android tv box with superSU and then I restarted it. From that moment when I plug the device it only reach the T9 logo (not the android one) and don't go further.
I've tried different ways to try to unstuck it, but nothing has worked.
I tried:
- enter recovery boot by holding the button in the av hole -> nothing happens
- install new firmware with adb sideload with both ubuntu and windows 10 -> always get errors (often error: closed, sometime other errors that at the moment don't remember)
- install new firmware with sd card using SDCard Installer -> the device doesn't boot when the sd is inserted
Moreover, with adb in ubuntu sometimes it recognises the device and I can enter the adb shell (but obtain errors when try any tipe of command), and sometimes don't (after adb devices I see list of attached devices: ??????????????? offline)
Now I'm thinking to try to install an ubuntu like on an usb pendrive...
I will be very grateful of any help/suggestion to how to revive my device :fingers-crossed:
Thank you!!!
Does this happen to be a pendoo model? I have a pendoo x10 MAX and i actually simply just installed supersu while it was rooted. Since then, I haven't gotten this thing to boot. Just stays on the boot screen the entire way. I wiped in recovery, knew that'd do nothing. I just wanted a root MANAGER. I tried Magisk, my favorite.. no go.. so then I went a bit old school.. so I tried ChainFire's SuperSU.. and THAT updated the SU binary! It said it succeeded.. it asked to do recovery install or normal install.. on phones, I've always done normal.. so I chose normal. Plus.. this thing has no custom recovery. I found it on Amazon. Overpriced, but great with the controller it had. It looks like I'll need a replacement and maybe a request to ask this guy if he could possibly NOT use something like KingRoot/KingoRoot/AmaraRoot or ANY One click root tool.. they just cause more bloatware, inciting boot issues and problems within the Android box itself. These One Click Root tools are out of control. It's to the point where I need to find a way in to adb and find the firmware for the latest version of this thing... X10Max from Pendoo.. I have not found a thing anywhere regarding firmware, and their website is ****. NOTHING *anywhere* on these things.. hell I'm about to return it as I bought it for $72. I have another one, same model.. wondering if the root method was different. About to boot that up and find out. I'll even swap the board. At this point.. he rooted it.. the WRONG way.. you can MOUNT THE /SYSTEM PARTITION IN RECOVERY. THIS IS ANDROID 9 we're talking about--the recovery supported by API v3.
This can and should have a TWRP custom recovery. If none exists, don't bother. As long as you can mount /system then you have a chance, at least, to root the damn thing.. which is why I'm still messing with it. I have another two weeks to return it. I'll give it another couple of days before I call it off and just switch out the good board for the bad one, return it, then return the other one and just use it until I find a way to use a custom recovery on this thing. There has to be.. unless there is no firmware available in sight (for an RK3318 or 3328, can't tell.. recovery mode says 3328, model name says RK3318. I see no difference at the moment aside from processor naming at this point--maybe speed?)
I'm still a nub with Android TV boxes so don't hold it against me for updating the damn root binary. If I could find a way to just reinstall the entire firmware and delete all previous stuff, I would. It would be worth it to learn. I would then mount /system in recovery and soldier on.
One little issue with this thing.. there's only one USB port that actually works. Same applies for the same exact product, a replication of the same thing.. was a "replacement" that still have/has the same qualities.
I've ranted enough. I vote more research into RK33xx processors and possible custom recoveries. I'm about to look for it based on only the device itself.
Note: Been stuck at boot screen ever since the binary was updated. I felt it was necessary to have a boot manager. I don't know where to even find the firmware. Can.. anyone point me in any direction? Something that MIGHT work on this thing? Android 6 or 7 would even suffice, return or no return, as "stuck on boot screen" will be my complaint. That's.. the actual complaint. I can't just *flash it* like the old days.. and maybe the original Android 9.0 firmware would suffice.. I don't know, but Pendoo.. wouldn't that be preferred?
You will need an SDcard to recover this box. I think the T9 32GB 4GB rom will do the job since its a cut down version.
Make a update SDcard and pop it in and power on the box. It will start the recovery on its own.
hello, sorry for my English I live in France I would have a question about the box: TV T9 RK3318, 4gb / 64gb. the problem is that the time is desynchronized on restart and creates problems to connect to applications when the time is out of order, I tried everything changed the time zone to deactivate and entered the time Manual it goes out of order all the time . is there a custom version or a version 10?
Very cook did I checked this out awhile back alot of good information that's for your contribution
I have 2 firestick 4ks.
Both identical in that they are rooted and debloated with (the same) various system apps frozen...
Both been running fine for a month or so...
Where I live I get frequent power cuts.
Yesterday after a power cut... one reboots correctly the other just goes to a black screen.
I connected it to my PC and ADB into it, I reenabled all apps via adb and rebooted, it just went to the same black screen.
So I booted to TWRP and reflashed RBoxes prerooted image, still nothing...
I then installed a stock image (Skel40's).... Still nothing.
Up to this point I had only been wiping Cache & Dalvik and dirty flashing.
I figured that there was a corrupted file that was affecting full boot, so I made the mistake of wiping data and installing stock again...
When I rebooted I had lost ADB!
I could still see the firestick in windows, however it just comes up as "Fire" in device manager with no ADB..
I grabbed an OTG cable and booted to TWRP and tried a few more times... each time gave exactly the same black screen (no orange amazon logo).
Finally I tried wiping system as well in case something was corrupted and reflashed stock.... Still nothing!
So I don't really know where to go from here... (I'm going to backup the other firestick and restore that over this one then reflash stock and see where that gets me...)
Does anyone have any ideas! I can get into TWRP, but I'm not sure it's wiping or flashing things correctly...
Any help greatly appreciated... Thx
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Michajin said:
Have you done any of the ideas listed in the other thread? Let me know if i can help #lockdown
Click to expand...
Click to collapse
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
tinybilbo said:
Hi Michajin...
Thanks for taking the time to help
I'll fill you in as to what I have and haven't tried...
I have wiped all standard partitions ( cache, dalvik, data, system) and reflashed both rooted and stock images *.*.6.8 and *.*.7.1
I think I may have wiped the Vendor partition, I'm not sure.
Under backup in TWRP I can see the Vendor partition, however under Wipe I see an extra 2 partitions (both) called storage and having not made a backup (I know!... )
I did'nt realise that the storage partition(s) may have been the Vendor partition.
After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal.
A couple of points that I can tell you...
I can boot to TWRP
I can reboot to hacked Bootloader
When I connect the firestick to my windows PC It's senses it straight away for a bout 10 seconds then drops it... It then senses it again and stays connected to my PC.
Windows recognizes it under portable devices as simply "fire" and an empty explorer window pops up, if I right click on the firestick in windows explorer (it shows as drive) I can pull a properties page which shows its serial number...!
On both my firesticks I have modified my build.prop for a faster boot which doesn't show the splash screen.
Both sticks were modified identically about a month ago and once setup had nothing added to them. They just get used for Kodi and catch-up TV apps.
I root them so as to boot directly into Kodi and freeze the bloat.
Both sticks have been rebooted multiple times.. This one failed after a powercut...
I been reading in the main rooting thread and have come across something about sticks not booting properly due to dm_verity failing and having to flash magisk before (or after... I'm not sure) the image flash.
I'm still reading through the thread so haven't tried anything yet... When i get head round what it is, I'll try.
The other 2 ideas I thought to try was to
1) flash an image directly from the bootloader (if possible.. I need to find more info on this) and
2) taking a backup of the working stick and trying that (It's in use a lot... due to #TotalLockdown! we're at 4 weeks with heavy police curfew! So I haven't had access to it)
If have any ideas or thoughts... I would be very grateful. Also I'm happy to try anything...
Click to expand...
Click to collapse
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Thanks guys for the replies, I couldn't respond earlier due to an 8 hr powercut today!
Pretoriano80 said:
It's really strange. Usually these steps should fix the issue :
1) Factory Reset from TWRP
2)Wipe System from TWRP
3) Flash full stock (non rooted) firmware
Of course, you could try flashing each image with hacked fastboot, or just boot, system and vendor with TWRP, which also have an option (install image) for that.
But you will have to convert system and vendor from sparse (.dat) to . img before being able to flash them.
Click to expand...
Click to collapse
Hi Pretoriano80
Yeah... It's really weird... I'm starting to think that the stick is damaged in some way, although the fact I can get in both the hacked bootloader and TWRP confuses me!
I've even wiped each partition 3 or 4 times (and rebooted back into recovery to remount) before writing the new image just to make sure.!
I'm ready to try anything at this point, since the stick is a brick at this point.
I'm not really sure how or what to flash from the bootloader, I'll read up a bit before I try especially your tips about converting from sparse to .img.
(I may have some further questions for you, if that's alright )
I will try to restore a backup from another stick first (if I can get access to that stick for long enough...)
Michajin said:
Wiping these should have taken care of you issue.
"After wiping cache, dalvik, data, system partitions and then flashing stock and rooted images multiple times and still getting a black screen... I tried wiping the one storage then the other and then finally Internal."
What stock did you flash from where?
When you flash stock are there any errors?
You should be able to take a backup from you other one also for other one (if you are doing a full backup/restore, i would wipe data and cache after restore)
Click to expand...
Click to collapse
Hi Michajin
Thanks again for taking the time to reply... much appreciated...
I have tried this stock image update-kindle-mantis-NS6271_user_2493_0003590962564
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
as well as a update-kindle-mantis-NS6268_user_2315_0003255372676 image (stock that I think i got from the main rooting thread)
I've also used Rboxes pre-rooted image mantis-6.2.6.8-rooted_r1
which was the image that worked fine on both boxes...
I'm happy to try any other image that you might have a link for.....
When I wipe the partitions there are no errors, except for when I wiped the storage partitions - they did throw up an error - although at this point I had already tried flashing new images at least a dozen times,
All the images flash without error as well!
I'm stumped... I've never had any android device brick before... (soft bricks many times! but never a hard brick), and it's weird since I have access to both the bootloader and TWRP.
Tomorrow I'll be able to get a restore image from the other stick, Then I'll try flashing from bootloader..
The only other thing i thought to try was to crack the case open and redo the the whole root procedure from scratch...
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
tinybilbo said:
Sorry to double-post...
However I wanted to add this as a separate post rather than an edit.
After playing with my firestick for a few days, during which I tried a working backup and erasing from the bootloader and then restoring multiple images (stock and prerooted), as well running the exploit again.
I realised that the OS was loading (I regained ADB after the full restore) despite not giving an image over HDMI (just a black screen).
I was about to give up when I happened to be going through the options in ADBLink and I found the screenshot button.
I gave it a try and to my surprise it sent back an image of the stick with a working OS/screen.
I even manged to navigate through the settings and do a full reset from within FireOS by taking screengrabs.
After the reset it still gave a black screen, I re-enabled ADB from TWRP and was able to verify that it had reset correctly...
From ADB I ran a logcat...
I'm not really familiar with logcat but a couple of things seemed to jump out...
Code:
1) 596 617 I DisplayManagerService: Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 480, modeId 4, defaultModeId 1, supportedModes [{id=1, width=1920, height=1080, fps=60.000004}, {id=2, width=1920, height=1080, fps=59.94}, {id=3, width=720, height=576, fps=50.0}, {id=4, width=720, height=480, fps=60.000004}], colorMode 0, supportedColorModes [0], HdrCapabilities [email protected], density 320, 213.0 x 216.0 dpi, appVsyncOff 1000000, presDeadline 16666666, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
2) 1145 1145 I AmazonHdmiServiceManager: resolution applied and hdmi turned off
3) 596 2438 E AmazonHdmiService: Settings client binder died.
Seeing that there were some issues with the HDMI display (Display device change to built-In screen? and HDMI turned off?), I used the screengrab to navigate my way to display settings which wouldn't allow me to change resolution
So to sum it up...
Everything is loading and running correctly, however I can't get an image over HDMI only by getting screengrabs via ADBlink.
Maybe something on the chip (HDMI output) is damaged, I've had the stick for a while and it's had heavy usage, or something has stuck in a toggled state.
I don't know....
If anyone has any ideas how to test it I have full root access via TWRP and probably can get it over ADB, so any help or commands to try would greatly appreciated....
Thanks :good:
Click to expand...
Click to collapse
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Michajin said:
Just checking, but have you tried another HDMI cable and different TV? Somehow it is not recognizing the format in the OS. TWRP uses a lower format i believe. I have had a power surge before damaging HDMI here, but I wouldn't get anything with it plugged in.
Click to expand...
Click to collapse
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
tinybilbo said:
Hi Michajin,
Thanks for your reply...
Yes I have tried multiple TV's, Monitors , and cables... Including the TV that it had been running on for almost a year...
I get frequent powercuts where I live, and often power surges when the power comes back on...
I do use surge protectors, however they don't always work....
One time the electricity board double one of the phases to 440v and knocked out £5k worth of equipment!
So between that and the humidity I think there is some minor damage to the stick... shame because it's still running.
I'm going to see if I can get a logcat from TWRP and see what it says about the HDMI output, not that it'll help...
Click to expand...
Click to collapse
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Michajin said:
So you get a display in TWRP, but go black after booting? I wonder if you can force whatever display mode and setting as used in TWRP as your display mode in FireOS. Had you tried another wall outlet (higher mA) ? A long shot at this point that you havent tried it....
Click to expand...
Click to collapse
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
tinybilbo said:
Correct, I can get a display with TWRP, but it goes black when it boots into FireOS (from which I can get screengrab via adblink of the stick displaying FireOS or whatever app is running).
Up until now (for almost a year) I've just used the power adapter that came with the stick, but it's a good idea to try something more powerful (I have a 2.4a one that I'll try a little later).
Another thing I'm going to try is "adb shell wm size ***x***" "adb shell wm density ***" command to change the resolution & pixel density (I think).
I hadn't thought about power being an issue up until you mentioned it (because so far it hasn't been), but maybe a component has (or is) failed (or failing) so it might need more power...
I can't try until a little later this evening, but at least I have something to try now cheers! I'll let you know how I get on....
Click to expand...
Click to collapse
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Skel40 said:
Hey I have a debloated clean stable rom that will be available soon. You can try that and you need to be sure to have either a usb otg or a hub for transferring this backup which will be titled ftvs4kdebloatedv1.0. Paste this folder to TWRP/BACKUPS/YOUR SERIAL #/ftvs4kdebloatedv1.0.
Click to expand...
Click to collapse
Thanks Skel40
I'll definitely give the clean rom a go
I have an OTG & Hub and the serial number already
hi guys
i have a firestick 2th gen model ly78pr its brick stock on logo , the problem is usb debbug was off and i tried with the key board and otg cable pressing alt + printscreen + i and it does not work as , i tried different combination and nothing help , also i connected to the pc and it does not work with adb it doesnt reconize , if anyone can help to find any solution
Hi all,
first post in this section, so be nice I have a very recent build Xtrons TQ700L unit that i have managed to soft(?) brick after rooting and removing a factory app ("Easy Connect"). On boot I get the initial logo, then after a long time a black screen that goes nowhere. I'm looking for advice on the best strategy to recover/rebuild it.
Hardware details...
build number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20200521.120545 test-keys
MCU version:
MTCE_GS_V3.53_3
As i understand it i have an "MTCE, GS" MCU and can ONLY flash MCU updates from the GS manufacturer. The MCU is probably not the problem here though.
I have a PX6, Android 10 build date of 20200521. Am I correct in saying i can flash any android 10 ROM designed for the PX6 that is newer than this date? Are the only differences between manufacturers cosmetic, like the nice launcher Xtrons supplies?
When i look on Yandex (https://yadi.sk/d/umCvHqCDzHccr), there is no PX6/Android 10 firmware at all from "GS", but there is from "HCT". Should i be looking at flashing the HCT/PX6/Android 10 firmware date 20200612 from the recovery menu? I can get to recovery easily enough by holding, then double clicking the reset button - i just dont know whether i should be flashing part of or the whole of the above package to fix my brick.
thanks.
So in case this helps anyone else, it was an easy fix. Baby steps below.
- grab the latest "Android 10", "PX6/RK3399" factory ROM either from threads here, or from Yandex. I found HA3_RK3399_10.0_ota(20200706).zip here on XDA.
- unzip the outer layer ZIP file and copy the inner "update.zip" to a micro SD card. The stock recovery systems dont allow any selection of ROM file names, so it must be update.zip.
- put the SD card in the "GPS" SD slot.
- with the unit on, reboot to recovery. My way was using a nail to hold the reset button in until the touch button lights began the flash, then quickly release and double click the reset again.
- in recovery, menu items can be scrolled through by either clicking the reset button, or (in my case) touching anywhere on the screen (easier).
- push and hold the rest button (or screen) to select the item.
- do a "wipe data/factory reset" (i guess) to be sure of cleaning out the old mess.
- then do "Apply update from SD card". it should automatically find the update.zip and apply it to all partitions.
- select reboot. Done.
The ROM i used was a "HA" branded generic ROM, so it didnt have the same launcher as my original "GS" (Xtrons) branded ROM. Xtrons wouldn't supply me with their stock ROM when i asked. The generic one was a little better anyway, since it has a stack of boot animations to choose from, whereas the Xtrons one only had the Xtrons logo. It also doesnt have the Easy Connect app, which is what I was trying to remove in the first place!
Additionally, i was able to obtain root easily by using the wifi ADB method here.
I did the same thing. Stupid app kept opening.
I don't have a micro sd card slot, hope it works with usb stick. Don't have one at the moment to try.
Same as yours.
Also, entering recovery mode you..
Hold reset button for 10 sec, release and immediately press it once.
I have a dicola px6 mtce
I'll update if i get it working.
Unit is a Joying JY-UQ124 PX3 - https://www.amazon.com/gp/product/B00XGEYU26
No idea what specific MCU and all that it is now as I bricked it several years ago when I accidentally put the wrong firmware on when attempting to go back to stock from a Malaysk ROM, and now only get black screen on power on with front panel lights on. Can't get into recovery, attempting to restore via SD card isn't working - never seems to start loading from the SD, screen just stays black.
Bought a new radio, put this one on the shelf, and now I'm trying to recover it again via the ST-LINK. Except that the only 5 holes empty on my board aren't marked, and I suspect it may actually be an unpopulated USB connector.
The PX3 SOM is a card edge RAM style connector, so I can't easily attach to header pins there either.
Do I have options here for recovery, or am I SOL with a paperweight on my hands?
SOM or MCU, photo show SOM. What is bricked, som or MCU
I'm _guessing_ it's the MCU? If the SOM gets bricked, wouldn't I still be seeing _something_ on the screen at boot?
It's been a while since I played with this one last, but I seem to recall that I accidentally tried to push the update image from my Sofia unit into this one, and didn't catch my mistake until after it was too late to do anything about it.
But honestly, I'm not really sure what exactly is wrong with it at this point, nor do I remember exactly what I did to it prior, other than trying to roll back to stock from a Malaysk ROM, and it didn't boot afterwards.