[GUIDE] Continuous restart / bootloop fix for Philips Android TV with Wipe Data Tool - Philips, Sony, TCL Android TV

Use this tool in connection to:
*Get rid of cyclic spontaneous reboots of your Philips Android TV...
*Recover your Philips Android TV in case you get continuous boot-loops, where Philips and/or Android logo does not even show up...
*Stop your Philips Android TV to wake up spontaneously from stand-by mode...
*Delete all data and refresh TV's android system
Part A - Wiping Data (All data/apps/settings will be deleted):
1. Unplug the power cord from the power outlet.
2. Press and hold arrow "Down" on the joypad at the back of the TV.
3. Afterwards re-plug the TV to the power outlet, wait 10 seconds and enter "Android System Recovery" mode. Please not that on some models of Philips Android TV's joypad does not trigger "Android System Recovery" therefore use ADB command: adb reboot recovery (help)
4. Download ZIP file containing "WipeDataTool.upg" to your PC and unzip it to the root of USB drive.
5. It is recommended to disconnect all other USB devices from the TV.
6. Connect USB drive with a prepared file to the TV.
7. Select the menu item "Apply update from external storage" with up/down buttons on remote control and start the "WipeDataTool.upg".
8. Wait until you see the recovery menu again with confirmation message "WipeData completed".
9. Use remote control to select "Reboot system now". TV needs to boot into the operating mode.
Warning! If the TV will continue to restart, contact your local Philips technical support to further address your Philips Android TV issue
Part B - Reinstall TV (All data/apps/settings will be deleted):
1. Reinstall the device via Setup - General Settings - Reinstall TV
2. Select "Yes".
3. After displaying initial settings on TV screen, remove the power cord from the outlet for 10-15 minutes.
List of Android Philips TV's with chassis QV15.1E LA (See label on the rear panel of the TV):
43PUK7100 / 12, 43PUS7100 / 12, 43PUS7100 / 60, 43PUS7150 / 12, 48PUS7600 / 12, 48PUS7600 / 60, 49PUK7100 / 12, 49PUK7150 / 12, 49PUS7100 / 12, 49PUS7100 / 60, 49PUS7150 / 12, 49PUS7150 / 60, 49PUS7170 / 12, 49PUS7180 / 12, 55PUK7100 / 12, 55PUK7150 / 12, 55PUS7100 / 12, 55PUS7100 / 60, 55PUS7150 / 12, 55PUS7150 / 60 , 55PUS7170 / 12, 55PUS7180 / 12, 55PUS7600 / 12, 55PUS7600 / 60, 55PUS8700 / 12, 55PUS8700 / 60, 65PUK7120 / 12, 65PUS7120 / 12, 65PUS7120 / 60, 65PUS7600 / 12, 65PUS7600 / 60, 65PUS8700 / 12, 65PUS8700 / 60
List of Android Philips TV's with chassis QV14.1E LA (See label on the rear panel of the TV):
48PFS8109 / 12, 55PFS8109 / 12, 55PUS8809 / 12, 48PFS8109 / 60, 55PFS8109 / 60, 55PUS8809 / 60, 48PFS8159 / 12, 55PFS8159 / 12, 55PUS8909C / 12, 48PFS8159 / 60, 55PFS8159 / 60, 55PUS9109 / 12, 48PFS8209 / 12, 55PFS8209 / 12, 55PUS9109 / 60, 48PFS8209 / 60, 55PFS8209 / 60, 65PUS9109 / 12, 49PUK7909 / 12, 55PFS9999 / 12 65PUS9109 / 60, 49PUS7909 / 12, 55PUS7909 / 12, 65PUS9809 / 12, 49PUS7909 / 60, 55PUS7909 / 60, 65PUS9809 / 60
List of Android Philips TV's with chassis QM15.2E LA (See label on the rear panel of the TV):
32PFH5500 / 88, 40PFT6550 / 12, 50PUT6400 / 12, 32PFH6500 / 88, 40PUH6400 / 88, 50PUT6400 / 60, 32PFK5500 / 12, 40PUK6400 / 12, 55PFH5500 / 88, 32PFK6500 / 12, 40PUT6400 / 12, 55PFK5500 / 12, 32PFT5500 / 12, 40PUT6400 / 60, 55PFK6510 / 12, 32PFT5500 / 60, 48PFH5500 / 88, 55PFK6550 / 12, 32PFT6500 / 12, 48PFK5500 / 12 , 55PFK6570 / 12, 40PFH5500 / 88, 48PFT5500 / 12, 55PFT5500 / 12, 40PFH6510 / 88, 48PFT5500 / 60, 55PFT6510 / 12, 40PFH6550 / 88, 50PFH6510 / 88, 55PFT6510 / 60, 40PFK5500 / 12, 50PFH6550 / 88, 55PFT6550 / 12, 40PFK6510 / 12, 50PFK6510 / 12, 55PUH6400 / 88, 40PFK6550 / 12, 50PFK6550 / 12, 55PUK6400 / 12, 40PFK6560 / 12, 50PFK6570 / 12, 55PUT6400 / 12, 40PFK6570 / 12, 50PFT6510 / 12, 55PUT6400 / 60 , 40PFT5500 / 12, 50PFT6510 / 60, 65PFK6520 / 12, 40PFT5500 / 60, 50PFT6550 / 12, 65PFK6570 / 12, 40PFT6510 / 12, 50PUH6400 / 88, 65PFT6520 / 12, 40PFT6510 / 60, 50PUK6400 / 12, 65PFT6520 / 60
Other models of Philips Android TV
You can find Wipe Data Tool on your TV's filesystem in folder \etc\virgin
Download it to USB, rename it to "wipedatatool.upg" and you are good to go...
{
"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"
}
NOTE FOR SKEPTICS: Above guide and below attached files are made by Philips [TP Vision]. Additionally, UPG files are encrypted with unique key known only to the manufacturer confirming their originality. . .
SOURCE: Philips Support website - Russia (благодарю/Thanks for great tool)
DEC2020: Links for all ZIP files below:
wipedatatool QV15.1ELA.zip
uloz.to
wipedatatool QV14.1ELA.zip
uloz.to
wipedatatool QM15.2ELA.zip
uloz.to

