yashsingh1/xdaforums huggingface dataset:
[Xiaomi 11T Pro] Akk0099:
Hi guys, has the title says when i try to turn on my device it shows the message "The system has been destroyed".

After searching and understanding the issue it seems i need to flash a new image.

The issue is that the device seems to be lock (1st screenshot - from MiFlash), but I also can't unlock it as i didn't unlock it before and i can't turn it on because of the issue, also through MiUnlock doesn't work (2nd screenshot).

Is there anyway to unlock the bootloader without having to turn on in the developer options ?

View attachment 5862401

View attachment 5862403
[Xiaomi 11T Pro] Domniak:
You could try to install XiaoMiTool v2 on your computer, connect your phone and follow onscreen instructions to repair your system. What did you do in the first place, that such error happened?
[Xiaomi 11T Pro] santiagobbotero:
If you can't log in download the program $$$. the only problem is that it asks for credits you must buy. It is an optimal and functional solution.

Spoiler content hidden.

Mod. edit: post translated. link removed. alecxs
[Xiaomi 11T Pro] alecxs:
Hello @santiagobbotero,

I've edited your above post. Please do not promote paid services on XDA! Thanks for your cooperation.

alecxs

moderator
[Oppo A37 Questions & Answers] dliakh:
Hello Everyone,

Didn't anybody try making Oppo A37f work with LTE (or at least WCDMA) in the EU?

I have one I bought in Thailand years ago and now I would like to use it in France (because why not (well it has the FM Radio which my newer phone doesn't have, that's why :) )

The problem is that it doesn't connect to LTE at all, and it connects to WCDMA and the download speed is even decent for the phone (11, 12 mbps) but the connection is unstable (it works, displays H+, then 3G then disconnects and can then stay disconnected for some long time until connects again)

It looks like it should support LTE bands 1, 3. My cell carrier (Free.fr) supports 1, 3, 7, 28 (with the 1 marked as limited coverage), so theoretically, it should connect with the band 3 or 1 (right?) but in practice it never does. My newer phone (Alcatel 3L 2020) connects with the LTE band 7 to the same network.

I though about trying to enable some additional bands (7, perhaps) by editing the NV_LTE_BC_CONFIG_I (still need to figure out how to do that: I can read the NV and see the values with the QPST's QCN Viewer and can also even dump the QCN as XQCN (something like XML) and even find and change that item, just need to figure out how to change it to enable the 7-th band)

Another thing I'm thinking about (even though pretty much everywhere it's said it won't work), is trying to use the baseband (or even just the QCN) from the Moto XT1541 (the europeran version of the Moto G3 which uses the same MSM8916 chipset).

Didn't anybody have such kind of the connectivity problem and maybe a solution for it?

Thank you

Best regards
[Oppo A37 Questions & Answers] dliakh:
Well, tried doing what I think should enable bands (7 and 20):

changed the NV_LTE_BC_CONFIG_I from 00000000000010000101 (85 00 00 00 00 00 00 00) (which apparently, means bands 1, 3, 8 enabled)

to 10000000000011000101 (C5 00 08 00 00 00 00 00) (which I guess, should have added 7 and 20):

the phone still didn't connect to LTE: still the same: HSPAP.

Anything else to do? (may the hardware even support the disabled bands?)
[Oppo A37 Questions & Answers] dliakh:
P.S.

#include <inttypes.h>
#include <stdio.h>
#include <stdlib.h>

int
main(argc, argv)
int argc;
char *argv[];
{
uint64_t item6828 = 0 ;

for (int i = 1; i < argc; ++i) {
item6828 |= 1<<(atoi(argv[i]) - 1);
}

for (int i = 0; i < sizeof item6828; ++i) {
printf("%02X ", (unsigned)((item6828 >> (8*i)) & 0x000000FF));
}
printf("\n");

return 0;
}

$ cc -o bands bands.c && ./bands 1 3 7 8 20 28
C5 00 08 08 00 00 00 00

This is how one calculates the value to insert into the XQCN, right?
[Oppo A37 Questions & Answers] dliakh:
(sorry for keeping conversation with only myself still :) )

