leoniadspod
Members
- Nov 3, 2017
- 9
- 15
The buffer error will happen if you do "fastboot boot twrp.img", which is not what I said to do.Sorry, didn't work for me. It gave me the "buffer" error.
The relevant translation repository. No point in talking about it on the forum.Which is the right thread to comment about translation?
Try this twrp and install rompoco f3!!! after i flash the twrp it only boot in fastboot mode....any suggections
What comand you use?poco f3!!! after i flash the twrp it only boot in fastboot mode....any suggections
Had the same on 12S Ultra and this fixedSadly its going right into fastboot, I'm so confused it doesn't show mi logo are anything, just straight to fastboot, volume up power, nothing volume down pwer nothing
Thanks!Code:fastboot erase misc fastboot set_active a fastboot reboot recovery
If you have a recovery then just flash it I always flash a recovery after flashing this ROM twrp is littered with bugs so I don't want to use itCan you advise me the right way to update my recovery to the A13 recovery.
Is it possible through the .IMG recovery file installation, in recovery partition?
I really hate the CMD command method. It took me 4 hours to install
i get this message:
For Poco F3/K40 - Put the new recovery image on both your PC and Phone.What comand you use?
Try enter in recovery = pwr + vol+
You cannot flash a recovery to the F3/K40 directly. See the post directly above this one.i get this message:
C:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (196608 KB) OKAY [ 6.609s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
fastboot boot twrp.imgi get this message:
C:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (196608 KB) OKAY [ 6.609s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
ok i made it...thank you very matchYou cannot flash a recovery to the F3/K40 directly. See the post directly above this one.
Edit: Had to tone down the reply to be less angry because people aren't reading what has already been posted.
Do NOT try to use instructions meant for different phone models if you don't know how the recovery is stored on your device (ie single recovery partition, A/B, or as a ramdisk inside of the boot.img).
Mi Wi-Fi works just fine for me.Miwifi doesn't work in this build.
Alioth uses ramdiskYou cannot flash a recovery to the F3/K40 directly. See the post directly above this one.
Edit: Had to tone down the reply to be less angry because people aren't reading what has already been posted.
Do NOT try to use instructions meant for different phone models if you don't know how the recovery is stored on your device (ie single recovery partition, A/B, or as a ramdisk inside of the boot.img).
If your device is Poco F3 you need to use fastboot command:i am getting this error... what can i do?
On K50G is normal.Poco f3.
I did a clean format and installed last rom.
I tried many time to disable the vibration on the principal key.. I already disabled haptic feedback... but still vibration.... casuallly. Any advice?
Just no. Use the recommended recovery for the ROM.If you have a recovery then just flash it I always flash a recovery after flashing this ROM twrp is littered with bugs so I don't want to use it
No kidding, I've only said that in this thread like half a dozen times and people still try to flash it directly...Alioth uses ramdisk
Thank you very much for your feedback about MIUI 14 on 12T Pro. I have been asking for it many times without answer.Xiaomi really are taking their time to release global rom for 12T pro... Tried the MIUI 14 beta, it is really good, haven't found any bugs, but without the camera libraries can't use it for daily driver. Hopefully waiting will be over soon. Until then MIUI 13 is still good.
Which version and which device?Mi Wi-Fi works just fine for me.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation