As the title says global beta 7.2.9 is out. Anyone installed it?
What about twrp and root compatibility?
http://en.miui.com/download-299.html here is the link
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
mysa50 said:
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
Click to expand...
Click to collapse
Can you confirm the process please? Is it just:
1. Download the recovery version of the update to the phone.
2. Boot to recovery (TWRP).
3. Install the update zip file.
4. Re install TWRP.
5. Reinstall the SuperSU zip.
6. Reboot to system.
Do we need additional reboots between the steps? Do we need to unroot before installing the update? Does it matter if the existing global beta ROM is several versions old?
Sorry for asking so many questions. I have not updated the ROM since unlocking the bootloader and installing TWRP/SuperSU several months ago and am worried about bricking my phone.
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
mysa50 said:
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
Click to expand...
Click to collapse
That's good to know. Just to confirm, the update could be applied "dirty" without a need to reinstall all apps and data afterwards?
I am still on global beta 6.11.3 (which is MM) and twrp 3.0.2.0. Is 7.2.9 based on nougat which would require the update of twrp? I had thought that the nougat beta was on a separate thread open to a closed group only...
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Delete
Bhatyasirr said:
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Click to expand...
Click to collapse
Look in the mi5 developement thread There is twrp section and in the 3rd post the op uploaded a unofficial release of twrp 3.0.3 but stable enough to be considered as official.
mysa50 said:
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Click to expand...
Click to collapse
Thanks a lot. Shall try over the weekend.
Few screenshots
mysa50 said:
Few screenshots
Click to expand...
Click to collapse
This is on light use, with heavy use (games,messages,phone calls) battery last a day from 6.30 am to midnight and still 10-15% and ~5h30 sot
That's good
how to revert back to miui from LOS ?
it didnt boot up
harrez said:
how to revert back to miui from LOS ?
it didnt boot up
Click to expand...
Click to collapse
Did you try fastboot rom from xiaomi site? Give a look in the Q&A thread you should find how to revert back to miui
chan200606 said:
Thanks a lot. Shall try over the weekend.
Click to expand...
Click to collapse
Finally did it, but not without scare - my Mi5 was stuck at the boot logo with "Bootloader unlock" message screen after flashing the recovery version of 7.2.9 update and reflashing TWRP 3.0.3.0. Luckily managed to get the phone into fastboot mode to flash the fastboot version of 7.2.9 and get the phone back on again. Finally reinstalled TWRP and boot into TWRP before rebooting to system successfully.
The key step I had forgotten was the booting into TWRP after its installation over the 7.2.9 stock recovery, which had led to the bootloop.
So I now have updated to 7.2.9. I do notice that the boot process takes quite a bit longer than 6.11.3 (design of nougat?), but once up, the phone feels as responsive as before.
Related
Hello everyone,
I rooted my OnePlus X using Kingroot. Now that the update for Marshmallow is available, I am willing to update my unit to the same. I had unrooted my device using the SuperSU app. After that, I unlocked my bootloader and tried to boot to TWRP and install OTA update, no success. I also tried installing the update via stock recovery but it shows installation failed.
Also tried resetting my device and then installing the update but no dice. Nor do I have the unrooted backup. Also,have changed the system font.
Tried searching the forums. Please tell me how can I update to the official Marshmallow latest build?
Device Information:
Oxygen OS version: 2.1.3-x
Bootloader State: Unlocked
Recovery: Stock
Thanks in advance!
You need this update file. Because rooted your opx!
http://forum.xda-developers.com/showpost.php?p=68655787&postcount=49
Zat.o.ichi said:
You need this update file. Because rooted your opx!
http://forum.xda-developers.com/showpost.php?p=68655787&postcount=49
Click to expand...
Click to collapse
What about the system font? And will I get OTA updates as I have unlocked my device's bootloader?
mukul2259 said:
Hello everyone,
I rooted my OnePlus X using Kingroot. Now that the update for Marshmallow is available, I am willing to update my unit to the same. I had unrooted my device using the SuperSU app. After that, I unlocked my bootloader and tried to boot to TWRP and install OTA update, no success. I also tried installing the update via stock recovery but it shows installation failed.
Also tried resetting my device and then installing the update but no dice. Nor do I have the unrooted backup. Also,have changed the system font.
Tried searching the forums. Please tell me how can I update to the official Marshmallow latest build?
Device Information:
Oxygen OS version: 2.1.3-x
Bootloader State: Unlocked
Recovery: Stock
Thanks in advance!
Click to expand...
Click to collapse
Download your current version oxygen os rom put it in sd card and flash it via stock recovery, once u done that it ll again make ur phone us unmodified system now then download oxygen os 3.1.3 from oneplus website and and flash it by stock recovery this time it ll work cos of unmodified system.
Flash this first it ll work Oos 2.1.4 download link https://s3.amazonaws.com/oxygenos.oneplus.net/OnePlusOxygen_14_OTA_007_all_201512161752.zip
Boot into system reboot flash oos3.1.3
Marshmellow oos 3.1.3 download link https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
Doubts? Feel free to ask
I suggest you go step by step, from 2.1.3 upgrade to 2.1.4, move to 2.2.2 then 2.2.3, finally the MM, It worked in my case, I was also on 2.1.3 and faced trouble.. Hope it helps you.
Infact, after upgrading to 2.2.2, the system should have been unrooted. Just flash stock Lollipop recovery and leave it. You should get the rest of the updates as OTA immediately.
mukul2259 said:
Hello everyone,
I rooted my OnePlus X using Kingroot. Now that the update for Marshmallow is available, I am willing to update my unit to the same. I had unrooted my device using the SuperSU app. After that, I unlocked my bootloader and tried to boot to TWRP and install OTA update, no success. I also tried installing the update via stock recovery but it shows installation failed.
Also tried resetting my device and then installing the update but no dice. Nor do I have the unrooted backup. Also,have changed the system font.
Tried searching the forums. Please tell me how can I update to the official Marshmallow latest build?
Device Information:
Oxygen OS version: 2.1.3-x
Bootloader State: Unlocked
Recovery: Stock
Thanks in advance!
Click to expand...
Click to collapse
Did you check that the OEM unlocking was enabled after you unlocked the bootloader? Maybe that can be a problem. And I guess flashing the OOS Marshmallow build is possible only with the stock recovery (if you do not want to delete some lines from the code). So I'd stick to stock recovery if I want to update the OOS.
aamodjoshi23 said:
Did you check that the OEM unlocking was enabled after you unlocked the bootloader? Maybe that can be a problem. And I guess flashing the OOS Marshmallow build is possible only with the stock recovery (if you do not want to delete some lines from the code). So I'd stick to stock recovery if I want to update the OOS.
Click to expand...
Click to collapse
Yes, I did check it. It is enabled.
sagar2208 said:
I suggest you go step by step, from 2.1.3 upgrade to 2.1.4, move to 2.2.2 then 2.2.3, finally the MM, It worked in my case, I was also on 2.1.3 and faced trouble.. Hope it helps you.
Infact, after upgrading to 2.2.2, the system should have been unrooted. Just flash stock Lollipop recovery and leave it. You should get the rest of the updates as OTA immediately.
Click to expand...
Click to collapse
I guess this is more logical to do right now. Maybe it's something in the system that can be overwritten after upgrading to OOS 2.2.2. Because when I flashed the beta testing ROM on my device when I had the OOS 2.2.2, it worked just fine. But I guess it won't work if you don't have an older version of OxygenOS because of the small tweaks
aamodjoshi23 said:
I guess this is more logical to do right now. Maybe it's something in the system that can be overwritten after upgrading to OOS 2.2.2. Because when I flashed the beta testing ROM on my device when I had the OOS 2.2.2, it worked just fine. But I guess it won't work if you don't have an older version of OxygenOS because of the small tweaks
Click to expand...
Click to collapse
So, I should flash 2.1.3 via stock recovery and then go to 2.2.2, right?
mukul2259 said:
So, I should flash 2.1.3 via stock recovery and then go to 2.2.2, right?
Click to expand...
Click to collapse
You could just update the ROM by checking for updates in the about phone
Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !
It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input
Link: https://www.fshare.vn/file/RTJXVAH9KSY9?token=1535025145
Update Miui 8.8.29:
link: http://www.fshare.vn/file/KQNTVM7UGGK9
link mega: https://mega.nz/#!Ws9mXYhb!fdDQrJWY-rAQEJSidTQRnI39E2xadWaXOMZl9rA1YGs
flash with twrp or ota with accout xiaomi beta test
Update link Miui 8.8.30 from Xiaomi:
http://bigota.d.miui.com/8.8.30/miui_MI8Global_8.8.30_1e559f40ab_8.1.zip
Ziarrr said:
update link Miui 8.9.4: https://mega.nz/#!S8k2WIzA!idZKZN2q1mlW5JkhtkAD38q-_HWWxbrBy_bgPUQG7RU
Click to expand...
Click to collapse
Ziarrr said:
Link: https://www.fshare.vn/file/RTJXVAH9KSY9?token=1535025145
Click to expand...
Click to collapse
Hello,
Is this a fastboot rom or recovery rom?
Ziarrr said:
Link: https://www.fshare.vn/file/RTJXVAH9KSY9?token=1535025145
Click to expand...
Click to collapse
hugge18 said:
Hello,
Is this a fastboot rom or recovery rom?
Click to expand...
Click to collapse
Recovery rom
Wow this download page is so bad. Any other page where we can download the rom? I only understand "ding dang dong" and have no idea where to click to download.
grootooter said:
Wow this download page is so bad. Any other page where we can download the rom? I only understand "ding dang dong" and have no idea where to click to download.
Click to expand...
Click to collapse
click at testview white and wait 30s
downloading.. ETA 16 hours...
Hello,
Do I need an authorized beta account?
---------- Post added at 04:21 PM ---------- Previous post was at 04:17 PM ----------
alternative link: http://bigota.d.miui.com/8.8.21/miui_MI8Global_8.8.21_fc07cb2c7d_8.1.zip
You guys will need an authorized beta account unless you want to flash the ROM via TWRP Recovery
So, I updated without an authorized account though TWRP. As soon as I tried to reboot to system, it brought me back to TWRP.
I suppose I had to disable encryption all over again so I formatted Data, installed the update again and started to move the required zip for Magisk and encryption disabling back in the internal memory. During the installation the system rebooted (I didn't ask to, the first time it didn't reboot til I asked) and something crashed on the first screen pf MIUI 10. Then it decided to reboot again to recovery... and the TWRP was gone, I have the MIUI stock recovery again. Anyway, I formatted the data once more and the system is running without problems now.
tldr: Updated, data was deleted, TWRP is gone, system seems good
Fabrz said:
So, I updated without an authorized account though TWRP. As soon as I tried to reboot to system, it brought me back to TWRP.
I suppose I had to disable encryption all over again so I formatted Data, installed the update again and started to move the required zip for Magisk and encryption disabling back in the internal memory. During the installation the system rebooted (I didn't ask to, the first time it didn't reboot til I asked) and something crashed on the first screen pf MIUI 10. Then it decided to reboot again to recovery... and the TWRP was gone, I have the MIUI stock recovery again. Anyway, I formatted the data once more and the system is running without problems now.
tldr: Updated, data was deleted, TWRP is gone, system seems good
Click to expand...
Click to collapse
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Hello, i had buy a china Version. After waiting Time toi unlock i Do it ans install xiaomi.eu rom. Now i would like to install this global.
What Can i need to do?
Just wipe data ans Factory reset and flash thé rom with TWRP ans wipe dalvik cache when finish and reboot?
Do i need to use dm-verity for twrp and to doesn't brick phone or bootloop? Sorry for my english.
3597dxta said:
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Click to expand...
Click to collapse
I had the 3.2.3 and global 8.8.7, same as you. Maybe you formatted data before flashing? That's the only thing I can think of.
Anyway, an happy feedback: Gps is working after few hours, that's what pushed me to try this update
Fabrz said:
I had the 3.2.3 and global 8.8.7, same as you. Maybe you formatted data before flashing? That's the only thing I can think of.
Anyway, an happy feedback: Gps is working after few hours, that's what pushed me to try this update
Click to expand...
Click to collapse
I didn't format data, I entered my lockscreen password into twrp the first time opened it, it said data was decrypted successfully and voilq, I was able to wipe and flash without any problem
3597dxta said:
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Click to expand...
Click to collapse
do i still to wipe before flashing? im on global 8.8.7
vizard101 said:
do i still to wipe before flashing? im on global 8.8.7
Click to expand...
Click to collapse
Just wipe cache & dalvik cache. No need to wipe all
No fastboot version available ?
Best regards [emoji6]
Envoyé de mon MI 8 en utilisant Tapatalk
3597dxta said:
Try flashing the new version 3.2.3 of TWRP for MI 8, I was on global dev 8.8.7, flashed the recovery image flawlessly then I flashed the ROM 8.8.21 here and reboot successfully.
Click to expand...
Click to collapse
Do I need to unlock bootloader first before flash?
cheehong93 said:
Do I need to unlock bootloader first before flash?
Click to expand...
Click to collapse
Here the procedure for guys who haven't unlocked their bootloader
1.unlock bootloader
2.download and flash fastboot 8.8.7 Global Beta (closed beta)
3. Download and flash TWRP 3.2.3
4.download this recovery rom 8.8.21 and flash via Twrp (no need to wipe all but cache and dalvik)
8.8.23 is out since yesterday, do someone have the download link for the Mi 8?
Hello,
but the global beta miui 10 8.8.7 and more old global beta miui 10 8.8.21 ?
Hi,
I am on 11.0.5.0 PEJMIXM PIE i was trying to upgrade to V11.0.6.0.QEJMIXM android 10 using dirty flash.
Using Twrp recovery 3.3 i installed the rom and installed magisk 20.4 and disable force encrypt 01.19.20 still my phone bootloops.
So i reverted back to 11.0.5.0 PEJMIXM
And the phone boots properly i dirty flashed 11.0.6.0 over 11.0.5.0 what i am doing wrong? I followed every steps carefully. My bootloader is unlocked officially.
Please guide me
Cheers
iaintken said:
Hi,
I am on 11.0.5.0 PEJMIXM PIE i was trying to upgrade to V11.0.6.0.QEJMIXM android 10 using dirty flash.
Using Twrp recovery 3.3 i installed the rom and installed magisk 20.4 and disable force encrypt 01.19.20 still my phone bootloops.
So i reverted back to 11.0.5.0 PEJMIXM
And the phone boots properly i dirty flashed 11.0.6.0 over 11.0.5.0 what i am doing wrong? I followed every steps carefully. My bootloader is unlocked officially.
Please guide me
Cheers
Click to expand...
Click to collapse
First of all remove any password or fingerprint you have on it. Also remove your google account. Backup your data. Now try flashing zips one by one. First flash the rom, boot it. Setup everything and reboot to recovery. Now flash magisk. If that doesn't work clean flash is your only way. Dirty flashing usually causes problems.
Use pitchblack recovery.
https://sourceforge.net/projects/pi...ium-2.9.1-20200411-0512-OFFICIAL.zip/download
And forget all common problems and encryption
callmebutcher101 said:
First of all remove any password or fingerprint you have on it. Also remove your google account. Backup your data. Now try flashing zips one by one. First flash the rom, boot it. Setup everything and reboot to recovery. Now flash magisk. If that doesn't work clean flash is your only way. Dirty flashing usually causes problems.
Click to expand...
Click to collapse
Thanks i will try ot
Mezoo23 said:
Use pitchblack recovery.
https://sourceforge.net/projects/pi...ium-2.9.1-20200411-0512-OFFICIAL.zip/download
And forget all common problems and encryption
Click to expand...
Click to collapse
Great will try it
iaintken said:
Hi,
I am on 11.0.5.0 PEJMIXM PIE i was trying to upgrade to V11.0.6.0.QEJMIXM android 10 using dirty flash.
Using Twrp recovery 3.3 i installed the rom and installed magisk 20.4 and disable force encrypt 01.19.20 still my phone bootloops.
So i reverted back to 11.0.5.0 PEJMIXM
And the phone boots properly i dirty flashed 11.0.6.0 over 11.0.5.0 what i am doing wrong? I followed every steps carefully. My bootloader is unlocked officially.
Please guide me
Cheers
Click to expand...
Click to collapse
Goto twrp and advanced wipe and type yes it will format all data and then reboot your phone must be boot
varunsngh786 said:
Goto twrp and advanced wipe and type yes it will format all data and then reboot your phone must be boot
Click to expand...
Click to collapse
Thanks