Why are there many of them? (may I need to change some other one that I did (the one that has the index 0) ?

View attachment 5863223
[Google Pixel 7] JJT211:
Hi,

I havent used the Pixelflasher yet, so unfortunately do not have any support files (i went old school side load factory image). But I unknowingly used the latest v34 platform tools and looks like ive hard bricked my phone (completely unresponsive, will not power on, first hard brick EVER in 10+ years!)).

Got the error everyone else has gotten

Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

After I got the error, I couldnt restart phone. I then got the:

“Your device is corrupt. It can’t be trusted and may not work properly."

And then when I tried booting to bootloader....it just became unresponsive.

Any ideas on how to bring my P7 back to life?? Or am I at the mercy of Google warranty/repair store??
[Google Pixel 7] kafisc:
Use Platform Tools with Factory Image (Flash_all.bat).

It's not as comfortable as other tools but it's official from google and it works.

Platform Tools:

https://developer.android.com/studio/releases/platform-tools

Factory Image (not available for March update till now)

https://developers.google.com/android/images?hl=de#panther

Tutorial from point 2:

https://xdaforums.com/t/guide-root-...nlock-bootloader-pass-safetynet-more.4505353/
[Google Pixel 7] rekids:
My bad, should have researched all the updates and threads before thinking that the newest releases were bad.

Next time will play it safe and wait another month to see what shakes out. I know, shouldn't have said anything.
[Google Pixel 7] t-ryder:
By now platform tools 34.0.0 & 34.0.1 is reported being buggy/faulty causing a lot of problems. Stick to platform tools 33.0.3 until further updates, do research before switching to a newer version if updates are released. Pixel Flasher for example warns users by now not to use anything above 33.0.3 atm.
[Google Pixel 7] Sh0X31:
Had the same Problem

https://xdaforums.com/t/march-13-20...etah-safetynet.4502805/page-104#post-88281529

https://xdaforums.com/t/march-13-20...etah-safetynet.4502805/page-106#post-88285365

Second Link somebody say

but it was to late for my I wiped
[Google Pixel 3a Questions & Answers] Boowho 1234:
Nandoid B/U with TWRP. Seems to backup just fine, but (immediately) restore on the same device causes boot loops.

It looks like the backup filed are something like win000, win001, etc that are actually tar files.

I'm wondering if I got into terminal mode on TWRP, could I just extract the tar files to restore the partition?? I've always used tar to b/u and restore /data/media.

FWIW, the device is a Pixel 3a running android 11 and the version 11 compatible TWRP flash file.

Help if you can...... Thanks
[Google Pixel 3a Questions & Answers] alecxs:
Hi @Boowho 1234,

seems you have accidentially posted in the wrong forum. I have moved your question to the Google Pixel 3a Questions & Answers forum.

regards

alecxs

moderator
[Google Pixel 3a Questions & Answers] Boowho 1234:
sorry......
[Google Pixel 3a Questions & Answers] alecxs:
You're welcome! Regarding your question. May you clarify why you want to extract tar files manually - did the restoring via TWRP menu not extract the files successfully? Usually TWRP would throw an Error code in that case, and you can always have a look into /tmp/recovery.log
[Google Pixel 3a Questions & Answers] Boowho 1234:
Restoring using the TWRP restore option restored the files perfectly. But, upon rebooting back to SYSTEM just boot loops. No error code thrown, but I've not looked at recovery.log
[Google Pixel 3a Questions & Answers] alecxs:
It's probably because of one or more outdated files restored. try to delete this. you should also try to restore on formatted userdata partition (beware of / data/media = /sdcard is not included in backup)

/data/unencrypted

/data/misc/keystore

/data/misc/gatekeeper

/data/misc/vold

