I hope I post this correct !
Butt I installed the OxygenOS Android 11 Open Beta 1 for OnePlus 6/6T so fare works great !
Link to OnePlus 6 forum
Yeah I installed this too and feels smoother than A10 but there is still some bugs on customization and weather sometimes
mangkoeboemi said:
Yeah I installed this too and feels smoother than A10 but there is still some bugs on customization and weather sometimes
Click to expand...
Click to collapse
Yes and I think some photo bugs because some pictures won't save and I tried multiple apps
NLhardcore said:
Yes and I think some photo bugs because some pictures won't save and I tried multiple apps
Click to expand...
Click to collapse
If you clear cache of the camer app and camera services, then it will work.
twrp seem to be crashing , waiting for maruf for compiling new twrp
cpt.macp said:
twrp seem to be crashing , waiting for maruf for compiling new twrp
Click to expand...
Click to collapse
i have dualboot installed ,butt thats working fine
cpt.macp said:
twrp seem to be crashing , waiting for maruf for compiling new twrp
Click to expand...
Click to collapse
You will wait, probably. Better to download and flash 3.5.2 twrp from the official source.
meanwhile , you can use this boot image and boot into twrp from bootloader
fastboot flash boot test.img
( for ench )
cpt.macp said:
meanwhile , you can use this boot image and boot into twrp from bootloader
fastboot flash boot test.img
( for ench )
Click to expand...
Click to collapse
nothing happen, device just restart to system My bad, i just only type bood without flash. It works
OP6 OOS11 Open Beta 1 Hotfix: https://oxygenos.oneplus.net/OnePlus6Oxygen_22.Y.76_OTA_0760_all_2107130227_0263a33cf60f4185.zip
Attached is the stock boot.img (extracted from payload.bin) and Magisk patched boot.img (patched through the Magisk Manager app)
Flash via fastboot:
fastboot flash boot_a magisk_patched-23000_9GVnK.img
fastboot flash boot_b magisk_patched-23000_9GVnK.img
just flash the new zip file , get it from officail website
Link to 1+6
Meanwhile I reviewed the rom
I've been using this beta since 2 weeks now. Did you guys notice the battery life is really terrible. Maybe AOD is the culprit.
But OnePlus does really weird things. Like they gave an option for AOD in this beta but it's not there even in there OnePlus 7 stable. If they think the option is not sustainable then why even include it here </rant>
7alvi said:
I've been using this beta since 2 weeks now. Did you guys notice the battery life is really terrible. Maybe AOD is the culprit.
But OnePlus does really weird things. Like they gave an option for AOD in this beta but it's not there even in there OnePlus 7 stable. If they think the option is not sustainable then why even include it here </rant>
Click to expand...
Click to collapse
Not that much VS android 10 !
There is a update to open beta 2 also available in the oxygen app in the Playstore !
7alvi said:
I've been using this beta since 2 weeks now. Did you guys notice the battery life is really terrible. Maybe AOD is the culprit.
But OnePlus does really weird things. Like they gave an option for AOD in this beta but it's not there even in there OnePlus 7 stable. If they think the option is not sustainable then why even include it here </rant>
Click to expand...
Click to collapse
same for me, did you try to set the AOD option off and compare the results?
other thing i've noticed is the memory usage higher than before.
i got 3.5~4% battery off per hour when standby with AOD on. (btw. my battery state is 81% healthy according to oneplus diagnostic app.)
OnePlus 6 OOS11 Open Beta 2: https://otafsg-cost-az.coloros.com/...en_22.Y.77_OTA_0770_all_2107220200_eabc4b.zip
Attached is the stock boot.img (extracted from payload.bin) and Magisk patched boot.img (patched through the Magisk Manager app). These are for OnePlus 6, not 6T!
Flash via fastboot:
fastboot flash boot_a magisk_patched-23000_PwJFG.img
fastboot flash boot_b magisk_patched-23000_PwJFG.img
EDIT: couldn't attach the files directly to the post for some reason, so here's a GDrive link: https://drive.google.com/drive/folders/1R6s0hojdajer15aw8gMi1wgx7gRynrR7?usp=sharing
CrysisLTU said:
OnePlus 6 OOS11 Open Beta 2: https://otafsg-cost-az.coloros.com/...en_22.Y.77_OTA_0770_all_2107220200_eabc4b.zip
Attached is the stock boot.img (extracted from payload.bin) and Magisk patched boot.img (patched through the Magisk Manager app). These are for OnePlus 6, not 6T!
Flash via fastboot:
fastboot flash boot_a magisk_patched-23000_PwJFG.img
fastboot flash boot_b magisk_patched-23000_PwJFG.img
EDIT: couldn't attach the files directly to the post for some reason, so here's a GDrive link: https://drive.google.com/drive/folders/1R6s0hojdajer15aw8gMi1wgx7gRynrR7?usp=sharing
Click to expand...
Click to collapse
Only way to flash is via fastboot?
withdean said:
same for me, did you try to set the AOD option off and compare the results?
other thing i've noticed is the memory usage higher than before.
i got 3.5~4% battery off per hour when standby with AOD on. (btw. my battery state is 81% healthy according to oneplus diagnostic app.)
Click to expand...
Click to collapse
Yes, I did. I didnt really check the screen on time but on a full travelling day for me, while the AOD was on, the phone died mid-day. When turned off, the standby seems much better, lasted a full travelling day.
OnePlus 6 OOS11 Open Beta 3: https://otafsg-cost-az.coloros.com/...en_22.Y.78_OTA_0780_all_2108052353_9ad8a0.zip
Attached is the stock boot.img (extracted from payload.bin) and Magisk patched boot.img (patched through the Magisk Manager app). These are for OnePlus 6, not 6T!
Flash via fastboot:
fastboot flash boot_a magisk_patched-23000_ygvOI.img
fastboot flash boot_b magisk_patched-23000_ygvOI.img
fastboot reboot
Related
complete unrooting procedure for Mi A1 [Android Oreo]
1) remove all magisk modules
I mean untick all magisk modules and click on delete icon beside them
After this reboot your device
2) then open magisk manager and uninstall using completely uninstall option
3) then power off your device
4) go to fastboot mode
( by pressing vol- + power buttons simultaneously)
5) then unlock OEM using command
fastboot oem unlock
6) then check for current slot by using below command
fastboot getvar current-slot
7) then we should flash stock boot image
Using this command
fastboot flash boot_a boot.img
( If a is current slot )
Or
fastboot flash boot_b boot.img
( if current slot is b )
Boot image file : https://drive.google.com/file/d/1EsuVTv5zIrfhDH7VG6uSyTXUWPS7Dvfl/view?usp=drivesdk
8) then lock your OEM using command
fastboot oem lock
9) then reboot using command
fastboot reboot
Congratulations your device is unrooted successfully !!
Suggested vedios for mi A1 users
Iam maintaing my channel for mi A1 related vedios and other technical stuff
Do subscribe for latest updates
Rooting using magisk :
Complete gcam setup :
#reserved
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Thank you very much!!!! Was looking for this in a pretty long time!!!
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
nicolasmart said:
Nope. This boot.img doesn't work for me. After completing the instructions I'm just getting the Mi logo and then restart and it goes on forever. Maybe my system.img is bad??? Can anybody give me a link to a perfect Oreo fastboot ROM, becuase I found two: the one is my current ROM and the other one's system.img "cannot be extracted".
Click to expand...
Click to collapse
This one works for me https://forum.xda-developers.com/showpost.php?p=75027522&postcount=63
Currently I'm rooted, but I fully booted right after flashing it without any mods and ROM started fine.
It will show some sparse warning during flashing, but it will complete the process OK.
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
nicolasmart said:
Really? Is that what you're using? That's the exact one with the system.img errors. Nah, maybe a bad download.
Click to expand...
Click to collapse
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
_mysiak_ said:
Yep, working fine (well, except the video recording bug, but that is most probably Xiaomi's fault). I downloaded this file as well (https://forum.xda-developers.com/mi-a1/development/tool-aosp-8-0-ql1515-dec-8-2017-t3722184) and extracted and compared both system.img files and they are exactly the same except the very small difference - second one allows encryption as optional (modified) vs. forced (stock) in fstab. It might cause bootloop if you try to lock the bootloader with that system. Try to redownload files from Mega..
Click to expand...
Click to collapse
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
nicolasmart said:
Hmm... redownloaded from Mega, says
Code:
error: cannot load '.\system.img'
Yes, I'm sure the file is in the current folder.
I tried a different fastboot.exe and the error is more specific this time :
Code:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magi
Edit: The weird thing is that all other images from this Fastboot ROM install and work just fine. I've even used the boot.img from it. It works without any problems. The system is problematic.
Click to expand...
Click to collapse
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
_mysiak_ said:
First fastboot.exe is probably old, second one seems to be fine. Just wait until it starts flashing system.img, it will take a minute or two and will look like frozen (fastboot has to split file into 6 smaller ones, probably has something to do with missing sparse format), be patient and don't interrupt the process.
Click to expand...
Click to collapse
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
nicolasmart said:
THANK YOU!!!! IT WORKED!!! I AM NOW WITH LOCKED BOOTLOADER AGAIN! :victory: :victory: :victory:
Click to expand...
Click to collapse
You saved me too.
presented error in the "no command" and did not accept the January update
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
rkview37 said:
No need to uninstall modules and magisk
Just download & flash stock rom is enough to return to stock unrooted rom.
Is this you saying?
Click to expand...
Click to collapse
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
_mysiak_ said:
If you want to return to stock ROM and never use Magisk again, then you might want to uninstall Magisk first. But if you are only unrooting to apply OTA for example, it is enough to flash stock ROM and then reinstall Magisk - all your modules and settings will be kept.
Click to expand...
Click to collapse
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
rkview37 said:
Actually sir
I have flashed patched boot image not just just boot
is your method work then
&Of course I just unroot to apply ota
Click to expand...
Click to collapse
For OTA update, just reflash the latest stock ROM (keep data), apply OTA and root with Magisk again.
camerlengo said:
Thank it worked for me!
After this unroot method i could install the january ota.
Then I used this https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 method to root again
Click to expand...
Click to collapse
Ok bro
_mysiak_ said:
Or..
1. download fastboot ROM from Xiaomi, run flash_all_except_storage.bat (or flash it in MiFlash)
Congrats, you have stock device!
This way you are sure that you have correct boot.img corresponding to your ROM (otherwise OTA update will fail) and not some "random file from the Internet".
Click to expand...
Click to collapse
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
AlwaysWin said:
Can u link me to the latest fastboot rom? , The link in the thread on the mi forums is too old I guess
Click to expand...
Click to collapse
http://ru.miui.com/thread-1308-1-1.html
This website is in Russian but download from this site
Rom is Oreo Jan official rom flash it using mi flash tool
https://sourceforge.net/projects/xi....eu_multi_MIMix2S_8.6.18_v10-8.0.zip/download
https://androidfilehost.com/?fid=962339331459002161
http://miui.dedyk.gq/8.6.18/xiaomi.eu_multi_MIMix2S_8.6.18_v10-8.0.zip
https://xiaomi.eu/community/threads/8-6-14-16-18.44522/
i flashed with twrp unofficial but bootloop. i came from global 8.6.16 someone have my same problem?
PITTAR said:
i flashed with twrp unofficial but bootloop. i came from global 8.6.16 someone have my same problem?
Click to expand...
Click to collapse
use this recovery https://androidfilehost.com/?fid=818070582850507462
Flashed it with TWRP unofficial (v6). Had loads of bootloops, failed flashes etc. I think it had to do with encryption. After doing a complete wipe to remove the encryption and flashing it over ADB (No MTP in v6) it works like a charm.
Have some issues with random app crashes.
- Facebook crashes randomly
- Facebook messenger crashes when someone links a Facebook video in chat
- My Reddit app (Joey) crashes every x minutes.
All quite annoying, but facebook lite and messenger lite work. Other reddit apps seem to be more or less stable as well.
Everything else so far runs buttersmooth.
Yeah! First custom non-treble!
Many thanks for bring it to us
Adriano-A3 said:
Yeah! First custom non-treble!
Many thanks for bring it to us
Click to expand...
Click to collapse
Well it's available for weeks now... It's the xiaomi.eu rom, they just don't post their releases on xda
ok guys i used polaris twrp and it's ok i did format data before flash the rom and booted at first time.
Ok so I flashed successfully this rom after doing a full wipe (system, data...). Without wiping system, I was stuck on MI logo with dots.
I flashed Magisk and I'm rooted without problem, but the TWRP recovery doesn't stay.
I tried to flash the recovery many times using these commands (before and after being rooted), using the TWRP for Polaris linked by xiaomi.eu, but the Mi fastboot takes over everytime I try to boot TWRP.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Am I missing something?
I can start TWRP using those ADB fastboot commands of course, but not using just power down/power as usual.
mod please delete
Got Miui 10 8.6.20 last night, got 8.6.18 early yesterday.
Can anyone state if miui 10 supports the following:
- 1080p 120fps
- 1080p 60fps
- 4k 60fps
- Camera 2 api
DanDroidOS said:
Got Miui 10 8.6.20 last night, got 8.6.18 early yesterday.
Click to expand...
Click to collapse
Mi mix 2s?
hayatesan said:
Ok so I flashed successfully this rom after doing a full wipe (system, data...). Without wiping system, I was stuck on MI logo with dots.
I flashed Magisk and I'm rooted without problem, but the TWRP recovery doesn't stay.
I tried to flash the recovery many times using these commands (before and after being rooted), using the TWRP for Polaris linked by xiaomi.eu, but the Mi fastboot takes over everytime I try to boot TWRP.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Am I missing something?
I can start TWRP using those ADB fastboot commands of course, but not using just power down/power as usual.
Click to expand...
Click to collapse
Which version of TWRP are you using? You will need to use the Yellow theme one for flashing roms and the Blue theme version for flashing Magisk.
DanDroidOS said:
Got Miui 10 8.6.20 last night, got 8.6.18 early yesterday.
Click to expand...
Click to collapse
I checked update and no update.
Could you share the update.zip file ?
Mr.Titiv said:
I checked update and no update.
Could you share the update.zip file ?
Click to expand...
Click to collapse
You guys are talking about two different versions of miui. Eu Rom hast weekly builds. China beta Rom has daily builds. So I assume when talking in this thread, the topic should be the EU Rom and not an update of Chinese version. This is confusing to some inexperienced users.
MacLaughlin said:
You guys are talking about two different versions of miui. Eu Rom hast weekly builds. China beta Rom has daily builds. So I assume when talking in this thread, the topic should be the EU Rom and not an update of Chinese version. This is confusing to some inexperienced users.
Click to expand...
Click to collapse
Yes thanks for your remind, last night i already switched to EU rom 8.6.18.
andyphone said:
Which version of TWRP are you using? You will need to use the Yellow theme one for flashing roms and the Blue theme version for flashing Magisk.
Click to expand...
Click to collapse
i used the yellow one(polaris) for the rom and for magisk no problems at all
8.6.21 just came through.
PITTAR said:
i used the yellow one(polaris) for the rom and for magisk no problems at all
Click to expand...
Click to collapse
So you're able to boot on TWRP without ADB ?
Did you just flashed TWRP via ADB ?
I'm using the "yellow" version also (even though it's slow, it work without problem)
DanDroidOS said:
8.6.21 just came through.
Click to expand...
Click to collapse
I don't think this is the Xiaomi EU version.
So you are talking of another rom.
Or maybe I'm wrong.
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest fastboot ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same fastboot ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
DragonSlayer7# said:
So I was using PixelExperiece ROM and decided to switch back to MIUI. I downloaded latest recovery ROM from MIUI website, Flashed it using MI FLash Tool.
While flashing my phone displayed "System has been destroyed" in between. And MIFlash tool showed some error.
So, I tried flashing again and MIFlash tool now said Bootloader was locked. (Because lock_all_and_install was selected previously).
Therefore I downloaded MI Bootloader unlock tool. (The phone still shows "System has been destroyed"). Ignoring that warning, I went to fastboot and ran unlocker. To my surprise, after unlocking was complete and phone restarted it booted into MIUI. I thought "System has been destroyed" problem would be solved. But later I realised, my camera was not focusing on close range object. It wasnt focusing at all. Then after playing around to check everything I found out, my camera was not focusing, gyro was not working (No auto rotate and noting in CIT test) neither was my compass working. So there is some kind of problem with my hardware now.
Later I tried flashing same recovery ROM again hoping it will install fully now and not ending up in "System has been destroyed" error. And I also chose option to not lock bootloader while flashing in MI Flash tool. This time the phone did started on to MIUI but in MI Flash tool it kept showing flashing as status. Even after I disconnected my phone USB cable it said flashing. And those hardware things are still not working.
While using PixelExperience I did changed SELinux mode to make ANXCamera work. Would it (SELinux mode) be a problem for hardware not working? Or is there any other problem?
Thanks in advance for any help.
Click to expand...
Click to collapse
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
hackermssharma said:
Wait what u said u flashed recovery rom via mi flash ? U have to flash persist.img (u will find this in your fastboot rom) from custom recovery in system/persist partition. Thats it.
Click to expand...
Click to collapse
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
DragonSlayer7# said:
Im sorry, my mistake. I flased fastboot ROM only. Not recovery. MIFlash tool won't allow you to flash recovery ROM at all.
Click to expand...
Click to collapse
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
DragonSlayer7# said:
Instead of fixing existing sensors, flashing persist.img screwed up my wifi and hotspot. After flashing whole fastboot ROM againg they are now working. But other sensors are still not working.
Click to expand...
Click to collapse
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
flashing persist.img worked for me.
hackermssharma said:
Really? I mean i used same method last time for my sensors to work again and that worked for me. Next workaround is u should clean flash miui 10 fastboot rom then update to miui 11 using updater app. Hope it should work for u.
Click to expand...
Click to collapse
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
Great ??
Sensors
DragonSlayer7# said:
I flashed same MIUI fastboot ROM again, and miraculously all sensors started working again.:good::good:
Click to expand...
Click to collapse
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Widevine L1
hackermssharma said:
Mmmm... No need to worry extract persist.img from fastboot rom folder and flash via OF recovery in system/persist partition. Then boot u get all your sensors back.
Click to expand...
Click to collapse
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Azhar001 said:
I am also facing the same problem (sensors are not working) after i switched back from Pixel Experience to MIUI 11. Though i read all replies i did get some ideas but not clearly. Can you please little explain how to do it. Step by step method explanation will be much appriciated !! (only installation part, i have all required software and ROM ready for fastboot) I am just not clear how fix my sensors.
--------------------------------------------------------------
EDIT: No need guide. I understood how to do it. Some the things mentioned in reply were new for me so it was hard time for me to understand?.. I am new to Redmi phone
Click to expand...
Click to collapse
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Its fine. Just install Netflix from ApkMirror (not from Google Play) and it should work.
Azhar001 said:
Well i just got to know that by flashing 'persist.img' from a recovery will void Widevine L1 certification (Netflix with no HD, also other HD content streaming platform that requires Widevine L1 certification). I heard it will be permanent warrenty void and i don't know it can be fixed or not.
Click to expand...
Click to collapse
Also if you are coming back to MIUI, use this method...
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
DragonSlayer7# said:
This persist.img thing might work for you or might not.
The full proof way is to reinstall Pixel Experience (Android 10) so that you get your sensors up and running again, then flash MIUI 10 and upgrade to MIUI 11 using system updater app.
Click to expand...
Click to collapse
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Azhar001 said:
should i flash MIUI 10 using custom recovery or fastboot after reinstalling Pixel Experience ?
Click to expand...
Click to collapse
Fastboot ROM using MIFlashTool
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
okay, i willl let you know if it works
I think you should try reflashing the stock firmware using the Mi Flash and select wipe data option.
Sent from my Redmi Note 7 Pro using Tapatalk
DragonSlayer7# said:
Fastboot ROM using MIFlashTool
Click to expand...
Click to collapse
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Azhar001 said:
I got all the sensors back again, everything working fine.
Here is what is did (using PC):
1) i installed Pixek Experience ROM (Android 10) using ADB Fastboot method.
Pros: Every sensors started to work, back to normal.
Cons: None i noticed.
2) Then i turn off the phone and entered into fastboot mode
3) I flashed MIUI 10 fastboot ROM using MIFlash Tool. Though i didn't get the "Success" message on MIFlash Tool but phone booted itself (did show MIUI 10 during boot up, and Set Up screen was appearing) so i assumed flashing was complete. Then i unplugged phone from USB cable.
After setup,
Pros: Every sensors was working perfectly fine.
Cons: None i noticed.
4) i updated from MIUI 10 to MIUI 11 using System update on phone. Now i am on MIUI 11 and everything works FINE!!
So what i found is there is some problem with MIUI 11 fastboot ROM itself. Directly flashing MIUI 11 fastboot ROM is the reason sensors stops working!!
Click to expand...
Click to collapse
Yes, its kernel problem. It happens if you are flashing MIUI 11 based on Android Pie from any AOSP based ROM running Android 10.
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
Did you ever get any help? I am in the same boat.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
Piricho said:
Did you ever get any help? I am in the same boat.
Click to expand...
Click to collapse
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
RokCruz said:
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
saurabh_op7 said:
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
Click to expand...
Click to collapse
Just flash stock boot.img
RokCruz said:
Just flash stock boot.img
Click to expand...
Click to collapse
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
saurabh_op7 said:
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
Click to expand...
Click to collapse
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
RokCruz said:
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
RokCruz said:
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
Click to expand...
Click to collapse
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
saurabh_op7 said:
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
Click to expand...
Click to collapse
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
RokCruz said:
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
Click to expand...
Click to collapse
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
saurabh_op7 said:
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
Click to expand...
Click to collapse
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
RokCruz said:
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
Click to expand...
Click to collapse
My model is GM1901, in support intro for the link you provided, that's not included?
saurabh_op7 said:
My model is GM1901, in support intro for the link you provided, that's not included?
Click to expand...
Click to collapse
Wait GM1901 is a OnePlus 7(non pro) right?
RokCruz said:
Wait GM1901 is a OnePlus 7(non pro) right?
Click to expand...
Click to collapse
Yeah.. ?
saurabh_op7 said:
Yeah.. ?
Click to expand...
Click to collapse
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from HereI
Click to expand...
Click to collapse
Yeah man, I realised.. anyway, I flashed the boot image from Xda for OP7.. nevertheless, mom tool it is.. thanks..!
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
Click to expand...
Click to collapse
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Update: I have been roaming around the corridors of this forum since about a week now. Thanks @RokCruz !!
Finally, used msm tool, although I suspect I still had the option of flashing TWRP and Magisk as I had access to phone and fastboot, but the system was super glitchy.
saurabh_op7 said:
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Click to expand...
Click to collapse
I guess that the only way is using the fastboot ROM
RokCruz said:
I guess that the only way is using the fastboot ROM
Click to expand...
Click to collapse
Any idea if we're gonna get one soon?
As you may know the a12 has some issues with gsi and random reboots on post kernel installations,I found some work around especially for U variants models.
Install stock rom,unlocked bootloader is needed.Install TWRP then install Rainbow kernel(choose the last on in the thread on the last page,no reboot issues on U variants) and let device boot up.Find a GSI that's your preference,then flash as system img in TWRP.Wipe data/Cache.No magisk zip require just install the app and finish the setup for root ect.
Best to use PHH base but I have gotten lineage 19 to work,also the kernel fixes the Screen issue where it shuts off.Also can confirm Official TWRP works on the a125u variant.The new android 13 GSI is confirmed working if curious just don't flash vbmeta and wipe data or you'll get a bootloop
RomLord14495 said:
As you may know the a12 has some issues with gsi and random reboots on post kernel installations,I found some work around especially for U variants models.
Install stock rom,unlocked bootloader is needed.Install TWRP then install Rainbow kernel(choose the last on in the thread on the last page,no reboot issues on U variants) and let device boot up.Find a GSI that's your preference,then flash as system img in TWRP.Wipe data/Cache.No magisk zip require just install the app and finish the setup for root ect.
Best to use PHH base but I have gotten lineage 19 to work,also the kernel fixes the Screen issue where it shuts off.Also can confirm Official TWRP works on the a125u variant.The new android 13 GSI is confirmed working if curious just don't flash vbmeta and wipe data or you'll get a bootloop
Click to expand...
Click to collapse
hello i recently got storage issues where i cant install any app or thing... and when i open the storage in settings its just crashing, do you have that issue? And can you also give me a link of lineage os 19? Thanks.
i tried to flash 19 but i get in a bootloop
and i cant boot in twrp without flashing vbmeta
dav1234444 said:
hello i recently got storage issues where i cant install any app or thing... and when i open the storage in settings its just crashing, do you have that issue? And can you also give me a link of lineage os 19? Thanks.
Click to expand...
Click to collapse
I had the same issue,there's no resize partition in TWRP but on GSI storage is the norm 32gb.
dav1234444 said:
i tried to flash 19 but i get in a bootloop
Click to expand...
Click to collapse
What variant are you using,I'm using the a125u with the a125w bootloader,and vbmeta I used to unlock from another thread here,never had a problem with TWRP,does your phone say cannot verify vbmeta when it boots up? Mine says it in blue text.
dav1234444 said:
i tried to flash 19 but i get in a bootloop
Click to expand...
Click to collapse
It works,depends on what version you used,I used Andy's Lineage based on his and PHHs commits,only issues I've had with is is headset detection issues,which is fixed by going into phh settings,also you need to wipe data after install.ill link it for you
thanks can u give me android 12
RomLord14495 said:
It works,depends on what version you used,I used Andy's Lineage based on his and PHHs commits,only issues I've had with is is headset detection issues,which is fixed by going into phh settings,also you need to wipe data after install.ill link it for you
Click to expand...
Click to collapse
Do you have problems when trying to restart its hungs up or other problem stuck on deadboot in gsi12 rom the only way to fix is doing force reboot via volume down and power
No problems except when I try to place a call it instantly hangs up
hmm i flashed the version with gapps and google play has no internet aaaand i have 2 like routers and i connected to 1 then i cant connect to the second one hmm?
it always goes to the one i connected first
seems like pixel expereince has less bugs
dav1234444 said:
seems like pixel expereince has less bugs
Click to expand...
Click to collapse
Cherish os is better i tried pixel experience i experience lag while cherish os is smooth and so much added features like theme
Sheepmister said:
Cherish os is better i tried pixel experience i experience lag while cherish os is smooth and so much added features like theme
Click to expand...
Click to collapse
can u download apps
btw can u give me a link to it
dav1234444 said:
btw can u give me a link to it
Click to expand...
Click to collapse
and is it android 12
dav1234444 said:
and is it android 12
Click to expand...
Click to collapse
https://xiaomemeindex.com/treble/Cherish/20220715/CherishOS_v414-arm64-bgS-slim_20220715.img.xz
Its android 12L
thanks
finally a good rom with no bugs thanks a lot