So we currently have a situation where it can be quite frightening to try anything cool on the Intel head units, since if you brick it, you might not be able to recover it.
I tried to pull this information out of the manufacturer of the units I've chosen to buy (Joying), but they started out playing retarded, then after about a hundred emails exchanged including links to videos of head units booting into recovery, and a detailed explanation of why it is needed (factory reset when android can't boot, for example), the last thing I was able to get out of them (because they landed themselves into an idiot infinite loop) was "Nice day, this is Candy from Joying, Thanks for your email and info, new model is muchly stable than old model, recovery not needed, don't worry, Hope you well-understanding, Any more questions pls feel free to contact us, Best regards, Candy".
<sarcasm>HOW BLOODY USEFUL!</sarcasm>
So lets use this thread to record known methods of booting into recovery.
If you are able to get into recovery, make note of the following details;
1) Brand and model number,
2) MCU firmware brand and version,
3) Exact reproducible process to boot into recovery.
One person here (@MMTK84) has apparently been able to get into recovery to the "no command" screen by plugging in an external keyboard and pressing some buttons on it.
This is for a Joying UL135N2: http://forum.xda-developers.com/showpost.php?p=69757832&postcount=133
Now the concerning thins about this particular procedure, is that it starts booting, and then reboots and goes into recovery. The reason this is concerning, is if it starts booting off the BOOT partition, registers the button clicks to reboot to recovery, and then reboots to recovery. This case could be bad if you happen to have a broken boot image. In other words, without further information, I wouldn't depend on it.
For... I'm not sure which unit, I found this on a Russian forum indicating pressing and holding the BACK button for about 10 seconds, releasing when the lights start flashing, and tapping it again: http://4pda.ru/pages/go/?u=https://...%3D140&usg=ALkJrhiZ8C2dCOO73ghthzievLV2mKtXyQ
*** further down in the same thread, someone else said the same process, but with the RESET button.
The reset button method might be able to apply to devices without physical buttons.
There are also TWO MORE buttons on all devices than what you see on the front panels -- the steering wheel interface buttons. Perhaps one or the other of those could, in some instances, trigger a boot to recovery?
So anybody who has these Intel head units, post your methods to achieve a boot into recovery.
Please keep the questions and discussions OUT of this thread, I'd like for it to be used exclusively to list SUCCESSFUL methods of booting into recovery.
More brainstorming;
If it becomes absolutely a problem and we find out that some devices *simply cannot* be booted into recovery, this could yield a solution;
http://forum.xda-developers.com/showthread.php?t=1522226
What that is, is an additional bootloader based on Das U-Boot, which adds in some of the missing multi-boot functionality. You stick that one in to the original boot partition, and instead of starting the kernel and Android, it instead launches a menu that lets you pick what you want to start. HOWEVER, given that this hardware is x86, we might actually have some luck with something more conventional, like GRUB.
Thanks for your work on this @doitright. I've been emailing with Joying as well and the language barrier can be frustrating.
With my previous MTCB unit I dealt with Hotaudio and they seemed to actually get useful information from their engineer rather than infinite looping at the front line customer service.
Hopefully a working recovery can be achieved independently of the manufacturer. I'm willing to test on my unit but trying not to brick it.
Unfortunately I haven't found a successful recovery method yet. But as a data point for my unit:
Its a Joying 8" non-MTC Intel unit with capacative buttons(only physical buttons are RST and POW).
MCU is dated 10/31 "Newlap", picture attached. Interestingly Serial Number in Settings > About Device reads all zeros: 00000000.
I'm getting to the same recovery screen as @MMTK84 with the laying down Android background. It first displays "No Command." soon followed by "Error!".
None of the usual recovery menu options are present to scroll up/down/select. Pressing the capacative buttons causes no change.
Short click POW does nothing, long click POW turns the screen off(short click POW again turns back on), Short or Long clicking RST reboots.
To get to recovery I used terminal on the unit itself: "su" then "reboot recovery". Unit is rooted per: http://forum.xda-developers.com/and...-intel-cpu-t3494083/post69648860#post69648860 It also works via WiFi adb: "adb connect <ip>" then "adb reboot recovery".
I have not yet found a hardware key combo to boot into recovery from power off. I tried the 4pda method you found with the RST button, held for 10 seconds but the lights never flashed, unit just rebooted after about 15 seconds of holding RST. I also tried this RST/PWR sequence that reportedly works for the 5.1.1 MTCD units but I can confirm it does not work on this non-MTC Intel unit: http://forum.xda-developers.com/showpost.php?p=66733286&postcount=2
Fingers crossed for a creative solution. U-Boot sounds promising.
I am also in a slump and unfortunately I actually need to enter recovery as my unit will not boot. I am waiting on the seller to respond and it's been a week and he still does not know. My unit is a MTCD Intel soft touch unit. Long press reset does nothing. Pressing any of the soft touch buttons while the unit is booting up also does nothing. That includes long press back, power, or anything else. If anyone comes across a way to enter recovery for a soft touch intel MTCD unit please let me know as mine is currently bricked.
Boot to recovery with USB keyboard (VIDEO)
1.) README:
As described in my post http://forum.xda-developers.com/showpost.php?p=69757832&postcount=133, here is the VIDEO how to enter recovery with hardware buttons (USB keyboard).
The device (Joying UL-135N2) was freshly resetted (factory settings), so it is not rooted.
The USB keyboard has QWERTZ design (Europe), but that is not important AFAIK.
After someone modified/adapted the "recovery.img" to TWRP (or similar), or someone patches the current recovery, we should be able to use this method to enter recovery when android is on a boot-loop..... :good:
2.) LINK to VIDEO:
http://sendvid.com/kyxa5xdz
Video created on: 12/05/2016
Device frmware from: 10/31/2016
3.) Feedback
MMTK84 said:
1.) README:
As described in my post http://forum.xda-developers.com/showpost.php?p=69757832&postcount=133, here is the VIDEO how to enter recovery with hardware buttons (USB keyboard).
The device (Joying UL-135N2) was freshly resetted (factory settings), so it is not rooted.
The USB keyboard has QWERTZ design (Europe), but that is not important AFAIK.
After someone modified/adapted the "recovery.img" to TWRP (or similar), or someone patches the current recovery, we should be able to use this method to enter recovery when android is on a boot-loop..... :good:
2.) LINK to VIDEO:
http://sendvid.com/kyxa5xdz
Video created on: 12/05/2016
Device frmware from: 10/31/2016
3.) Feedback
Click to expand...
Click to collapse
Good information there, but my only concern with this method, is whether the recovery boot is initiated from the bootloader, or from something in the primary boot partition. If it is initiated from the bootloader, we are golden. If it is initiated from something in the primary boot partition, this will not help with problems in the boot partition.
Have you tried using just the "e" button straight off the bat and skipping the alt-print?
FYI: My UL128N2's are *supposed* to arrive tomorrow, so I'll be able to start my own experiments with them. They're basically the same as your UL135N2, but all glass screen instead of buttons that click.
I greatly appreciate your information and your video, but unfortunately this did not work on my unit
Need4Camaro said:
I greatly appreciate your information and your video, but unfortunately this did not work on my unit
Click to expand...
Click to collapse
Important to note that YOUR unit is an MTCD, whereas MMTK84's is a Joying (FYT5009).
doitright said:
Important to note that YOUR unit is an MTCD, whereas MMTK84's is a Joying (FYT5009).
Click to expand...
Click to collapse
I did notice a few things while trying this.
#1 I have absolutely no power coming out of the USB ports. For example if I plug my phone into it, it does not even attempt nor do any other power consuming USB peripherals get power. I am concerned that if this is the case then even a USB keyboard may not work.
#2 when I press the reset button with ign off, then the lights on the unit flickers for 1 second then goes back off. Where as if I turn IGN ON then the units lights turn on and remain on for about 2 minutes before going off.
Need4Camaro said:
I did notice a few things while trying this.
#1 I have absolutely no power coming out of the USB ports. For example if I plug my phone into it, it does not even attempt nor do any other power consuming USB peripherals get power. I am concerned that if this is the case then even a USB keyboard may not work.
#2 when I press the reset button with ign off, then the lights on the unit flickers for 1 second then goes back off. Where as if I turn IGN ON then the units lights turn on and remain on for about 2 minutes before going off.
Click to expand...
Click to collapse
Have you tried to press and hold the reset button, and then turn on the ignition?
You need to try all kinds of different things.
hi
readme: my unit: Joying JY-UL135N2 2G RAM 32G
CPU: Intel ATOM QuadCore, GPU3D: Mali-400 MP4, RAM; 2G DDR3
MCU Version: 2016-10-31 14:30:43 JY_(NOR)_90_C9_7706_5009_CAN(GX)_Newlap
I have tried the keyboard method for booting to recovery and it was successful.
I have followed @MMTK84
1.) I hooked up a USB keyboard
2.) Pressed ALT(right one on the keyboard)+PRINT........keep it holding all the time
3.) Turned on power supply. Started pressing "E".
4.) The HU booted and the car logo appeared. After 10 seconds the HU reboots.
5.) When the logo appeared the second time I've released ALT+PRINT keys and began to press only "e" for about 10 seconds.
6.) Suddenly the "no command" screen appeared (this is according to user doitright the unusable recovery menu)
I didnt try by pressing "e" alone without pressing ALT+PRINT keys. If it is so will it make any good?
doitright said:
Good information there, but my only concern with this method, is whether the recovery boot is initiated from the bootloader, or from something in the primary boot partition. If it is initiated from the bootloader, we are golden. If it is initiated from something in the primary boot partition, this will not help with problems in the boot partition.
Have you tried using just the "e" button straight off the bat and skipping the alt-print?
FYI: My UL128N2's are *supposed* to arrive tomorrow, so I'll be able to start my own experiments with them. They're basically the same as your UL135N2, but all glass screen instead of buttons that click.
Click to expand...
Click to collapse
Are there any reported methods to recovering my unit?
https://www.aliexpress.com/store/pr...uad-Core-1-2G-4-1024/1396993_32747116176.html
I purchased a new Joying Unit as well. Will there be any way to install a recovery partition on this device?
http://www.ebay.com/itm/232157503276?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT
The method MMTK84 describes also works for the UL128N2 device.
Edit:
You can even skip step 5 and 6 of the tutorial. Just keep holding ALT + printscreen and pressing e. After the logo disappears release all keys.
If you hold alt + printscreen and start pressing F when it boots the joying logo disappears and goes black for a few seconds, goes white and boots into recovery.
Open up the case and you will see that the red led stops blinking when you do above procedure.
The keys e, i and f will reboot in recovery.
When pressing j the joying logo stays and the system does nothing, the led inside blinks all the time
When pressing c the led stops blinking and the system shutsdown
When pressing b the led goes off and the system hangs.
When pressing 0 the system shutsdown
The keys q,w,r,t,y,u,p,a,s,d,g,h,k,l,z,x,v,n,m do nothing.
I tried all combinations in combination with the alt + printscreen button.
I bricked the MTCD GS (XTRONS TL702AP) when trying to install one of the root kits (I knew that doing dd if... of=/mmcblk... is not going to be 100% safe...) and I managed to find how to reliably enter the recovery:
1. make sure that ILL is connected to ACC or BATT. Without it, touch buttons won't lit up and you won't know when to release RST
2. turn off the power completely, then turn it back on (both ACC and BATT), wait 1-2 seconds, then press and hold the RST button
3. wait ~5 seconds until the touch buttons start blinking, release immediately and press RST again shortly then release it
4. wait a few seconds and recovery shows up
When I bricked mine, the LCD backlight was blinking like crazy (1-2 Hz) and the display was showing the device booting up. Instead booting to the Android 'desktop', white screen appeared and unit crashed later on. When I managed to enter the recovery, the LCD backlight was solid immediately as I started pressing the RST...
extracted recovery partition from intel joying unit
extracted recovery partition from intel joying unit.
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121 -> /dev/block/mmcblk0p10
Code:
./fstab.zram
./dev
./seapp_contexts
./sys
./selinux_version
./sepolicy.ptest
./service_contexts
./res
./res/DVDBOOT_SOFIA.bin
./res/README
./res/keys
./res/images
./res/images/update_warn_en.png
./res/images/icon_error.png
./res/images/error_text.png
./res/images/icon_installing.png
./res/images/update_done.png
./res/images/stage_fill.png
./res/images/warning.bin
./res/images/installing_text.png
./res/images/progress_fill.png
./res/images/erasing_text.png
./res/images/font.png
./res/images/stage_empty.png
./res/images/fail_warn.png
./res/images/update_done_en.png
./res/images/warning_en.bin
./res/images/fail_warn_en.png
./res/images/warning_en.png
./res/images/warning.png
./res/images/progress_empty.png
./res/images/no_command_text.png
./res/images/update_warn.png
./sbin
./sbin/watchdogd
./sbin/busybox
./sbin/sh
./sbin/healthd
./sbin/e2fsck
./sbin/recovery
./sbin/newfs_msdos
./sbin/ueventd
./sbin/bootwatcher
./sbin/sqldebug
./sbin/resize2fs
./init.rc
./fstab.rk30board.bootmode.emmc
./fstab.rk30board.bootmode.unknown
./etc
./etc/recovery.fstab_emmc
./etc/recovery.fstab_nand
./data
./fstab.sofiaboard_nand
./default.prop
./init.bootmode.unknown.rc
./system
./fstab.sofiaboard_emmc
./init.bootmode.emmc.rc
./file_contexts
./property_contexts
./ueventd.sofiaboard.rc
./init.recovery.sofiaboard.rc
./tmp
./sepolicy
./proc
./ueventd.rc
./charger
./init
recovery_joying.zip extracted image with recovery in /sbin
recovery_joying_image image file.
fstab with common names for intel joying sofia units
Code:
#
# Copyright (C) 2013 Intel Mobile Communications GmbH
#
# Sec Class: Intel Confidential (IC)
#
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 /system ext4 defaults defaults
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 /data ext4 defaults encryptable=footer
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID070 /cache ext4 defaults defaults
#/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 /mnt/internal_sd vfat defaults defaults
/dev/block/mmcblk0p1 /mnt/external_sd vfat /dev/block/mmcblk0 defaults
/dev/block/mmcblk1p1 /mnt/external_sdio vfat /dev/block/mmcblk1 defaults
/dev/block/sda1 /mnt/usb_storage vfat /dev/block/sda defaults
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID076 /nvm_fs_partition ext4 defaults defaults
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID074 /misc emmc defaults defaults
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID071 /boot emmc defaults defaults
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121 /recovery emmc defaults defaults
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID122 /fwu emmc defaults defaults
#/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID122 /recoverym emmc defaults defaults
#/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID001 /mobilevisor emmc defaults defaults
#/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID114 /radio emmc defaults defaults
#/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID013 /splash_screen emmc defaults defaults
#/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID115 /mvconfig emmc defaults defaults
#/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID118 /secvm emmc defaults defaults
How to recover from a bad recovery.img flash:
In preparation of creating a modified recovery.img, I inadvertantly flashed over a malformed image file. The unit wouldn't boot at all! I thought I hard bricked the unit forever!
1. Disconnect ACC and BAT
2. Hold down the POWER BUTTON
3. Attach ACC and BAT
unit will boot.
After flash, unit refused to boot at all. Black screen. Probably trying to load from bad recovery partition. Nothing else would work, no Alt-PrnScrn combo, reset button, nada. Red light on sofia module would blink and then turn off. Research time. Then I saw that another MTCD unit was able to boot using this method. Success!
Note that this method will only work if your system partition is intact. If both recovery and system are hosed, I don't know of a way other than JTAG (possibly) to reflash the partitions.
Almost....
Has anyone tried a PC <-> PC OTG cable on one of these units?
I can reboot to recovery from the command line ( reboot recovery ). Getting into recovery mode isn't an issue, the problem is no way to access the unit once it reboots into recovery. From the recovery image, it looks like there is an adb process started from init and also wired USB support. I'm guessing you just need the right cable to connect.
gustden said:
Has anyone tried a PC <-> PC OTG cable on one of these units?
I can reboot to recovery from the command line ( reboot recovery ). Getting into recovery mode isn't an issue, the problem is no way to access the unit once it reboots into recovery. From the recovery image, it looks like there is an adb process started from init and also wired USB support. I'm guessing you just need the right cable to connect.
Click to expand...
Click to collapse
Is there anything special to the cable? I tried a USB A to A cable and neither linux nor windows detect it.
gtxaspec said:
Is there anything special to the cable? I tried a USB A to A cable and neither linux nor windows detect it.
Click to expand...
Click to collapse
An OTG cable has a chip in the middle so two USB hosts "think" they are both connecting to a device. A USB host knows a device is present, when the USB device pulls either d+ or d- line to ~3.3v to signal the connect speed. None of the signaling will happen with a straight A to A cable (connecting 2 host ports ).
I was going to get one and try it, just thought I would see if anyone else has before I buy one. Hopefully, I can find one locally so I can return it if it doesn't work.
Does anyone have experience with unpacking and repacking recovery images? I am unable to successfully repack recovery.img from the joying intel units. My repacked images will not boot! Arg!
Related
Hello everyone, I am new to the forums, so apologies if this is posted in the wrong section.
I purchased an android headunit, MTCB type, but immediately after installation unit does not work.
Unit is 1024x600 with rk3188. it is one of the custom fitted units to a civic, has volume knob (power button when pushed), tuning knob (also a button when pushed), disc eject button, back button, and small recessed reset button.
I am able to boot in recovery mode, and have tried everything from that menu..
I have installed different 5.1.1 firmwares, tried different MCUs, and nothing seems to work.
I always have the same problem where it displays the Andorid Auto Lollipop 5.1.1 screen, button lights are on, then it turns off.
Only way to reboot is to hold the reset and power button and boot into recovery mode.
When I connect to my laptop, it recognizes it as a rockchip device, but I am not sure if there is any troubleshooting I can try with PC connection.
On one occasion, after installing new firmware it went passed the lollipop screen and displayed the Android boot animation but hung at that screen forever.
After reboot, same issue persisted.
I have been unable to find my factory MCU, & manufacturer is of no help. My unit is: MTCB-KLD-V2.08
Installing the original MCU for 2.08 is the only thing I havent been able to do, because I can't find a download for it, so if someone has a link, that would be appreciated.
Otherwise, is this issue a factory defect, or is there some type of sleep mode it's entering? Any help would be greatly appreciated.
try wiping the data 3x and then reflash the update.img and mcu.img
the first boot will take 20mins or so (seems like it is forever)
I recently upgraded to the eonon GA6151 and was trying to flash update_RK3188_1024x600.img " booroondook RK3188" , well I renamed the file wrong to dupate.img instead of update.img I started flashing it and it was too late before I realized. Now the unit will not boot up or go to recovery. I can reset it and see the buttons flash like it wants to go to recovery but nothing ever appears on the screen. Is there a way to adb into this unit? Can I put files on a card and have it auto install them? Any help would be appreciated.
FIXED IT!!
I fixed it using this method. I realized after the fact that this new unit is MTCD not MTCB.
https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
I then had the error
https://forum.xda-developers.com/showpost.php?p=67309331&postcount=116
Which I fixed doing this
https://forum.xda-developers.com/showpost.php?p=67598154&postcount=319
I used the dupdate from here.
http://huifei.fs-fileserver.de/content/firmware/MTCD Custom ROMS - NOT FOR MTC-/RK3188/2017.02.21/
I loaded it onto the sdcard and the usb drive , the sdcard was created using upgrade disk tool and has to be 16gb or smaller fat 32. The usb drive just had a copy of the dupate.img file on the root of it.
To get into recovery on this unit do the below. http://www.eonon.com/Android-Car-GPS/Vehicle-Specific-GPS/GA6151.html
Press and Hold HOME AND POWER buttons
Press RESET while still holding HOME AND POWER
Let go of HOME AND POWER and then press HOME AND POWER down again and hold until the lights flash 3 times " is about 10 seconds to hold them "
Now Let Go of the HOME button then the POWER button the press the POWER button once "do not hold" and wait for it to boot into recovery.
This is the only method I found that reliably will get you into recovery. Make sure you use the GPS slot for any sd stuff you need to do in recovery.
Did you have to take the unit out of the car? I’ve made the bootable SD but nothing is happening.
Sent from my iPhone using Tapatalk
Hi
My unit is totally brick. It's like dead only when press reset button the lights flashes each time push but nothing happens i tried the above methods but can't enter to recovery mode nothing happen in the screen it's like off.
Please help
Rodrizio said:
Hi
My unit is totally brick. It's like dead only when press reset button the lights flashes each time push but nothing happens i tried the above methods but can't enter to recovery mode nothing happen in the screen it's like off.
Please help
Click to expand...
Click to collapse
From the posts and threads that relate to recovery, what options have you tried.
marchnz said:
From the posts and threads that relate to recovery, what options have you tried.
Click to expand...
Click to collapse
I tried push the buttons in the combination on the first post and tried too enter to flash the unit with a PC with the batch tool but can't achieve USB mode to flash My unit i don't know if need it Push something button and tried too create a boot sdcard with the tool but nothing. My unit it's like dead only when press reset button the lights flash each time
Hi,
my Philips 48PFS8109/12 made problems for a long time already when trying to power it on: it needed several attempts to cut off the power, reconnect the power and let it try to boot, cut off the power and reconnect again, etc.
Sometimes it entered the famous boot loop, sometimes it freezed, showing the Philips logo on screen, sometimes it only enabled the Philips logo on the camera and the screen remained black.
Over time it got worse: the more and more power cycles were needed to let it successfully boot.
But now it seems to be dead forever: most of the times it remains black now, only sometimes the logo appears on screen and I didn't managed to get it to boot successfully again.
Repair costs are around 500€ and would result in different features, due to no availability of the original hardware.
I tried everything I found on the internet to try to recover it:
- Let it boot to safe mode, a) using the joystick button on the back with pressing it in every direction and directly for over a minute when connecting the power, b) using the remote control OK and power buttons for the same time
- Let it boot from a FAT USB stick containing a) the wipe data tool, b) the firmware upgrade package, either in root directory, or in an "upgrades" subdirectory
- Connect it via USB A-to-A cable, and try to connect to it via "adb" command
Nothing helped/worked.
Problem is, that I am unable to enable any developer settings, as I am unable to get it running at all.
Question to the community: is there any other possibility to rescue the device (e. g. access the Android storage without the need to power it on, any secret way to clean the internal storage via hardware access/shortcut of some contacts)?
Its such a pity, the other hardware is so excellent, its just the Android system (or what Philips degenerated it to) that prevents the system from running.
Any help greatly appreciated.
Hello,
I had the same problem, let me explain what I do :
- Unplug power cable. Boot to safe mode using the joystick button on the back only with down arrow (without pressing it)
- Wipe data partition
- Flash the rom
- Flash android with the last update
- reboot
tontonfrancky said:
Hello,
I had the same problem, let me explain what I do :
- Unplug power cable. Boot to safe mode using the joystick button on the back only with down arrow (without pressing it)
- Wipe data partition
- Flash the rom
- Flash android with the last update
- reboot
Click to expand...
Click to collapse
Hi,
thank you for your answer. As I wrote, I already tried this in the past.
But I tried it again now and it still doesn't works. I hold the button for approx. 15 minutes, but it does not boot into safe mode. It only shows the Philips logo after some times, then goes black again. At the beginning it took long a time to first show the logo (approx. 1,5 minutes) and the logo was diplayed approx. 8 seconds, then later on the cycles got shorter and shorter. At the end, the logo was displayed for a second only.
Does s. o. knows if it is possible to just use the display? E. g. take some old Android hardware and connect it to the display only?
I don't want to throw this thing away, as the hardware is so excellent.... :cyclops:
Hi,
maybe the hardware upgrade kit is a solution for you:
https://toengel.net/philipsblog/201...pgrade-kit-fuer-2013er-2014er-und-2015er-tvs/
[email protected]
Toengel said:
[..] maybe the hardware upgrade kit is a solution for you: [..]
Click to expand...
Click to collapse
Hi and thanks for these informations.
This definitely is an option for me!
I already visited a certified Philips repair center and they offered me to replace the hardware which costs approx. 500 € all in all. I asked them for giving me the hardware to let me replace it on my own, but they denied it in answering that the new hardware has to be programmed, which is too complicated for an end user.
Using your informations, I will evaluate if this would be a doable approach for me.
Hi,
this "programming" is very easy... just putting 2 files on USB and start the TV... And 500 EUR is way to much... you should get it below 300 EUR.
[email protected]
So I've recently experienced some problems booting with my Xtrons TQ709IPL, so I thought I would share the method I used to fix it. This will probably work with other Xtrons devices (especially TE706PL since it just seems to be a TQ709IPL that comes with Android 10-- which oddly my TQ709IPL did as well when it was supposed to come with 9.0) and possibly other non-physical/touch button head units with similiar setups. This method is based on a post by @marchnz found here: [url]https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933[/URL] but fine-tuned to Xtrons unit.
To Preface this, I was unable to find the correct method to boot directly into recovery mode from RST. If anyone knows how on this unit, it'd be appreciated if they could share.
Beyond that, this also works if your device doesn't boot at all but the hardware buttons still react to RST being held in-- this will probably be due to a bad boot.img flash.
Required items:
Rockchip Head Unit with USB Port that can be recognized
Computer with Windows or Linux
USB-A to USB-A (or USB-C if your computer has the port)
Small pin, screwdriver-- something to push in the rst button
Rockchip Drivers and Android Tools: [url]https://github.com/rockchip-linux/tools[/URL]
ROM for your device in .img format: [url]https://yadi.sk/d/umCvHqCDzHccr[/URL]
Steps:
Install Rockchip Drivers and launch RKDevTool.
Plug Computer/Laptop into the Head Unit's Yellow USB-A port (this might be different on other models-- just try each out after doing the next step if it doesn't recognize your device)
Use a pin/small screw driver/etc to push in the RST button.
Hold button down until panel lights flash then stop pressing for about a second before pressing in again and holding (this should be done before the splash screen shows).
- If you did this successfully, your computer will now recognize your device in Maskrom mode. RKDevTool should show that a device is found.
Move over to the "Upgrade Firmware" tab and click firmware.
Select the .img file for your device.
Then click the "Upgrade" tab when the firmware has loaded.
- MAKE SURE YOU DO IT FROM HERE INSTEAD OF TRYING TO FLASH INDIVIDUAL IMGS IN THE "DOWNLOAD IMAGE" TAB! This caused my unit to not boot after I flashed the boot.img of my current firmware to it. Luckily, I was still able to get into Maskrom mode. So if you really want to try, make sure to use caution using that method!
It should now start flashing the firmware.
When it finishes, it should be recovered.
- Though, it failed and booted to recovery on mine once.
Done.
Hopefully, this will be of some use to some of you.
iamrance.asa said:
So I've recently experienced some problems booting with my Xtrons TQ709IPL, so I thought I would share the method I used to fix it. This will probably work with other Xtrons devices (especially TE706PL since it just seems to be a TQ709IPL that comes with Android 10-- which oddly my TQ709IPL did as well when it was supposed to come with 9.0) and possibly other non-physical/touch button head units with similiar setups. This method is based on a post by @marchnz found here: [url]https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933[/URL] but fine-tuned to Xtrons unit.
To Preface this, I was unable to find the correct method to boot directly into recovery mode from RST. If anyone knows how on this unit, it'd be appreciated if they could share.
Beyond that, this also works if your device doesn't boot at all but the hardware buttons still react to RST being held in-- this will probably be due to a bad boot.img flash.
Required items:
Rockchip Head Unit with USB Port that can be recognized
Computer with Windows or Linux
USB-A to USB-A (or USB-C if your computer has the port)
Small pin, screwdriver-- something to push in the rst button
Rockchip Drivers and Android Tools: [url]https://github.com/rockchip-linux/tools[/URL]
ROM for your device in .img format: [url]https://yadi.sk/d/umCvHqCDzHccr[/URL]
Steps:
Install Rockchip Drivers and launch RKDevTool.
Plug Computer/Laptop into the Head Unit's Yellow USB-A port (this might be different on other models-- just try each out after doing the next step if it doesn't recognize your device)
Use a pin/small screw driver/etc to push in the RST button.
Hold button down until panel lights flash then stop pressing for about a second before pressing in again and holding (this should be done before the splash screen shows).
- If you did this successfully, your computer will now recognize your device in Maskrom mode. RKDevTool should show that a device is found.
Move over to the "Upgrade Firmware" tab and click firmware.
Select the .img file for your device.
Then click the "Upgrade" tab when the firmware has loaded.
- MAKE SURE YOU DO IT FROM HERE INSTEAD OF TRYING TO FLASH INDIVIDUAL IMGS IN THE "DOWNLOAD IMAGE" TAB! This caused my unit to not boot after I flashed the boot.img of my current firmware to it. Luckily, I was still able to get into Maskrom mode. So if you really want to try, make sure to use caution using that method!
It should now start flashing the firmware.
When it finishes, it should be recovered.
- Though, it failed and booted to recovery on mine once.
Done.
Hopefully, this will be of some use to some of you.
Click to expand...
Click to collapse
Please help, I'm about 2 seconds from getting a new HU...
I also have the Xtrons TQ709IPL. I installed the drivers, but no matter what I do, when I finally get the HU into the correct mode, the USB insertion noise happens but then windows tells me that the device failed to install correctly. I also am unable to manually install the driver. This was on Windows 10, but I also tried it on Windows 8.1 and Windows7 all with the same results.
I must be doing something different than you, but I followed your instructions?
Ok, my USB cable was too long, I was using an extender to get to my laptop on my workbench from my car. If anyone else has this problem, make sure your USB cable is short. I am in now!
Next question, I have the TQ709IPL just like you. So which ROM do I need from the link you provided?
Hi - I was installing some external memory, a 16gb Sandisk USB memory stick. The fire cube recognised it straight away & I proceeded to format it as ‘internal storage’. I got a msg to say that the format was complete. The TV screen then flashed & the next thing the fire cube re-booted & all I have is an Android Recovery screen. I’ve tried the mute + the volume down for 60 secs. None of the keys on the remote are doing anything nor are any of the buttons on the fire cube.
Can anybody help or is this bricked due to the software version?
All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.
Finnzz said:
All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.
Click to expand...
Click to collapse
Hi - Yes, I’ve tried the mute & volume down button on the cube & held down for 60+ seconds. Nothing happened. It does seem to know when a key is pressed because if I press the right hand button with a circle on it, the ‘try again’ turns green. I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…
Clubcard said:
if I press the right hand button with a circle on it, the ‘try again’ turns green.
Click to expand...
Click to collapse
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Clubcard said:
I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…
Click to expand...
Click to collapse
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.
Functioner said:
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.
Click to expand...
Click to collapse
Hi - It’s unplugged as all the cube is doing is flashing blue all the time. When I apply power, I get the FireTv logo & then the Android recovery screen comes up. The cube doesn’t do anything. When the ‘try again‘ hightlights green, nothing I do will make it reboot. I’ve pressed every button on the remote & all the buttons on the cube.
The USB on the back is a micro USB & all I have is a USB keyboard which is why I had to connect it via the OTG I had. I’ve attached a photo. I do have a different OTG cable which has a micro USB input for a power supply. I’ve tried that & the keyboard has power but I still can’t select the factory reset..
I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.
Functioner said:
I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.
[/QUOTE
It’s very good of you to do that but it’s rather extreme. What if you brick yours?
Click to expand...
Click to collapse
My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.
Functioner said:
My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.
Click to expand...
Click to collapse
Hi - Have you managed to sort anything out yet?
tengo el mismo caso lograste resolverlo?
Clubcard said:
Hi - Have you managed to sort anything out yet?
Click to expand...
Click to collapse
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.
Functioner said:
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.
Click to expand...
Click to collapse
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..
Clubcard said:
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..
Click to expand...
Click to collapse
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.
Functioner said:
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.
Click to expand...
Click to collapse
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..
Clubcard said:
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..
Click to expand...
Click to collapse
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?
Pro-me3us said:
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?
Click to expand...
Click to collapse
Hi - Will check that out later when I finish work. Thanks..
Clubcard said:
Hi - Will check that out later when I finish work. Thanks..
Click to expand...
Click to collapse
Hi - When I re-read your Instructions I couldn’t figure out how to do what you advised. Anyway I made what must have been my 10th phone call to Amazon. It went from them offering me 15% discount, then 20% & then 30%. I said no to all & finally after a lot of polite badgering, they have allowed to me buy a new one & I have an email from Amazon stating that I will get a full refund when my cube is delivered tomorrow
Clubcard said:
they have allowed to me buy a new one
Click to expand...
Click to collapse
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.
Pro-me3us said:
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.
Click to expand...
Click to collapse
Hi - Yes, it’s a 3rd Gen I’m getting. I had the downloader app & had kodi & few other apps on my 2nd Gen. Will this 3rd Gen not allow me to have any of these 3rd party apps on?