/data/system/locksettings.db*

You should ask TWRP maintainer to fix that issue.
[Google Pixel 3a Questions & Answers] Boowho 1234:
I'm now using a Windows .bat file to backup ALL partitions on the device. It works great except throws errors on these two partitions : mmcblk0 and mmcblk0rpmb

I've read that these two partitions are not REALLY partitions at all, but are some sort of "special" files within the /dev/block directory.

The question is do I have a complete Nandroid back up without these two included?? Anyone??

Thanks
[General Topics] spangelsaregreat:
Hi,

My MDA Compact IV has stopped reading HTML files.

I think it was when I removed Opera from it and that is when it stopped.

I can still look up the internet and the pages display, however, if there is a HTML page saved on the phone it won't recongise it as a web page. It is a bit of a pain because I use RunGPS which allows you to show training files as HTML pages. However, when it tries to load the file it gives this error.

"The file Training Report cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found."

Even if I save this file to the phone, it does not display it as a readable file in explorer.

I am assuming that the phone has somehow lost its ability to recognise these files as HTML.

I also use Skyfire browser but the problem started before I installed this.

Any ideas?

Regards
[Android Stick & Console AMLogic based Computers] yahya_elaidi498:
At first it was a red light problem, and I was able to fix it by flashing the stock android 9 rom after that ,I flashed atvX v4 - AndroidTV 9.0 (S905W) in the first boot it worked fine, and after about an hour I rebooted, the remote went crazy.

The back button is now the home

The down button is now the volume down

The power button isn't working any more

And more

When i rebooted again it show the X96Mini fingerprint ⬇️⬇️

View attachment 5862431

And it won't boot even if i format the data partition

And i can't boot in to recovery or flashing with USB Burning Tool or an Sdcard.

And just to make sure that the cable work i test it on an TX3 Mini and it worked.

Any clue how to fix this?
[Android Stick & Console AMLogic based Computers] mAtvXk:
NAND Chip Mask ROM Mode Short Location

Bricking and unbricking Vontar X96 mini | danman's blog

blog.danman.eu
[Android Stick & Console AMLogic based Computers] Lomxitrum:
tx3 mini + NAND CHIP ?
[General Questions and Answers] TheMystic:
Everytime I try to attach a file and the built-in file manager (com.google.android.documentsUI) is launched, the Recent section (which opens by default) lists all files in duplicate, as seen in the attachment.

I have seen the same behaviour on all my devices. Can this be fixed?
[Samsung Galaxy A12] lexuslain77@gmail.com:
Hey you'll, I have this samsung a12 a127f U5 rooted with magisk and twrp installed. Have tried installing custom roms/gsi of all nature,LOS,PE,HAVOC...etc. All the ROMs works fine except one issue, touchscreen. Once the screen goes off....(either by pressing the power button or as a result of screen timeout) turning it on again reproduces the problem. Screen doesn't respond to touches. I as a result have to reboot to get it working again until the next screen timeout or otherwise triggering it using the power button. Anyone with a possible solution please help me out and I'll be very grateful 🙏 🥲
[Samsung Galaxy A12] V0latyle:
As this is a Question, you need to use the Question tag. As a courtesy, I have changed it for you.

Are you using a custom kernel? GSIs are meant to be used with the OEM kernel.
[Samsung Galaxy A12] lexuslain77@gmail.com:
Yes,I did try physwizz a127f kernel but the problem still persists
[Samsung Galaxy A12] V0latyle:
Try the stock kernel.
[Samsung Galaxy A12] lexuslain77@gmail.com:
Tried but same problem still
[Samsung Galaxy A12] Extremusjkr:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

I think I found a solution more like I don't know how to apply it I'm just waiting one day maybe physwizz will apply

fix touch gsi · manteiga25/rainbow-kernel-samsung-a12@d46f7c6

Contribute to manteiga25/rainbow-kernel-samsung-a12 development by creating an account on GitHub.

github.com

