Hello
Year ago i bought Xiaomi TV 3 55' it runs Android 5 with MIUI stuff. I rooted to install GApps using King Root. month tried to update it using OTA after unroot but it stock on boot logo. it has recovery and two systems both are not booting i tried wipe everything from recovery with no luck. contacted them they asked to ship it to them (not an option for me because of shipping cost).
i should mention that i have another device just like it running fine. and the system is in the sound bar looking thing.
please if anyone has an idea i can try to fix because i cant use my tv any more.
specs
CPU: MStar 6A928 Cortex A17
GPU: Mali-760 MP4
2GB DDR3 8GB eMMC 5.0
same issue
Hi, I am in similar situation and my MiTV 3 60'' is also not booting up - stuck at Mi Logo screen. any updates?
saalmaan said:
Hi, I am in similar situation and my MiTV 3 60'' is also not booting up - stuck at Mi Logo screen. any updates?
Click to expand...
Click to collapse
No still not working. Did try recovery options?
I'm looking for replacment for the main board in chinese websites with no luck. I might just give up and buy new sound bar although shipping it will be expensive.
Solved
found a video on youtube to solve the problem
watch?v=KipVFueoSTw
So my phone failed to boot up and it was happened when i've updated the OS via updater. Does anyone have "CN Firmware" of Black Shark 2 pro??, the repairman said he can't do anything if there's no Firmware available at the moment, so i'd like to ask for help if theres someone who have the right firmware for Black Shark 2 Pro CN version (not OTA). Thanks beforehand!!
Hello, Recently I discovered that my Pixel 3 XL couldn't use widevine L1. And I did some research and they said it's probably the persist.img. (Thread: https://forum.xda-developers.com/pixel-3-xl/how-to/widevine-l1-t4183011 ).
And today comparing my pixel 3 XL with my pixel 3 a I found out that my Pixel 3 XL doesn't have secure boot enabled and doesn't have NOS- production (idk what they mean but looks pretty important).
What I'm asking is if anyone could tell me how to correctly flash my device to get those back (and hopefully get widevine L1?). So far I've used Google website flash tool, if I'll have to use adb can someone tell how to do it exactly?
Ty.
Images of both phones fastboot mode info:
https://photos.app.goo.gl/Wj1Vudi8fasbpXfk6
https://photos.app.goo.gl/wbpGg2RyXEmn8aFSA
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Lol, 11 will never be "fixed".
If the bootloader was updated you're boned.
Apparently on the OTA updates on at least some devices it's not being updated, you can rollback.
The 5th digit from the end of the boot loader version and the firmware are the significant digits. If the boot loader version is the same or less than the firmware, you can rollback. In this case it's a 2.
Not sure that this Samsung rule applies to Motorola updates.
RETIEF said:
Not sure that this Samsung rule applies to Motorola updates.
Click to expand...
Click to collapse
No idea, it may be a Samsung idiosyncrasy.
A very annoying one...
PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
Check the software channel from Settings>Telephone information (or similar), which software channel do you have? If it is timit you are on the tim software channel (and the updates depends on the carrier, but actually seems in line with reteu, the european standar), if you are on reteu this is really strange. I don't know why they miss the boot animation but the firmware is right.
Yes the software channel is timit, but in android 10 it showed the boot animation for reteu channel. And i dont know why now it shows an edge logo animation that has nothing to do with this model. It looks like they put something from another model in the update. Look at the attached photo.
I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.
PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
You can always just root phone and change the boot animation files. They're in system/media/bootanimation.zip
Just download android 10 firmware get this file from system.img and put it on your phone
the.real.p3y0t3 said:
I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.
Click to expand...
Click to collapse
Hello and sorry for asking a newbie question here but I don't want this to go sideways...
I have a new XT2113-2 (TM) that is yet to be boot loader unlocked/rooted/etc. I don't want to do that until I am sure. I got this variant of the phone so I could unlock the bootloader, root, TWRP, etc and was afraid the "global" variant -3 might not work with USA 5G. The phone came with Android 11 installed (and has since auto-installed at least one security update). It shows the build as RZKS31.Q3-45-16-3-11 and the baseband ends with Kiev_TMO_CUST. I am using it on ATT (via Red Pocket) since TM service just sucks where I live. And I do get the 5G icon on it now.
But ideally, I want to get this to the original TM Android 10, which I think is shown here as the file XT2113-2_KIEV_TMO_10_QZKS30.Q4-40-95-6_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip as I hope it will undo some of the "security" crap Google has added to Android with each successive release.
So I need to be sure of the following:
1. Can I downgrade from 11 to 10?
2. Is there some reason to NOT use the firmware mentioned above? Should I use retail US (RETUS) instead? I am not sure the differences (it would be great if that would permit me to use this phone on Red Pocket Verizon but the IMEI now shows as incompatible on Verizon).
3. Must I unlock the boot loader to downgrade? I know I must to do other stuff and I have the unlock code on hand and ready to put it if needed. If I must unlock the boot loader to downgrade, will I have to re-unlock it afterwards? And, if so, will I have to go through the same process of getting a code or will the code I have now work?
4. How do I flash to do the downgrade? I have the Lenovo Rescue/Smart Assistant installed on my PC and was able to download the stock firmware (I assume it matches what is on there now) and stashed it aside. But is there some other tool needed?
5. Once I achieve downgrade, what is the best way to avoid having the thing auto-update to Android 11?
Thanks for your help with these questions.
Hello, I've bought a OnePlus 7 Pro a while ago, and during my first efforts of installing the OnePlus drivers on the computer, then flashing it (unfortunately, I can't recall which image that was), my phone was identified as "GM1917" in the Windows notification area and the phone's about screen.
I continued playing around with ROMs, and at some point I bricked it...
I think it was guacamole_21_P.01_211210_repack.ops together with "MSM download tool 4.0-patched" (which also happened to be in a "Rebrand T-Mobile to Global 7 Pro" package) that allowed me to unbrick & flash it with an image again - however, it was now identified as "GM1915"! Using any other unbricking packages (like OnePlus_7_Pro_Global_OxygenOS_11.0.5.1.zip) resulted in the MSM tool saying "Param preload: Device not match image".
The phone's about screen says I'm using model 1915, but it runs 11.0.7.1.GM21AA!
I'm completely confused. I would feel better if I could use the seemingly better-supported GM21AA ROMs (not just OxygenOS, but maybe also others), can I 'convert' my phone somehow?
rookey said:
Hello, I've bought a OnePlus 7 Pro a while ago, and during my first efforts of installing the OnePlus drivers on the computer, then flashing it (unfortunately, I can't recall which image that was), my phone was identified as "GM1917" in the Windows notification area and the phone's about screen.
I continued playing around with ROMs, and at some point I bricked it...
I think it was guacamole_21_P.01_211210_repack.ops together with "MSM download tool 4.0-patched" (which also happened to be in a "Rebrand T-Mobile to Global 7 Pro" package) that allowed me to unbrick & flash it with an image again - however, it was now identified as "GM1915"! Using any other unbricking packages (like OnePlus_7_Pro_Global_OxygenOS_11.0.5.1.zip) resulted in the MSM tool saying "Param preload: Device not match image".
The phone's about screen says I'm using model 1915, but it runs 11.0.7.1.GM21AA!
I'm completely confused. I would feel better if I could use the seemingly better-supported GM21AA ROMs (not just OxygenOS, but maybe also others), can I 'convert' my phone somehow?
Click to expand...
Click to collapse
Ever figure out how to get your phone back to reading as GM1917? I have a similar issue.
Whether or not your phone says GM1917 or GM1915 completely depends on the rom. But idk why that matters, everything functions the exact same way.