yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
I've got my POCO F3 global for 4 months or so and unlocked the bootloader to install a custom ROM.

Since then I've installed Pixel Extended (stayed with it for 2 months or so) and then installed crDroid. I experienced a lot of random reboots since then which I thought could be a rom install problem or something like that so I clean flashed arrow OS but the device wouldn't boot up at all. So I downloaded fastboot stock V12.5.2.0.RKHMIXM GLOBAL (which is as of now the latest stable for Global version) but the device would always bootloop and eventually go to fastboot mode. I tried reflashing it several times and even flashing a previous version of the GLOBAL V12.0.2.0.RKHMIXM and it just doesn't boot the system up - it just bootloops and eventually falls into fastboot mode. I've learned that when I have just flashed it, I'm even able to go POWER + VOL(+) to go to Mi recovery (and even tried to wipe all data from there hoping it would make a difference). But if I let it try boot the system, after it goes to fastboot mode once, I can never access the recovery again.

I'm currently able to boot TWRP, and flash any ROM on top of this non booting stock image and sometimes it does boot up the first time but if I try to flash anything on top of it like opengapps it just fails to boot up ever again. I must say that even after I flash crDroid, it bootloops a lot of time before crDroid logo appears.

So my problem is that for the last 3 weeks or so I'm not able to boot up stock flashed on fastboot and if I flash any custom ROM on top of it it is completely bugged out (random reboots, can't flash gapps, bootloops 10 times before loading the ROM when restarting the phone). I don't know if I somehow messed up any partitions or if there's any problem with my actual hardware that may be causing this. By the way I've been using TWRP-3.5.1-alioth-Nebrassy-2 for flashing and latest platform tools for adb and fastboot (31.0.3). And also, I've been using the usb c cable that came with the device connected to a usb 2.0 hub.

I have the impression that if I'm able to flash stock appropriately and boot it up it might fix the problem but I could be wrong. Also, it's the first time that I flash an A/B device which sometimes gets me confused about the slots.

I've been flashing my android devices since 2010 (Motorola Quench was my first android device) and I've always had to read the forums but I never encountered a problem I couldn't just fix it by returrning to stock or wiping it.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Welcome to the forum mate.

Did you flash the Global Fastboot Stock ROM using Mi Flash? I'd recommend it, instead of using the .BAT files directly.

After it's done, it should automatically boot you into System.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
Thank you for a prompt response, @dreamytom :)

I think I've used that but of course I'll try it again. I'm downloading MiFlash20210226 (latest as of now).

Should I check clean all before flashing it?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
Just dont select flash and lock...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
I reflashed it using MiFlash the first time and it gave me a crclist flash error.

I proceeded and removed the following 2 lines from flash_all.bat file

fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist

I've seen this trick before on other forums and I've never seen it gone badly so I'm trying again without those lines
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
oh, that lesson I learned the hard way in the past. thanks for reminding me of that :)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
After flashing, I got an error on FlashDone step but all previous images seems to be successfully flashed.

It rebooted several times until it ended up on fastboot mode again.

Here's the tail of the log

