Database Users

[RECOVERY][M86][UNOFFICIAL] TWRP 3.0 for Meizu PRO5

DISCLAIMER
I'm not responsible for any damage, bootloop, bricked or broken handsets.
Notice
The recovery can't be flashed to the handset with locked bootloader! Unlock it first!
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom and stock (with some remarks) ROMs to your device, repair broken file systems, and root your device.
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Update 29.03.2016
It's alive! First experimental working build published at internal 4pda Russian board.
Download
TWRP 3.0 M86 fastboot flashable image
TWRP 3.0 M86 flashable zip
Stock Recovery flashable zip
Unlocked BL flashable zip
Install
With BL unlocked reboot into fastboot mode and flash:
Code:
fastboot flash recovery TWRP_3.0_m86.img
Cautions
Before flashing stock rom with TWRP replace bootloader file with unlocked one inside rom archive!!!!
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)

JUST IN CASE this is an April fools.... I'll wait ?

Great mate, u've stolen my idea in the end, right ?!
Gooooood work, thank u very much ! Testing wip :highfive:
---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------
Nein, first step doesn't work
Flashing unlocked BL through stock recovery, I get always the same result :
FIRMWARE CORRUPT
Click to expand...
Click to collapse

faust93 said:
Update 01.04.2016 (it is not a joke )
First stable release
Have fixed screen flickering and UI lagging
Click to expand...
Click to collapse
*Working fine
PYCON said:
Nein, first step doesn't work
Click to expand...
Click to collapse
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...

toms157 said:
Didn't we discuss it yesterday ? No official zip signature => not flashable with locked bootloader...
Click to expand...
Click to collapse
Ahahah yes yes but the purpose of BL_UNLOCKED.ZIP is to unlock bootloader. But in order to flash it correctly... we've to have the bootloader already unlocked
Damn it, it's really stupid, right ?

PYCON said:
Damn it, it's really stupid, right ?
Click to expand...
Click to collapse
Filename could lead to confusion, sure... It's needed for this :
Another method is to flash unlocked BL and TWRP zips immediately after flashing stock rom (need testing)"
Click to expand...
Click to collapse
Meanning flash 3 files from custom recovery without rebooting
Anyway this is not a catch-22, leaked beta from tutorial is the entry point

Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...

showofdeth said:
Will this work on a device that was originally the Chinese variant but changed to the international one after editing the proinfo file? I'm really eager to try this but I'd hate to jump in blindly and brick...
Click to expand...
Click to collapse
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked

naboleo said:
ID is only checked while using stock recovery .... Anyway it's safe, i'm in the same case and worked
Click to expand...
Click to collapse
Oh man that's great to hear! Thanks. Bought myself a laptop specifically to get my PRO 5 all TWRP'd up.
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?

showofdeth said:
One last thing. I have updated firmwares many times in the last couple of months with full factory wipes each time, currently on the latest test version. Will the bootloader unlock in the tutorial still work? Meizu can't have patched anything. Right?
Click to expand...
Click to collapse
Never had troubles to downgrade to leaked beta

naboleo said:
Never had troubles to downgrade to leaked beta
Click to expand...
Click to collapse
Brilliant. Thanks a lot. Can't wait to hear people's experiences with this.

mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot

That TWRP works perfectly for me, backup nandroid, restore it, flash ZIP rom and ZIP other ( Xposed, etc ), no problem at all :highfive:
Good job !!! Great, thx !!!

Thank you so much for this!!! could i ask you how you managed to create a recovery for the pro5?

Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
I assume youare still on 5.6.1.19: Thats an error with this version.... put the updatefile manually (in the PC) on the external sd and flash via TWRP... you should later update your modified Pro 5 to 5.1.3.0, the error ist gone then...

Solitario88 said:
mate problem solved..now finally i can go into twrp it's fantastic but there is a problem...when i try to put a update.zip (nodified with unlock bootloader) the pc give me an error: impossible transfer file and the phone reboot
Click to expand...
Click to collapse
Copy UPDATE.ZIP from PC to phone BUT CONNECTING THE PHONE WHEN IT'S OPENED TWRP
MTP mode works great, even u'r on 5.6.1.19 :highfive:

Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!

PYCON said:
Sometimes... Rarely... A strange thing happens :
I go to INSTALL in order to flash a ZIP of something but... NO MEMORY SEEMS TO BE ACCESSIBLE
If I reboot another time into recovery, all my memory contents is perfect and visible... :silly: Really strange !!!
Click to expand...
Click to collapse
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:

cedric3 said:
Have you installed the updated TWRP (20-04-16) : http://xep.8800.org/pro5/
I tried the old (30-03-16), and I noticed some bugs, like flash screen when touching the screen buttons...
Maybe I helped you :laugh:
Click to expand...
Click to collapse
Uh I didn't know that a new version was released... Maybe, I could be. I download it again and try... Thx man ! :highfive:

The last version can't read the micro sd.

Bricked, bootloop tried all I can think of

I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P

maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t

Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...

maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?

v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image

maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?

v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image

I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.

maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.

same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?

mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528

v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"

maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...

