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 !
Related
Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.
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.
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Apcoolboy said:
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Click to expand...
Click to collapse
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
There is flashable zip file which is extracted from miui rom only. So both way will be good as flash latest stable miui rom and then twrp > rom zip > gapps. Or twr0 > firmware zip (search in any custom rom thread you will get one) > custom rom zip > gapps.
Only benefit of flashing firmware zip is less time consuming and less file size (around 50mb) compare to full miui rom.
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
unlock your bootloader again it will run without problem..
System Configuration:
ROM: MIUI Global 8.1.25 | Beta
Kernel: 3.10.84-perf-g1cb6922
RAM: 2.00 GB
Device: Redmi note 3 (kenzo) with officially unlocked bootloader.
There are a number of tutorials and posts on XDA and YouTube with varying content. Some of them do not flash the boot.img, some of them do.
I will be using Ubuntu to flash using adb and fastboot. Any suggestions regarding that would be great.
Here are the steps I think I should follow ( from the posts I read):
1. Boot into fastboot.
2. Flash twrp-**.img
3. Boot into TWRP recovery.
4. Flash SuperSU
5. Flash Lazyflasher
Would that sequence cause any problem?
No problem, just flash twrp without prior boot.img flashing.
NealSchwartz said:
System Configuration:
ROM: MIUI Global 8.1.25 | Beta
Kernel: 3.10.84-perf-g1cb6922
RAM: 2.00 GB
Device: Redmi note 3 (kenzo) with officially unlocked bootloader.
There are a number of tutorials and posts on XDA and YouTube with varying content. Some of them do not flash the boot.img, some of them do.
I will be using Ubuntu to flash using adb and fastboot. Any suggestions regarding that would be great.
Here are the steps I think I should follow ( from the posts I read):
1. Boot into fastboot.
2. Flash twrp-**.img
3. Boot into TWRP recovery.
4. Flash SuperSU
5. Flash Lazyflasher
Would that sequence cause any problem?
Click to expand...
Click to collapse
yes the steps you're mentioned above is correct, you don't have to flash boot.img. just do the steps above.
Zasnizas said:
yes the steps you're mentioned above is correct, you don't have to flash boot.img. just do the steps above.
Click to expand...
Click to collapse
Thank you, bud! I have successfully install TWRP and also installed RR Rom on my Redmi Note 3. However, I have now lost root access.
I tried flashing the SuperSU.zip again, but to no avail. Where did I go wrong? How can I get root access back?
mistake37 said:
No problem, just flash twrp without prior boot.img flashing.
Click to expand...
Click to collapse
Thanks! Worked like charm. But I now lost root after installing RR custom Rom.
hey
I'm glad it worked, would you be so kind to post the links for those files you mentioned?
Also I'm on the latest stable Miui 9(snapdragon), will it work for me?
NealSchwartz said:
Thank you, bud! I have successfully install TWRP and also installed RR Rom on my Redmi Note 3. However, I have now lost root access.
I tried flashing the SuperSU.zip again, but to no avail. Where did I go wrong? How can I get root access back?
Click to expand...
Click to collapse
I recommend you to use magisk as a root access. To be safe you need to make clean flash your rom again , who's know maybe superSu already exists in your system but not appear on apps drawer by doing this your device will be cleaned from anything that can cause you into bootloop. First download magisk and magisk manager and place it in phone memory or SD card it's up to you and then reboot to TWRP ,wipe everything cache , dalvik cache , system and data then flash rom , gapps and magisk.. reboot. Search for magisk at XDA and download it.
Karanfil said:
I'm glad it worked, would you be so kind to post the links for those files you mentioned?
Also I'm on the latest stable Miui 9(snapdragon), will it work for me?
Click to expand...
Click to collapse
TWRP: Go to official website and download latest version
SuperSU: https://androidfilehost.com/?fid=385035244224394155
lazy-flasher: https://androidfilehost.com/?fid=457095661767111293
I am not sure if it would work, but I was also on MIUI 9 and it worked for me. Hopefully, someone else here will be able to let you know. AFAIK, it should work.
Zasnizas said:
I recommend you to use magisk as a root access. To be safe you need to make clean flash your rom again , who's know maybe superSu already exists in your system but not appear on apps drawer by doing this your device will be cleaned from anything that can cause you into bootloop. First download magisk and magisk manager and place it in phone memory or SD card it's up to you and then reboot to TWRP ,wipe everything cache , dalvik cache , system and data then flash rom , gapps and magisk.. reboot. Search for magisk at XDA and download it.
Click to expand...
Click to collapse
Thank you so much! It worked. I followed the steps, did a clean install and this time opted for Magisk. Awesome!
NealSchwartz said:
Thank you so much! It worked. I followed the steps, did a clean install and this time opted for Magisk. Awesome!
Click to expand...
Click to collapse
awesome.. glad it worked for you :good:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
ultramag69 said:
You have an old version of TWRP... You need to install a newer version - 3.2.3.2 - which you will find by doing a search for it here on XDA...
Just load img file on INTERNAL storage of phone, choose install>install image file> and click on recovery partition. After install go to home menu and restart recovery...
If you still have issues then download magisk again, it may be corrupt...
Cheers....
Click to expand...
Click to collapse
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
fajniejest said:
First of all, I'm not going to install TWRP - I want only to boot into TWRP once for flashing Magisk's ZIP.
Second - in this guide OP says that Unofficial TWRP should be used. I've tried v1 and v2 TWRP from the guide. So which other TWRP should I try to boot into? This? https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-x-t3836241
Click to expand...
Click to collapse
I am new on this forum (pocophone) and i seee how messed up it is. You should definitly use official twrp
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
fajniejest said:
Hello. I was going through this guide --> https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
I've got a problem. I've unlocked bootloader and next I'm booting correctly to TWRP, but when I try to flash any zip of magisk manager I receive an error: "invalid zip file format". I'm using TWRP 3.2.3-0 from first post in guide - I was trying to use both 20181012 and 20181211 versions and no result - still the same error. What can I do? I'm using POCOPHONE F1 with MIUI Global 10.2.3.0
Click to expand...
Click to collapse
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
tnsmani said:
what are you trying to flash? If it is Magisk Manager, it is in apk format and you just click it to install. No TWRP.
If it is Magisk, which version are you trying to flash? Try 18.1. And preferably download any file from its source.
EDIT: If Magisk v18.1 is also not flashing, try Magisk Canary version. Some phones need that.
Click to expand...
Click to collapse
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
fajniejest said:
I'm trying to flash zip with Magisk Manager, as it is said in guide. I know that I can have an apk, but is it enough to just install apk without having custom recovery (but having bootloader unlocked)?
I will try it if nothing from "my" guide will work, because I really don't want to lose my storage (I see that in this guide installing Magisk needs it)
Click to expand...
Click to collapse
Well Here is how i managed it to work. After i unlocked my bootloader i launched twrp and flashed beta magisk 19.0 (not latest anymore because 19.1 just today showed up) then i reminded that i forgot about DisableForceEncryption_Treble_v18.0.zip so i flashed iit and after it flashed again magisk 19.0, after reboot it everything was fine
GrecoNeoV said:
You don't need official TWRP, but I think you need to install Disable Force Encryption, before installing the Magisk app
This thread will be more helpful.
Click to expand...
Click to collapse
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'flashboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
The command is 'fastboot boot twrp-<version>.img'
tnsmani said:
The command is 'fastboot boot twrp-<version>.img'
Click to expand...
Click to collapse
Thanks for the correction. I really don't know where I got flashboot from.
Cheers!
guhvanoh said:
There is no need to flash DFE. I've unlocked my bootloader, installed TWRP, flashed PE and Magisk 19.0 all without DFE which I don't need.
@OP, you need TWRP version 3.2.3-2 at a minimum, which you can boot using 'fastboot boot twrp-<version>.img' . Then flash Magisk. You'll
need at least version 18.1.
HTH
Click to expand...
Click to collapse
So, to make it clear (and to not brick my poco... ):
1. I should use TWRP image from this link --> https://twrp.me/xiaomi/xiaomipocophonef1.html...
2. ...and I don't need to replace my recovery - just booting it once (as You described) is enough.
3. I should flash Magisk's ZIP, not MagiskManager's ZIP or Magisk.apk
4. No more flashing, clearing data and other operations needed.
Am I right?
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
guhvanoh said:
1 - Yes.
2 - That's down to you. I have TWRP recovery installed and I have the app as well.
3 - You need to flash Magisk and install the apk. See this link for instructions on installing Magisk.
4 - Yes, you need to clear data, wipe dalvik and cache when installing a new ROM. If updating a current rom, I just wipe dalvik & cache.
HTH
Click to expand...
Click to collapse
Big thanks! Finally dealt with it. So grateful for Your help. :victory:
Dearminder said:
Hey I know its not a thread related but if u install magisk can u tell me if you have 60fps screen recoding option? Because I already Dirty flashed rom once and nothing changed still cant unlock it :/
Click to expand...
Click to collapse
Yes, I do. I've not tried it though...