I think you need to compile a kernel to mount this, but I don't know if that's really what you should do

If you manage to know what to do with it or even manage to apply it in some way, come back here and tell me what to do.

(I'm using a translator, if there's anything that doesn't make sense I'm sorry)

my model is 125m binary 4

*********************************

acho que encontrei uma solução mais tipo não sei como aplicar só estou esperando um dia talvez o physwizz se aplique

fix touch gsi · manteiga25/rainbow-kernel-samsung-a12@d46f7c6

Contribute to manteiga25/rainbow-kernel-samsung-a12 development by creating an account on GitHub.

github.com

Acho que você precisa compilar um kernel para montar isso, mas não sei se é realmente isso que você deve fazer

Se você conseguir saber o que fazer com ele ou mesmo conseguir aplicá-lo de alguma forma, volte aqui para me dizer o que fazer.

(estou usando um tradutor, se houver algo que não faça sentido me desculpem)

my model is 125m binary 4
[Samsung Galaxy A12] lexuslain77@gmail.com:
I don't think this will work on exynos,,,it's built for A125( mediaTek)...A127 is based on exynos type of chipset...hopefully someone comes up with a possible solution 🥲
[Samsung Galaxy A12] Oswald Boelcke:
Hello and good afternoon, @Extremusjkr

As a one-time courtesy for I've translated your above quoted post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Portuguese posts.

Spoiler content hidden.

And I grant you 48 hours to translate your other "Portuguese-only" posts. Unless accomplished within this timeframe, I'm deleting them.

Regards

Oswald Boelcke

Senior Moderator
[General Questions and Answers] Androiduser065:
Here is a forum for Infinix Smart 6 phone.
[General Questions and Answers] Androiduser065:
can anyone guide me how to extract recovery of Infinix smart 6 x6511e device it is not available in firmware file. Other forums says it's in boot.img.

Here is boot img ---> https://xdaforums.com/attachments/boot-img.5862409/
[General Questions and Answers] powerput77:
Как получить root на infinix x6511,подскажите пожалуйста,если конечно это возможно,загрузчик разблокировать-вот в чем проблемма.
[General Questions and Answers] Androiduser065:
Unlock bootloader firstly from fastboot, then flash magisk patched boot image, finally flash vbmeta with --disable-verity and --disable-verification tag
[Xiaomi 13] OberZine:
As title suggests,

I have had the phone since 10th March, and since day 1 I bound the account in Mi Unlock Status in developer settings successfully, enabled OEM unlocking and USB debugging.

However, I have tried the Mi Unlock tool version 6.5.406.31 and 6.5.224.28.

I even tried XiaomiToolV2-99.9.9 (the one on github)

They all say the same message

Couldn't Unlock

Please add your account in MIUI's Settings > Developer options > Mi Unlock status

I have followed what it said multiple times, and I get no error messages, just a added successful message.

I'm at a loss on what to do, I've never had this issue before on any of my previous Xiaomi phones since Xiaomi Mi 6.

For some scope, I got the phone from WondaMobile 12GB Ram 512GB Storage China model.

I even contacted Xiaomi Customer service, they said "I've passed this on to the technical team" then ended the chat haha

Can anyone advise what I can do?
[Xiaomi 13] NOSS8:
The only official tool is Mi Unlock, not using XiaomiToolV2.

Check here just in case:

Unlock bootloader

Xiaomi Community

new.c.mi.com

Apply for unlocking Mi devices

en.miui.com

Similar case resolved.

https://xdaforums.com/t/resolved-ye...ount-in-miuis-settings.4563769/#post-88276565
[Xiaomi 13] OberZine:
Yep, believe me, I've tried both.

I have used two versions of the Mi Unlock tool as seen in the original post: I have tried the Mi Unlock tool version 6.5.406.31 and 6.5.224.28.
[Xiaomi 13] NOSS8:
Have you tried everything suggested in this thread?

