** Warning For Those Using Latest Global Beta's 10.x.x **
Problem I Encountered:
After this morning's update to the Weekly Global ROM 8.12.13 (through stock software updater), the update went just fine and i was using my phone most of the day. As you all know i have a China phone (no root, factory recovery) with the Global ROM (bootloader unlocked always). I decided to reboot the phone later on that day, it took forever to restart, and eventually restarted with the TOUCHSCREEN not working! I mean -like it was DEAD. I loaded up TWRP in fastboot, still was dead in recovery (and took forever to boot to). I factory reset (god i hated to do that), it was still dead! I downloaded the fastboot ROM from 8.12.7 beta and flashed all the partitions.... IT WAS STILL DEAD. I fastboot flashed the 10.0.2 Stable ROM... STILL DEAD. I even plugged in a USB-C dongle from Samsung to use my logitec wireless keyboard and mouse on my phone (which worked well) and setup to enter the CIT mode for diagnostics. There was no touch screen function / logging period. Bad news, i figured my Digitizer just went bad. I was converting my backup phone (old LG G2) to use, and also figured i'd put my Mi8 back to China Factory 9.6.7 (no rollback isn't enabled yet) before locking the bootloader back and getting it RMA'd. When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either.
Conclusion:
They (Xiaomi) have something totally F***ed up in their new betas that randomly screws up firmware for the touchscreen. I'm still going to use them (i know ) because they are so much better now than before.
Soooo Many Xiaomi Questions:
What if my bootloader was locked and i couldn't have flashed back to the old MIUI ROM?
What if the Anti-Rollback actually WAS enabled and i couldn't have flashed back to the old MIUI ROM?
What the he** is in China 9.6.7 that fixed the issue that Global 10.x.x couldn't have? And WHY?
* At least we all have a solution for now..... But i hope that bug doesn't show up for anyone else....
Solution:
1.) Set you phone to Fastboot Mode (Reboot and hold down the volume-down button and power button)
2.) Connect your phone to your computer
3.) With your previously downloaded Fastboot image file of V9.6.7 China ROM, enter your choice of command
-- The command with "Flash all partitions" is recommended. ** Do Not Choose To Re-Lock Bootloader **
4.) When it finishes and reboots, your touchscreen will be functional again!
/.
boot your phone and use mouse using otg.
and try to use camera den try to vibrate...
if working... i think that is digitizer if not...
u need to flash the one partition for sensor ?
Bull****.
Sigray said:
Bull****.
Click to expand...
Click to collapse
Obviously this.
OP somehow managed to delete parts of the persist partition..or some freak accident or defective device.
I had the same experience. My device is global version, but I imported it and since I don't have un authorisation Mi store to rely on I just flashed oreo based rom with mi flash tool without knowing if ARB will trigger because I had nothing to lose. The digitizer turned on and out of curiosity I flashed 8.12.13 with the flash tool. It is working fine but for now I won't trust the updater app.
Sent from my MI 8 using XDA-Developers Legacy app
@Agimax Can confirm the issue. Faced the same problem. Followed your procedure and everything is up and running. I wonder what Xiaomi screwed up this time. Thanks a ton for the guide, was really worried for a while!
Mhm...wouldn't have thought.
Possibly something going wrong with Oreo>Pie upgrade on china devices running global roms ?
9.6.7 was the last stable release one can downgrade to on global devices and use to upgrade to pie based global beta.
I really wonder what is missing in Pie vs Oreo that the digitizer needs. I'm just worried in the future when anti-rollback is truly enabled we won't have a way to fix the issue until we find the missing/corrupted driver or file problem. Pie flashed from fastboot with all partitions should fix any issue, with files -but doesn't. That's a real problem and means they omitted something critical.
Touch Screen out of use!
Touch Screen out of use!
Same thing happened to me too. Simply after a reboot, as if the phone was initialized after the first installation (very strange) and just started, the touch no longer works.
Version Rom 8.12.13 Weekly
Agimax said:
** Warning For Those Using Latest Global Beta's 10.x.x **
Problem
After this morning's update to the Weekly Global ROM 8.12.13 (through stock software updater), the update went just fine and i was using my phone most of the day. As you all know i have a China phone (no root, factory recovery) with the Global ROM (bootloader unlocked always). I decided to reboot the phone later on that day, it took forever to restart, and eventually restarted with the TOUCHSCREEN not working! I mean -like it was DEAD. I loaded up TWRP in fastboot, still was dead in recovery (and took forever to boot to). I factory reset (god i hated to do that), it was still dead! I downloaded the fastboot ROM from 8.12.7 beta and flashed all the partitions.... IT WAS STILL DEAD. I fastboot flashed the 10.0.2 Stable ROM... STILL DEAD. I even plugged in a USB-C dongle from Samsung to use my logitec wireless keyboard and mouse on my phone (which worked well) and setup to enter the CIT mode for diagnostics. There was no touch screen function / logging period. Bad news, i figured my Digitizer just went bad. I was converting my backup phone (old LG G2) to use, and also figured i'd put my Mi8 back to China Factory 9.6.7 (no rollback isn't enabled yet) before locking the bootloader back and getting it RMA'd. When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either.
Conclusion:
They (Xiaomi) have something totally F***ed up in their new betas. I'm still going to use them (i know ) because they are so much better now than before.
Soooo Many Xiaomi Questions:
What if my bootloader was locked and i couldn't have flashed back to the old MIUI ROM?
What if the Anti-Rollback actually WAS enabled and i couldn't have flashed back to the old MIUI ROM?
What the he** is in 9.6.7 that fixed the issue that 10.x.x couldn't have? And WHY?
* At least we all have a solution for now..... But i hope that bug doesn't show up for anyone else....
Click to expand...
Click to collapse
I had same problem, from version xiaomi.eu 8.12.13...
This manual from Agimax is excellent !!! Helped me.
Many thanks.
@Agimax
hello, I have the same problem, I was in the Xiaomi eu version 8.12.7 and all good, update to version 8.12.13 and it was all good, restart the mobile and the touch stopped working, everything you mention makes, go down to another beta version, in twrp it does not work either and just take the mouse. You can tell me how to do the process, he was in the stable global version 10.0.3.0 (oeamifh) how he made this installation, it is not clear to me the antirollback, I only have the bootloader unlocked and a backup of that version through TWRP, but I'm afraid that going back to Oreo while standing generates a brick. Please your help indicating me step by step and things to keep in mind
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Which Manual?
Which Manual? Can you post a link?
Luko69 said:
I had same problem, from version xiaomi.eu 8.12.13...
This manual from Agimax is excellent !!! Helped me.
Many thanks.
Click to expand...
Click to collapse
1MaxMar1 said:
Which Manual? Can you post a link?
Click to expand...
Click to collapse
If you read the whole paragraph of my issue, i explained the downgrade on my China phone to 9.6.7 with the Fastboot mode ROM method worked when the others didn't:
So download the china ROM 9.6.7, reboot to fastboot mode, flash the rom from your computer in fastboot, then reboot.
From OP:
"When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either."
Agimax said:
If you read the whole paragraph of my issue, i explained the downgrade on my China phone to 9.6.7 with the Fastboot mode ROM method worked when the others didn't:
So download the china ROM 9.6.7, reboot to fastboot mode, flash the rom from your computer in fastboot, then reboot.
From OP:
"When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either."
Click to expand...
Click to collapse
hello, any recommendation to rollback, according to what you say the rollback protection is not active, but I do not want to take any other surprise, I have the 8.12.13 eu! regards
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
I had also 8.12.13 xiaomi.eu, (now 8.12.20), no problem with rollback after downgrade to china 9.6.7
@Agimax
hello sorry but I'm somewhat desperate, my team is global version, I'm in Xiaomi eu 8.12.13 which version I install to recover my touch ??? The truth is I'm afraid of a brick because of that antirollback !! I hope you can help me!
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Reading is hard
Stoffl_ said:
Reading is hard
Click to expand...
Click to collapse
Sometimes i wonder why i maintain all these threads to help users......
For some reason it's especially bad with xiaomi devices. The miui forums are horrendous.
Maybe it's the user base, they are are mostly sold in Asia and India..
Agimax said:
Sometimes i wonder why i maintain all these threads to help users......
Click to expand...
Click to collapse
In my case I have read the post several times, only that I have some doubts and the truth is that I am new to the Xiaomi scene.
* I must install the Chinese version if or if or also can the global one?
* Should it be Fastboot if or if or MiFlash?
* I must install something else to avoid brick by downgrade or something from the antirollback since as you say it is not activated, it is for all devices.
I hope you understand me and before I thank you for your help, since I am desperate because I thought I would lose my cell phone.
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Related
I encountered this problem about 2 weeks ago
I have flash every ROM (Official, MIUI based custom ROM, and AOSP) including in fastboot mode
and only CM12.1, CM13 and RR survived from random reboot
I won't use both CM13 and RR because its RIL
Now i used CM12, but I have super fast draining battery
My phone will die, even in standby, because Android OS and System used battery more than SOT
When I checked it, the CPU always stay awake and won't enter deep sleep, so my phone always went heating even in standby (screen turned off)
The only problem I would fix is the random reboot issue when I used MIUI and other Custom ROM I had mention above
This is driving me crazy. Does it hardware problem or something?
If not, how to fix fast draining battery from CM12.1?
Sorry for my bad english
putrairlangga said:
I encountered this problem about 2 weeks ago
I have flash every ROM (Official, MIUI based custom ROM, and AOSP) including in fastboot mode
and only CM12.1, CM13 and RR survived from random reboot
I won't use both CM13 and RR because its RIL
Now i used CM12, but I have super fast draining battery
My phone will die, even in standby, because Android OS and System used battery more than SOT
When I checked it, the CPU always stay awake and won't enter deep sleep, so my phone always went heating even in standby (screen turned off)
The only problem I would fix is the random reboot issue when I used MIUI and other Custom ROM I had mention above
This is driving me crazy. Does it hardware problem or something?
If not, how to fix fast draining battery from CM12.1?
Sorry for my bad english
Click to expand...
Click to collapse
hello I would like to know if you solved because I have a very similar problem to your......
If it's down to some ROMs being a WIP then perhaps the best option is to go back to stock?
Sent from my Redmi Note 3 using XDA-Developers mobile app
samanderson said:
If it's down to some ROMs being a WIP then perhaps the best option is to go back to stock?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
the problem is only present in rom stock because it seems to work just a core of 6 and do not know how to solve
HydroAG said:
hello I would like to know if you solved because I have a very similar problem to your......
Click to expand...
Click to collapse
No, I haven't have you?
samanderson said:
If it's down to some ROMs being a WIP then perhaps the best option is to go back to stock?
Click to expand...
Click to collapse
I just tried Flash Official ROM via Fastboot (MiFlash) but my problem still exist like I mentioned above
HydroAG said:
the problem is only present in rom stock because it seems to work just a core of 6 and do not know how to solve
Click to expand...
Click to collapse
but why it didn't happen before?
I often wipe and flash my device, does it caused the problem?
Hi, i'm having the same issue as yours, have you try to send for repair? Xiaomi centre at my place refuse to repair it as mine from china set, any luck at your place?
Edit- mine was unlocked officially, don't think it related to this issue as it was working without any problem previously,the last thing i did before this happened was making a call in lte before it turned off suddenly, then heat up a lot and keep on rebooting,
asared89 said:
Hi, i'm having the same issue as yours, have you try to send for repair? Xiaomi centre at my place refuse to repair it as mine from china set, any luck at your place?
Edit- mine was unlocked officially, don't think it related to this issue as it was working without any problem previously,the last thing i did before this happened was making a call in lte before it turned off suddenly, then heat up a lot and keep on rebooting,
Click to expand...
Click to collapse
No I could not solve, even to me has happened after a call was 7.2 on global you?
I live in Italy therefore it is difficult to send it to a service center
HydroAG said:
No I could not solve, even to me has happened after a call was 7.2 on global you?
I live in Italy therefore it is difficult to send it to a service center
Click to expand...
Click to collapse
I'm on aosp when this happened, maybe it is hardware related,
Will try to send it to repair shop nearby and hope they can do something about it, it's only a month and now it's completely unusable, maybe just a bad lemon unit
Same problem here...I bought this phone from China and it worked fine for 10 days...Suddenly it begun to rebooting every 20-30 seconds, i can't do anything in the phone...
I managed to flash it with other roms and the problem remains...
I am absolutly disgraced for this....I loved this phone, it lasted only ten days....
Rofellos_Chile said:
Same problem here...I bought this phone from China and it worked fine for 10 days...Suddenly it begun to rebooting every 20-30 seconds, i can't do anything in the phone...
I managed to flash it with other roms and the problem remains...
I am absolutly disgraced for this....I loved this phone, it lasted only ten days....
Click to expand...
Click to collapse
where did you buy it?
xGiorgos said:
where did you buy it?
Click to expand...
Click to collapse
Goldway store, aliexpress...I am still in the protection period so i think it won't be difficult to obtaining a refund...But still i prefer to fix it...
I think is a hardware problem though...i think it has something to do with the energy or temperature managment or circuitry...
Rofellos_Chile said:
Goldway store, aliexpress...I am still in the protection period so i think it won't be difficult to obtaining a refund...But still i prefer to fix it...
I think is a hardware problem though...i think it has something to do with the energy or temperature managment or circuitry...
Click to expand...
Click to collapse
Should be hardware problem and there's nothing we could do i guess, there's a few people affected already.. problem with this model and we're the first.. so sad. Luckily my nexus 5 still going strong despite the screen shattered, even can see the circuit inside, showed the difference between brands quality.
Did someone with this problem can Instal CM13 ROM with fingerprint compatible?
because mine always stuck in Mi Logo and then can't enter TWRP until it re-unlocked and back to MIUI with Mi flash to able flash TWRP)
If not flash fastboot MIUI, the TWRP can't be installed even the phone have unlocked
WTH is going on with my phone
putrairlangga said:
Did someone with this problem can Instal CM13 ROM with fingerprint compatible?
because mine always stuck in Mi Logo and then can't enter TWRP until it re-unlocked and back to MIUI with Mi flash to able flash TWRP)
If not flash fastboot MIUI, the TWRP can't be installed even the phone have unlocked
WTH is going on with my phone
Click to expand...
Click to collapse
It is almost ending its lifespan, I presume.
Unlock, twrp and flash cm. if all else fails, go to Service Center
Sent from my Unlocked kenzo, the power unleashed
any news with that issue?
cause of what i understood , there is a bug hardware isuue with Charging Controller on Xiaomi Redmi Note 3 pro ,
and hardware must be repaired....
Try flashing global stable through MiFlash and tick the option flash all or equivalent.
Ivanlai said:
Try flashing global stable through MiFlash and tick the option flash all or equivalent.
Click to expand...
Click to collapse
Thanks Ivanlai,
What Exactly do you mean by your answer?
did you had this Problem on your Xiaomi Device?
had you manage succesfuly solving it?
my device is new and i dont want to do something that will harm the Warrenty.
I haven't had this situation exactly, but the reason I said to tick flash all is because I have bricked and bootlooped my device before.
By ticking the flash all option, it reduces the risk of some remnants of the previous ROM causing conflict.
Also, I tried several different global stable ROMs before I successfully unbricked my device.
As for warranty, I remember someone mentioning that a xiaomi customer service operator emailed them saying that rooting and flashing custom ROM would not void the warranty, but I would email them again on this issue just to make sure.
Ivanlai said:
Try flashing global stable through MiFlash and tick the option flash all or equivalent.
Click to expand...
Click to collapse
Ivanlai said:
I haven't had this situation exactly, but the reason I said to tick flash all is because I have bricked and bootlooped my device before.
By ticking the flash all option, it reduces the risk of some remnants of the previous ROM causing conflict.
Also, I tried several different global stable ROMs before I successfully unbricked my device.
As for warranty, I remember someone mentioning that a xiaomi customer service operator emailed them saying that rooting and flashing custom ROM would not void the warranty, but I would email them again on this issue just to make sure.
Click to expand...
Click to collapse
Thanks Ivanlai,
very strange what happening to my device.
reboots stopped (have no idea of what reason : recharge again from 5% battery, get into test mode (push 3 button for 10 sec': vol+, vol-, power).
but now other issue showed up : very lots of screen glitches, can use the phone like this, like some bad soldering inside.
first time i got into test mode, there were also screen glitches,
but now, whenever i get into test mode, downloading mode or the 3rd mode (with phone and cable picture), there is not glitchs at all,.
but after phone is starting - lots of screen glitches !!
i am lost
I also bought my Redmi 4 Prime from goldway store, do you know what is their return policy like?
Hi
Today after installing the update to xiaomi.eu rom, Android 10, my touch screen just died. I tried flashing 3 various roms by MiFlash with no success. I am able to use fastboot, adb and install TRWP but no matter what I do the touchscreen is dead making the phone useless.
When I boot it up I get asked to unlock it by providing the password to my mi account, which previously worked, but currently I'm unable to use my phone.
Anybody had a similar issue? any way to fix it?
Did you choose clear all option when flashing from fastboot
Yes, with no result unfortunately.
Can you use the touchscreen while in TWRP/recovery mode? If you have a OTG cable you can connect a normal USB mouse to your phone and use that to navigate. Maybe it is just locking up at the password boot stage?
Try to flash it back to stock with stock recovery with a different build date preferably 9 and see if you can wipe it that way......
will try both ideas later today
SOLVED
I finally managed to get it back to life. It turned out that I must have damaged the touch drivers and flashing the phone by fastboot didn't help at all as the drivers are located on prevent partition (as I was told by someone)
So the thing I did was to flash a custom kernel with touch drivers. I used franco kernel kernels.franco-lnx.net. First I installed (using physical mouse) xiaomi eu android 9 rom, than I flashed the franco kernel for android 9. At that point the touch screen came back to life. Afterwards I was able to update to xiaomi eu android 10 rom with no problem.
Hope it can be helpful for anybody with similar problem.
Just few days after installing miui 12, got this problem. The phone is stuck on a boot loop. If I pattern unlock the phone, I get a toast saying "find device stopped unexpectedly". Unfortunately, I don't have a backup. :crying:
Is there any way to save my phone? or may be get a backup?
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Dhamo200694 said:
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Click to expand...
Click to collapse
Use an Intel pc. Amd has issues with mi flash unlock too l. Run as admin. Turn off all anti virus/ firewall applications.
Having the exact same issue on my POCO F1, recently updated to MIUI 12. It was working pretty well up until 10 mins ago.
Battery went under 5% and the device went into ultra power saving mode, then restarted. Now every time I unlock the pattern, the toast pops up "Find my device..." and it goes into bootloop.
Now there isn't even a pop up, device immediately goes into bootloop.
bro, i just now facing this.. can you help me out
Well, MIUI 12 is not going good in poco F1.
If anyone who has not updated to MIUI 12, don't update the phone. Currently there are many bugs in the update
Long story short -
Some are unable to boot up the phone, some stuck in bootloop, some unable to use their passwords, some unable to set up new password, Second space not working, etc etc ...
I also updated to MIUI 12 and was unaware of the bugs.
But the device booted up and password (both fingerprint and face unlock) was working fine but I was unable to change it. Second space was working too. So I was happy that there is not much issue.
But then come the buggy part.
I started playing COD m after update and battery drained like hell 100 to 30 in 1.5 hour. I was shocked by this.
After charging I started to play again but this time (with battery issue) screen freezing happened and then happened at regular intervals. So the gaming experience on MIUI 12 was ruined.
Then I just find MIUI 9 for it and flashed it. (Ya, factory reset in this process too ?) But it is working fine now. Got fast charging module and custom thermal for gaming and it worked.
Currently no issue at all.
But I am still finding a custom kernel for poco F1 to overclock cpu and GPU (not able to find any till now).
Nearly every kernel is ment for MIUI 11 and 10 only. So I am digging deep for now to find a kernel for MIUI 9.
At last just one message - Don't update untill mi release a stable and bug free MIUI 12 version.
If MIUI 12 is working fine on your poco F1, either you are lucky or you have not encountered a bug till yet.
Without data loss, is this method come back to normal as before for poco f1 mobile?
Without data loss, is this method come back to normal as before for poco f1 mobile?
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
arulprakash2000 said:
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
Click to expand...
Click to collapse
If you don't want to loose your data, try flashing the rom using mi flash tool. But nothing can guarantee data security. You should back up your data regularly, waiting for a mishap or trusting on a single electronic device is just foolish, do make multiple copies of important data, if you want it to be secure.
I also have this problem. Updated my POCO F1 to miui 12 and it is in bootloop all the time. The bootloader is locked but I cannot unlock it now with no access to the device. How can I flash again a lower version?
If I don't mind losing the data how can I go back to previous version?
No brother, I encountered the same issues you mentioned. I stuck with MIUI logo loop after that I did a hard reset to mobile phone working condition.
EDIT: IF RESET FACTORY DOESNT WORK FOR U JUST GO TO SERVICE CENTER(I did it after all)
Hello
My device is Global version with miui V13.0.4.0.SKIMIXM
my fingerprint stopped working a week ago, then i contaced the support and they said these solutions:
1-factory reset
2-wipe data
3-download latest package
4-clean fingerprint area
i did all and somethimes just right after booting device my fingerprint showed up and working but after about couple hours back to the problem.
on early time of this problem i had fingerprint setting but couldnt open it (couldnt add fingerprint hint) but after some times it removes from setting too then at last after wiping data and solution above , fingerprint never showed up. so i decided to flash the original rom with fastboot and after i did that my fingerprint comesback and was working but again after couple hours stopped.
the thing is if safe mode it was working. even after rebooting to normal working 2 or 3 times then after that stop working again. in safe mode CIT fingerprint tests passed successfully untill right now after half a day i dont have fingerprints even in safe mod.
so i think of downgrading to miui 12.5.7 just want to be sure is it safe to downgrade because when i wanted to flash miui13 it errored with rollback but i edited script and flash was successful.
script edit is safe for downgrade ?
and maybe is there any othe solution that im not aware of?
13eauty said:
Hello
My device is Global version with miui V13.0.4.0.SKIMIXM
my fingerprint stopped working a week ago, then i contaced the support and they said these solutions:
1-factory reset
2-wipe data
3-download latest package
4-clean fingerprint area
i did all and somethimes just right after booting device my fingerprint showed up and working but after about couple hours back to the problem.
on early time of this problem i had fingerprint setting but couldnt open it (couldnt add fingerprint hint) but after some times it removes from setting too then at last after wiping data and solution above , fingerprint never showed up. so i decided to flash the original rom with fastboot and after i did that my fingerprint comesback and was working but again after couple hours stopped.
the thing is if safe mode it was working. even after rebooting to normal working 2 or 3 times then after that stop working again. in safe mode CIT fingerprint tests passed successfully untill right now after half a day i dont have fingerprints even in safe mod.
so i think of downgrading to miui 12.5.7 just want to be sure is it safe to downgrade because when i wanted to flash miui13 it errored with rollback but i edited script and flash was successful.
script edit is safe for downgrade ?
and maybe is there any othe solution that im not aware of?
Click to expand...
Click to collapse
solution is service center...in theory no anti rollback....just check in script before flash
rayman95 said:
solution is service center...in theory no anti rollback....just check in script before flash
Click to expand...
Click to collapse
thansk for reply so youre saying that in theory there is no problem to downgrade with editing script but in real life God knows right?
Unfortunately I have the same problem on my MI11 Lite 5G.
I would be interested if I install a custom ROM e.g. CorvusOS 3.2-V v12.1 if it works with it
So if anyone has experience with it?
norryhox said:
Unfortunately I have the same problem on my MI11 Lite 5G.
I would be interested if I install a custom ROM e.g. CorvusOS 3.2-V v12.1 if it works with it
So if anyone has experience with it?
Click to expand...
Click to collapse
i tried some custom roms before i send my phone to the service center and none of them worked.today i recieved my phone back and everything is great after replacing fingerprint.
After waiting many months for an update for my OnePlus Nord 2 Europe (EUEX), I managed to easily get the Android 12 update. Shortly, I installed over my EU Android 11 (with A.21 version and June patch security) the Indian firmware C.09 with September patch.
Phone is not rooted, bootloader is locked and has the orriginal recovery.
So in OxygenUpdater I selected India and full rom, instead of EU. After download, I shut down the phone, then by pressing Power and Volume down I entered recovery. I selected the desired language, then Local install and the firmware which is a file with long alphanumeric name. The full update takes no more than 5 minutes.
No data is deleted, the apps and the settings are there.
Greetings and credits to @asotmike who helped me.
Interface is buttery smooth, no lags, no bugs after 6 hours of playing with the phone. All functions work ok, Vowifi, Volte and 5g working fine in Romania.
For now, I don't know if there is an easy way to return to Europe version, without using MSM tools and losing data, so please everyone think well if you take the risk of making this movement.
Can you enter fastbootd and BROM mode?
Updating to EU ROM will be posible when / if OP releases full ROM > C.09 for DN2103.
Adb reboot fastboot works, it enters fastboot mode where it shows Format data, Reboot, Power off. In brom mode how can I enter, to test later? And I think you are right about moving back to Eu, only when a Eu build C.09 or newer is released
everything ok for me also. thanks to OP for this, finally we got android 12.
Thank you from Romania also ! A12 is something else ... It's OK for now .
Glad you like it guys! Hope to see many updates now for our great phone.
ruh01 said:
Adb reboot fastboot works, it enters fastboot mode where it shows Format data, Reboot, Power off. In brom mode how can I enter, to test later? And I think you are right about moving back to Eu, only when a Eu build C.09 or newer is released
Click to expand...
Click to collapse
You confirm that fastbootd is not available anymore. The phone boots to recovery.
For testing BROM mode you need mtk client. To enter you need to switch off completely the phone, connect the USB cable to the PC only. Then connect this cable to the phone and immediately press and hold all 3 buttons ( vol+, vol-, power ). The device screen should remain completely black and mtk client should detect your phone and connect it. Once detected you can release all the buttons.
I suppose, as per other reports that BROM is disabled too, so no more easy custom ROM installation or servicing.
Thank you.
For recovery and fastboot there is a difference, but small.
If I use adb reboot recovery I get to select language and after there is a menu named Recovery with options Fromat data, Reboot device and Power off.
If I use adb reboot fastboot, I select language and after there is a menu named Fastboot but with the same options as in case of recovery.
I cannot test Brom because I have downloaded several versions of MTK client but none of them even starts on my computer...
ruh01 said:
For recovery and fastboot there is a difference, but small.
If I use adb reboot recovery I get to select language and after there is a menu named Recovery with options Fromat data, Reboot device and Power off.
If I use adb reboot fastboot, I select language and after there is a menu named Fastboot but with the same options as in case of recovery.
I cannot test Brom because I have downloaded several versions of MTK client but none of them even starts on my computer...
Click to expand...
Click to collapse
Yes, install mtk client involves installing drivers, python, etc. It's a bit complicated. Unfortunately without fastbootd and BROM, one cannot customize the phone. If is ok with stock no matters.
Cheers.
I am very happy with this non-orriginal version. I found no problems yet, in 1 and half day. Should OnePlus start pouring with updates for EU, maybe I will return with a newer variant of DN2103. Else, adieu. Everything works fine, all apps, network bands work fine. Fast, smooth, no bugs, same great camera and performante, no sound problem. I will study further and play with it.
Unfortunately I found some small insignificant bugs like annoying slow connection to WiFi 6 , A11 was quite fast . Ambient display still don't work , picking wallpaper from Settings is blocked (I can set wallpaper only from particular 3.rd launcher apk . Percent battery is randomly shown despite it isn't set . Battery drain is bigger then A11 . Browsing is also slower . Fingerprint gave several errors and send me to PIN even I re-enroll new fingerprint , animation are ugly . Proximity sensor has also rare errors . More then that there are some stupid bloatware (maybe for Indian Market ). I didn't use for now Bluetooth , Android Auto , Portrait camera , and other complaints of indians users ... But overall A12 is working fine although I expect further EU version if it comes anymore !
Untill we have a proper EU version and a good update frequency for it, I am more than happy to stay with this version. We'll see if this happens, ever...
Yeah , right ... Am I pleased with A12 ? NO ! Should I go back to A11 ? NO... hahahahaha
thanks. it works also for me. Model name changed to DN2101 XD
tbh, i didn't find any bugs on IN version. 5G is working fine (Greece), wifi is the same fast as A11 (less than 1 sec.), bluetooth also ok. i can't compare the battery drain because i own the phone for less than a month but i think it's the same as before. if they decide to give EU version and update it regurarly maybe I will switch again, but I don't mind staying with the IN that updates every month. cheers!
greg10 said:
tbh, i didn't find any bugs on IN version. 5G is working fine (Greece), wifi is the same fast as A11 (less than 1 sec.), bluetooth also ok. i can't compare the battery drain because i own the phone for less than a month but i think it's the same as before. if they decide to give EU version and update it regurarly maybe I will switch again, but I don't mind staying with the IN that updates every month. cheers!
Click to expand...
Click to collapse
They release primary for DN2101. When fixed the main bugs, OP made it available for the DN2103. So we can expect European releases will be more stables, but delayed...
roldev said:
They release primary for DN2101. When fixed the main bugs, OP made it available for the DN2103. So we can expect European releases will be more stables, but delayed...
Click to expand...
Click to collapse
the latest version they released for EU was C.01 and we weren't able to get the update, so I'm not really sure for that
greg10 said:
the latest version they released for EU was C.01 and we weren't able to get the update, so I'm not really sure for that
Click to expand...
Click to collapse
They have weird schedule. C.01 is available for Spain since the first day released. Through system update or oxygen updater.
roldev said:
They have weird schedule. C.01 is available for Spain since the first day released. Through system update or oxygen updater.
Click to expand...
Click to collapse
HI I have EU and version is DN2103_11_ cC08 got it about 2 weeks ago. Before update I had C.01
jis251 said:
HI I have EU and version is DN2103_11_ cC08 got it about 2 weeks ago. Before update I had C.01
Click to expand...
Click to collapse
Thanks for confirming. There are various regions which got the C.08. My oxygen updater still shows C.01 as latest available.