hello , I have Philips S231C4AFD/00 and I need to enter in recovery to wipe it, but I don't know it has some touch buttons , i tried button down + plug in with charger , it power but no recovery , can you help me please?

dfani511 said:
hello , I have Philips S231C4AFD/00 and I need to enter in recovery to wipe it, but I don't know it has some touch buttons , i tried button down + plug in with charger , it power but no recovery , can you help me please?
Click to expand...
Click to collapse
This is though question as there is no service manual for your device available online.
If I am in your shoes, I would be trying different combinations of the "press+hold" buttons during booting.
I would also try to connect to the device from PC via ADB using Micro-USB (Mini-A) at the back to see whether the device is listed...

ovso said:
This is though question as there is no service manual for your device available online.
If I am in your shoes, I would be trying different combinations of the "press+hold" buttons during booting.
I would also try to connect to the device from PC via ADB using Micro-USB (Mini-A) at the back to see whether the device is listed...
Click to expand...
Click to collapse
should I use a keyboard or only the buttons from touchpad ?

dfani511 said:
should I use a keyboard or only the buttons from touchpad ?
Click to expand...
Click to collapse
I would use ONLY buttons directly on device. Keep in mind that you may have to keep button(s) pressed for longer period of time (roughly up to minute). Start step by step with individual buttons and than logical combinations of two etc.

Doesn't work on 40PFH5500
Anyone successful on on 40PFH5500? I trying this about half hour (power cord, joystick) but tv won't boot to recovery mode, just android OS is restarting :/.
Software v. QM152E_000.005.210.000 (bugly version finally removed by philips from support site ).

xonv717 said:
Anyone successful on on 40PFH5500? I trying this about half hour (power cord, joystick) but tv won't boot to recovery mode, just android OS is restarting :/.
Software v. QM152E_000.005.210.000 (bugly version finally removed by philips from support site ).
Click to expand...
Click to collapse
Many users ran into the same problem on updated QM152E firmware...
For now you can enter recovery mode via ADB command from you PC: adb reboot recovery
Hopefully TP Vision developers will re-enable recovery mode for QM15.2E LA chassis in the future firmware updates via joypad again...

ovso said:
Many users ran into the same problem on updated QM152E firmware...
For now you can enter recovery mode via ADB command from you PC: adb reboot recovery
Hopefully TP Vision developers will re-enable recovery mode for QM15.2E LA chassis in the future firmware updates via joypad again...
Click to expand...
Click to collapse
Thanks it works like that. Very simple now to put into recovery via adb.

flrazvan said:
Thanks it works like that. Very simple now to put into recovery via adb.
Click to expand...
Click to collapse
Issue with restart was aolved but the lag on audio still there on my 40pfh5500 .

flrazvan said:
Issue with restart was aolved but the lag on audio still there on my 40pfh5500 .
Click to expand...
Click to collapse
Happy to hear that restarts are solved. Audio lag is known issue reported by users for example here. Philips claims, that they will release new firmware for your TV during upcoming week, so I hope they will fix your issue. I am happy that I do not own TV with QM15.2E LA chassis...

