Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
gamerboy_010 said:
Hello Guys,
I am facing this weird issue. Whenever i am trying to switch to my front camera the camera keeps switching between both the rear ones. I tried flashing stock, tried different roms, nothing is helping.
Please suggest a solutions. Thanks
Click to expand...
Click to collapse
very unusual sounding problem ...sounds like you tried to play around with vendor props and to make aux camera working
flash stock using miflash ...do it in edl mode using fastboot
fastboot oem.edl
when finished ...BOOT not flash orange fox revovery
fastboot boot recovery.img
*"might be different command depending on pc amd name and location of downloaded recovery
then use a persist restorer flashable zip you can.find in jasmine/wayne official telegram.group and flash that ..
them reboot and use as normal
Thanks, i will try and rever
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
gamerboy_010 said:
I tried the process you suggested and followed every step. Even after that the camera is still switching between rear ones. Can't switch to front camera.
Click to expand...
Click to collapse
yeah no bro that is impossible even if nothing is impossible that is 99% impossible and you didn't do everything that i suggested
make a video of the problem and a video of applying my fix
if not i can't help you further ..
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
gamerboy_010 said:
Here's what i did.
Rebooted the phone to fastboot - used fastboot oem edl
Phone was detected as COM 10 in Mi FlashTool.
Flashed whole Pie Stock Rom.
Without booting, went to fastboot and unlocked bootloader although it was showing its already unlocked.
Used fastboot boot recovery.img and went into recovery.
Flashed persistrestorer6X.zip, found in Mi A2 telegram group, there is only zip.
Booted the phone. Tell me a few things.
Which stock version to flash?
What's wrong in above steps that i did?
Click to expand...
Click to collapse
what device are you using ?
jasmine or wayne
which recovery did you use ?
_what i can tell you is not all twrp recovery works or can flash persist
_ try to use orange fox but use another recovery that can backup and flash persist ..
press
mount button ...if you don't see persist partition option here the recovery can not flash it even if .zip seems to flash well
look for pie persist.img for your device according to if it is jasmine or wayne ...look for recovery that can mount, backup and flash .img files to persist
---------- Post added at 09:01 PM ---------- Previous post was at 08:42 PM ----------
use these files bro
https://www.dropbox.com/s/w2d2z92yn6115ot/persist.img?dl=0
https://www.dropbox.com/s/zy8prxeum9qbkx5/TWRP-3.2.3-0810-XIAOMI6X-RU-wzsx150-hypeartist.zip?dl=0
https://www.dropbox.com/s/or0n7b6hxagr2ee/4_6050642049911227980.zip?dl=0
if you have jasmine flash persist in both slots
Thanks, i have jasmine. Let me use your files and revert.
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
gamerboy_010 said:
Hello,
Sorry took a little longer.
I tried again with the process you suggested.
I used two different recoveries after flashing stock.
1. TWRP 3.2.3 unofficial
2. Orange Fox Recovery
I was successfully able to flash Persist using Orange Fox Recovery but it didn't helped. I was still not able to switch to front camera.
I tried to download and flash another Pie Stock Rom, same thing was happening on that as well.
Now i don't understand how else i can fix this. I have tried different versions of stock, i tried different recovery to flash persist, still the same issue.
Click to expand...
Click to collapse
flash stock rom but in edl mode , using Miflash. Use the cmd :
fastboot oem edl
_dont use custom rom
_dont flash in normal fastboot
the only way this problem could be happening is if you were trying modifications in vendor and when you flash a new rom it doesn't overwrite the changes because it is modifying only vendor ...flashing custom roms in recovery won't help , neither will stock in fastboot mode . Only edl mode .... furthermore directly after flashing stock ...flash persist ...that way you start 100% fresh ..if it still doesn't work it is hardware failure
but i can do nothing more for you unless you send videos or photos of you following the steps and the problem with the camera .
**if you know how try removing back and enter edl with testpoint ...flash ... disconnect cameras and reconnect them ... then start phone
***if you remember what you changed just change it back ( did you try modifications? , what did you do ?)
****copy vendor files for camera from friend
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
no problem man glad you succeeded ... probably it worked but after flashing persist everything usually starts working Normally after a few reboots ..so probably by then it was when you flashed derp
gamerboy_010 said:
Thanks for your help. I managed to get out of this in a weird way.
Flashed Stock in EDL. Tried different different Pie version this time.
Unlocked BL and Critical. Flashed Persist, didn't helped though.
Flashed Derpfest Rom with Mystic kernal and suddenly it started working.
Thanks for the help.
Click to expand...
Click to collapse
today i experienced a funny situation ...i took the new stock update for wayne and then i had the same camera problem ..
after thinking a little i realised it was after uodate so i had to just reapply the api2 for camera and then it started working normally so in future before going the long way make sure to enable api2 again after you update or flash a new thing . if camera works great if not take the long way...
Related
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 .
Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.
Recently, I reverted to stock oreo only to go back to PE again. Since then, I have been wondering if it's causing some of my issues. Camera quality with gcam isn't what it used to be, the network indicator in the status bar shows no bars but I can get and receive calls, random wakeup's while the phone is in my pocket and performance issues on my keyboard(sometimes I press the keys but there's no response).
What are your guys thoughts? Should I have had updated to latest version before going to PE?
BungeeWatcher47 said:
Recently, I reverted to stock oreo only to go back to PE again. Since then, I have been wondering if it's causing some of my issues. Camera quality with gcam isn't what it used to be, the network indicator in the status bar shows no bars but I can get and receive calls, random wakeup's while the phone is in my pocket and performance issues on my keyboard(sometimes I press the keys but there's no response).
What are your guys thoughts? Should I have had updated to latest version before going to PE?
Click to expand...
Click to collapse
if you go from oreo to 10 and back again you need to restore your persist partition or it will be corrupted and give you problems with everything from wifi to camera to compass
so either go to stock rom android 10 or restore your persist or go to Pe and stay there .. I've explained this to another guy like a day ago with links so just search for that post because I'm too lazy to repeat it again
KevMetal said:
if you go from oreo to 10 and back again you need to restore your persist partition or it will be corrupted and give you problems with everything from wifi to camera to compass
so either go to stock rom android 10 or restore your persist or go to Pe and stay there .. I've explained this to another guy like a day ago with links so just search for that post because I'm too lazy to repeat it again
Click to expand...
Click to collapse
I found your reply on the pixel experience forum, page 48. From there, I have flashed persidtgood.zip file using sky hawk recovery. After, I rebooted thrice. My camera and WiFi have seen some improvement but not my sim network. Anyway, do you think I should flash the latest PE now or go back to stock android 10 using edl mode and then go back to PE May 24 update..
BungeeWatcher47 said:
I found your reply on the pixel experience forum, page 48. From there, I have flashed persidtgood.zip file using sky hawk recovery. After, I rebooted thrice. My camera and WiFi have seen some improvement but not my sim network. Anyway, do you think I should flash the latest PE now or go back to stock android 10 using edl mode and then go back to PE May 24 update..
Click to expand...
Click to collapse
return to stock with edl mode if everything is not 100% but if everything is working well now you can proceed with any custom rom
KevMetal said:
return to stock with edl mode if everything is not 100% but if everything is working well now you can proceed with any custom rom
Click to expand...
Click to collapse
I will go back to stock just to make sure that the network issues are not from my side.. How do you actually flash from edl? I have tried searching for it but I couldn't find anything substantial..
Do I use fastboot reboot edl on fastboot screen and proceed to flash with Mi flash tool? But I remember you mentioning that Mi flash isn't very good since it doesn't flash important partitions..
BungeeWatcher47 said:
I will go back to stock just to make sure that the network issues are not from my side.. How do you actually flash from edl? I have tried searching for it but I couldn't find anything substantial..
Do I use fastboot reboot edl on fastboot screen and proceed to flash with Mi flash tool? But I remember you mentioning that Mi flash isn't very good since it doesn't flash important partitions..
Click to expand...
Click to collapse
use cmd:
fastboot oem edl
then :
use miflash and select unzipped stock fastboot rom and select the "clear all" option in the box at the bottom
THEN :
fastboot boot recovery.img
THEN :
custom recovery should boot on phone without installing ...then restore/ flash persist img or persist zip
Reboot & Enjoy fully functioning phone
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Did you flash anything?
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
VD171 said:
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
Click to expand...
Click to collapse
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
jeromeof said:
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
Click to expand...
Click to collapse
You need to flash the stock MIUI rom again using SPFLASHTOOL.
[GUIDE] How to properly solve the errors of the SP FLASH TOOL for MERLIN ? (Redmi Note 9 / Redmi 10X 4G)
WARNINGS: Keep your backup files safe and secure ! If you can, encrypt them. If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again ! Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and...
forum.xda-developers.com
jeromeof said:
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Click to expand...
Click to collapse
If you have have adb drivers installed in your pc, try connecting your phone and open power shell. Then try this command.
Code:
adb devices
If it shows the device, then simply command
Code:
adb reboot fastboot
and flash the fastboot rom.
If not works, then follow VD171.
Also you should read threads carefully before flashing anything. Like there a tread about pixelplus UI. And they recommend to force reboot when you see the boot logo. To avoid boot loop.
Good luck
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Don't flash pixel experience. It's unofficial and it's and old version. I recommend you to flash pixel extended after solving and flashing latest fastboot rom. It's official and provide update every month. This rom is also a pure aosp based Stock rom.
Always read new treads before deciding
Redmi Note 9 ROMs, Kernels, Recoveries, & Other De
Improve your Redmi Note 9's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Mobarok_ said:
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Click to expand...
Click to collapse
Indonesia V12.0.1.0 precisely (V12.0.1.0.QJOIDXM).
Here, you can find and download the rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.1.0.QJOIDXM/
Hello! Just created an account in this forum to seek help because this is driving me nuts.
I have a Xiaomi Redmi Note 9 (Merlin) which has no system (Android), but I still can access fastboot and recovery menu, so I went ahead and unlocked the bootloader and flashed MIUI without any issue. To my surprise, when I booted the phone back up, it was like I didn't do anything as it still bootlooped, it didn't even show the MIUI logo, so I tried again; still nothing.
So, I tried the following:
- I followed the guide in this forum for hard-bricked Note 9 phones (https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/), and I can tell the firmware flashes because the starting menu and the fastboot logo changed from the rabbit to FASTBOOT in orange letters, but still no system.
- I flashed stock firmware, but still no system.
- I flashed the MIUI version that the phone came with through fastboot, but still no system
- I tried to flash the newest version of MIUI the phone came with through TWRP using the recovery version, but still no system (and when I try to reboot, TWRP says there is no system)
- I tried installing Pixel Experience to see if MIUI was the issue but, still no system. The phone just keeps bootlooping endlessly.
- I tried running https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt to see if the encryption was the problem, but no progress.
I would appreciate any help to at least have my phone working, even if it's not with MIUI but with a custom ROM. At this point I don't care anymore, just want a useable phone.
Thank you.
Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data (you did first make a backup of your personal data right?)
Then phone should boot again.
I hope this helps. Good luck!
lebigmac said:
Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data
I hope this helps. Good luck!
Click to expand...
Click to collapse
I've tried that a couple of times but it's like I didn't do anything, when I reboot I still get no system
bump
bump - really desperate about this matter
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!
lebigmac said:
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!
Click to expand...
Click to collapse
Yeah, I even tried with other PCs to see if that was the issue. Will try looking in the logs. Thank you!