All,
Can someone produce an how to to downgrade baseband from 52 to 4X. Im on beta 4 and wanting to go to 2.3.2.
I understand there is some files J has put in the zip that may be flashed using recovery?
Regards,
Yea all you need to do is flash folder correct_baseband onto your phone and you are good to go.
Regards
E
Click on the thanks button if my reply was of any use
I need too
Sent from my X10i using Tapatalk
STEP 1) go to http://forum.xda-developers.com/showthread.php?t=920746 download the flasher
STEP 2) Extract the flasher zip file, open the program X10FlashTool.exe
STEP 3) Advanced -> Bundle creation -> select the folder corect_baseband -> enter details required ( Device, Branding, version -> select all the files present in the folder list (on the left side) and transfer to the firmware content -> click ok
STEP 4) -> click on flash -> select the firmware -> when asked connect the phone in flasher mode (Turn off the phone and connect the USB while holding down the back button, this will result in the GREEN notification light being turned ON)
STEP 5) If you require busybox or root or xrecovery it will be found in the advanced menu.
And upon rebooting you will have the baseband required for 2.3.2.
Regards
E
Click on the thanks button if my reply was of any use
http://www.mediafire.com/?f077eodoubh7687
Excuse my ignorance, but what do you need to downgrade the base band for?
caifanX10 said:
Excuse my ignorance, but what do you need to downgrade the base band for?
Click to expand...
Click to collapse
check my sig and the the file from post above yours
Hey guys. For those of you who are having problems of no sound on your Lumia after trying to enable root access and have no SBL3 for your phone eg lumia 720, you're in luck.
Firstly a big thanks to @Heathcliff74 for WPinternals tool and @Riyad_ for list of changes to the registry.
Lets get started!!!
1. Flash your phone with the original ROM and there after unlock the bootloader(You don't need SBL3 ).
2. Using WPinternals, dump EFIESP, MainOS and Data partitions.
3. Mount EFIESP and MainOS with OSFMount or similar software.
4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition.
5. Locate mounted MainOS and navigate to Windows\Packages\RegistryFiles. Here you will find SOFTWARE.reg. Copy it to you desktop.
6. Open 7-zip and double click on the SOFTWARE.reg file. Right click on the file named SOFTWARE inside it and select Edit.
7. Copy and paste the contents of the attachment below into the SOFTWARE file then save and exit. 7-zip will give a message, just click OK.
8. Delete the SOFTWARE.reg from your MainOS and copy the modded SOFTWARE.reg from your desktop to you mounted MainOS. Once you have done this, unmount EFIESP and MainOS drives.
9. Go back to WPinternals and now flash all 3 partitions.
10. Wait for phone to flash and reboot then go to "about" in settings and reset your phone and enjoy interop/cap unlocked phone.
so we can't use mass storage mode with this TUT?
mybabysexy said:
so we can't use mass storage mode with this TUT?
Click to expand...
Click to collapse
Unfortunately not becoz there's no SBL3
are you adding tweak in this reg file? and adding your wallapers, sounds and etc for your mainOs?
this is basis for custom rom(backup rom, as huawei w1) with wpinternals(flashed).
reksden said:
are you adding tweak in this reg file? and adding your wallapers, sounds and etc for your mainOs?
this is basis for custom rom(backup rom, as huawei w1) with wpinternals(flashed).
Click to expand...
Click to collapse
Yes the SOFTWARE.reg file is being modified. I haven't added any wallpapers or sounds to my MainOS as yet.
Rivo17 said:
Yes the SOFTWARE.reg file is being modified. I haven't added any wallpapers or sounds to my MainOS as yet.
Click to expand...
Click to collapse
okay.
MainOS.bin\PROGRAMS\CommonFiles\ - sounds and other( replace the names on the modified files).
i'm waiting to flashing plat( change image on the run).
@Rivo17
Sound has always working if Root-access not installed (with or without SBL3)
titi66200 said:
@Rivo17
Sound has always working if Root-access not installed (with or without SBL3)
Click to expand...
Click to collapse
Yeah but now you will have root access and sound working. Most people had problems of no sound with root access.
Sorry but with This
"4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition."
You don't have root Access
titi66200 said:
Sorry but with This
"4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition."
You don't have root Access
Click to expand...
Click to collapse
Yes, you have to do this so you can flash the modded MainOS. Read WPinternals tool.
titi66200 said:
Sorry but with This
"4. Go to enable root access in WPinternals and unlock ONLY the EFIESP partition."
You don't have root Access
Click to expand...
Click to collapse
Yes, you have to do this so you can flash the modded MainOS(which contains the changes for root access). Read WPinternals tool.
sounds great for phones which doesn't has sbl3 partition but suppoted in wpinternals..
I have a problem, when I go to Windows Phone Internals and enable root access at EFIESP, the program say enable root access... but it is in a loop, it is loading.... Sorry For my english...
What to do in case of receiving a OTA or want to update BUT don´t want to loose fastboot or TWRP???
If you receive a OTA or want to update through update.zip and you have ROOT:
1 - Downlaod the update (only download ) DON'T INSTALL IT
2 - Go to /data/data/com.tcl.fota/.fotadownload/ and copy to SD Card the update.zip that you will find there.
3 - Copy de update.zip to PC
4 - Use Winrar or other program and open the update.zip
5 - Delete the emmc_appsboot.mbn file, is aboot.img and doesn´t have fastboot commands ( Alcatel think we don´t need it ) OR replace it with aboot.img from 5.0.2 but you must name it emmc_appsboot.mbn!
Code:
package_extract_file("emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
6 - Delete the recovery folder, it will change your recovery ( TWRP ) with default recovery it have a patch for that ...
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/bootdevice/by-name/recovery:9483564:409bc65c46703bf8be7fdf0238242a46af8be079; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/bootdevice/by-name/boot:8629544:3d67952f7ebe6d2fe46e2daa760b2f743f824f0d EMMC:/dev/block/bootdevice/by-name/recovery 409bc65c46703bf8be7fdf0238242a46af8be079 9483564 3d67952f7ebe6d2fe46e2daa760b2f743f824f0d:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
7 - replace the update.zip from /data/data/com.tcl.fota/.fotadownload/ with your modify update.zip
8 - Unroot your phone
9 - update!
You can copy the update.zip with TWRP, download the update DON`T install it, turn off the phone, Boot in to TWRP, go to /data/data/com.tcl.fota/.fotadownload, copy the update.zip to SD Card, etc, etc..
Note: But this is my theory, I don´t have how to test this ...
I hope it helps you!
Tell me if you made it!
Any one try it?
do alcatol idol 3 still get otas? lol, atleast the 6045X doesn't
panchovix said:
do alcatol idol 3 still get otas? lol, atleast the 6045X doesn't
Click to expand...
Click to collapse
Some OTAs are only patches, no full roms
persona78 said:
Some OTAs are only patches, no full roms
Click to expand...
Click to collapse
oh i know, but still they get it? for example, roms with security patch of 2017?
panchovix said:
oh i know, but still they get it? for example, roms with security patch of 2017?
Click to expand...
Click to collapse
Some times
Hi guys I'm blocking the Amazon's system updates or over-the-air updates with modded DeviceSoftwareOTA.apk under the post
Features of modded DeviceSoftwareOTA.apk
-> Removed OTA links
-> Removed unwanted component declaration like permissions, services and receivers
-> Modified any classes like AmazonDownloadManager
-> Removed and corrupted OTA controller to prevent forcing the updates
Let's Get Started
1. Go to Settings -> Device Options -> About Fire tablet -> Serial number and tap the several times until you see the Developer Options appear.
2. After the Developer Options appears under the About Fire tablet menu, Go to Developer Options -> USB Debugging and enable it.
3. Open Command Prompt on your PC and approve the USB device
4. Verify the attached devices
Code:
adb devices
5. Install the modded DeviceSoftwareOTA.apk as an existing
Code:
adb install -r path/to/DeviceSoftwareOTA.apk
Legend: -r = re-install an existing app, -d = downgrade the version code of DeviceSoftwareOTA.apk to causing an error, fails and never forcing the OTA updates
or can also add -d to downgrade the version code
Code:
adb install -r -d path\to\DeviceSoftwareOTA.apk
6. Go to Settings -> Device Options -> System updates and tap CHECK NOW to checking for getting an error and fails
The OTA updates has been blocked.
AmznUser444 Dev said:
Hi guys I'm blocking the Amazon's system updates or over-the-air updates with modded DeviceSoftwareOTA.apk under the post
Features of modded DeviceSoftwareOTA.apk
-> Removed OTA links
-> Removed unwanted component declaration like permissions, services and receivers
-> Modified any classes like AmazonDownloadManager
-> Removed and corrupted OTA controller to prevent forcing the updates
Let's Get Started
1. Go to Settings -> Device Options -> About Fire tablet -> Serial number and tap the several times until you see the Developer Options appear.
2. After the Developer Options appears under the About Fire tablet menu, Go to Developer Options -> USB Debugging and enable it.
3. Open Command Prompt on your PC and approve the USB device
4. Verify the attached devices
Code:
adb devices
5. Install the modded DeviceSoftwareOTA.apk as an existing
Code:
adb install -r path/to/DeviceSoftwareOTA.apk
Legend: -r = re-install an existing app, -d = downgrade the version code of DeviceSoftwareOTA.apk to causing an error, fails and never forcing the OTA updates
or can also add -d to downgrade the version code
Code:
adb install -r -d path\to\DeviceSoftwareOTA.apk
6. Go to Settings -> Device Options -> System updates and tap CHECK NOW to checking for getting an error and fails
The OTA updates has been blocked.
Click to expand...
Click to collapse
I cannot install this apk because the signatures do not match. :crying:
Datastream33 said:
Hi guys I'm blocking the Amazon's system updates or over-the-air updates with modded DeviceSoftwareOTA.apk under the post
Features of modded DeviceSoftwareOTA.apk
-> Removed OTA links
-> Removed unwanted component declaration like permissions, services and receivers
-> Modified any classes like AmazonDownloadManager
-> Removed and corrupted OTA controller to prevent forcing the updates
Let's Get Started
1. Go to Settings -> Device Options -> About Fire tablet -> Serial number and tap the several times until you see the Developer Options appear.
2. After the Developer Options appears under the About Fire tablet menu, Go to Developer Options -> USB Debugging and enable it.
3. Open Command Prompt on your PC and approve the USB device
4. Verify the attached devices
5. Install the modded DeviceSoftwareOTA.apk as an existing
Legend: -r = re-install an existing app, -d = downgrade the version code of DeviceSoftwareOTA.apk to causing an error, fails and never forcing the OTA updates
or can also add -d to downgrade the version code
I cannot install this apk because the signatures do not match. :crying:
Click to expand...
Click to collapse
Can you install via ADB
AmznUser444 Dev said:
Can you install via ADB
Click to expand...
Click to collapse
Unfortunately, I cannot. It just returns the invalid signature error.
Newbie question as I'm just about to receive my Fire 10; what customizations will an OTA break?
After you got a failed to install the modded DeviceSoftwareOTA.apk because the signature verification?
Re-install the modded DeviceSoftwareOTA.apk as a root and reboot your device
I got Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE] message on a Fire Stick 2, 5.2.7.0, any ideas about how to solve it?
Lochy19 said:
I got Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE] message on a Fire Stick 2, 5.2.7.0, any ideas about how to solve it?
Click to expand...
Click to collapse
Can you only install it to root?
Lochy19 said:
I got Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE] message on a Fire Stick 2, 5.2.7.0, any ideas about how to solve it?
Click to expand...
Click to collapse
Tried it too but it will not work. You need to be rooted Best thing that you can do is install No Root Firewall.
Good evening everyone!
I recently bought a Junsun V1 head unit for my Golf 7. I specifically chose it because of the AC8227L SOC, which is a renamed MT8127. It includes a few more peripherals that are useful in car infotainment systems, but the core is identical.
I'm in the process of creating a new firmware from scratch, to replace the chinglish, buggy stock one. However, I have not succeeded yet.
What I have done so far is create a TWRP image for it, completely from source, using the prebuilt kernel. It's available here (any mirrors will be appreciated and linked in this post):
https://mega.nz/file/1Gp2gJ5S#gAxcP1WK8nwXivYTpAlyEsWNoWwNZBZ8VTs3fm57gEc
I have also dumped the firmware from the 2GB + 32GB version: https://mega.nz/file/hXhEjTab#AowvrX36nn9rXIkeu_zgnGmLyDxtiSUSWswwmXcN46k
To install install TWRP simply put it on the "RECOVERY" section in SP Flash Tool using the scatter and preloader provided in the firmware dump. Uncheck everything else and press flash.
You'll need a type-a to type-a USB cable connected to the 4-pin USB connector (not the 6-pin), and then give power to the unit.
Any other information about the device, serial communication between android and the MCU, decompiled apps, modified apps, etc are also welcome!
I hope this is useful for somebody.
UPDATE 07-01-2021:
I've been reverse engineering the MainUI apk for a week now. I've extracted the MCU communication protocol, now I'm trying to extract the DSP protocol, and CAN will be next.
The touch buttons on the left side of the unit is managed by this .apk as well, and that has already been reverse engineered, only the implementation has to be done with the available API I wrote.
All help is welcome. You can find the source code in github. The important work is being done in native libraries, the java stuff is useless right now. https://github.com/Iscle/MainUI
root
hi, i think i have a HU similar to yours ( se e attached pucture ). Btw did you manage to root the original fw? what about your development, it sounds interesting...
root
......see attachment
maxou2 said:
hi, i think i have a HU similar to yours ( se e attached pucture ). Btw did you manage to root the original fw? what about your development, it sounds interesting...
Click to expand...
Click to collapse
maxou2 said:
......see attachment
Click to expand...
Click to collapse
If you can install TWRP then you will be able to root.
iceblue1980 said:
If you can install TWRP then you will be able to root.
Click to expand...
Click to collapse
magisk?
maxou2 said:
magisk?
Click to expand...
Click to collapse
Anything you want but I would really recommend SuperSU as Magisk doesn't work as intended on these units. Also make sure you run SuperSU v2.79 and no higher. As for TWRP, only version 3.0.2 is stable in my experience.
I'm stuck unlocking the bootloader, the command "fastboot oem unlock" works and the unit ask to confirm by pressing vol+, unfortunately the touch on the panel does not work... tried to put a wireless keyboard dongle on the other USb but it doesn't work....
{
"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"
}
Magisk works just fine, I actually recommend it over SuperSU, as SuperSU is practically obsolete nowadays.
Also, no need to unlock the bootloader, just flash the recovery image as I explained on the first post.
Just made a deep study and tests on this unit, here my results, thoughts, mods and other considerations hoping this will help.
Being scared to brick the unit I used a conservative approach by making step by step mods rather than flash the firmware at the first post.
Here's my changment pattern:
Firmware : Before rooting I updated to the last version of the firmware the vendor gave me ( the latest OEM firmware ).
It's an OTA update ( use the "five fingers screen touch & move" method ) after putting the the files .bin and .upd in a USB key connected to a USB port when you powerup the unit.
I enclose a link to download it.
OTA update
I've made a DUMP of the partitions ( by using the SP tool Readback feature, you can find a lot of tutos on the internet how to use it ) and with the WwR tools i managed to have a full flashable original FW backup.
Another interesting method is to retrieve the partition content on a "live" system by use a shell and the dd unix command :
Enable the developer option on the system and connect the 4 wire USB port to a PC ( by using a 4 wire male to male USB cable ).
If you have an ADB command environment installed on your PC you can just fire a "adb shell" command,
followed by an "su @#zxcvbnmasdfghjklqwertyuiop1234567890,." to have a shell with superuser rights.
Now you can navigate trought your file system as root.
Anyway here's the partions table :
/dev/block/platform/soc/11230000.mmc/by-name # ls -l
lrwxrwxrwx 1 root root 21 Dec 3 14:26 ANDROID -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Dec 3 14:26 ARM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 3 14:26 BOOTIMG -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Dec 3 14:26 CACHE -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Dec 3 14:26 DKB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Dec 3 14:26 EXPDB -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Dec 3 14:26 FRP -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Dec 3 14:26 KB -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Dec 3 14:26 LK -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Dec 3 14:26 LOGO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Dec 3 14:26 METAZONE -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Dec 3 14:26 MISC -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Dec 3 14:26 NVRAM -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Dec 3 14:26 ODMDTBO -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_F -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_S -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PRO_INFO -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Dec 3 14:26 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Dec 3 14:26 SECCFG -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Dec 3 14:26 SEC_RO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE1 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE2 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Dec 3 14:26 VENDOR -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Dec 3 14:26 forfanzone -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Dec 3 14:26 tszone -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Dec 3 14:26 userdata -> /dev/block/mmcblk0p26
Just use the dd unix command to dump every partitions content to a /sdcard directory where you can easily copy to an external USB stick or PC via adb pull.
E.g: dd if=/dev/block/mmcblk0p10 of=/sdcard/TWRP/boot_from_dd.img
Luckily I didn't have to use these datas to unbrick my system...
TWRP : I used another version ,it's a v3.3.1, works well. Flashed with SP Flash tool and the scatter contained in the .zip firmware at first post. I enclosed it so someone can tell what's the best option amongst these.
ROOT : Flashing magisk zip from TWRP worked flawlessy, but in my case i experienced an additional delay at boot ( let's say between 20-30 sec ), now a cold boot takes about 1 minute whereas with no root it was about 35 secs. I suspect this is due to the magisk modification to the boot process .
HW mods, temp controls and other infos will follow.
Any questions, just ask.
I have v1 1ram 16rom with ac8227l, but when I tried to update my radio I was only able to with an update-ty.zip with a manual process like this:
What I can do????
this is the last firmware that junsun send to me https://drive.google.com/file/d/1OjZcB0yqVQsu8O63l58VrMneZBmr25p5/view?usp=sharing
jabatillo_2001 said:
this is the last firmware that junsun send to me https://drive.google.com/file/d/1OjZcB0yqVQsu8O63l58VrMneZBmr25p5/view?usp=sharing
Click to expand...
Click to collapse
jabatillo_2001 said:
I have v1 1ram 16rom with ac8227l, but when I tried to update my radio I was only able to with an update-ty.zip with a manual process like this:
What I can do????
Click to expand...
Click to collapse
Your update process is very different from mine, probably you should tick every checkbox ( the most dangerous could be the MCU IMHO ) and start the update process. You should check first with the vendor, but it seems the correct procedure if the files he sent you match your Head Unit.
BTW take some picture of the MCu version, FW revision etc... of your unit.
Actually the compressed file they sent you contains BOOT, SYSTEM, TEE AND VENDOR updated partitions, and .bin update file ( usually the mcu update are .bin file but in my experience are really smaller then the one contained in the zip so it's diffucult to know what is for ).
So probably you should tick the "Sistema - > update_ty.zip" ONLY and start the update process....
The update only works with this name of file update-ty.zip, others don't work. My problem is bluetooth, It Connects and disconnects all the time. I'm crazy with this, I think the problem is bttool.apk or MTK but I'm not sure.I'm not allow to call or answer calls, either I can't dial by numbers.
I need to try some other firmware to resolve the problem.
Perhaps you can give me one idea or some trick to help me.
Thanks a lot.
My Android mobile XDA app don't work properly, after I'll attach you photos of my radio characteristics.
maxou2 said:
Actually the compressed file they sent you contains BOOT, SYSTEM, TEE AND VENDOR updated partitions, and .bin update file ( usually the mcu update are .bin file but in my experience are really smaller then the one contained in the zip so it's diffucult to know what is for ).
So probably you should tick the "Sistema - > update_ty.zip" ONLY and start the update process....
Click to expand...
Click to collapse
jabatillo_2001 said:
The update only works with this name of file update-ty.zip, others don't work. My problem is bluetooth, It Connects and disconnects all the time. I'm crazy with this, I think the problem is bttool.apk or MTK but I'm not sure.I'm not allow to call or answer calls, either I can't dial by numbers.
I need to try some other firmware to resolve the problem.
Perhaps you can give me one idea or some trick to help me.
Thanks a lot.
My Android mobile XDA app don't work properly, after I'll attach you photos of my radio characteristics.
Click to expand...
Click to collapse
Need to be sure that the firmware in this thread match your unit first, take pictures of your system infos. BTW your unit is only 1 GB RAM right?
Can you post the link where you bought it? ( Probably aliexpress... )
Keep in mind that generally on these chinese HU the BT is not managed by the android system as with cellphones, it's the MCU and dedicated apk that usually do that ( you do not have any BT option in the android system settings ).
So:
1) Did you try with a system reset?
2) Can you reach an advanced system option menu ( a little bit tricky in my unit ) where you can interact deeply ( BE VERY CAREFUL ) with several options, here you can set some BT systemwide parameters.
3) Maybe an MCU update could also help
1) yes
2)Wells, only development options of Android, the firmware not contains BT options. If you turn off BT, It turns off automatically. BT music only works if you play by mobile, neither by radio.
3) Perhaps, but it's the same problem, to update MCU I need a file named m51_update. You can see in image.
I have a A2 Lite of Xiaomi, but I try in a note 6 pro and the same problem.
What can I do?
I don't know what I can modify native MCU, but I like to probe another compatible ROM.
All my test, without rooting, are around Android 8.1 BT problems..
Bttool.apk don't work properly, disconnects for example, when I try to syncronize the contacts.
I'm afraid to brick It installing by flashing.
maxou2 said:
Keep in mind that generally on these chinese HU the BT is not managed by the android system as with cellphones, it's the MCU and dedicated apk that usually do that ( you do not have any BT option in the android system settings ).
So:
1) Did you try with a system reset?
2) Can you reach an advanced system option menu ( a little bit tricky in my unit ) where you can interact deeply ( BE VERY CAREFUL ) with several options, here you can set some BT systemwide parameters.
3) Maybe an MCU update could also help
Click to expand...
Click to collapse
maxou2 said:
Need to be sure that the firmware in this thread match your unit first, take pictures of your system infos. BTW your unit is only 1 GB RAM right?
Can you post the link where you bought it? ( Probably aliexpress... )
Click to expand...
Click to collapse
The firmware I posted on the first post was also extracted with SP Flash Tools + WwR tools. I sent it to a friend who uploaded a dump made with dumpyara here: https://git.rip/dumps/ffkj/ff-5000
This way we can navigate the filesystem easily, and grab anything we need.
I'm in the process of creating a kernel source for this SoC, I don't know if it will work, but if it does, the first thing I'll do is overclock it haha
jabatillo_2001 said:
1) yes
2)Wells, only development options of Android, the firmware not contains BT options. If you turn off BT, It turns off automatically. BT music only works if you play by mobile, neither by radio.
3) Perhaps, but it's the same problem, to update MCU I need a file named m51_update. You can see in image.
I have a A2 Lite of Xiaomi, but I try in a note 6 pro and the same problem.
What can I do?
I don't know what I can modify native MCU, but I like to probe another compatible ROM.
All my test, without rooting, are around Android 8.1 BT problems..
Bttool.apk don't work properly, disconnects for example, when I try to syncronize the contacts.
I'm afraid to brick It installing by flashing.
Click to expand...
Click to collapse
You should check your HU Hardware parameters, so you can figure is this thread is for you.
System "About device" - see picture.. Take a picture of the values on the screen.
After that touch the Gear icon on the top right of the screen a popup menu will appear, digit 8888 and ok.
An advanced system setting menu will appear, choose "others", scroll down and you'll see some BT options ( see picture ), try to change them.
Save and reboot.
If your system doesn't have such as menus I strongly recommend you to check elsewhere because probably your HU is different from mine.