Last week, a new firmware version was released that should fix this issue according to the philips helpdesk. Updated Today, so far so good! Ver:000.005.234.010 28apr2016.
Update: a factory reset was necessary after the update to get rid of the random reset. No random reboots since (12h and counting)

quazar666 said:
Last week, a new firmware version was released that should fix this issue according to the philips helpdesk. Updated Today, so far so good! Ver:000.005.234.010 28apr2016.
Click to expand...
Click to collapse
If yes, that would be than only solved for chassis QM15.2E LA, but other chassis are still likely to be affected...

Question, is this any different than reinstalling TV from menu? I have constant reboots, but after a minute or two, so I have enough time to choose reinstall TV from menu. I did it that way like 5 times and still have issues.
Will try this guide anyway latter today when I'm home, but I thought I ask anyway.

GasperG said:
Question, is this any different than reinstalling TV from menu? I have constant reboots, but after a minute or two, so I have enough time to choose reinstall TV from menu. I did it that way like 5 times and still have issues.
Will try this guide anyway latter today when I'm home, but I thought I ask anyway.
Click to expand...
Click to collapse
This is different than TV re-installation. This will basically, clear all cache data even from system apps. After TV re-install cache of system apps already contains 'bloatware' data responsible for restarts...

ovso said:
This is different than TV re-installation. This will basically, clear all cache data even from system apps. After TV re-install cache of system apps already contains 'bloatware' data responsible for restarts...
Click to expand...
Click to collapse
Great news, thanks. I hope I can avoid taking TV to service 50 km away.

GasperG said:
Great news, thanks. I hope I can avoid taking TV to service 50 km away.
Click to expand...
Click to collapse
This little utility fixed our TV during the 2 weeks waiting time for Philips service (just around Easter). My wife was so happy she could watch her tv-novela stuff Anyways, give us a feedback here if it worked for you...

Call me stupid, but how do I enter recovery mode, is it possible only with ADB on QM15.2E? How can I connect it as there are only normal USB (Type-A?) plugs on the back of the TV? Non-standard cable?

GasperG said:
Call me stupid, but how do I enter recovery mode, is it possible only with ADB on QM15.2E? How can I connect it as there are only normal USB (Type-A?) plugs on the back of the TV? Non-standard cable?
Click to expand...
Click to collapse
Yep, via ADB command: adb reboot recovery ,since certain firmware version...

Still problems with reboot into recovery. I enabled developer mode on TV (click "Build" 7x times), I enabled USB debugging, enabled unknown sources ...
Connected USB type-A M/M in any of the 3 ports on TV with no luck, there was even no sound "ding" when I hocked it up. Also tried with micro USB from Windows 10 tablet to TV, no luck. "ADB devices" returned none. I tried the same setup on my Android phone and I could connect with ADB straight away.
Suggestions?