5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C

maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...

maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.

DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...

We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.

5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful

so i'm going thru the same thing as OP.
I need help.

Huawei Nova Dload Bootlop

Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.

Noctyk said:
Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.
Click to expand...
Click to collapse
Hello!
Check this post.

#Henkate said:
Hello!
Check this post.
Click to expand...
Click to collapse
Hi! Thank you for the fast reply, I remember that I've tried method 1 already and since it reset my bootloader, it's no longer unlocked. The first thing I did when I realised it was a bootloop I tried to reflash my TWRP as I have a backup but it fails everytime I try to flash anything through fastboot as my bootloader is locked.
I was slightly naive and didn't think it would wipe my TWRP and bootloader back to locked.
What do you recommend I try?

Well, Unlock your Bootloader again.. ^^

Bad2hold said:
Well, Unlock your Bootloader again.. ^^
Click to expand...
Click to collapse
I've fixed the issue now thanks, I forgot to wipe the cache and extra bits after the Dload update thats why it was stuck on the bootloop :silly:
My problem before was I couldnt get the IDs needed for my bootloader unlock code since I couldn't actually check the IDs through settings.

WiFi Won't Toggle After Root Attempt

Hey guys, VERY new to the phone customization game. I gave rooting my ph-1 a shot and it crashed and burned. I tried flashing Magisk with no luck and now my WiFi will not turn on. It is stuck I the off position. This is incredibly frustrating. I tried restoring the phone and nothing seems to be working. Anyone out there able to help?

Silver1212 said:
Hey guys, VERY new to the phone customization game. I gave rooting my ph-1 a shot and it crashed and burned. I tried flashing Magisk with no luck and now my WiFi will not turn on. It is stuck I the off position. This is incredibly frustrating. I tried restoring the phone and nothing seems to be working. Anyone out there able to help?
Click to expand...
Click to collapse
Flash Back to stock zip from Development Section.
You should be good to start experimenting again..
:laugh:

indian84 said:
Flash Back to stock zip from Development Section.
You should be good to start experimenting again..
:laugh:
Click to expand...
Click to collapse
I tried flashing OPM1.180104.166 AFH from @invisiblek (that's the latest 8.1 Oreo) the problem is still there. WiFi Won't toggle on. Should I flash the earliest build? NM181C?

Silver1212 said:
I tried flashing OPM1.180104.166 AFH from @invisiblek (that's the latest 8.1 Oreo) the problem is still there. WiFi Won't toggle on. Should I flash the earliest build? NM181C?
Click to expand...
Click to collapse
Did you do critical flashing unlock?
If you have messed up with the modem, without critical flashing unlock, it would not flash modem partitions

indian84 said:
Did you do critical flashing unlock?
If you have messed up with the modem, without critical flashing unlock, it would not flash modem partitions
Click to expand...
Click to collapse
Are you referring to unlocking the bootloader? If so then yes I did that.

Silver1212 said:
Are you referring to unlocking the bootloader? If so then yes I did that.
Click to expand...
Click to collapse
Nope. Not only bootloader. You have to unlock critical.
Read below.
http://mata.readthedocs.io/en/latest/

Silver1212 said:
Hey guys, VERY new to the phone customization game. I gave rooting my ph-1 a shot and it crashed and burned. I tried flashing Magisk with no luck and now my WiFi will not turn on. It is stuck I the off position. This is incredibly frustrating. I tried restoring the phone and nothing seems to be working. Anyone out there able to help?
Click to expand...
Click to collapse
You have a firmware mismatch...
Because I don't think you can boot the device into the OS with the TWRP kernel anymore...
Which I'm pretty sure means you missed unlock critical...
And didn't read the output from the terminal window after running the flashall

rignfool said:
You have a firmware mismatch...
Because I don't think you can boot the device into the OS with the TWRP kernel anymore...
Which I'm pretty sure means you missed unlock critical...
And didn't read the output from the terminal window after running the flashall
Click to expand...
Click to collapse
Is there a way to bring this thing back to original bare bones stock? Are there tutorials around for that?

Silver1212 said:
Is there a way to bring this thing back to original bare bones stock? Are there tutorials around for that?
Click to expand...
Click to collapse
Just like you unlocked the bootloader, you now need unlock_critical.
Then go through the flash procedure.

Silver1212 said:
Is there a way to bring this thing back to original bare bones stock? Are there tutorials around for that?
Click to expand...
Click to collapse
1) boot to bootloader
2) fastboot flashing unlock
3) fastboot flashing unlock_critical
4) get the latest rom 9OPM1.180104.166 AFH from @invisiblek) and use flash all.

I had this same issue when flashing the wrong version boot image. Downloaded correct boot image, flashed and then flashed Magisk and fixed her right up.

xorwin said:
1) boot to bootloader
2) fastboot flashing unlock
3) fastboot flashing unlock_critical
4) get the latest rom 9OPM1.180104.166 AFH from @invisiblek) and use flash all.
Click to expand...
Click to collapse
Okay so this is the current situation:
I typed in:
1) fastboot flashing unlock - everything looked as it should.
2) fastboot flashing unlock_critical - the script ran and then said: FAILED (remote : device already : unlocked!)
3) I went forward with the flash-all-WIPE and the issue is still not corrected. I honestly don't know what else to do here.
I wholeheartedly appreciate all the help so far! Id like to figure this out!