[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename set_active a ||
[1:38:59 PM 9d3839f8]:info2:Setting current slot to 'a' OKAY [ 0.008s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.010s
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename reboot ||
[1:38:59 PM 9d3839f8]:info2:Rebooting OKAY [ 0.000s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.000s
[1:38:59 PM 9d3839f8]:begin FlashDone
[1:38:59 PM 9d3839f8]:errMsg is null
[1:38:59 PM 9d3839f8]:begin checkPoint
[1:38:59 PM 9d3839f8]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[1:38:59 PM 9d3839f8]:process exit.
[1:39:00 PM 9d3839f8]:flashSuccess False
[1:39:00 PM 9d3839f8]:isFactory False CheckCPUID False
[1:39:00 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[1:39:00 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Yes definitely check "Clean All" before Flashing.

The default checkmark "Clean All and Lock" will lock your bootloader (which you probably don't want happening).

Let us know how it goes.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
It bootloops 5 or 6 times until it lands on fastboot mode again :(

(flashing V12.5.2.0.RKHMIXM Global version)

I'm able to enter the MIUI recovery though
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Try the following:

- Disconnect phone from PC and reboot Fastboot Mode (with POWER + Volume Down)

- Close & Re-open Mi Flash

- Connect phone to PC

- Go into Mi Flash's Configuration page:

Remove the text in the picture:

https://www.thecustomdroid.com/wp-content/uploads/2018/01/Fix-Mi-Flash-Tool-Not-Catch-CheckPoint-Error.jpg

- Check "Clean All" in bottom right corner

- Flash
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
Now I get a success message on MiFlash but it bootlooped 7 times until it got to fastboot mode again :/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
I'm going to flash again with these configs

View attachment 5403253

Trying to see if I get more detailed logs or something..
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
Add the lines into the .BAT script again, that you've removed. This time, try flashing with "Erase All" and "Verbose" enabled in the Mi Flash Configuration-page.

You can also try "check MD5 before Flash" to see if perhaps the ROM is corrupt.

Leave the "CheckPoint" argument removed, that argument is unnecessary.

Keep in mind that you have to disconnect your phone, reboot Fastboot Mode, and re-connect phone to PC.

This is because Fastboot Mode stops receiving any input after an initiated Flash and will result in an error. It may also error out, if you reboot Fastboot Mode while it's already plugged into your PC, for some reason.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
Will do and report back.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
MD5 validation succeeded, put back the CheckPoint argument and checked Verbose and EraseAll.

I just noticed that when I check EraseAll and click OK, next time I open the Configuration menu the EraseAll checkbox is unchecked. I checked it the first time anyways and procceeded with flashing.

This is the tail log:

[2:19:17 PM 9d3839f8]:info2:Sending sparse 'super' 1/9 (722352 KB) OKAY [ 17.075s]
[2:19:17 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:19:54 PM 9d3839f8]:info2:Sending sparse 'super' 2/9 (785380 KB) OKAY [ 36.804s]
[2:19:54 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:20:31 PM 9d3839f8]:info2:Sending sparse 'super' 3/9 (720896 KB) OKAY [ 37.195s]
[2:20:31 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:21:06 PM 9d3839f8]:info2:Sending sparse 'super' 4/9 (766564 KB) OKAY [ 34.844s]
[2:21:06 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.001s]
[2:21:43 PM 9d3839f8]:info2:Sending sparse 'super' 5/9 (744476 KB) OKAY [ 37.345s]
[2:21:43 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:22:20 PM 9d3839f8]:info2:Sending sparse 'super' 6/9 (768840 KB) OKAY [ 36.824s]
[2:22:20 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.001s]
[2:22:57 PM 9d3839f8]:info2:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:info2:fastboot: error: Command failed
[2:22:57 PM 9d3839f8]:info1:"Flash super error"
[2:22:57 PM 9d3839f8]:begin FlashDone
[2:22:57 PM 9d3839f8]:error:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:process exit.
[2:22:57 PM 9d3839f8]:flashSuccess False
[2:22:57 PM 9d3839f8]:isFactory False CheckCPUID False
[2:22:57 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[2:22:57 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true

This is what was failing before I removed the

fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist

lines.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
I've seen the error "Failed to check Sparse CRC" quite a few times and had it myself.

Try Rebooting your PC and switching the USB port. You can also try changing the cable.

That doesn't sound like it'd do much, but a dude I've chatted with from here, and myself had this error, and we both succeeded in flashing our ROMs by doing the above. ^

Also make sure the path to your ROM doesn't contain spaces. Mi Flash is stubborn.

I just temporarily put the ROM folder in C:/
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Animesh Singh:
Try flashing with this tool.

XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone

XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!

www.xiaomitool.com

While you have your phone connected to the PC, Select my device is bricked, Choose your phone model from it's list. It will download the stock ROM on itself and flash it. I had gone through the same problem a few months ago when i had the k20 pro. This tool got it sorted out. Give it a try. Goodluck.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
Created a folder for the image at C:\mi\ even though my previous folder didn't have any spaces.

Changed the cable and the port (I was using a USB C dock + USB A dongle and now it's directly in the back of my computer)

Result is the same 'failed to check sparse crc' :(

I'll try different combinations of ports and cables to see if the outcome changes and report back.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
Thank you for replying.

I got this tool installed and even tried it in the past weeks. It downloaded the fastboot ROM again but I had the same problems as mentioned above. I'll try it again soon.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
That sucks. Try EU ROM (or if you're not in the EU, your specific region), instead of Global.

I don't know how on earth that would make a difference, but just to see...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Animesh Singh:
Good lord . If you're under warranty, MI will fix it. If not and in a hurry, There's this guy Unlockafe on Telegram, Who will remotely flash your device for some fee (25$ if i can remember) . He uses factory software's which will flash your device in any condition. MiFlash has given me problems all my life. The guy helped me during lockdown when the service center was closed. I'm not promoting him, I'm Just letting you know.

The rest is upto you.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
I'll try flashing EEA V12.5.3.0.RKHEUXM now, let's see if that makes a difference.

My phone originally had GLOBAL version installed.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
Unfortunately no warrranty :(

But I'm sure interested in this guy's services.. How do I contact him?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Animesh Singh:
On Telegram @Unlockafe
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Rstment ^m^:
couple of things ...

If u just want ur phone up and running download poco f3 eea 12.5.3. Asuuming u have poco f3.

If that doesnt work for u - u must have global for whatever reason? I guess ur trying to go into global enhanced edition? then download from here fastboot rom: https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.2.0.RKHMIXM/

Download propper miflash - I used drivers from mi flash v2 by letting it start and auto install all drivers and stuff then I open MiFlash20210226 ( Search for it online ) and 12.5.2 flashes succesfully - I fked up like 3 times by starting flash w locked selected so I stopped 3 times the process... reboot back into fastboot and on 4th time actually selected the right optionand it flashed well. When I tried without miflash I was given same crc error. In the past when I tried removing crc check it flashes everything but phone bootloops. So you must not remove it ... Gotta find what mi flash will work for u

EEA always works for me via miflash or just manuially flashing using flash_all.bat script and by far is the best version of miui... I had to move because of miui enhanced but I'm going back when it arrives there
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] chrisparkerrr:
It booted up in this version. No errors flashing 🥳🥳🥳

Let's see if I can get crDroid so it's all back to normal
[Connected Car] Ainslei76:
Good Day

I am hoping to get some help from this Forum.

I have a Seicane Android Head Unit

PX5 - rk3368

Android 10

MTCE HF V3.55

Problem is that the screen on the head unit is very dark and the touch does not work.

My phone is connected via bluetooth and the strange thing when I receive a call the screen comes to life ... It is bright and works fine when the call is active. As soon as the call ends the screen goes dark and the touch stops working.

Any idea what is the cause and how to fix?

Thanks
[Huawei Developers] Mrjonez1991:
I beleive my phone has been hacked. I think its been double cloned what can i do.
[Huawei Developers] blackhawk:
Backup data, be aware there may be infected files in it. A cross infection (ie another package targeting that platform) to the PC is unlikely but possible.

Using 2 OTG flashsticks (redundant backup) be safer.

Or use cloud plus a OTG flashstick.

Delete Google, Email accounts etc.

Factory reset.

Change all account passwords.

Verify it is secure before adding apps and backup data, if it reoccurs after adding backup data... there's an infected file(s) in the backup data or a rogue 3rd party app you installed.

Don't repeat the mistake that caused this.
[Samsung Galaxy Z Flip 3] jc83:
Hi folks,

Sorry for the dumb question but my last new phone was my Sammy S10 awhile back (still using) and I wanted to know if I need to run to a tmobile store once my grey z flip 3 arrives to get a new sim card? My S10 is 4GLTE and this flip 3 will be 5g (unlocked version via samsung website).

Thank you!
[Samsung Galaxy Z Flip 3] twistedumbrella:
As long as it's a micro SIM (slightly smaller than a micro sd), you're fine.
[Samsung Galaxy Z Flip 3] manderspaul:
Its the same sim-card :)
[JAMin, XDA Neo, S200 General] kordi666:
Has anyone tried using wmwifirouter to create ad-hoc wifi connection with the PC?

I installed the program however the computer does not see the connection. Maybe you had more luck with it?
[General Questions and Answers] BryanFake:
Is it still possible to unlock the bootloader on a SM-G965W from Canada (BWA) with Android 10 G965WVLU9FUE2 (May 2021). I cannot get OEM Unlock to show up. Tried all the normal steps to get it to show up. Change time, disable updates, reboot, wifi connected, logged into google, logged into samsung, etc. and probably evey combination of these settings. In the process of actually waiting 7 days.
[General Questions and Answers] :
My POV: If OEM Unlock option isn't offered, then manufacturer doesn't allow unlocking the booloader.
[Asus Zenfone 4 (2017) Questions & Answers] StevePC:
I'm not sure whether anyone still looks at these forums, but here goes.

Bought a used Zenfone 4 ZE554KL off Ebay, as I already had one and wanted to have another to tinker with. It was clearly labelled not working and not receiving network service. I thought I would have a look and see if I could do anything about that, and if not, I could still use it to try and (finally) learn how to root this thing without bricking my own!

I have managed the latter (i.e. unlocked the bootloader and then rooted the phone) thanks to some threads on here, but I still cannot sort the no service issue. But it is interesting as the phone shows a baseband, indicates that it has an IMEI (under setting), and it did connect the first time I put my own sim in it (after doing a factory reset through recovery), but then as soon as I turned the phone off and on again, it was no longer getting service, and I haven't managed to get it back since.

Dialling *#*#4636#*#* and looking under device information shows no IMEI, no network, signal strength 0, and the mobile radio power button is off and when turned on, goes back to off as soon as I go away from that screen.

A question I would like answered if anyone can, is whether this is a baseband issue, i.e. a hardware issue, or whether it is worth trying to resolve this in some other way. I have seen suggestions that rewriting the xqcn/qcn (?) file can/might help, but I have run up against problems trying to do this.

So, if anyone has any ideas, I'd be very grateful, but bear in mind, I am pretty new to all this.
[Galaxy S6 Q&A, Help & Troubleshooting] max4578:
Hello everyone, will miui firmware be released on s6 ???
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Harshadd30:
I'm on MIUI 12, I'm not able to install TWRP recovery properly.. internal storage is encrypted.. not able to flash anything. anyone has a solution ? thanks in advance !
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
When, entering TWRP, it asks you for PIN/password.

You have to enter your pin/password you have defined in Android for unlocking the screen.

TWRP must then confirm that it successfully decrypted for user 0 (for user 999 it would fail, do not wory about)

This is really nothing new, but you must not use an outdated TWRP that does not ask or does not support it properly

If having problems, reboot to Android and reset your pin/password.

Some TWRP versions may not support properly if you use pattern in Android - hence better switch to pin.

However, if you cannot make it with pin, reboot again to Android, redefine to pattern and try
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Harshadd30:
i have tried, i swiped to allow modification but it does not asked for password, goes straight in recovery mode & i can not access my files from there, i also tried removing password completely to unlock phone but still got the same issue.. i have heard that files are encrypted on android 11, so i posted this question..

thank you
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] zgfg:
Make sure you use the latest official TWRP for davinci

Which "notifications" - it's about Passwords and Security in Android. You can try by removing Android unlock pin/pass, reboot to Android and set it again and then try with TWRP.

Again, make sure you use up-to-date TWRP, best the official

twrp-3.5.2_9-0-davinci.img (if you were not familiar with and TWRP does not ask, maybe you are on an ancient and maybe some unofficial TWRP)
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Vanmanman:
HI, I updated to V12.1.4.0.RFJMIXM and tried to install the latest TWRP but booting into recovery mode TWRP is in this like read only mode and dosnt bring up the usual thing to decrypt your files. It says unmodified system partition. Keep system read only? TWRP can leave your system partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root your device. Then it says keep read only or swipe to allow modifications. Any suggestions? Tried removing and adding security pin but didnt work

I need it to install magisk. I tried patching a recovery image with magisk which worked. But trying to boot to magisk with recovery dosnt work. I hold the keys and then when it vibrates let go but it always goes to stock recovery. Not system with magisk as it talks about.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] giannism13:
This seems like a bootloop. Did you change any roms before this happened? You might have to format (not wipe) your data partition which unfortunately will also delete all your files from the phone's internal storage.
[Lenovo P11] kure94:
Hi everyone.

I´ve decided today that I want to re-lock my bootloader on Lenovo P11 tablet and I discovered no fastboot commands work on that.

I installed clean version of ROM from Lenovo Rescue and Smart Assistant (TB_J606L_S120217_210805_ROW) but still nothing works.

Normally i reboot to Fastboot and try "fastboot flashing lock" but i recieve:

< waiting for any device >

FAILED (remote: 'Unrecognized command flashing lock')

fastboot: error: Command failed

When i try others like "fastboot oem lock" i recieve:

FAILED (remote: 'Command not supported in default implementation')

fastboot: error: Command failed

Does anyone has any advice what can I do to relock bootloader?
[Lenovo P11] ong14:
1. enable developer option

2. enable oem unlock in developer option

3. boot to fastboot mode and run

fastboot flashing lock
[Lenovo P11] kure94:
Thanks @ong14 for your reply but as you can see above I already tried that...
[Lenovo P11] ong14:
If you're on chinese firmware, try "fastboot oem unlock-go".
[Lenovo P11] kure94:
Sadly I get this response for this command:

FAILED (remote: 'Command not supported in default implementation')

fastboot: error: Command failed

Is it possibly because of version of my ADB and Fastboot tools? I downloaded many versions (lastly directly from Android Studio) but it didn´t fix anything. @ong14, could you possibly upload the tools you are using?
[Lenovo P11] ong14:
Sorry for my last reply, it should be "fastboot oem lock-go".

AFAIK, if you're on global rom, use this "fastboot flashing lock".

And if you're on chinese rom, use this "fastboot oem lock-go"

I'm using an old minimal adb and fastboot.
[Lenovo P11] kure94:
It is totally OK, I am grateful that you are trying to help me at all.

I will try your old adb and fastboot tools and see what happens.

Sadly I don´t have much hope. I am on global rom and command "fastboot flashing lock" resulted only in:

"

FAILED (remote: 'Unrecognized command flashing lock')

fastboot: error: Command failed

"

I will keep you posted about my progress and what else I tried.
[Lenovo P11] kure94:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.

Did anyone else run into this problem?

Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".

Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"

Does anyone pls have working drivers or should I continue trying fastboot mode?

Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
[Lenovo P11] Casperx7:
My guy, you are brilliant. I wonder why the change from oem to flashing was done and were you getting sent to that fastbootd menu too? This worked for my 2020 Moto Edge and I don't know how much longer I would have needed without you.

Thanks.
[Lenovo P11] mingkee:
Install RSA from Lenovo also works, and you can run rescue if you want to go back to 100% bone stock