GasperG said:
Still problems with reboot into recovery. I enabled developer mode on TV (click "Build" 7x times), I enabled USB debugging, enabled unknown sources ...
Connected USB type-A M/M in any of the 3 ports on TV with no luck, there was even no sound "ding" when I hocked it up. Also tried with micro USB from Windows 10 tablet to TV, no luck. "ADB devices" returned none. I tried the same setup on my Android phone and I could connect with ADB straight away.
Suggestions?
Click to expand...
Click to collapse
Philips Android TV does not support USB OTG connections, therefore only way to connect to ADB is over wifi.. TV will be listed as emulator.
Use command: adb connect 192.168.1.2 (this is your TV's IP address) , than: adb shell and you are good to go...

Related

[FAQ] General FAQs + Quick guide to MTK 6516 android phones repair flasher etc...

[GUIDE]Chinese phone CPU MTK6516 based Windows Mobile Android
MTK Android Pattren Unlock [No Need any Box or PC]
Q: How do hard reset?
A: 1. Connect the cable from the computer while holding down the "-" - the volume below the sidebar.
2. Turn on your phone
3. Phone will boot in FACTORY MODE
4. Select the Clear Flash using the same button "-"
5. Confirmed by pressing the button "Menu" button on the left touch of a round button.
Q: How do hard reset?
A: 1. Connect the cable from the computer while holding down the "-" - the volume below the sidebar.
2. Turn on your phone
3. Phone will boot in FACTORY MODE
4. Select the Clear Flash using the same button "-"
5. Confirmed by pressing the button "Menu" button on the left touch of a round button.
Q: How to get into the engineering menu?
A: Dial * # * # 3646633 # * # *
Q: What is behind the right of the crack dynamics at the front of the phone? Image
A: The sensor ear (absorbs / locks the screen during a conversation).
Q: Were you able to run Skype?
A: Not yet. Skype for Android can run in the presence of not less than percent of 600 MHz.
At the same time, you can run Skype Beta - will only work as a messenger.
Q: Do not load an application from Android Market / error prirabote with supermarkets. What should I do?
A: Perform a factory reset to the factory.
In: Tache begins to react strangely when charging. What should I do?
A: The problem of poor assembly of the battery charger. Change it to any brand.
Q: Nechayno removed the lower horizontal menu - namely, removed the browser, phone book and an icon with a pipe (for calls), as now all be back?
A: The menu button, add, LauncherActions, TCI / close sliding cover.
Q: Where can I get the correct working Navitel?
A:
1. Read thread p. 41-42
2. I give a link to the archive in which he invested with apk Navitel 5.0 + card working for him. Detailed instructions for installation.
Installation
- Apk scores on the memory card (to adjust. Apk NOT from Android Market, need to Settings> Applications> pukto on "Unknown sources" tick).
- Using a file manager (eg ES conductor, in a market can be downloaded free of charge) and start waiting for the completion of the installation.
- When you first start the program creates a folder on your memory card NavitelContent.
- In the folder NavitelContent / Maps, you can copy the entire map or atlas.
Installation Procedure RePack:
install apk
NavitelContent - copy to SDCard
NavitelContentMaps - copy the map
NavitelContentSkins - copy skins
NavitelContentSpeedcams - copy spidkamy
All taken from the famous resource 4pda.info
Deposit Files
http://ge.tt/7BZKdCA
�качать NavitelContent.rar
Then you need to download a map to your country, which would be the correct extension (for Navitel 5.0.
extension must be. nm3
Map of Ukraine
Q: How do I get the right root?
A: example program z4root (works on 2.1 and 2.2).
Q: How do I know I got a Root-law?
A: If you can install rootexplorer, see the folder init, in / data / app to see how many meters above Mem, root permissions are granted.
It is also useful to read the FAQ for Android OS
Drivers
Deposit Files
Upgrade to A3 Android 2.1
A3TAndroid20101224.zip - depositfiles.com | ge.tt | yabadaba.ru primary firmware A3 Android UI, with no Russian language
A3TIphone20101224.zip - depositfiles.com | ge.tt | yabadaba.ru firmware A3 + + (with the Apple UI and the Russian language, but not to start an apple, and Android)
A3 + A3 + firmware (with the Apple UI and the Russian language, starting in the apple)
A3T android_update20101127 Android shell but the language is only English and Chinese - ear sensor operates normally
Installation manual
1. Unpack the archive.
2. Copy this whole thing in root of your SD Card. You have to be there and the file folder factory.img tflashupdate with subfolders in which images are 5 image files.
3. Turn off the phone
4. Turn the phone mode FACTORY MODE (Hold down the "sound less" click on "Insert")
5. In the corner of the picture seems a penguin, and then flee bukovki.
6. When the screen starts flashing sign "Done" take out the battery
7. Turn on the phone and wait three to five minutes until the phone turns on.
Upgrade to A3 Android 2.2
WARNING! Put to the Android 2.1!!! (Rename to update.zip)
A3_SDCard_Android_2.2_AppleUI_ROM - depositfiles.com | ge.tt | yabadaba.ru Apple shell, many languages ??that are not running a mute button
A3_SDCard_Android_2.2_ROM - depositfiles.com | ge.tt | yabadaba.ru Android shell, many languages.
in the archive file A32.2tflash20110304.zip find update.zip (for normal) and update2.zip (for Apple UI) March 2011
VNIMANEIE the update will be removed accounts, settings, address book, so the need to keep this business contacts in gmail, or on a flash drive to copy everything (have a function in your notebook).
Detailed instructions on how to flash the firmware MARCH
1. Swing by the link I gave ap0stol file (it is one, just different file sharing, but on each one and the same file compressed). Unpack it - there is, among other things (they have interisuyut) files and update.zip update2.zip. Next, you need to choose your update. Update.zip file needed for those who have regular A3 (without Apple UI), and update2.zip needed for those who have A3 with Apple UI. In his instructions below, I'll write about update.zip, but those who let Apple UI is beneath him understand update2.zip.
2. Connect your smartphone to your computer as a USB flash drive, put it in the root of the flash file update.zip,
3. Create a flash drive an empty file named AAAAB3NzaC1kc3MAAACBANLc2NCufBz0lBUupztiXI7rUnhY3bOojTMmGD0SR68e8kK00EM5n0ghfpaDxayZD.zip
4. Turn off all smartphone. Connect your smartphone to USB-cable (standard) connected to a computer or charging. We look forward to when you are charging scale, hold the "+" and not squeezing it as the top button "inclusion". We are waiting for the appearance of diamond with an exclamation point. press the central button HOME.
5. In the menu that appears, select (side rocker) to "establish a SD card file update.zip" and press the left touch button (left of center). Will the installation process, which in the end to slow down and give oshibku.6. Turn off your smartphone. We took him out of the stick, insert into the card reader, remove or cut the root of flash file update.zip. Extract all the contents of the saved file on your computer update.zip in a separate folder, remove it from the file uboot.bin (not to be confused with boot.img). Packs everything back to the file update.zip (without the uboot) and throw it on the stick. Put it in a smartphone.
7. Again connect the USB-cable to the smartphone, which the other end connected to a computer or charging. We look forward to when you are charging scale, hold the "+" and not squeezing it as the top button "inclusion". We are waiting for the appearance of diamond with an exclamation point. press the central button HOME. In the menu that appears, select (side rocker) to "establish a SD card file update.zip" and press the left touch button (left of center). Will the installation process, which is a second to tell us - that the operation is aborted.
8. Pull out USB, distorts the battery, turn on your smartphone without a cable connected YUSB as usual.
9. Android boot 2.2.1. with firmware version 0304, but in Chinese. Go to the menu - choose RUSSIAN. 10. Connect your smartphone as a USB flash drive to your computer, and instead of a file update.zip (without uboot) change it to a normal full-update.zip (with uboot). In the menu on the phone (in applications) is called prilozhenetse UPDATE SYSTEM, click on it and agree. Smartphone reboot (from YUSB cable do not disable) and set the correct normal update.zip uboot without swearing.
11. Connect your smartphone to your computer - Deletes a file update.zip and AAAAB3NzaC1kc3MAAACBANLc2NCufBz0lBUupztiXI7rUnhY3bOojTMmGD0SR68e8kK00EM5n0ghfpaDxayZD.zip differently each time you boot with a connected smartphone will YUSB instalit update.
12. Go to Settings - PRIVACY - click on the Reset All Settings. This one fell swoop remove the Chinese crap, settings and programs from the type CAT TOM TOM (as I understood - Chinese Tamagotchi).
13. Again set the Russian language. Set up an account and enjoy.
From the observed changes. Indeed the names of the operators in the system correctly displays a string. Was really fast work smart (maybe because of the fact that while it does not cost anything, he was ***** and barefoot)
Firmware for the transition from 2.1 to 2.2
FIRMWARE AVAILABLE ONLY WITH CABLE Saddle (pinout in the manual)
Firmware file and all necessary instructions - karelia.ru | ge.tt | yabadaba.ru
Some have problems with the transition to 2.2, so make sure you carefully read the topic!
For work and thank AlexxNB Angel_Hranitel
Working with the IMEI (replacement, restoration, without broaching the cable)
Change IMEI on Making your own risk
1. Downloading tool: imei.rar with ge.tt
2. Obtain the root-and.
3. Copy the file (for example through the Root Explorer) / data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 somewhere in a safe place.
4. Extract imei.rar somewhere.
5. At the command prompt, run imei.exe c with 2 IMEI
For example: imei.exe 355812010064326 355812010064326
matter are different or the same (you can from your other phones). The main thing that IMEI codes according to the algorithm were the Moon
6. In the folder with the file imei.exe get MP0B_001
7. The resulting file MP0B_001 put in / data / nvram / md / NVRAM / NVD_IMEI / instead of the old (I hope I / r \ w guessed peremauntit through the same Root Explorer for example).
8. Check access rights. Must be:-rw-r-x ---
Or for Root Explorer as follows:
User - read and write
Group - Read and Execute
Other - No
9. Reboot.
10. Enjoying a new IMEI.
2 imei restore way use META exe
Maui META ver 6.1032.0\Meta2.exe
use chine pin finder box and find pinouts..
{
"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"
}
Make edit txt file what u want imei.. save and send to phone
Flasher...
https://rapidshare.com/files/3658583445/SP_Flash_Tool_v1.1051.05.rar
flasher working with usb and with pinfinder..
First starting flash with tx rx after flash tools asking USB cable plug..
All in one 1 pack complete
http://www.multiupload.com/BOPC0DK06R
Sir links not working, please check it
Links not working
Files are removed from all Places. Please can you re upload on goggle drive or drop-box..???

[MTCD/E] [PX5] BT Search and connection issues with device name and pin

Recently some users including me are having issues with BT Connection, device search, setting device name and making changes persistent.
BT MODULES THAT IT WAS TEST ON:
SD-968 - [HA] [MCU MTCE 2.75] Firmware 20180201 and few earlier = WORKS
MD725 - [??] [MCU ???] Oreo Firmware = DO NOT WORK (According to feedback) LogCat needed to see if Firmware communicate with BT Module at all.
METHOD 1 (SHORTER):
1. Force Stop BT app
2. Clear DATA and CACHE for BT app
METHOD 2 (LONGER):
Here are the steps I've done to make it work.
1. Boot device (restart if it was not in deep sleep)
2. Directly go to system BT settings (drop notification and tap on BT)
3. Set Device name and PIN
4. Press refresh
5. Go to Home Screen (Home Button)
6. Open BT App -> Configuration
7. Name and PIN should be entered now
8. Disable/enable Auto Connect and exit app
9. reenter app and configuration to enable Auto connect
10. Make sure that all previous BT profiles for HU are deleted on phone and that phone is visible for all devices (usually when BT configuration is open device is visible)
11. Try to search for devices. It should fail (it failed for me)
12. Go to factory settings
13. Change BT Device even it is wrong one (I have SD-968 I changed to MD725)
14. Tap Apply -> Exit -> CANCEL on reboot prompt (without doing step 13 there will be no scheduled restart)
15. Reenter Factory settings and set correct BT Module (I have SET SD-968) Tap Apply -> Exit -> and Confirm REBOOT
16. After Reboot Go to BT App and try to search for phone it should be found (make sure it is visible like in step 10)
17. If all is OK you should see the phone and you should be able to use it normally (it worked for me)
Attached pictures of some steps for METHOD 2.
NOTE: I'm ATM at HA 6.0.1 Firmware from 20180201 and issue happened after upgrade. Also from what I see Users have same issue with and after Oreo update. Hope I helped
Thanks for the info. Have you tried this method also for oreo rom as well ?
A step that worked for me was to clear data and cache for bluetooth app..
julien_blanche said:
Thanks for the info. Have you tried this method also for oreo rom as well ?
Click to expand...
Click to collapse
Haven't updated to Oreo yet.
Phycopat said:
A step that worked for me was to clear data and cache for bluetooth app..
Click to expand...
Click to collapse
Good point it didn't worked for me but, it can also help. Added to main post.
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
Click to expand...
Click to collapse
I have same GS MTCE 2.75 PX5 OREO but an old OBD2, give HU same password as OBD2 adapter..
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
Click to expand...
Click to collapse
Point of 12-15 is that HU re init Module itself along with software. Not sure if it works that way on MTCD/E but usually it works on modular systems.
Tried with PX5 oreo installed with no luck. Both methods are not working for me.
PekeMM said:
Haven't updated to Oreo yet.
Click to expand...
Click to collapse
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
I'm sorry, but as I wrote I have SD-968 BT module not MD725. I'll update main thread with so far know to work devices.
Any news?
JonatanP said:
Any news?
Click to expand...
Click to collapse
Not that I know, I'll be back from Trip on Sunday, so I hope I'll finally finish the tests and upgrade to Oreo in April.
seems to be the same
The solution is to go back to android 6, the problem is that it is not as fluid in my case as android 8.
Hi, same problem here....
I can not use my ODB2 connector on my Android 8 radio either.
Is there an adapter that works?
Is there a trick to make it work?
Greetings and thank you!!
Hi..any update on how to get the bluetooth working on android 8..
Mtcd ksp px5
warata said:
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
Click to expand...
Click to collapse
if you still have android 8 installed, try going to factory setting and change the BT Device even it is wrong one (anything other then MD725) tap apply and exit and reboot.
after reboot change the BT device back to the original one (MD725) tap apply and exit and reboot.
after reboot go to the system BT and try to search if the phone name appears let me know.
i still didn't try the above method on android 8, but if anyone with MD725 module is still using android 8 please try and update us.
thanks
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
macoloco said:
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
Click to expand...
Click to collapse
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
bjt2 said:
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
Click to expand...
Click to collapse
i wrote all my procedure here
https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
and here
https://forum.xda-developers.com/showpost.php?p=77538182&postcount=796
Dasaita MMCNP - BT connection problem
Hi, I have Dasaita HA2106-V840-8 a problem with Bluetooth connectivity. First time I managed to connect my phone to Dasaita MMCP (car_kit), but after a few days the devices failed to connect. I guess my device has embedded SD968 BT chip, in accordance with the description.
When I enter the name of the device and new PIN in BT settings, and then turn on finding the device, they are not visible to each other. I tried this other day too, but when I turned MMCP, entered settings was gone (not memorized). No name, no PIN, but also there is no connection. Search doesn't have results. At the end I tried to unpair devices and pair them again, but I get a message on my phone "Unable to communicate with CAR_KIT".
When I entered in settings for BT (settings/car/factory setting/application-choose...) it was set to WQ_BC6. And then I tried to set up SD_BC6, reboot, search BT, nothing was found again. Then I returned to WQ_BC6, reboot, search BT, without success. In the end, I tried to set up SD968, but it's not worth it anyway, MMCP does not see a mobile phone. I also tried several phone models without success. I also went to the BT application and clear data and cache, but always the same thing - BT devices do not see each other. I'm not even sure BT is ON because it doesn't have a special slider to move On/Off.
What should I do? Please help me!

wipe data problem

Hi my Max 3 has gone into MI-Recovery 3.0 mode
The options are (a) reboot - when I click on this it brings up a picture of Miui 10 in background with some chinese options about entering wifi passwords?
(b) wipe data - when I click on this it takes me to 'wipe all data', I click again and it asks me to confirm 'wipe all data', it then gets to about 3% on a spacebar and says 'data wiped successfully', and then takes me back to main menu again
(c) connect with mi assistant - asks me to plug phone in using USB then doesn't seem to recognise it
Any body any ideas please on how to reboot my Max 3?
Thank you
Unfortunately your phone is in EDL mode (download mode). Only an authorized Xiaomi account can recover it.
This is due to ARB which is active in Mi Max 3 and other Xiaomis. If you try to go back to the Android or Rom version (in some cases), this will start.

Mi A2 Lite Bluetooth Audio Problems? Back To Oreo?

Hi There,
Just bought my GF a Mi A2 Lite a few weeks ago and she is loving it compared to her old iPhone 5s but one major issue atm is that her bluetooth headphones seem to be giving her issues!
The audio stutters a LOT even when right next to the phone. Tried resetting the Bluetooth connection but to no avail.
I had a quick scan through the forums and seen that people recommend going back to Oreo to solve the issues.
Is there any clear guides or links on how to do this? I know my way around tech so should have any issues following a guide.
Thanks in advance!
Yes, it's a very annoying bug.... I have it too, but didn't find a solution
That's the reason why I downgraded to Oreo!
If you want to downgrade,
1. you must unlock the bootloader, but this will erase all of your data. So, don't forget to make a backup of your internal storage. https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-official-t3885578
2. Install MiFlash and ADB on your computer: https://www.xiaomiflash.com/download/ https://forum.xda-developers.com/showthread.php?t=2317790
3. Download an oreo stock rom and unzip it: https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
4. Boot your phone into bootloader
-> Connect your phone with your computer and enable ADB in developer settings
-> Shutdown your phone and hold Volume Down and Power-Button to boot your phone into fastboot/bootloader
5. Open the MiFlash-Tool on your computer and select the Oreo-Stock-Rom which you want to install.
6. At the bottom of the MiFlash window you must choose clean all, this will erase all of your data!
7. If your phone gets recognized from your computer and the programm, then you can hit the button flash on the top of the window
8. This procedure takes a while, so be patient.
9. If everything works, it will reboot your phone automatically.
10. Maybe you will have the bug of swapped SIMs. You must install TWRP: https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
and flash this file to fix it: https://forum.xda-developers.com/attachment.php?attachmentid=4704476&stc=1&d=1550012435
11. Perfect! You downgraded to Oreo!
I hope this little guide could help you, and sorry if it's a bit complicated
If it's any consolation, I had this issue on Oreo and Pie!
I'm now upgrading to a Pixel 3a, but keeping this phone for development. Might try porting Ubuntu Touch some time. ?
iforgotmylogin said:
If it's any consolation, I had this issue on Oreo and Pie!
I'm now upgrading to a Pixel 3a, but keeping this phone for development. Might try porting Ubuntu Touch some time. ?
Click to expand...
Click to collapse
Okay, that's weird ?
Maybe there was a problem with your Bluetooth headset?
00norman00 said:
Okay, that's weird ?
Maybe there was a problem with your Bluetooth headset?
Click to expand...
Click to collapse
If so, it was a problem with every one I tried!
I tried on a generic Bluetooth speaker, two different generations of Echo Dot, and on a current gen regular Echo.
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
LotR656 said:
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
Click to expand...
Click to collapse
Interesting... sounds like a pain in the ass, but I'll try this next time I get chance.
Thanks!
LotR656 said:
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
Click to expand...
Click to collapse
But it stutters also when wifi is offline. And on Android 8 I don't have this frequency-problem
00norman00 said:
But it stutters also when wifi is offline. And on Android 8 I don't have this frequency-problem
Click to expand...
Click to collapse
You can solve by adding the the missing codecs, all the routes are still there, xiaomi removed licensed codecs
Downgrade helped as of 30.05.2019
Mi A2 lite
Bought Galaxy Buds. Stuttered and eventually lost connection.
NOTE:What comes ahead is my personal experience (with some software errors that doesnt seem to have effect on our goal) downgrading my MI A2 lite to Oreo.
Downloaded Android Oreo 9.6.11 , ADB and Fastboot, Miflash(latest from site) from links in the beginning of the thread.
Very few proper video tutorials (Indian mostlyXD).
Enabled developer options on my phone (tapping 7 times on build number). In developer options enabled allow OEM unlock and turned on usb debug mode.
Turned off phone and launched it it fastboot mode (hold "volume down" and power button simultaneously). Connect phone to PC via usb.
Open folder on PC where you installed ADB and fastboot software. Launch cmd.exe or smth. In black window type "fastboot oem unlock" Enter. The phone reboots (takes a lot of time dont be alert) and wipes data from your phone. You will see a scary message/warning (disappear s after few sec) that asks you to lock bootloader back.
NOTE: somehow my device did not ask for any confirmations for enabling unlocked bootloader.
NOTE 2: I was trying to do this whole process by video and text guides. Some ppl type commands in cmd "fastboot flashing unlock" and then "fastboot flashing unlock_critical" BUT for some reason this commands did nothing. So all I did is oem unlock command.
After OEM unlock command rebooted phone skip all phone setups and open developer mode again (if it is locked) and in dev options check if "allow oem unlock" and usb debug mode is turned on. Turn off your phone and load it in fastboot mode (volume down+power).
On PC unpack Android Oreo files. It should look like a long name folder with some .bat files and folder (avoid unpacking in place with strange name paths).
Launch MiFlash tool. NOTE: it gave me a prompt for installing drivers and after i pressed it gave an error. It is fixed by creating inside MiFlash tool folder a new folder and naming it "log". Then launch the tool again and press install drivers.
Once you are in MiFlash program there is a ling space where you can insert a file path. You need to copy a file path that leads to your unpacked Android Oreo files (the path should lead inside where the .bat files located). Paste this copied path into MiFlash path bar and press refresh button. If there is no error you can proceed by pressing in the bottom right corner a "clear all" option and in the top right "flash" button. This will install Android Oreo on your mi a2 lite.
After the process is done i had an error in MiFlash program BUT the phone reboots on its own with downgraded Android version. Turn the phone off, load it in fastboot mode, connect via usb and run in ADB folder CMD.exe and run "fastboot oem lock" command. The phone reboots, takes a while.
!!!
After it reboots immediately skip all phone setup menus especially wifi and account options and go straight in settings to unlock developer mode. In developer options TURN OFF AUTOMATIC SYSTEM UPDATES! After it you can finish phone setup process ,accounts, networks and everything else.
An Android message "update available" can pop up. To get rid of it for good simply swipe it slowly A BIT (not all the way) till you see a cog sign (options icon) and there turn of this notification.
Now you can go smoke a cigar. Android 8.1.0 Oreo installed AND it wont update automaticlly to PIE. You can use your bluetooth devices properly (or whatever problems you had).
Have a nice day. Gonna probably go buy Samsung A30. This **** is unacceptable. Pie update rolled out long time ago (Android Q is releasing in 3 months from now) and this stuff is still not fixed. Wtf
Solution
I did a simple step to fix pair
Reboot into safe mode, pair the select device, after pair reboot out the safe mode and you see the device paired.
Cheers
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
I did a simple step to fix pair
Reboot into safe mode, pair the select device, after pair reboot out the safe mode and you see the device paired.
Cheers

Android auto - Skoda Octavia III

Hi,
Trying run Andorid Auto(5.4.502264-release from gPlay) on Skoda Octavia but no success. Of course I was try run with different device (Lenovo Tab) and it works.
Is it working with:
Note10+ Exynos
Baseband version N975FXXU4CTE9
Steps for reproduce:
Connect over USB
Allow permissions on Phone
Choose Android Auto on car infotainment screen
connecting
Connection lost
on Note10+ I can see Android Auto running in
What I was try
- change usb cable (3 different types)
- in Andorid Auto app on Phone setting I was try delete connected phone
- delete Phone in car infotainment
Any Idea how to solve it? Do you have similar experience?
Thank you
Update:
after testing S10 in the same car and it works again, I was made factory reset of Note10 and it works too.

Categories

Resources