GOT IT! WOOOO! Thanks guys!

Silver1212 said:
GOT IT! WOOOO! Thanks guys!
Click to expand...
Click to collapse
Hi Silver1212, Please can you advice how did you fix this issue? I did the following as you did too:
1) flashboot flashing unlock
2) flashboot flashing unlock_critical
3) bash flashall.sh
It completed with no errors, but wifi still won't turn on
What did you have to do to fix this problem?

zenga_82 said:
Hi Silver1212, Please can you advice how did you fix this issue? I did the following as you did too:
1) flashboot flashing unlock
2) flashboot flashing unlock_critical
3) bash flashall.sh
It completed with no errors, but wifi still won't turn on
What did you have to do to fix this problem?
Click to expand...
Click to collapse
Use the flashall wipe

zenga_82 said:
Hi Silver1212, Please can you advice how did you fix this issue? I did the following as you did too:
1) flashboot flashing unlock
2) flashboot flashing unlock_critical
3) bash flashall.sh
It completed with no errors, but wifi still won't turn on
What did you have to do to fix this problem?
Click to expand...
Click to collapse
Do a reset of all your network settings. It fixed it for me some time back earlier this year

[Guide] ROOT OP8T OOS (A13)

Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13 and F.15
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot" ~name of img~
Profit!
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com

Thank's

BobbyLynn said:
Here's the patched boot.img for OnePlus 8T Android 13 KB2005_11_F.13
Bootloader must be unlocked
(Have the img on your PC)
Instructions:
1: Reboot to bootloader "adb reboot bootloader"
2: Run CMD "fastboot flash boot magisk_patched-25200_575Sf.img"
You're now rooted.
I've also attached the stock boot.img just in case anyone wants it.
Boot - Google Drive
drive.google.com
Click to expand...
Click to collapse
what if there is ota update?

MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.

MevishL said:
what if there is ota update?
Click to expand...
Click to collapse
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/

BobbyLynn said:
I highly doubt there'll be another OTA until next month. Check with the developer of the unofficial orange fox recovery, he'll most likely release a new version for A13. If not, I'll pull the boot.img and patch it again and post it here.
Click to expand...
Click to collapse
okay thx , much appreciated

BobbyLynn said:
Nevermind he's already released a version for A13. Here it is
Thread '[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [13-Nov-2022]' https://forum.xda-developers.com/t/...ry-project-oneplus-8t-9r-13-nov-2022.4391139/
Click to expand...
Click to collapse
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?

MevishL said:
what if i bricked my phone , how do i flash stock file. do i need to download it in oxygen updater , and then?
Click to expand...
Click to collapse
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.

BobbyLynn said:
Lol don't tell me you've bricked it!!! You can probably flash the stock boot.img and that might fix it. Otherwise you'll have to use the msm tool to reflash the firmware.
Click to expand...
Click to collapse
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping

MevishL said:
no i didn't ! i'm just scared i might brick it cuz oneplus is harder to deal with than my previous phones . thnks for helping
Click to expand...
Click to collapse
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool

BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
BobbyLynn said:
Well if you're worried about bricking it then before you start making modifications, be sure to have the latest msm for it on your PC, and also take a full backup using Orange Fox recovery, and also have the stock boot.img on your PC. And if anything goes wrong just flash the stock boot.img. And if that doesn't fix it then restore the backup, and if that still doesn't work then you'll have to do a complete restore using a msm tool
Click to expand...
Click to collapse
now u made it clear in my head , thx for all

MevishL said:
now u made it clear in my head , thx for all
Click to expand...
Click to collapse
No problem. If you run into any problems just let me know and I'll do what I can to figure out the simplest solution

I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks

Can these instructions be used for the KB2007?

kevinco1 said:
Can these instructions be used for the KB2007?
Click to expand...
Click to collapse
If it's Android 13 11_F.13 then yes. But Orange Fox has a working recovery for A13 on our phone. So you can always flash Magisk that way if you want

MrOnizuka said:
I flash this boot.img and work like a charm easy root. Don't forget to post boot for next updates for KB2005. Thanks
Click to expand...
Click to collapse
As long as I have this phone I'll continue to post the patched boot.img after each update

BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.

BobbyLynn said:
As long as I have this phone I'll continue to post the patched boot.img after each update
Click to expand...
Click to collapse
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?

Marduc said:
It is your time to shine again, good sir F.15 is upon us!
Thank you, kindly.
Click to expand...
Click to collapse
Thanks for reminding me. I'll upload the new boot.img shortly

MevishL said:
i have kb2005 but when i install ota update f.15 , it says installation failed at 26% . before that , i fastboot flashed stock boot.img. What should i do ?
Click to expand...
Click to collapse
You did flash unmodified boot.img before trying to update? Well, honestly idk why it won't install. Maybe you should try a different method of installing the update, like manually installing it