Hi to all,
Yesterday i tried to install android 10 OTA update to my xiaomi a3 with adb - twrp method. It was a bad choice because the rom was very laggy with many bugs. I reinstalled the official A3 android 9 rom and lock the bootloader. Everything was working fine except of all my sensors. Gyroscope, proximity sensors etc. I can't even see them in DEv check apps neither with the call method. In addition i cant find any other posts refering the specific topic. Thank you
graffalo said:
Hi to all,
Yesterday i tried to install android 10 OTA update to my xiaomi a3 with adb - twrp method. It was a bad choice because the rom was very laggy with many bugs. I reinstalled the official A3 android 9 rom and lock the bootloader. Everything was working fine except of all my sensors. Gyroscope, proximity sensors etc. I can't even see them in DEv check apps neither with the call method. In addition i cant find any other posts refering the specific topic. Thank you
Click to expand...
Click to collapse
I managed to fix the issue by flashing the pixel experience rom. The sensors started working again and then i went back to stock. Some suggest flashing the persist partition but you may lose Widevine DRM L1 by doing so.....
eltonb said:
I managed to fix the issue by flashing the pixel experience rom. The sensors started working again and then i went back to stock. Some suggest flashing the persist partition but you may lose Widevine DRM L1 by doing so.....
Click to expand...
Click to collapse
You did not loose l1?
amnher said:
You did not loose l1?
Click to expand...
Click to collapse
No. As i said i flashed a custom rom, in this case PE, instead of flashing persist and as soon as the rom booted the sensors started working again. Then i flashed the latest stock fastboot rom and everything is fine.
eltonb said:
No. As i said i flashed a custom rom, in this case PE, instead of flashing persist and as soon as the rom booted the sensors started working again. Then i flashed the latest stock fastboot rom and everything is fine.
Click to expand...
Click to collapse
I should have done that anyway the service center will change the motherboard
Related
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Edit- solved
Flash CM firmware if your ROM is CM based at all, of course. If not, look for something in the ROM thread.
Dev.Katalyst said:
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Click to expand...
Click to collapse
Personally I always flash it anyway. Fixes a few bugs like settings FC etc.
Dev.Katalyst said:
Hello people, i just bought RN3 (Indian version with FPC sensor), i unlocked unofficially by flashing MIUI 7.1 and installed AICP 11 MM just after that, do i had to flash CM13 Firmware first?
Everything works fine but sometimes screen glitches and phone freezes so i have to force reboot it.
So should i now flash CM firmware? if yes with which TWRP? i'm using official twrp 3.0.2-2, reply soon....
Click to expand...
Click to collapse
Dev.Katalyst,
any news with your glitches issue ?
did you successed solving it?
iTaisHi said:
Dev.Katalyst,
any news with your glitches issue ?
did you successed solving it?
Click to expand...
Click to collapse
yes, that was live display bug in old kernels. fixed after a week of this post.
Hello,
Currently running RR Rom but I'm running it with a lots of bugs like proximity sensor, auto rotate does not work. Except that everything works great. Can anyone suggest me a ROM so I can get over this problems.
Thank you.
For sure, i use latest xiaomi.eu rom and have non of this bugs
The only problem for me is that I'm in love with stock android. I had a Nexus 5x before.
NitrogenOS
Just flash with MiFlash latest global dev fastboot rom with flash_all option.
Set it up, enable usb debbugging, OEM unlock, check that you are unlocked.
Flash ZCX twrp, backup all partitions to microSD(46 or so), format data, wipe all partitions except microSD.
Flash NitrogenOS
AOSPExtended
ionutarbanasi said:
Hello,
Currently running RR Rom but I'm running it with a lots of bugs like proximity sensor, auto rotate does not work. Except that everything works great. Can anyone suggest me a ROM so I can get over this problems.
Thank you.
Click to expand...
Click to collapse
Did u root it wit super su
What do you mean? I flash kate firmware, rom, gapps, and install kate modem.. whats wrong?
Ive installed the latest update of LineageOs and none of the proximity sensors are working. Can i get help regarding these. Thanks in advance.
when is it not working?
what do u expect it to be worked?
During calls, and also auto brightness doesn't work and also the maps gyroscope doesn't work.
wasifr said:
During calls, and also auto brightness doesn't work and also the maps gyroscope doesn't work.
Click to expand...
Click to collapse
make a clean flash of official linage.
you can also try Resurrection Remix or Nitrogen OS.
for clean flash, wipe system+data+cache+dalvik
then flash firmware+rom+gapps
if also not working, fastboot flash miui rom, unlock bootloader officially, then flash custom rom
I already did a clean flash, but I've had a rom and gapps.. What's the firmware? My bootloader is unlocked officially
wasifr said:
I already did a clean flash, but I've had a rom and gapps.. What's the firmware? My bootloader is unlocked officially
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
download the exact firmware
next time, use the reply button under my post so i can get notification
Solved!! Reflashed the same rom again.
thank you
wasifr said:
Ive installed the latest update of LineageOs and none of the proximity sensors are working. Can i get help regarding these. Thanks in advance.
Click to expand...
Click to collapse
Simoom Sadik said:
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
download the exact firmware
next time, use the reply button under my post so i can get notification
Click to expand...
Click to collapse
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Clean flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Try without f2fs. Use ext4
geokilla said:
Been using the Xiaomi Redmi Note 3 (Kenzo) for a long time now and since the ROM was outdated, I decided to update it this past weekend. However for whatever reason, something broke and I've been getting bootloops. Since then, this is what I did and it still doesn't work.
Used MiFlash to fastboot flash MIUI v8.5.1.0 Global Stable, and then OTA updated to v8.5.2.0.
Test the phone to make sure all functions work properly.
Immediately officially unlocked the bootloader using Mi Unlock.
Fastboot flashed TWRP 3.1.1.0.
Made EFS and ROM backups as usual.
Flashed Resurrection Remix 5.7.4 (Radon kernel) with /data and /cache as F2FS.
Flashed Open Gapps 6.0 ARM64 Mini.
Right now, I'm back to running stock MIUI v8.5.1.0, which was flashed using MiFlash. Then I did the OTA update to MIUI v8.5.2.0. May someone please guide me or correct the above steps in order to install the linked Resurrection Remix ROM? Or maybe a Nougat ROM?
Click to expand...
Click to collapse
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
vistaabalaji said:
Try without f2fs. Use ext4
Click to expand...
Click to collapse
EXT4 had the same issue. Just bootloops forever.
naturist said:
Flash LOS 13 which is far stable than the RR 5.7.4. You should've flashed another rom before moving back to MIUI. The process you followed is correct but you also need to flash the compatible firmware like for RR you need CM13 firmare and for LOS you'll the recommended firmware posted in the thread itself.
Click to expand...
Click to collapse
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
geokilla said:
I went through some ROM threads and one recommended flashing MIUI8 Global DEVELOPER and not Global STABLE. Am I supposed to be using MIUI 8 Global DEVELOPER as the starting point?
EXT4 had the same issue. Just bootloops forever.
The Resurrection Remix build I linked is based off of LineageOS 13 so it should be stable.
So you're saying I missed flashing a firmware? I see some ROMs recommend flashing the firmware, while others don't. Which is the proper firmware to flash if the ROM thread doesn't state which firmware to use?
Click to expand...
Click to collapse
The one on this thread. Second post.
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Felheipe said:
I've been having very similar issues (updated official firmware in a non officially unlocked bootloader).
It's been hell but I've managed to get los14.1 installed. Now my issue lies with constant gapps crashes. I'm thinking of just giving up and getting miui.
Click to expand...
Click to collapse
use latest gapps.outdated or older one causes crashes...
adithyan25 said:
use latest gapps.outdated or older one causes crashes...
Click to expand...
Click to collapse
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Felheipe said:
One would think so but in reality is the other way around. I'm using a 20170303 and it has been the most stable version across all my devices and so on.
Click to expand...
Click to collapse
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
adithyan25 said:
well seems to be a new problem...
so what must be done... i will suggest to get latest miui fastboot rom from here
https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488
flash it via mi flash tool (im running 64 bit os ,so using mi flash beta ) in edl mode by wiping full things including storage..
if your boot loader is unlocked official way it must be unlocked now also if not i guess you know how to unlock it officially.
then use official twrp from
www.twrp.me
i faced this issue once and did the exact steps above and now no problem..
by the way i tried things like unplugging battery from the board... lol... read in miui forum...
Click to expand...
Click to collapse
That's exactly what I did, as I mentioned in OP lol. Except I wasn't flashing MIUI 8 in EDL mode.
adithyan25 said:
seriously the one from march??
dude just download older gapps wont work on latest updates. ot will force close for sure...
at least try before telling ..use latest one from opengapps... there is a reason they are updating tje sote everyday...ftom the may builds you need latest gapps as petr release dates... just give a try ..its only 150 mb or so.... i can vonform its duw to outdated gapps
Click to expand...
Click to collapse
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Felheipe said:
I tried 0625 and the newest one. 0303 is the latest stable Google play services (as far as i am aware).
Click to expand...
Click to collapse
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
edit:- playservices had updated many times after 0303.. so i can say its outdated
adithyan25 said:
no idont guess so...
pls try after downloading latest one from here
www.opengapps.org
arm64-7.1- pico(if you want Google assistant you must use nano or above)
iam using yesterday build of opengapps and not facing any issues...and do a clean flash if possible...
or else you can tru beansgapps....
Click to expand...
Click to collapse
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Felheipe said:
I've tried yesterdays version. Play store wouldn't even open. Dirty flashed 0625 play store opens but a lot of apps crash, everything works fine with 0303.
I'm flashing miui and I'm going to try the official bootloader unlock, but this have been a couple of strange days.
Click to expand...
Click to collapse
dirty flashing isn't a solution ... theres changes in trees of the rom and kernel..
anyway head back to miui unlocl officially and when coming back to custom rom do wipe everything and give it a shot..probably the crash may be due to over written or exiating files...
happy flashing
~peace
I should mention I clean flashed the ROMs. Updated OP.
Ok trying it again right now and so far, this is what I did:
Used MiFlash to fastboot flash MIUI v7.7.6 Global DEV.
Test the phone to make sure all functions work properly.
Tried to unlock bootloader using Mi Unlock but it said bootloader is already unlocked.
Boot into MIUI again.
Fastboot flashed TWRP 3.1.1.0.
No boot into MIUI.
Flash Kenzo firmware 8.2.4.0 in TWRP
Clean flash LineageOS 13 and Open Gapps 6.0 ARM64 Mini with /data and /cache in EXT4
IT WORKS!
I guess now I'll try Resurrection Remix.
hello everyone
I was using miui 11 port on my MI a3 and it was good
I updated my A3 to stock a10 but that was a bad idea.
now i want to switch back to the miui but every time i flash the twrp image on slot b , after reboot the phone automaticlly reboots to fastboot (of course i long press vol+ ). it's the same with slot a
can you guys help me with that?
I made a big mistake buying android one phone . I used to have redmi note 3 with miui . i wanted a new exprience but miui is perfect
thank you
UPDATE
I flashed the latest official fastboot rom and that was ok with the anti rollback. But all the sensors were gone . Then I installed twrp and that was successful ( thanks God) . But after flashing miui , it stock at boot animation for about one our. Then i format data > flashed the firmware in the miui A3 channel in slot b
Installed miui again and the twrp after that . Then changed the slot to a and reboot. It's booted up now the miui is ok battery is ok and all of the sensors are working fine
Thanks to @bitnet for the great job porting this rom
Now that you have updated to 10 downgrading to earlier version may cause some unpleasant like sensor errors. Not sure though I have not flashed MIUI yet but I have downgraded from 10 to stock 9 and all sensors are broken. I was forced to flash persist partition and it was ok but I lost widevine L1 forever. So no more HD MOVIES watching from netflix or amazon
amnher said:
Now that you have updated to 10 downgrading to earlier version may cause some unpleasant like sensor errors. Not sure though I have not flashed MIUI yet but I have downgraded from 10 to stock 9 and all sensors are broken. I was forced to flash persist partition and it was ok but I lost widevine L1 forever. So no more HD MOVIES watching from netflix or amazon
Click to expand...
Click to collapse
In iran we don't have those services
miladsola said:
In iran we don't have those services
Click to expand...
Click to collapse
You should use Pie firmware to rollback to miui.
You can find it in A3 MIUI telegram gp.
AgentW said:
You should use Pie firmware to rollback to miui.
You can find it in A3 MIUI telegram gp.
Click to expand...
Click to collapse
i downloaded that but there was no instructions.
miladsola said:
i downloaded that but there was no instructions.
Click to expand...
Click to collapse
Try flashing with recovery
Can you post the link of that room ? i cant find it
miladsola said:
UPDATE
I flashed the latest official fastboot rom and that was ok with the anti rollback. But all the sensors were gone . Then I installed twrp and that was successful ( thanks God) . But after flashing miui , it stock at boot animation for about one our. Then i format data > flashed the firmware in the miui A3 channel in slot b
Installed miui again and the twrp after that . Then changed the slot to a and reboot. It's booted up now the miui is ok battery is ok and all of the sensors are working fine
Thanks to @bitnet for the great job porting this rom
Click to expand...
Click to collapse
Can you give link to the fastboot rom you used to clear this later