** BRICK WARNING/Disclaimer/Requirements **
>> Only flash with unlocked bootloader <<
>> Scripts are released under GPlv2 license <<
>> Run at own risk <<
Hi,
I patched the TWRP 3.0 recovery from faust93 to include important partitions
that make switching between different versions of Android/Ubuntu very simple.
All partitions are properly added to the fstab, but out of fear that some of
you will brick your device i disabled most of them.
Next version will contain a backup of all unique partitions, but i will have
to test this thoroughly.
Steps to install:
1. Download the zip file from attachments below
2. Unpack the zip file
3. Check checksum with md5sum -c *.md5
4. Put phone into fastboot mode (boot device with [vol-] and [power] button)
5. Flash recovery with:
# fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img
# fastboot reboot
then boot the device with [vol+] and [power] button, to enter recovery
[Requested by @p82maarj]
Already on an older TWRP version ?
- Flash "update_TWRP_3.0_m86_patched_st0rm77.zip" from TWRP
or
- Unpack the zip and flash the recovery manually in TWRP by selecting "install image"
Enjoy
Warning:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **
Hi @st0rm77
Thanks for your contrubution!
It will be good if you create a flashable zip of your new recovery. It can be flashed directly from the stock recovery or from the other twrp recovery without entering in fastboot.
Furthermore to have a flashable zip is usefull to flash a new rom update. For updating the new rom version I enter in TWRP, flash rom zip, flash unlocked bootloader zip and flash TWRP zip.
I attach the other flashable TWRP zip you can based on (only replace recovery.img by your recovery.img).
Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)
Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?
PYCON said:
Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?
Click to expand...
Click to collapse
Yeah, you get some extra abilities:
- Backup of Boot Logo
- Backup of Device Tree
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.
Thanks for everything you've been releasing, great work!
st0rm77 said:
Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)
Click to expand...
Click to collapse
Done Thanks!
st0rm77 said:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **
Click to expand...
Click to collapse
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!
Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?
PYCON said:
Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?
Click to expand...
Click to collapse
I know the answer to this one!
The first zip contains the img file that you can flash using fastboot.
The second (update) zip is the one you need if you already have (an older) TWRP and you wish to update to this version (use it from inside TWRP).
abePdIta said:
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!
Click to expand...
Click to collapse
boot.img is your boot partition, you need this one :good: (NEEDED)
bootloader is the locked bootloader from meizu, avoid this one as the plague (AVOID)
Dont brick your device, check everything carefully :fingers-crossed:
st0rm77 said:
Dont brick your device, check everything carefully :fingers-crossed:
Click to expand...
Click to collapse
Thank you very much! I will be careful in the future, I promise!
i follow the a to I tutorial
then unlock bootloader
then this
now when i conect meizu to pc i try to pass custom rom to internal memory and the phone restart
what is the problem
---------- Post added at 10:35 PM ---------- Previous post was at 09:56 PM ----------
managed to download the rom in phone browser now i have RR and all it´s ok
I flash stock recovery ( use update 5.1.10.0g) but not success, hÃc hÃc, help me restore stock recovery, many thanks!!!!
st0rm77 said:
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.
Click to expand...
Click to collapse
Just to be sure I understood :
Going from Flyme to CM :
-Backup Flyme (system+data+dtd)
-Flash CM archive
Going back to Flyme
-(optional) Backup CM (system+data+dtd)
-Restore Flyme (system+data+dtd)
Is there is a quikier way ?
TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:
help
hi .i change meizu pro 5 from china to national (5.6.1.19 daily )and unlock it and flash recover TWRP 3.0 but not login it the recovery .
i want updated
PYCON said:
TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:
Click to expand...
Click to collapse
I too vote for a port!
3.1.1 was released
munky-head said:
3.1.1 was released
Click to expand...
Click to collapse
Not for PRO5
Hey guys,
I was trying to unlock my phone and install a custom ROM so I installed TWRP and everything was going smooth until I tried installing a custom ROM. In TWRP I hit "Install" and click the zip file for the ROM I want (PureNexus) and it says "Invalid zip file format! Error installing zip file '/sdcard/PureNexus.zip"
Does anyone know what the problem is? I can't figure this out. This is the first time I'm doing anything from the bootloader so I'm a bit of a newb. I would be fine going back to stock everything if it means my phone will turn on. I tried installing the official image from google (7.1.1) and I get the same zip error.
So where I'm at is I do not have an OS installed on but I do have access to TWRP. In the command prompt on my desktop it recognizes my phone when I type 'adb devices' but it doesn't do anything when I type 'fastboot devices'.
Any help is greatly appreciated. I'm scared.
Okay, so I figured out what fastboot was and I was able to install Google's 7.1.1 stock image using the command prompt. I was freaking out for a few hours and even though I didn't get the custom ROM I wanted I'm really happy I didn't brick my phone. I've never done anything like this on my phone so it was a fun learning experience
I'm still curious what I did wrong and why TWRP couldn't unzip any of the zip files (PureNexus, Google Stock, etc). If anyone knows I'm still interested in learning what I did wrong.
Unheard7 said:
... why TWRP couldn't unzip any of the zip files (PureNexus, Google Stock, etc).....
Click to expand...
Click to collapse
TWRP: wrong version or damaged;
ZIP: damaged or incomplete download.
Latest version TWRP is 3.2.1.0.
NLBeev said:
TWRP: wrong version or damaged;
ZIP: damaged or incomplete download.
Latest version TWRP is 3.2.1.0.
Click to expand...
Click to collapse
Yes, and the Google factory image isn't meant to be flashed that way. I guess the Google OTA image might be flashed from TWRP, but I haven't tried it.
TWRP will flash an image (. img) file if you set it to by tapping the img button. If you don't have that set and try to flash an image it will error. If you have it set to img and try to flash a zip it will also error.
1. Unlock the bootloader.
2. Install the latest TWRP recovery.
3. Wipe.
4. Install the required ROM.
To go back to stock firmware, just download the relevant factory firmware zip, extract it and run the script. I think a readme file is provided in the zip explaining how to go about it.
Cheers! Happy New Year!
Hello everyone.
I had this issue recently that I figured out how to fix.
When I tried flashing a custom Android Q Rom in TWRP recently, it would either go reboot to Twrp or get stuck on the bootloader unlocked screen for a few seconds and then give me a qualcomm crash error. I found out the problem (at least with me) is that I upgraded my OOS to stable 10, tried it for a bit, and decided to use the downgrade pie zip that OnePlus provided, and I didn't know I was getting those errors because of that.
To hopefully fix it for you guys too, first, you wanna put your device into fastboot mode and download the zip from here https:// androidfilehost .com/?fid=11410932744536996577 then unzip the archive and inside the unzipped folder, unzip the other 2 archives and run the .bat file named flash-all-partitions-fastboot and let it run and finish, and after that your custom ROMs should boot. If you're still rebooting to TWRP for some reason after that, flash Twrp 3.3.1-20 by mauronofrio and that issue should be fixed.
Hopefully this quick guide will help some of you out.
Edit: Forgot to tell you guys in that link that I gave I put a couple of spaces so I could post you guys the link, because they won't let you post links with new accounts, so just delete the spaces
So today, I decided it was time to give the Pixel Experience ROM a try, because well.. it is one of the very few available for this phone for now (although some nice development arms to be going on for this phone).
Thing is, I couldn't succeed in any way at all. There is the Device page with its own instructions in the change logs:
https://download.pixelexperience.org/xqau52
FLASH OEM V9C AND NEWER OR YOUR DEVICE WON'T BOOT ********** IMPORTANT: README ********** ### Be sure to have the latest ODM, even when you get a OTA!!! ### To get this ROM and the OTA updater to work fine, you NEED TO follow a few steps: 1. Download Androxyde's FlashTool 2. Flash the latest STOCK firmware for your device, in order to get a bootloader bugfix for unlocked A/B 3. Before flashing this ROM through your favorite recovery environment, you *HAVE TO* flash the latest Sony Open Devices binaries for your device through fastboot. They cannot be distributed in this zip package because you have to accept their EULA. ** Make sure you flash the Sony ODM image to both slots: fastboot flash oem_a SW_binaries_for_Xperia_Android_(blahblah) fastboot flash oem_b SW_binaries_for_Xperia_Android_(blahblah) P.S.: If you get signature verification errors on TWRP, remember to disable package signature verification in the TWRP settings!!!
Click to expand...
Click to collapse
But then, there is also the generic installation guide here:
https://wiki.pixelexperience.org/devices/xqau52/install/
(I'm not going to quote this page because the install instructions is all there is on that page.)
Now the two instructions are quite contradictionary, and I couldn't figure out which one to follow, so I ended up following the part from the changelog that said to flash the Open Devices binaries to both slots (couldn't find the stock ROM but used Emma to clean flash it first), then flashed TWRP unofficial from the XDA device forums (tried both, stock and the other one) and was able to boot into TWRP. Since the device page kind of stopped there, I subsequently flashed the ROM as described on the installation page and got the device corrupt error upon booting the ROM, and the device stopped there. Couldn't get it to work.
Does anyone have any experience with tue installation of this ROM for this phone? I did prefer LOS but am quite eager to give this ROM a try, I just can't stand being unable to use navigation gestures in a normal way with a custom launcher (bad Sony!).
I have something similar but worse. The phone stopped working. It shows red light and it blinks by 30s interval. Can anyone help?
Hi all.
I hope this thread is ok.
I have previously tried to flash a custom rom on my Mi 11. I've followed all the steps but most roms fail due to the file not being recognised in CMD or Powershell. I've ran these as administrator and it still won't work.
One or two of the roms recognised the file & looked like it was going to complete the flash until I got an error saying:
Failed to flash - target API level is 3. Has this happened anyone before?
Also after having to flash a fsastboot stock rom I can no longer install system updates.
If anyone can help, I'd be really appreciative as I'm so frustrated with MiUi. Can't open Gmail attachments, videos won't load on certain apps etc.
Thanks very much.
stuedub said:
Hi all.
I hope this thread is ok.
I have previously tried to flash a custom rom on my Mi 11. I've followed all the steps but most roms fail due to the file not being recognised in CMD or Powershell. I've ran these as administrator and it still won't work.
One or two of the roms recognised the file & looked like it was going to complete the flash until I got an error saying:
Failed to flash - target API level is 3. Has this happened anyone before?
Also after having to flash a fsastboot stock rom I can no longer install system updates.
If anyone can help, I'd be really appreciative as I'm so frustrated with MiUi. Can't open Gmail attachments, videos won't load on certain apps etc.
Thanks very much.
Click to expand...
Click to collapse
The bootloader must be unlocked.
For Aosp rom or Xiaomi EU rom use TWRP https://androidfilehost.com/?w=files&flid=321497
For stock rom use https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
I should have mentioned that my bootloader is unlocked.
If I flash TWRP, can I install a custom ROM? I can't see any mention of TWRP on custom roms, just flashing via fastboot.
stuedub said:
I should have mentioned that my bootloader is unlocked.
If I flash TWRP, can I install a custom ROM? I can't see any mention of TWRP on custom roms, just flashing via fastboot.
Click to expand...
Click to collapse
This version of TWRP for a12 was released yesterday.
Some AOSP roms have their own recovery but you can use this TWRP.
The twrp is just an extension that avoids typing command lines.
Just use the twrp following the instructions of the OP of the rom you want to install.
The start is always the same:
Twrp/wipe/format data type yes/reboot Twrp=CLEAN FLASH
then flash as instructed by the OP.
For requested imgs, gapps etc.
Excellent. Thanks for your help