The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Flash fastboot room
Flash fastboot rom
always flash miui with mi flasher
[SOLVED]
alfarhaannizam said:
Flash fastboot rom
Click to expand...
Click to collapse
Worked like a charm. Downloaded MIUI 10.2.3 fastboot rom and flashed using Xiaomi Adb/Fastboot Tools. And then updated to MIUI 10.3.4 via system updater.
Thanks for the heads up. It was really helpful.
mendax99 said:
always flash miui with mi flasher
Click to expand...
Click to collapse
Mi Flasher don't work allright in my computer, since I only have USB 3.0 on my windows device and it seems MI Flasher doesn't work with USB 3.0
I'm using, usually command line abd and fastboot on windows. Today I've downloaded Xiaomi ADb/Fastboot Tolls and it was very useful.
I can't post links yet since I'm new on the forum. But search for Xiaomi ADB/Fastboot Tools GitHub. it is powerful.
otaodofino said:
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Click to expand...
Click to collapse
Why just not just freeze the app/ service ? That's what I did.
MasterFURQAN said:
Why just not just freeze the app/ service ? That's what I did.
Click to expand...
Click to collapse
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
otaodofino said:
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
Click to expand...
Click to collapse
Yeah. I know that flashing a fastboot ROM is the best way to repair corrupt partitions but it also resets the phone and I'm too lazy to restore everything back. Lol.
Related
Suggestion of a stable custom ROM and additional info how to "cleanly" install it.
Hello to the community.
I need your help in choosing a stable custom ROM and some info on the steps on how to make a clean install.
I was using a galaxy S3 i9300 with CM11 and TWRP 2.7, 2 years ago. I bought a used htc m8 and put the S3 on the drawer. Last year i turned it on again and used it some time. I checked for updates and without thinking it, i installed cm 13(snapshot). After restarting it, i had the problem with the " trebuchet stopped" and "google play services stopped".After that, i did sth that i don't remember and had the flashing(boot loop?) twrp logo and not being able to boot to the phone. And i put it again in the drawer. Now i want to give it to my little brother and today i took it out again.
Through terminal and adb i booted the phone with the "reboot" command but had the "trebuchet + google play stopped" message again. After some time fiddling around, i flashed the latest version of TWRP with Odin, thinking that i could solve the problem like that but the phone is stuck on the CM logo trying to boot. Even if it boots i think it will show these 2 messages all the time(but it doesn't boot) .
So i want your advice on choosing a good and stable custom ROM to flash, possibly with Odin. The language will be in english and i don't care if it's Android 6 or 7 or 5 as long as it's stable. He will use the phone for basic stuff and not sth too extreme. I remember using CM11 without issues but i know that now there are lots of others roms. Also i want to make the cleanest install to minimise the possibilities of crashes and to give him a clean from everything, phone. But i have forgotten some steps in TWRP.
Thank you in advance and i'm waiting for your suggestions and advice.
The last official stock firmware is probably best as it is the most stable and he won't be able to break it unlike with custom roms.
Beamed in by telepathy.
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
No custom roms at this time, why bother when you can custom Android 9 using Magisk , Xposed and Substratum. Although having a Lineage 17 would be nice.
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
lschafroth2 said:
I ask because the Android on this phone is so buggy and lacking features. I don't see how the options you gave will add features I need. They might as I'm new to these apps and don't know much about them.
Click to expand...
Click to collapse
If you private message me I cannot get to the messages here. If I click on messages it takes me to the register or reset password every time. I have no way to read them.
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
lschafroth2 said:
At this point it's useless to try since the mediatek drivers no longer work on Windows 10. Not a single guide on installing on Windows 10 64 bit work anymore. If anyone knows how to get the Oukitel drivers to work, let me know. No amount of driver sign or advanced boot works. Every time I plug in the phone it says the previous device malfunctioned.
It worked once and I have never connected the phone since. Will not work.
Click to expand...
Click to collapse
This might seem obvious, but could never get my PC (Windows10 64bit) to even recognize my Oukitel K9 until I (out of desperation, and to try to prove a point to someone) reinstalled Minimal ADB & Fastboot 1.4.3 from here:
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
It's the same thing I had previously installed, and I didn't expect it to suddenly/miraculously start working, but it did.
I'll pm you.
lschafroth2 said:
Are their any projects related to the Oukitel K9 phone? I purchased one and use it on the AT&T network here in the USA.
The phone is decent but the built in Android is very generic and buggy.
I would love to unlock the potential of this phone with a custom ROM.
Let me know if this isn't the right place to ask and point me in the right direction!
Lannie
Click to expand...
Click to collapse
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
nation888888 said:
Best rom floss october edition with buildprop tweaks transformed this phone into next level. Thanks to phherguson
Click to expand...
Click to collapse
Thanks, but I sold this phone and went to a Pixel 4 XL. I needed something reliable and InTune refused to work on the old Oukitel.
Has anyone worked out ramdisk partition for Magisk?
Discovery,
Thanks to Phh has developed the perfect ROM for the Oukitel K9. Strangely I have had to try many ROMs to find the perfect one. The Lineage ROM; I had GPS issues, the Recent app button not working, and signal loss. Wanted the latest OS and this one is the winner below.
https://github.com/phhusson/treble_experimentations/releases/download/v400.e/system-squeak-arm64-ab-vndklite-gapps-secure.img.xz
Llevo un par de semanas probando la rom y no funciona el detector de huellas,se puede mejorar?hay alguna rom(Android 12) mas estable y que todo funcione?,gracias
MOD Edit: I've been testing the rom for a couple of weeks and the fingerprint sensor doesn't work, can it be improved? Is there a more stable rom (Android 12) that makes everything work? Thanks
Try the updated version https://github.com/phhusson/treble_experimentations/releases/tag/v402
Should resolve the fingerprint issue. I have also tried the AOSP 12.1 v410 and the result is the phone goes into a boot loop. Not sure why when the previous version installs so easily. I have built a custom TWRP 3.6.1 and will be trying it soon. The reason why we need to update; that the TWRP 3.3.1 version is limited and could be the reason why there are install issues with some GSIs out there. The encryption keeps reactivating even if I use scripts, flash no verify-verity. Hopefully, this will work. I'm enjoying the new version too much to start again I will keep you posted.
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
nation888888 said:
This one is supreme V411 and distracts me away from my Note 20 Ultra. https://github.com/phhusson/treble_experimentations/releases/tag/v411 .Works well with the Oukitel K9, recommend to use swapram module for boosting memory 4gb to 8gb. Searching for a working TWRP 3.6.
Click to expand...
Click to collapse
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
[email protected]@ said:
Have you found better rom for k9? I've used several gsi images but system is very laggy. Yet to find a good fast custom rom for k9.
Click to expand...
Click to collapse
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
Thanks a lot. I will give it a try!
nation888888 said:
I found this one is the best;
https://www.mediafire.com/file/74b5bgfu0vsjcvg/CherishOS_A13-arm64-bgS-slim_20221121.img.xz/file
Click to expand...
Click to collapse
I've flashed this one and found it is as laggy as CrDroid. I thought it might be due to not wiping data before flashing. Decided to reboot to recovery to wipe data. And.. phone stuck at twrp logo. No go further. Do you have any better TWRP than mine 3.3.1?
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
TWRP logo is for hours here.
Now I can't even enter fastboot after I've chosen reboot to recovery from cherishos power menu.
I hit volup+pwr and boot menu doesn't even show up. Tried 20+ times already.
I'm stuck. The last hope is to wait for it to discharge on twrp logo and try my luck with fastboot menu again.
Otherwise I have no idea. Now I question myself why on Earth I would even try to better something that works at least average ))))
nation888888 said:
Try using the "Yet another Kernel Tweaker" module in Magisk. Through all my searches I could only find the TWRP 3.3.1. Tried building using kitchen but failed. Sometimes the TWRP will take up to 5 to 10 minutes, remember it is trying to decrypt. If it takes longer then SPflash, assuming done correctly with vbmeta. After the initial install the updates and synchronization starts processing. This causes a slow-down. I thought the same. Leave the device for a day to update and synchronize then should be faster.
Click to expand...
Click to collapse
I've managed to revive it. But still on cherishos and few other A13 roms screen is flickering. Have you got something like that?
So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
Code:
fastboot boot twrp-3.3.1-0-tucana-mauronofrio.img
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the
Code:
OrangeFox-Unofficial-tucana-20191120.zip
file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Thanks for taking the time to order it, good job
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
DeathByArmadillo said:
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
Click to expand...
Click to collapse
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
h8Aramex said:
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
Click to expand...
Click to collapse
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
DeathByArmadillo said:
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
Click to expand...
Click to collapse
Yea I tried to find blobs today for 730g but there is nothing on the internet (yet?).
I mean, the phone works for me - if they just fix the missing "Ignore Do Not Disturb" option, I am golden...
flashed orangefox through twrp, touch doesnt work at all. But it worked on the first time, flashed MIROOM. Maybe it is related to the currently installed rom.
Edit: Flashed TWRP from fastboot and touch is working again. Just to be sure, reflashed orangefox and it didn't work again... I'll stick to TWRP, although I dont know if it is a problem with TWRP but i can't flash GSI roms
Hello,
Sorry for my Bad english.
with the stable rom 11.0.7, the orange fox touch works perfectly.
but with development roms, touch does not work. tested with 20.1.9 and 20.1.15.
Touch work with flashed twrp from fastboot
h8Aramex said:
So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Click to expand...
Click to collapse
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
ronademe said:
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
Click to expand...
Click to collapse
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
h8Aramex said:
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
Click to expand...
Click to collapse
Don't worry bro my english is good enough to unserstand the guide ?...but i need to know for exemple words or expressions liké" boot to recovery" etc... How to do that ? What touches to use on Windows
You know what i mean ? I need images or pictures step by step if possible ?????
Can we just install Global Rom in the update option under settings ?
I mean, without needing to unlock the bootloader ?
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Checking for updates
how long does it take to cheking for updates i stuck ? Thank you.
anyone with this rom experiencing huge battery drain ?
sigma119 said:
anyone with this rom experiencing huge battery drain ?
Click to expand...
Click to collapse
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
H-Emmanuel said:
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Click to expand...
Click to collapse
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
There is a MIUI Global 11.0.13? The latest I see is 1.0.7?
I'm looking to update for improved camera speed etc.
First timer on Global Rom, now o EU Beta. Followed instructions, nothing else needed. Thanks a lot! (also, having an usb mouse just in case paid off)
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
sigma119 said:
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
Click to expand...
Click to collapse
Well, that's better than battery drain I hope android 10 with miui will be flawless:fingers-crossed:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
iJaviXR said:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
Click to expand...
Click to collapse
Check my POCO F1 Ultimate Collection & Guides. Try to Clean Install Pixel Experience for example, according my guide (u need to format data also). Let me know how it goes.
Tried Android 10 and 11 Pixel Experience, tried with stock and NG Kernels. Still stays forever in the first load of the SO.
Just got the properties file from XiaomiADBFastbootTools. Maybe someone can see something wrong on it.