https://xdaforums.com/t/resolved-ye...ount-in-miuis-settings.4563769/#post-88276565
[Xiaomi 13] OberZine:
Yep, tried it all. believe me, I'm good at this stuff, been doing it since 2010.

And I'm also a Software Engineer in my day job.

Just this one is being a little b.

I made sure my phone wasn't using a VPN, or a DNS as I do often use both.

But I was wondering, (I've never come across this myself) if because it's a china version that I might need to use a china vpn?
[Xiaomi 13] NOSS8:
Others have CN devices and not this problem and others with Global were never able to unlock the bootloader.

And/Or

Prefer an email address for you connected.

used the flash code to login.

can locate your device here:https://us.i.mi.com/

Change account.

perform a factory reset.
[Xiaomi 13] OberZine:
Yeah I've seen.

I've already tried everything you've suggested,

Login via email on both phone and tool,

Login via phone number on both phone and tool,

Login via account number on both phone and tool,

Login via QR Code on tool from phone.

I've already used the locate tool in the browser multiple times, can confirm I can locate all my Unlocked bootloaders xiaomi phones including this one.

I haven't changed my account, but I'm unsure why I would need to do that since I've never had issues with it before since 2014.

I'm worried about doing a factory reset because it's a china rom, which has english language support. but will not have Google play installed. I know I can install it, but it's hasle. I'd rather do this as a last resort, so I may login with a new account if I still can't unlock it later.

Unless theres any other suggestions.
[Xiaomi 13] NOSS8:
I'm worried about doing a factory reset because it's a china rom, which has english language support. but will not have Google play installed. I know I can install it, but it's hasle. I'd rather do this as a last resort, so I may login with a new account if I still can't unlock it later.

It seems to me that for recent phones, framework and play store are included.
[Xiaomi 13] raven213:
have you tried different ports? I know when i unlocked my bootloader mi 10 pro I had to use a different port usb 2.0
[Xiaomi 13] OberZine:
Not on the Xiaomi 13 I ordered. It didn't come with gapps. It was a pain to install, I also still get OTA updates.
[Xiaomi 13] OberZine:
Ironically I replying on my unlocked Xiaomi Mi 10 😂

I unlocked it using usb 3 ports.

I only have 2 usb 3.2 ports

and 4 usb C ports.

Never had an issue unlocking the bootloader on any of my other xiaomi phones. just this one.
[Xiaomi 13] raven213:
and you make sure your phone had your acc for 7 days correct? without formatting or anything ?
[Xiaomi 13] raven213:
i have the ch mi 10 pro lol and for whatever weird reason it didnt liked any usb 3.0 heck it didnt even liked any of my ports so i connected to my monitor usb and it worked lol that was the only was to unlock bootloader for me lol maybe try a usb hub if you have one?
[Xiaomi 13] OberZine:
What do you mean had my account for 7 days?

I've not wiped/formated the phone, I only set up the Xiaomi 13 on the 10th March. 4 days ago.

I've had my xiaomi account for at least 6 years.

I bound the account to the device on the day I got it with no error messages.

and have tried each day to unlock in the Mi unlock tool with the same message

Couldn't Unlock

Please add your account in MIUI's Settings > Developer options > Mi Unlock status
[Xiaomi 13] OberZine:
I had already tried in my hubs, but wouldn't have thought it would've made any difference because it's still going through either USB 3 or C

And it still said the same message:

Couldn't Unlock

Please add your account in MIUI's Settings > Developer options > Mi Unlock status
[Xiaomi 13] raven213:
from what i remember you are supposed to have your account connected to your phone for more than 7 days in order to unlock bootloader
[Xiaomi 13] OberZine:
I saw this somewhere else, but I have not seen an actual source for it. If you could find a source I'd greatly appreciate it.

This must be a new thing because I've never had this issue before. I created accounts and successfully unlocked bootloaders within 168 hours successfully.

On my main account it usually unlocks within 15 minutes. But this time, it's not taking to the binding.
[Xiaomi 13] raven213:
Xiaomi Community

new.c.mi.com

you can check I know before I needed to wait for me to be able to unlock idk if that changed now lol
[Xiaomi 13] dannejanne:
There is a waiting period for unlocking yes but that's not the OP's problem. My phone got recognized in the unlock tool minutes after adding it in developer options. Never seen this issue before on any of my Xiaomi phones.
[Xiaomi 13] OberZine:
Okay, I'm glad you noticed, I thought something was amiss, so it seems there is an issue with it not binding correctly?
[Xiaomi 13] NOSS8:
You have tried everything, the factory reset remains.(Unlock will erase your data anyway).
[Xiaomi 13] OberZine:
I've not got anything important on the device because I want to unlock it, but factory resetting it before I unlock really shouldn't be necessary.
[Xiaomi 13] NOSS8:
See that with Xiaomi.

Procedure advice before factory reset.

Disconnect account from phone and delete phone here.
[Xiaomi 13] OberZine:
I already tried that too,

I tried almost everything which is why I ended up posting.
[Xiaomi 13] NOSS8:
Ok,However in this post it was not the case.
[Xiaomi 13] OberZine:
I'm not entirely sure what your point is?

I had already logged out multiple times, deleted my device on the web portal and logged back in, used find device etc
[Xiaomi 13] NOSS8:
I am talking about factory reset.

"

Procedure advice before factory reset.

Disconnect account from phone and delete phone here."
[Xiaomi 13] OberZine:
I'll do that tonight or likely tomorrow, what a pain
[Xiaomi 13] NOSS8:
Anyway:

Unlocking or stock rom other version or Xiaomi Eu rom=data erased.
[Xiaomi 13] OberZine:
Yes I know, I make roms. ... ..
[Xiaomi 13] mike freegan:
Did yo work out a solution to this? I'm hitting exactly the same issue on the Xiaomi 13 Global Version
[Xiaomi 13] chaogei666:
Since September last year, Xiaomi has stipulated that each new mobile phone must wait for 168 hours to unlock any account, including the internal test account. If the number of new mobile phones unlocked by your account within a year exceeds 4, you will not be able to Unlock the new phone.
[Xiaomi 13] chaogei666:
Must wait 168 hours from the day of binding. If you are a MediaTek processor, you can bypass ta
[Xiaomi 13] mike freegan:
We can't even get to the part where you request the 168 hours. Process fails before the timer starts.
[Xiaomi 13] chaogei666:
Did you bind the account?

Developer Options - Device Unlock Status - Bind Account and Device (It should be noted that the network of the SIM card must be used to bind)
[Xiaomi 13] mike freegan:
Yes. Bound account. Disabled VPN. Tried multiple USB cables. Multiple ports. Removed device form account and added a new account. Nothing works.

I think maybe Xiaomi 13 cannot be unlockedin Europe.
[Xiaomi 13] chaogei666:
You can try the CN version of the unlock tool

申请解锁小米手机
[Xiaomi 13] OberZine:
I will try this. Thanks, I hope this works.

I bind the account to the device, but the mi unlock tool still says to bind it. So odd. I've been doing this since 2014 on Xiaomi devices. So frustrating.
[Xiaomi 13] OberZine:
Out of curiosity how do you actually try the Chinese version of the tool?

It just downloads the normal version from that link??
[Xiaomi 13] chaogei666:
The method is similar, just scan the QR code to log in
[Xiaomi 13] mike freegan:
The link above takes us to the English download page. Presume there is a redirect on the based on browser language or IP
[Xiaomi 13] dannejanne:
Mine is global and had no problem binding it to my account. On Sunday I can unlock it.
[Xiaomi 13] mike freegan:
Huh. I wonder what the difference could be. Perhaps the unlock tool doesn't like Windows 11?
[Xiaomi 13] OberZine:
I've tried it on windows 10 and 11, so it can't be that.