Related
hello, since upgraded from miui v.9.7 to v10 portrait mode on rear camera not working. i tried fastboot flash again and still a bug. anyone can help me or confirm it is a bug ? (v10.0.2.0)
I'm using Xiaomi.eu's beta MIUI 10 ROM & portrait works as it supposed to :/
@engloa Please move this to Mi 8 Q&A. This thread should not be here.
imortalitzik said:
hello, since upgraded from miui v.9.7 to v10 portrait mode on rear camera not working. i tried fastboot flash again and still a bug. anyone can help me or confirm it is a bug ? (v10.0.2.0)
Click to expand...
Click to collapse
Stop posting irrelevant stuff in this forum!, this is getting ridiculous,!!! Where are the moderators to sort things up ffs
imortalitzik said:
hello, since upgraded from miui v.9.7 to v10 portrait mode on rear camera not working. i tried fastboot flash again and still a bug. anyone can help me or confirm it is a bug ? (v10.0.2.0)
Click to expand...
Click to collapse
you should try flash persist ,like this:
fastboot flash persist persist.img
namesuanle said:
you should try flash persist ,like this:
fastboot flash persist persist.img
Click to expand...
Click to collapse
can i flash it without twrp ?
imortalitzik said:
can i flash it without twrp ?
Click to expand...
Click to collapse
you need search how to install and use fastboot
i think flash persist in fastboot mode can solve your problem
persist.img is in the rom file , you should unpacking the package and find it
I've got same problem, but I also have my camera options switched betweend rear and front.
Flashing persist.img doesn't help.
So after trying Xiaomi EU, MiGlobe Rom and Android Q Beta
I decided to flash back to MIUI 10.3.8 via fastboot
Somehow my front camera won't open properly, it kept saying "Can't open front camera, please calibrate".
And when I press Calibrate, popup cam goes up and down 3 times in a row and says "Can't calibrate".
Any idea how to fix this?
EDIT: Must be the fastboot rom I downloaded. Other rom's front cam worked fine...
I am having same issue. Initially I thought it was hardware problem.
But I noticed it seem to be related to software.
Took few restart of camera app and sometime phone restart, for it to work
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
LogicalMaverick said:
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
Click to expand...
Click to collapse
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Robbo.5000 said:
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Click to expand...
Click to collapse
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
What's LR?
degeaba1981 said:
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
What's LR?
Click to expand...
Click to collapse
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Robbo.5000 said:
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Click to expand...
Click to collapse
Problem solved! I flashed via miflash the Chinese rom, in fastboot and the front camera was working. Then I've put the Indian global version and front camera is working fine now.
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Ekalous said:
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Click to expand...
Click to collapse
I have the same problem. I'm trying to solve it but nothing for now!
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
topaloglu321 said:
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
Click to expand...
Click to collapse
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
znsvs123 said:
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
Click to expand...
Click to collapse
You can't show them up. The only way is to change TWRP, hoping that is supported
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
I'll try this thank you.
thelegoboy said:
You can't show them up. The only way is to change TWRP, hoping that is supported
Click to expand...
Click to collapse
thanks, not all of twrps are built equally. :good::good::good:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
i fixed that problem just flashing chinese.rom via miflash and.camera pop up working again
sagar.anits said:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
Click to expand...
Click to collapse
Same problem here
RAJIB AHMED0077 said:
Same problem here
Click to expand...
Click to collapse
try flashing 10.3.16 chinese rom via fastboot yesterday i flash that rom and it fix that problem in my k20 Pro
TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Have you ever tried fastboot rom ? Now it's the only solution to recover your phone !
macgyverx86 said:
TLDR: I tried installing AEX rom and I bricked my mi9, getting it in a fastboot loop. Flashed a bunch of things and now I think my firmware is messed up. Help.
First I flashed TWRP, then I flashed the AEX rom and gapps, but phone got in bootloop, then I tried just flashing the ROM and it worked. After I flashed gaps it got into bootloop again.
Then I read the instructions from the AEX thread and I flash the recommended Firmware file (v9.6.13), and the flash failed.
I wiped everything, reflashed the ROM without gapps, and at restart the phone. Got stuck in fastboot.
Tried reinstalling TWRP with no success. Tried flashing MIUI with their flash tool but it didn't ended the flash procedure even after 20 minutes...
I tried to directly boot the recovery image (TWRP) and I was surprised that the phone booted in MIUI, but wifi wasn't working. Did not test anything else. Restarting the phone got me again in fastboot loop.
I tried again flashing with mi flash tool and this time was succesfull.
Then I tried to flash a MIUI eu ROM and got the phone again in fastboot loop. Flash was succesfull, but when restarting TWRP said that there is no OS installed.
I decided to give up and flash global MIUI 10.2.13 back.
But now my phone has some problems. Auto brightness doesn't work and video recording freezes the camera app when image stabilization is enabled.
So, is there a way to reflash 10.2.13 rom firmware using mi flash tool?
I suppose the first Firmware flash that was unsuccessful messed the firmware up...
Or how do I get my phone back to factory status...
I suppose v9.6.13 firmware is China developer and was an upgrade and that I should downgrade to 10.2.13 rom firmware.
Or flashing developer global will solve the problem? And how do I do that?
TWRP: https://forum.xda-developers.com/Mi-9/development/recovery-twrp-3-3-1-siankatabg-t3934962
AEX: https://forum.xda-developers.com/Mi-9/development/rom-aospextended-v6-6-t3956100
Click to expand...
Click to collapse
Hmm, so where are you at now!? Have you got twrp installed? and 10.2.13 but with issues, right? or are you on stock recovery?
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
macgyverx86 said:
Current status: I managed to flash fastboot global ROM in mi flash, and stock recovery.
But the firmware is messed up.
Camera doesn't work well. And from normal use I saw that Gyroscope, light sensor and compas aren't working at all...
Phone reboots itself and I can't unlock it because pattern isn-t recognized anymore, untill I reset it by long pressing the power button.
From CIT menu gyro, light sensor and compass are definitely not working.
Would flashing latest firmware from TWRP be a possible solution? My bootloader is still unlocked and I can flash TWRP.
Or should I format vendor partition first? And then flash firmware?
Fastboot flash did solved firmware problem.
Click to expand...
Click to collapse
To be honest I'm not entirely sure if it'll help, but, I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. You could try using mauronfrio's twrp 3.3.1-35 instead of the one you linked get it here. That's just what I'd try, can't say whether it'll help and no guarantees it'll fix anything... Let us know the outcome bud.
You can download the latest flashable rom from here
I can't see why ur sensors etc aren't working anymore, it's got to be all software related me thinks
Do not try to reboot after wipes, you'll have nothing installed
reg66 said:
... I'd put global stable flashable zip on otg, then I'd flash twrp again, boot to twrp using buttons not commands, wipe cache, dalvik, vendor, system, data, internal. Then format data, swiping with confirmation 'yes'. Then flash latest global again over the clean device from otg. ....
Click to expand...
Click to collapse
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
macgyverx86 said:
Correct me if I am wrong, but flashing a stock MIUI zip form twrp won't work.
Or you are saying that I should flash a xiaomi eu ROM?
Click to expand...
Click to collapse
Hold tight bud, just checking. I remember doing that - and the stock rom flashes but you no longer have twrp, it flashes the whole system/vendor including recovery. But hang on 'cos I might be recalling my pocophone F1 for that proceedure. The reason I suggest to reflash twrp is simply to have better control over a fully clean wipe, before progressing to flash rom again. Like I say, hang on just checking...
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
macgyverx86 said:
Got another sugestion:
Someone said that there is the posibility that mi flash didn't flash persist partition and that I should try to force flash it.
Referred thread here: https://forum.xda-developers.com/re.../how-to-flash-persist-partiton-redmi-t3830310
Is this a possibility?
And shouldn't mi flash reflash everything?
Click to expand...
Click to collapse
Yes, miflash should flash everything, but you say you started flashing other stuff when it all went wrong, so I'm really not sure what's happened to ur device. Hang on anyway, still checking on the flashable zip ..
---------- Post added at 09:06 PM ---------- Previous post was at 08:49 PM ----------
Nope, I think you're right, it was the poco I was getting muddled with - haven't had to do this in while (poco has flashable stock zips somewhere...). It is possible to do it with lazy flasher, but that may start getting messy again. Have you tried re-flashing fastboot? Can you wipe much at all in the stock recovery - again, I can't remember.
Failing that, yeah, I'd seriously consider flashing twrp and flashing mi-globe or eu rom. I prefer mi-globe (although currently using beast rom) over eu simply because you can customize it more on the website. Though, I wouldn't recommend pre-rooting it. Root after, if need be. Any way, we'll cross that bridge later... For now just try to re-flash
reg66 said:
Can you wipe much at all in the stock recovery - again, I can't remember.
Click to expand...
Click to collapse
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
macgyverx86 said:
Didn't get this.
Is it ok to format vendor partition? will it be recreated wen flashing again? using mi flash or from twrp?
Click to expand...
Click to collapse
I'm pretty sure you won't be able to wipe much in stock recovery, but just wipe what you can and try and re-flash fastboot. Don't flash twrp yet. You could try downloading again the fastboot file, in case of any corruption. Hopefully on the second flash all will be well. But that said, it should've been OK on the first flash :/ in theory
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Glad you got it working, phew!
macgyverx86 said:
just flashed xiaomi eu rom and everything seems to work now. All sensors are working.
I had to disable signature check, and i got an mounting /system error -> got the message that is installed without changes... whatever that means
And now in TWRP, I think, my files are encrypted without enabling it.
Will try other roms later.
Thanks for the help.
Click to expand...
Click to collapse
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
gm007 said:
Go the same problem as you,i tried Android Q beta rom and after reflashing stock fastboot rom with mi flash,the sensors and video not working,any solution?
Click to expand...
Click to collapse
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
macgyverx86 said:
I just flashed Xiaomi EU rom, did a CIT test and all sensors were working.
Try that. I'm curious it it works for you.
Click to expand...
Click to collapse
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
gm007 said:
Yes it worked with eu rom,but i managed to fix it on stock global stable by flashing an old miui 10.2.6 fastboot rom,Than updated to the latest one 10.2.13
Click to expand...
Click to collapse
So 10.2.13 fastboot image is to blame here.
macgyverx86 said:
So 10.2.13 fastboot image is to blame here.
Click to expand...
Click to collapse
Not sure maybe flashing eu rom first have fix it .
my A2 Converted to 6X stuck in bootloop after making a BackUp by PitchBlack, It wont boot in System nor Recovery anymore,
what should I do?
if I try to go to recovery it turns off,
and if I connect charger cable it turns on and off repeatedly (each 2-3 secs)
Keep force rebooting by holding down the power button and volume up button continuously / connecting the charger multiple times until you manage to get into recovery mode (I tried it for over 5 mins and it will eventually work for sometimes).
Then flash the latest Wayne (6X) firmware (download in Xiaomi Firmware Updater's website), it fixed that situation for me.
I reflashed recovery by fastboot, and reboot it by command line, it boots, but if I restart the phone the problem occurs again,
sz.hatef said:
I reflashed recovery by fastboot, and reboot it by command line, it boots, but if I restart the phone the problem occurs again,
Click to expand...
Click to collapse
Yeah, it was the miui eu rom firmware problem. Some ppl, including me, fixed the issue by flashing latest wayne firmware in recovery.
MarcusMario0605 said:
Yeah, it was the miui eu rom firmware problem. Some ppl, including me, fixed the issue by flashing latest wayne firmware in recovery.
Click to expand...
Click to collapse
could you please share the link of the latest wayne firmware here?
sz.hatef said:
could you please share the link of the latest wayne firmware here?
Click to expand...
Click to collapse
https://xiaomifirmwareupdater.com/firmware/wayne/
just flash the zip file in recovery.
MarcusMario0605 said:
https://xiaomifirmwareupdater.com/firmware/wayne/
just flash the zip file in recovery.
Click to expand...
Click to collapse
I flashed the Stable One, now when it boots it does not show the Unlocked message !
is that mean that my bootloader is locked again??
the fastboot says: (bootloader) unlocked:yes
Bootloader is still unlocked despite you flashed the firmware since flashing firmware will definitely not lock the bootloader. (probs. the perk of miui 11 eu roms, i'm not sure)
MarcusMario0605 said:
https://xiaomifirmwareupdater.com/firmware/wayne/
just flash the zip file in recovery.
Click to expand...
Click to collapse
I have converted my a2 to 6x.. Will it be okay if i flash the zip without deleting firmware updater folder! I already triggered arb 4. In xiaomi eu rom camera doesn't work at all! So i have to use custom roms! Camera is fine in custom rom! And should i wipe my vendor too? Before flashing the zip?
I flash weekly roms of xioami.eu and camera just works fine, ( and I don't delete firmware folder) why do you want to delete it while you have already triggered ARB?!
Mozahid007 said:
I have converted my a2 to 6x.. Will it be okay if i flash the zip without deleting firmware updater folder! I already triggered arb 4. In xiaomi eu rom camera doesn't work at all! So i have to use custom roms! Camera is fine in custom rom! And should i wipe my vendor too? Before flashing the zip?
Click to expand...
Click to collapse
It is okay if you don't delete firmware update folder since you already triggered the arb 4.
And don't wipe your vendor if you are going to flash that zip, since that zip only contains firmware files.
sz.hatef said:
I flash weekly roms of xioami.eu and camera just works fine, ( and I don't delete firmware folder) why do you want to delete it while you have already triggered ARB?!
Click to expand...
Click to collapse
Last time i flashed with firmware updater folder my phone bricked and triggered arb 4! And after that i recovered it any how! Now in eu roms camera doesn't work at all!
Mozahid007 said:
Last time i flashed with firmware updater folder my phone bricked and triggered arb 4! And after that i recovered it any how! Now in eu roms camera doesn't work at all!
Click to expand...
Click to collapse
I think you miss something , if your bootloader is unlocked, when you flash the whole ROM intact it should works perfectly, but sometimes shifting from stable to beta could lead to boot loop, you need to wipe system , davilk, and cache partitions
MarcusMario0605 said:
It is okay if you don't delete firmware update folder since you already triggered the arb 4.
And don't wipe your vendor if you are going to flash that zip, since that zip only contains firmware files.
Click to expand...
Click to collapse
Okay thanks a lot! Gonna try it very soon...
I recently bricked my RN10s and then had to flash stock ROM using the SP flash tool now the sensors are not working properly.
The device turns its screen on and off because it thinks it's being picked up.
The sensors used by google maps show that I'm rotating constantly.
I am new while flashing on A/B partitions and thus ended up bricked, any help will be highly appreciated. I was trying to flash pixel 4 android 13 GSI A/B and also tried dot os but it seems like my device's flash memory after the brick is not working properly because it does not boot into custom twrp by the command Fastboot boot TWRP.img.
looking forward.
flash stock rom and done
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
dequr said:
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
Click to expand...
Click to collapse
I think it might be due to corrupted persist partition, I never custom romed a device but have been researching for my RN10s and I read that persist contains the sensor data control and l1 certification that's why you need to back it up in case it corrupts. Sadly you can't flash persist from the internet since it's unique to every phone if you flash it you loose l1 certification forever but get back sensor functions (I am not sure about sensor functions returning)
Also there is a tool to fix corrupted persist so do research it but whatever you do make sure you are 100% certain it's what you want changes to persist are permeant (except if you backed up persist before the brick in which case just flash the persist backup)
V.I: as I said I never flashed a device and don't know much about it this is what I read through reddit and research, take it with a grain of salt and do your own research aswell
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
dequr said:
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
Click to expand...
Click to collapse
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Okay will try this now truly appreciate the support thx. Tho the phone is working quite better by time apart from the sensors.
The degree sensor or smt like that is just increasing to 360 and then will start from 0 again
killer_v41 said:
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
Click to expand...
Click to collapse
A
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Any suggestions form where to download because there are lot of sites available
This is the sensor data and as you can see Orientation sensor along with the rotations third value and the z axis of gyroscope and accelerometer isn't working well so ill re-flash with the first miui this phone had and apply updates on it hopefully it will fix the errors.
Your browser is not able to display this video.
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
alright so I was going thru the images and I couldn't find any persistence in both 13.0 and 12.5 but now as I am now the question is how are the x and y axis keeping their value correct while z isn't so will tho ask for a persist file but just curious how is it detecting sensors then ??
dequr said:
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
Click to expand...
Click to collapse
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
killer_v41 said:
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
Click to expand...
Click to collapse
Yea I discovered the fastboot ROM didn't have persist.img and I've stopped trying because the gsi has detected it and some how some things have been fixed I've also seen. File named gsi_persist_data in /data nvr opened it but gyroscope while gaming doesn't stop and raise to wake works.