Hi
I updated My device Mecool KM3 with USB_Burning_Tool and selected Erase all
The change Security Level L1 to L3
Chromecast is not working
I tried the original ROM, version 9 and 10 and several unofficial ROMs, but without result
And I tried by DRM_L1_Patch
And the same problem
Is there a solution to recover
Azroui said:
Hi
I updated My device Mecool KM3 with USB_Burning_Tool and selected Erase all
The change Security Level L1 to L3
Chromecast is not working
I tried the original ROM, version 9 and 10 and several unofficial ROMs, but without result
And I tried by DRM_L1_Patch
And the same problem
Is there a solution to recover
Click to expand...
Click to collapse
Sorry Your Keys Are Lost Forever, They Are Stored In The Bootloader But Cannot Be Included In Update Files, They Are Added At The Factory Only, Its The Same With Android TV Netflix Certification
Thank you for your reply
I raised the issue because I found patches to restore DRM_L1 for some phones, and I thought it wa the same for my TV box
Currently, I use AirReceiver alternative to Program Chromecast built-in
Although it is not that good, but I could not find a better alternative
Related
Hi guys,
I have Tmobile LG V10 H90120j which its Wifi MAC address changes on every reboot.
Long story:
It was originally Lollipop, I updated to stock MM v20e then v20j. It was still OK after that.
Then I tried to root it using tungkick's method. However, the bad luck began, I forgot to change the Process to Upgrade instead of Refurbish when upgrading the TOT file. The phone bootloop to TWRP after that. Big thanks to @tungkick, he helped recover it.
I realized that from then the Wifi MAC address keeps changing on every reboot. The phone also cannot automatically get APNs from provider (I have to manually add them).
The really bad problem is the MAC issue. Only registered devices can connect to my home and my company Wifi networks. I can temporarily workaround by manually changing MAC address on rooted ROM after every reboot, but it's not an actual fix.
Factory Reset or Restoring to stock v20j can't help.
I did some search and found that some others also had the issue. Some said this method also can fix it: youtube . com /watch?v=8ejnFB5i5o8
But I can't see any nvram folder in my device.
Anyone has any ideas about fixing this, please help
Thanks.
anyone?
I have this with the T-mobile LG G5 H830 that is rooted on 20j (Nougat) with the dm-verity patch applied as well. I have 7 days left to return the phone). I also cannot find the nvram file/folder on my device (I am searching my LG G Pad 8.0 X to see where it is at via Root Explorer).
You mentioned you went back to stock (in TWRP, did you format the system and data directories and wipe the caches before; I ask because if you did not, I was going to do that, then re-stock).
My only other guess is the bootloader unlock would cause it (but then my LG G Pad 8.0 X is bootloader unlocked and doesn't do this). There was a CM7MAC.zip file (which I know is supposed to be for CM rom but I wonder if that fix would work for us).
uglyhoodlum said:
Hi guys,
I have Tmobile LG V10 H90120j which its Wifi MAC address changes on every reboot.
Long story:
It was originally Lollipop, I updated to stock MM v20e then v20j. It was still OK after that.
Then I tried to root it using tungkick's method. However, the bad luck began, I forgot to change the Process to Upgrade instead of Refurbish when upgrading the TOT file. The phone bootloop to TWRP after that. Big thanks to @tungkick, he helped recover it.
I realized that from then the Wifi MAC address keeps changing on every reboot. The phone also cannot automatically get APNs from provider (I have to manually add them).
The really bad problem is the MAC issue. Only registered devices can connect to my home and my company Wifi networks. I can temporarily workaround by manually changing MAC address on rooted ROM after every reboot, but it's not an actual fix.
Factory Reset or Restoring to stock v20j can't help.
I did some search and found that some others also had the issue. Some said this method also can fix it: youtube . com /watch?v=8ejnFB5i5o8
But I can't see any nvram folder in my device.
Anyone has any ideas about fixing this, please help
Thanks.
Click to expand...
Click to collapse
crazyut said:
I have this with the T-mobile LG G5 H830 that is rooted on 20j (Nougat) with the dm-verity patch applied as well. I have 7 days left to return the phone). I also cannot find the nvram file/folder on my device (I am searching my LG G Pad 8.0 X to see where it is at via Root Explorer).
You mentioned you went back to stock (in TWRP, did you format the system and data directories and wipe the caches before; I ask because if you did not, I was going to do that, then re-stock).
My only other guess is the bootloader unlock would cause it (but then my LG G Pad 8.0 X is bootloader unlocked and doesn't do this). There was a CM7MAC.zip file (which I know is supposed to be for CM rom but I wonder if that fix would work for us).
Click to expand...
Click to collapse
Been months, I cannot recovery my memory well. But I might not format the system and wipe the caches in TWRP before going back to stock. Still having the issue, and applying workaround after every reboot .
Bootloader unlock is unlikely the cause, cuz I rooted another H90120j (my cousin's) after that. I followed strictly the guide and made no mistake. The phone's still working well now.
Well I think you can give it a try. Looking forward to your good news
My 13th day is Saturday so I am going to get T-mobile to exchange it for a new one (since about 1/2 the posts on this topic says it's a hardware problem with certain chipset mac addresses and I hope that batch of phones that WA gets is different than the batch that HI gets) and reboot that several times before I leave.
I only found out I had this problem since Shaw Cable use MAC address for the 10 devices include in the Shaw Go wifi (wifi public hot spots) and when I put the original address in while still in HI, then got back to Calgary (after a couple of reboots had occurred during my trip) noticing Shaw would not auto-connect like it does on the other devices which are all rooted and sim unlocked (LG G Pad 8.0 X, Samsung Galaxy Note Edge, Moto X Play).
If not for Shaw, I would have been none the wiser until I got an employer that only used MAC address and by then, I'd be stuck with the phone.
I notice that this problem allegedly was based on a chipset and/or the Android software itself (there doesn't seem to be a consenus one direction or the other) when I googled this (and subsequently found your post on XDA). I have had several generations of Samsung Galaxy S and Note Series as well as Moto Triump (Sprint), the LG G Pad X, and Moto X Play and have never seen this phenomenon.
Since you say your cousins device is working well and you did the same thing with it as with yours, I suspect it's a hardware fault in our devices. I already returned a V20 to Freedom/WIND since that bootloader is locked and no root possible (will try to get T-mobile to give me the V20 instead of the G5 since I have to go through all this drama; the Freedom V20 was rebooted more than 7 times on purpose and no mac address change occurred).
uglyhoodlum said:
Been months, I cannot recovery my memory well. But I might not format the system and wipe the caches in TWRP before going back to stock. Still having the issue, and applying workaround after every reboot .
Bootloader unlock is unlikely the cause, cuz I rooted another H90120j (my cousin's) after that. I followed strictly the guide and made no mistake. The phone's still working well now.
Well I think you can give it a try. Looking forward to your good news
Click to expand...
Click to collapse
Hi,
last year I bought a NPET Android TV BOX with 2GB RAM and 8GB ROM. It was equipped with an Android 6.0 ROM from factory which I am searching now.
In December 18, I had the idea to install the ATV Xperience SW, because the factory one worked...lets say OK. But not flawless and with limitations.
I prepared a TWRP 3.0.2 mircoSD card and backuped BOOT, DATA and SYSTEM, just in case something goes wrong and...the ATV installation went wrong!
Red Light was the result and the box didn't boot up by pressing the power button. I plugged the USB Cable in and flashed a A95X firmware, which seemed to be similar in terms of HW with my boxes. And everything worked, except Wifi and BT. Doesn't matter, I thought, I have TWRP and my backup, but it doesn't worked out. BOOT and DATA partitions could be recovered but not the SYSTEM partition (createTarFork() process ended with ERROR=255). I tired several other images, but neither Wifi nor Bluetooth could be actitivated. For testing purcposes, I have installed OpenELEC on a microSD card and both, Wifi and BL, started to work again. But as this box is for my girlfried, she wants to have Android back on this device. Wifi and BT Chip is the KM63351412 (Please see attached PICS of the mainboard).
Does somebody of you has the factory image of this box?
I have searched the Internet the last couple of days, but couldn't find it. I have also contacted NPET directly, but no response so far.
Or does somebody know an android image with the KM63351412 chipset embedded?
Hi All,
fortunately, a guy called "aidanmacgregor" has made an universal image which contains various wifi and bt driver in this image.
https://forum.xda-developers.com/an...m-android-tv-custom-rom-7-1-2-s905x-t4098131/
for me, this box called npet s905x is now fully working again!
Thanks to the creator @aidenmacgregor!
Cheers,
Cromatic
??
I have a KM1 device - bootlooped - and Mecool doesn't want to send me the firmware, saying it's a secret. I have also tried flashing other ATV firmware, such as SuperCeleron and Sasvlad for X3, but stuck on startup. Someone says that the KM3 or KM9 firmware is compatible with this device, but the usb burning tool does not flash their U-BOOT ... only U-Boot Sasvlad Rom - i.e. Ugoos X3 devices - and U-Boot SuperCeleron uses being flashed correctly. but, as I said, the rom doesn't load and gets stuck on startup.
I'm having this same issue with my MeCool KM1
It was working fine and suddenly it crashed and now only boots into android's recovery menu.
MeCool email support staff was replying me telling to wipe cache/user data etc and stop replying when I told them the problem was beyond simply wiping data partition. They simply don't want to send me the procedure on how to fresh install system software....
I really do not recommend anyone to buy any mecool device.
Hi!
I received J8110 from Sony as a service exchange unit (they could not repair my other model). It came originally with Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1. I have not unlocked it.
It never got any OTA update for this over 2 years old firmware, so I decided to flash it myself using flashtool. As I could not find exactly matching 1317-9334 on XperiCheck, I used 1318-3803 Android 10 "Internal Service Exchange Unit 55.1.A.9.127-R1B" firmware. It did flash correctly, and almost everything works - except both Netflix and HBO Max reboot the phone whenever I try to play any video. Moreover, the phone reboots itself randomly once a few hours, and I must say it is really irritating issue.
The last entries in Android logcat just before reboot look like this:
Code:
03-07 10:18:41.251 886 17948 D WVCdm : [license.cpp(355):PrepareKeyRequest] PrepareKeyRequest: nonce=3174971344
03-07 10:18:41.313 886 6842 I WVCdm : [cdm_engine.cpp(191):CloseSession] CdmEngine::CloseSession: sid10
I suspect it might be somehow related to Widevine keys. But the DRM info app shows everything is OK and L1 support is enabled (as in the attached screenshot).
I tried to flash also other firmware images - everything available for J8110 in XperiCheck (including 55.2.A.4.332), but the phone won't boot - "Your device is corrupt. It can't be trusted and will not boot.". I even tried flashing J8170, but that eneded up even worse, in recovery: "cannot load Android system". This 55.1.A.9.127-R1B (that reboots my phone on Netflix) is the only firmware I was able to boot.
My first question: is there any way to downgrade to this original, obsolete but working Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1? I can't find it in XperiFirm.
And, of course - if you could point me on how to install the more recent Android versions that work I would be very grateful. I would prefer to leave the phone locked as I suspect some DRM issues with unlocking, but if that is the only way and it is confirmed working I can try it as well.
Service menu *#*#7378423#*#* "software info" of original and updated firmware attached.
Thanks for any help!
I forgot to mention that of course I tried clearing data and cache for Netflix app, as well as uninstalling and re-installing updates (can't fully uninstall the app as it was included in the firmware). I could fully reinstall HBO though, but fresh install did not help with the issue at all.
Did you tried the Firmware with version 205 on XperiFirm?
There is one called SA or ZA.
Get things into your PC and use newflasher by @munjeni. It will work if there is nothing wrong with hardware.
Thanks for the response.
I have tried the newflasher as well, but the results are exactly the same as for flashtool - "Your device is corrupt..." (or recovery error, depending on firmware). I don't think this is an issue with flashing itself, I did not notice any error in logs.
Yes, I have tried this 205 "Customized ZA" also - it does not boot, stops in recovery "Can't load Android system". I did not try to factory reset the data yet, as I really would prefer to keep my user data intact.
I have tried every single firmware available in XperiCheck for J8110, and only this 1318-3803 boots for me - but reboots my phone every hour or so and this is really annoying.
I have also asked XperiCheck maintainer to add my 1317-9334, but no response so far.
Plz provide the frimware that is working in your mobile i am facing the same problem my device stuck on sony logo i will be thankful to you brother
Hello.
After installing XperiFix, my camera is still not working. I am uploading the logs below. I noticed that the Magick 17.1 version from XperiFix doesn't work, and when I try to update or upload from a new one, I see a black screen after booting the phone, but when I press and hold power button I see a window to a turn off device and sometimes top bar appears (time, battery, etc.). I tried to install Magisk v25.2.
I also tried to upload the stock camera (https://gitlab.com/xperiance/camera/-/releases) but without the higher version of Magick I can't do it.
I have FW .205, before that I tried .270 but it didn't work, bootloop when starting the phone.
In the morning I will install the update from OTA to .235 and try to upload XperiFix or install the .145 version and see what happens next.
I tried Open Camera and made logs, but they didn't save, but the camera still doesn't work ;/
EDIT: I flashed FW .145 but didn't help.
I flashed Android 9 FW 47.2.A.11.228 to test, but I cant flashed XperiFix, because in TWRP write "read-only partition detected" and I see that I flashed Magisk nothing happens, it's as if it didn't install, I don't know why but I didn't have a problem with it before... In TWRP this options "read-only" is unchecked.
Translated with www.DeepL.com/Translator (free version)
Is it possible to fix this somehow, anyone know anything? I've read a lot of forum posts about it but nothing works, I'll just add that after installing some AOSP(probably Android 11) the front camera works but very poorly and after taking a picture you can see green artifacts on it.
Hey, do you know how to fix camera app on sony xperia xz1 not capturin?
My xperia xz1 is android 8, so I decided to flash an android 9 firmware using newflasher. After flashing the firmware, my camera has a problem that can't capture. Anyone can tell how to fix this issue? Plz help me. Sorry for bad English
Your browser is not able to display this video.
This is what happen on my xperia xz1. Camera is not capturing and not save a picture, recording also object tracking not working. This is happen after flash from android 8 version to android 9. Anybody know to fix this? Please help me. before flash the new android version, i didn't do any backup and my xperia is locked bootader. I'm using newflasher to flash the android 9 firmware.