Database Info

Acer Predator 8 TWRP 3.0.2

TWRP 3.0.2 for Acer Predator 8 ported by Ruben. - If you like my work please donate here, it will also give me a boost to make more things for this device : https://www.paypal.me/RubenCraveiro
----------- -----------
IMPORTANT NOTE ABOUT ROOTING AND UNLOCKING BOOTLOADER:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting. Unlocking bootloader will delete all your data, so please make a backup first. Thank you.
----------- -----------
CREDITS
And also, before anything i would like to say thanks to @arjaylzo for telling me the name of a device with TWRP which helped making this update possible.
REQUIREMENTS
1- Fastboot/ADB Drivers and ADB folder
For drivers: http://adbdriver.com - Download ADB Driver Installer (universal) from the website, extract it, connect device it should detect device(if not, enable USB Debugging and reconnect), and press install, it should install drivers.
For ADB Folder: download this and extract to your main drive(C:/): https://goo.gl/ZTrfBb
2- Unlocked Bootloader (you need requirement 1 to do this)
Instructions for Unlocking bootloader: Go on settings, about device, press build version several times till it says your a developer, go back to settings, press Developer Options, and enable OEM Unlocking. Power off, then press at same time Power and Vol+ button, then connect to pc and open a cmd and write cd c:\\adb and write fastboot oem unlock, then accept the prompt it will give on tablet, and follow the rest of the steps.
----------- -----------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
----------- -----------
BUGS:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the device name seems to change (which means that on /TWRP/BACKUPS/devicename/backupsinside/ changes every reboot so you have to go get the backup inside the old devicename folder and put on the new devicename folder).
----------- ADITIONAL NOTES -----------
Im leaving an unsecured boot image because system seems not want to boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
----------- -----------
Steps TO INSTALL TWRP AND ROOT
1. Download and extract the files: https://drive.google.com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view?usp=drivesdk
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip
----------- -----------
Acer Predator 8 Support website(sourcecode, manuals, drivers, stockrom):

http://www.acer.com/ac/en/US/content/support-product/6400?b=1
----------- -----------
SCREENSHOTS:
http://imgur.com/s7CgJPR

I stuck at step 4.
is this the directory where fastboot.exe is located -> C:\adb... I have 4 files there and 1 of them is named fastboot.
Also the files i downloaded and extracted from step 1 , do i need to put them in my device or they need to stay on my pc.

goleoldark said:
I stuck at step 4.
is this the directory where fastboot.exe is located -> C:\adb... I have 4 files there and 1 of them is named fastboot.
Also the files i downloaded and extracted from step 1 , do i need to put them in my device or they need to stay on my pc.
Click to expand...
Click to collapse
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...

Ruben Craveiro said:
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...
Click to expand...
Click to collapse
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????

goleoldark said:
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????
Click to expand...
Click to collapse
make sure you didnt put a folder inside the adb folder instead of the actual file and make sure your writing the right name of the file..

goleoldark said:
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????
Click to expand...
Click to collapse
also its not unsecboot, the name i added on this thread was just so it would be faster, the name is unsecuredboot.img and not unsecboot.img i guess ill have to edit that in order for people following the tutorial by line dont make these mistakes..

how do i flash the stock rom came from Acer Predator 8 Product Support Page.
can i just flash this Android 5.1 Lollipop Image via TWRP???
TIA

xdadevelopers13 said:
how do i flash the stock rom came from Acer Predator 8 Product Support Page.
can i just flash this Android 5.1 Lollipop Image via TWRP???
TIA
Click to expand...
Click to collapse
yes

thanks. will i have to flash the stockboot.img and P8AcerRecovery.img via fastboot?
tried flashing the stock rom via TWRP but to no avail.
still cant pass the boot logo

xdadevelopers13 said:
thanks. will i have to flash the stockboot.img and P8AcerRecovery.img via fastboot?
tried flashing the stock rom via TWRP but to no avail.
still cant pass the boot logo
Click to expand...
Click to collapse
If you flash stock rom, i think you have to reinstall stock recovery, the rom itself already brings stock boot.. after flashing stock recovery it should boot since no modifications have happend

Wow good job! Now i have a recovery where i can flash my custom rom for the Predator 8.

p8tgames said:
Wow good job! Now i have a recovery where i can flash my custom rom for the Predator 8.
Click to expand...
Click to collapse
no custom roms yet

How to enter the command ?
Hi i am not so sure how to execute those info in my head and act on it so can anyone teach me ? how to root my Predator 8 GT-810 Android 5.1
i saw the instruction i dk how do i Unlock Bootloader (Fastboot) i search all over google and i dont really got the solution to the question so anyone can teach me ? and "4. Open up command prompt and navigate to the directory where fastboot.exe is located." do i extract the whole file i downloaded into my Acer predator 8 or ?... im stupid sorry ...

ZaineJJ said:
Hi i am not so sure how to execute those info in my head and act on it so can anyone teach me ? how to root my Predator 8 GT-810 Android 5.1
i saw the instruction i dk how do i Unlock Bootloader (Fastboot) i search all over google and i dont really got the solution to the question so anyone can teach me ? and "4. Open up command prompt and navigate to the directory where fastboot.exe is located." do i extract the whole file i downloaded into my Acer predator 8 or ?... im stupid sorry ...
Click to expand...
Click to collapse
On step 4 You need the fastboot files, (adb & fastboot) just search how to install adb and fastboot drivers, choose the directory where to install them and place the needed files inside that folder and open a command prompt on that folder so you can flash the files.

Ruben Craveiro said:
On step 4 You need the fastboot files, (adb & fastboot) just search how to install adb and fastboot drivers, choose the directory where to install them and place the needed files inside that folder and open a command prompt on that folder so you can flash the files.
Click to expand...
Click to collapse
ir I tried finding how to install fastboot driver on Google all showed me downloads links must do survey or download or purchase item to unlock the download files ... So I don't trust it so I kept searching "how to unlock fastboot Acer predator 8"
So for ADB I can search on Google and install it on my tablet ?

ZaineJJ said:
ir I tried finding how to install fastboot driver on Google all showed me downloads links must do survey or download or purchase item to unlock the download files ... So I don't trust it so I kept searching "how to unlock fastboot Acer predator 8"
So for ADB I can search on Google and install it on my tablet ?
Click to expand...
Click to collapse
no, Search how to unlock bootloader, it should show the method that works for most devices and give necessary drivers..

Ruben Craveiro said:
no, Search how to unlock bootloader, it should show the method that works for most devices and give necessary drivers..
Click to expand...
Click to collapse
http://gsmusbdriver.com/acer-predator-8
Does this work ?
Or
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/

ZaineJJ said:
http://gsmusbdriver.com/acer-predator-8
Does this work ?
Or
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
Click to expand...
Click to collapse
Yes, and after you unlock the bootloader, you put the necessary files in adb folder and flash them according to the stepts

Ruben Craveiro said:
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...
Click to expand...
Click to collapse
Hi Ruben Craveiro is this the correct way ? i plugin usb cable into Predator 8 but it says its waiting for device is it the correct way ? after typing those Commands i go over to recovery mode to install SU from there then restart and its rooted ?

ZaineJJ said:
Hi Ruben Craveiro is this the correct way ? i plugin usb cable into Predator 8 but it says its waiting for device is it the correct way ? after typing those Commands i go over to recovery mode to install SU from there then restart and its rooted ?
Click to expand...
Click to collapse
That means adb drivers arent corrently installed, but i can see you have the folder with adb, all you have to now is download this(drivers): http://dl.adbdriver.com/upload/adbdriver.zip
Extract and open the software eith the tablet plugged in, it should tell of drivers is installer properly or not, and if not you can install, after installing it should work on the cmd the commands..

[Tutorial]Rooting Coolpad Note 5 [TWRP][ 6.0.1 & 7.0 ]

ROOT COOLPAD NOTE 5 & FLASH TWRP RECOVERY
New Guide - Simplified:
DOWNLOADS
[Don't worry about file name has 'Note5Lite' it will work for both]
Get necessary files from this zip - click here
TWRP RECOVERY : https://forum.xda-developers.com/an...fficial-twrp-recovery-coolpad-note-5-t3637568
Follow these steps to gain temporary root and update magisk app to make it permanent!!
CONNECT YOUR COOLPAD DEVICE TO PC
ALLOW USB DEBUGGING IN DEVELOPER SETTINGS:
NOW RUN CMD.BAT
COPY AND PASTE THESE CODES ONE BY ONE,
adb wait-for-device
Click to expand...
Click to collapse
adb install magisksu.apk
Click to expand...
Click to collapse
adb install rootcheck.apk
Click to expand...
Click to collapse
adb install root.apk
Click to expand...
Click to collapse
adb shell monkey -p com.yulong.openrp -v 500
Click to expand...
Click to collapse
adb reboot
Click to expand...
Click to collapse
WAIT TILL THE DEVICE COMES TO BOOT ANIMATION
OPEN MAGISK APP & COPY AND PASTE THIS CODE :
adb shell mount -o remount,rw /system
Click to expand...
Click to collapse
NOW :
adb push magisk /system/bin
Click to expand...
Click to collapse
IF SUCCES, TYPE:
adb shell magisk su
Click to expand...
Click to collapse
RUN THIS COMMAND AFTER EVERY REBOOT TO AGAIN GET ROOT ;
adb shell magisk su
Click to expand...
Click to collapse
OR
update magisk app to make it permanent!!
<end>
-------------------------------
Old Guide :
There are Two Main Steps:
1. Getting Temporary Root
2. Flashing TWRP and Rooting Permanently.
PROCEDURE:
Note: I do not own any of rooting file. Those all are available on chinease site/host.
Tested On Stock Nougat V226
Tested On Stock Marshmallow V35
Limitations:
Code:
this is not permanent root, bcoz of locked bootloader. Root permission reset whenever your phone reboot. To gain
root access again you need to adb installed on PC and run root app from adb.
Download:
-Download Root Package from here: >>
(Download these two )
1.
http://www.datafilehost.com/d/200f5056
2.
https://drive.google.com/file/d/0B3wvScQytk0ddmRQc0ZyT3BZR1U/view?usp=drivesdk
3. Download TWRP :
[Please Hit Thanks Button]
https://forum.xda-developers.com/an...fficial-twrp-recovery-coolpad-note-5-t3637568
Follow These Steps:
-Enable USB debugging Option from Developer menu
-Install Some Apk from root.zip file
-Now open "openRP" app
-You see just gray screen with "openpr" text.
-Connect phone to PC (Transfer file mode), open cmd.bat file from adbfolder which you downloaded.
-Run command adb reboot
-Now you see Factory mode text appear on boot screen. No problem
-Now your Note 5 is successfully rooted
-Open cmd.bat file again. And run
Code:
adb shell
You see "#" sign, that means Phone is rooted.
-Now we will install superuser.
-Open cmd.bat file, and type
Code:
adb remount
adb push magisk /system/bin
adb shell
magisk su
mount -o ro,remount /system
-Open Magisk Manager app that you installed from apk folder.
If you see below screen that means you successfull installed supersu
-Now lets check that Note 5 is rooted or not with Root checker.
-Open Root checker app. and Grant permission for Root check.
-And Finally wait is over
When you reboot phone you need to gain root access again.
so open cmd.bat and type
Code:
adb shell
magisk su
How to remove Root Permission and Factory mode text.
-Open cmd.bat and type
Code:
adb remount
adb shell audioelectric start
adb shell audioelectric setDM
adb shell reboot
Note:Whenever you open open RP app your phone will switch to factory mode.
2. FLASHING TWRP AND ROOTING PERMANENTLY:
Code:
First Download Rashr App From Google PlayStore
Then Open Rashr App And Give Root Access
Then Select Recovery Option As Shown In Screenshot
Now Select Recovery File
After Pop Up come Like Screenshot Click On Yes
Now After Flashing Recovery It Ask You To Boot In Recovery Select Yes
Now You Successfully Boot In Twrp Recovery
Now Swipe Allow Modification Option After Allowing Go Back To Main Twrp Recovery
Then Select Install option
Now Go Where You Store Super Su Zip File And Select
Now Swipe To Install Super Su
Now Wait For Installation Finished Then Select Reboot Option
Now It Ask To Install Twrp App Select
Do Not Install Option
And Reboot Your Phone
Now Open Root checker App And Check
Congratulations Now Your Phone Permanently Rooted
SPECIAL THANKS :
TONYSTARK
AMIT KUMAR SINGH
KuberSharma ( me )
#TeamZero
#Coolpad
And those who tested this method and my recovery THANKS.
PS: I DON'T OWN THIS DEVICE
Detailed Guide with Proper Images : SOURCE
HIT THANKS TO MOTIVATE ME. :good:​

Reserved
Guide by SuperModerator at CPForums : http://www.coolpadforums.com/forum.php?mod=viewthread&tid=24998
Video Tutorial ( Thanks to Karthik SB ) :
https://youtu.be/Z99LYY30CK8
F.A.Q
Q: I tried the method, didn't work.
A: Well try again, it works.
Q: I bricked my phone, it is stuck at the logo.
A: Flash Stock Firmware via Fastboot or Flash Tool.
Q: Is the bootloader unlocked?
A: No, As on 19th November 2017 - Bootloader is still locked and no way to open it.
Q: Will i still get warranty?
A: Yes only if you flash Stock ROM via Flash tool again.
Coolpad Note 5 Telegram Group :
https://telegram.me/coolpadnote5sd

Good work bro.
TeamZero rocks

At last some dev program initiated ...thanks dev @kuberrocks96

Please List the total commands properly.
I am unable to find the commands to enter.
In cmd when i entered the command "adb reboot" it is showing that there is no recognition of adb ....is it the drivers problem ?

narenderrao said:
Please List the total commands properly.
I am unable to find the commands to enter.
In cmd when i entered the command "adb reboot" it is showing that there is no recognition of adb ....is it the drivers problem ?
Click to expand...
Click to collapse
Install Driver properly

U have done a great job but the only request to u is please post a video tutorial of rooting coolpad note 5 @ kuberrocks96

Did Anybody try to root with this above procedure ?

where is su zip file?
where is the su zip file to flash from twrp
---------- Post added at 10:37 AM ---------- Previous post was at 10:27 AM ----------
after doing twrp, my phone is stuck at the power on screen. i think it is bricked. please help

please help
My phone is totally bricked and can only get into twrp recovery mode. it cannot even open bootloader so that i can flash custom firmware. i am doomed

icebreaker18 said:
My phone is totally bricked and can only get into twrp recovery mode. it cannot even open bootloader so that i can flash custom firmware. i am doomed
Click to expand...
Click to collapse
If you can access TWRP, do reboot to bootloader and flash Stock Rom, this method was tested Super Moderator of Coolpad Forums and it worked perfectly.
I don't know why it didn't work for you.

Hi it works in coolpad canvas 3636a.. But only is temporary.. I have not found twrp to coolpad canvas 3636a.. I don't know what twrp put it

After use above procedure to root coolpad note 5
The bug is usb debugging is not work
And when enable usb debugging and media transfer for transferring data isn't work whlie usb debugging is disabled..

Here is the Video Tutorial by Kathik SB :
https://youtu.be/Z99LYY30CK8

Thanks,,,,,,any custom rom for coolpad note 5

harichandra said:
Thanks,,,,,,any custom rom for coolpad note 5
Click to expand...
Click to collapse
None till now

Thread updated - simplified it and also added FAQ.

Hi my window 8 cmd magisk sush faile and Dirtrory how to slove problem

Hi thanks for this ..it worked for me :laugh: just a little doubt to make this root permanent ,how to update magisk app ? Thanks for your help

rooting prblm
i cant root permannently. i rooted my device temporary .please help me

How to lock bootloader after it was unlocked

This method was tested on P2a42 4/32 and P2c72 4/64 (both smartphones has 251 firmware installed).
Please, pay attention and read carefully:
You have a risk that P2 will go from EDL (9008) mode to 900E while you make a reconnect of connected to PC phone.
If you haven't successfully returned it by yourself into 9008 state - the only way is repair service. See details on 4Th step below the short instruction.
ADB and EDL (9008) drivers have to be pre-installed on your PC.​
For those, who faced with flashing firmware, gaining root, working with ADB and Fastboot commands, EDL mode on P2 and so on, here is the short instruction:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Wipe userdata via Fastboot: fastboot erase userdata .
4. P2 is connected to PC in EDL (9008) mode, make a reset via launching blank-flash.bat from blankflash folder.
5. Flash 251 firmware as for unlocked device using START script .
6. Choose region ( ####682# ) and then make a reset ( ####7777# ).
7. That's all folks! Now you have locked P2 with a region that you want. So you can set the phone as you always do.
Below there is the same instruction, but detailed and with pictures.
From Unlocked to Locked state on P2.
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
On this step you can use Total Commander with ADB plugin (YouTube will help you, there are tons of videos about it).
I prefer not to use PC, if there is another way.
What I've done:
Android Terminal Emulator installed and launched.
Gave it permission to root access.
In Emulator typed su and pressed Enter.
Sign $ will turned to # , which means that further commands will be under root access.
Type command: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp and press Enter.
If all done right, so you will see: Screenshot 1.
View attachment 4358523
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
Turn off P2.
Boot it into Fastboot mode - press and hold two buttons (Power And Volume -), on P2 screen you will see Fastboot mode: Screenshot 2.
View attachment 4358524
Connect P2 to PC (it is recommended not to use card readers; connect to USB which are situated on motherboard for PC, there is an exception for notebook (laptop)).
Press right mouse button and hold Shift on ADB folder, which is placed in the root of Disc C (С:\), choose "Open command line" - a CMD window will appear on the screen of PC.
In CMD window type fastboot erase secinfo and press Enter.
If all done properly, all drivers set properly, on the screen of your PC you will see: Screenshot 3.
View attachment 4358525
3. Wipe userdata via Fastboot: fastboot erase userdata .
Continue in CMD window. Type fastboot erase userdata and press Enter.
On the screen of your PC you will see: Screenshot 4.
View attachment 4358526
Close CMD window on PC.
4. P2 connected to PC in EDL (9008) mode, make a reset via launching blank-flash.bat from blankflash folder.
blankflash folder must be placed in the root of Disc C (С:\).
On PC you must hold opened window of "Device manager" with opened string "Ports (COM and LPT)".
Your P2 must be connected to PC in EDL (9008) mode.
Use P2 very carefully without further re-connections, because there is a high risk, that P2 can go to 900E mode.
P2 connected to PC, press and hold all three buttons (Power and both Volume).
Hold buttons (phone will be rebooted twice) until you will see "Qualcomm HS-USB QDLoader9008 (COM12)" in opened window of device manager in string "Ports (COM and LPT)".
You might get another number of port (not only 12Th), it doesn't matter.
The main aim is "Qualcomm HS-USB QDLoader9008..." string in device manager.
Please, be very careful, because even little re-press of button or re-connect of cable will send your P2 to 900E mode with constant vibration and blue LED.
Try to restore phone to EDL (9008) mode by pressing and holding three buttons.
If you have no luck (from 900E to EDL) - congrats, you've got a brick.
From this point you should ask for help in repair service.
Going further, if all is going right and P2 connected to PC in EDL (9008) mode.
In device manager window on PC you will see this: Screenshot 5.
View attachment 4358527
From blankflash folder launch (double click of left mouse button) blank-flash.bat: Screenshot 6.
View attachment 4358528
You will see a CMD window which shows you a reset process of your P2.
If all done properly (without any "ERROR False"), you will see: Screenshot 7.
View attachment 4358529
In the end of reset your P2 will automatically boots from EDL (9008) mode to Fastboot mode: Screenshot 8.
View attachment 4358530
I suppose that there is no need to speak about 5Th and 6Th steps, because it is a basic knowledge, that you should know, when you are going to lock bootloader on P2.
Important notice.
You have to use original or other cable that has been already successfully used in Fastboot mode with your Р2.
The simple way to check cable is to type fastboot oem config in CMD and look what info it will give to you.
For those, who have already locked bootloader, it is strictly recommended not to flash stock ROM via flashall.bat.
For flashing stock you should use method for unlocked device, so you need to use START script.
All will go right if you will flash via flashall.bat after bootloader was locked, without any errors, Р2 will be booted as usual - Wi-Fi, SIM-cards (with names of operators), IMEI's and Serial number - all will be OK ...
But!
Calling, SMS and Mobile data will not work, you will see crosses on antenna icons in Status bar (in the string of modem firmware in "About" you will see "X" instead of "R" (Screenshot 9, 10) as it was, modems region will be defective).
View attachment 4358708View attachment 4358709
You can switch on/of Mobile data from Notification drawer, but there will be no connection, only Wi-Fi will work.
I am searching for solution of this problem.
As soon as it will be ready, it will be posted here. See post #2.
ADB folder (download, unzip) - View attachment ADB.rar
blankflash folder (download, unzip) - View attachment blankflash.rar
All thanks addresses to https://forum.xda-developers.com/member.php?u=279908.
I've just translated it from Russian to English from 4PDA site
Good luck and have a nice day!
Remember ...backup rules.

Solution.
Your phone must be unlocked and you must already have TWRP-backups of modem (NON-HLOS) and EFS from Р2.
1. Unlock bootloader.
2. Install TWRP.
3. Restore modem (NON-HLOS) and EFS in TWRP - you will get working modem, but there might be no sound in telephony.
4. You should install modem image via TWRP for Android 6 or 7 to get back to a working telephony (for additional instructions see post #3).
Later, if there will be a method which will work without TWRP-backups and possibly without unlock of bootloader, it will be posted here.
Modem download links:
Android 6 (062): http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=75313
Android 7 (244): http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=75314

How to restore a modem.
Important notice - you need to use modem with the same OS version which is installed on your phone.
Look here:
Firmware 062 - this is Android 6.
Firmware 233 and higher - this is Android 7.
Flash this:
For Android 6 - Modem_P2_062_ROW.zip
For Android 7 - Modem_P2_244_ROW.zip
Flash modem via TWRP:
1. Download zip for OS that you need (do not unzip it, rename or choose extension).
2. Copy to the phone memory (or to external micro-SD card).
3. Boot to TWRP and act as it is shown on the screenshots ...
View attachment 4358546View attachment 4358547View attachment 4358548View attachment 4358549View attachment 4358550

EDIT: did the first step wrong, now it's Locked

Do you have data and calls working?
Enviado desde mi Lenovo P2a42 mediante Tapatalk

Is the warranty back if the bootloader is relocked?

Danoz88 said:
Is the warranty back if the bootloader is relocked?
Click to expand...
Click to collapse
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.

sergsinger said:
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.
Click to expand...
Click to collapse
Thanks I thought the same. But in this case why should we go back to locked bootloader

Danoz88 said:
why should we go back to locked bootloader
Click to expand...
Click to collapse
It is personal decision. May be someone don't like to see "UNLOCKED" state.

sergsinger said:
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.
Click to expand...
Click to collapse
I agree... But there are some reports on this forum suggesting otherwise.
One common report is the replacement of motherboard for bricked devices, that too for unlocked devices.

Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked

jitkr said:
Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked
Click to expand...
Click to collapse
Oh great. Is this all it have to be done or followed by previous page? Any problems or things to be aware of?

jitkr said:
Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked
Click to expand...
Click to collapse
I did not understand Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp

Shuvamilu said:
I did not understand Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp
Click to expand...
Click to collapse
First post, first picture.

Danoz88 said:
First post, first picture.
Click to expand...
Click to collapse
I don't understand

Shuvamilu said:
I don't understand
Click to expand...
Click to collapse
Every step which jitkr enumerated is explained by sergsinger who made this guide.
Read the complete first post of sergsinger. Also click on show content for full explanation.
If you farther understand nothing please clearly explain what exactly.
"I don't understand" does not help in any way.
sergsinger said:
From Unlocked to Locked state on P2.
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
On this step you can use Total Commander with ADB plugin (YouTube will help you, there are tons of videos about it).
I prefer not to use PC, if there is another way.
What I've done:
Android Terminal Emulator installed and launched.
Gave it permission to root access.
In Emulator typed su and pressed Enter.
Sign $ will turned to # , which means that further commands will be under root access.
Type command: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp and press Enter.
If all done right, so you will see: Screenshot 1.
View attachment 4358523
Click to expand...
Click to collapse

Danoz88 said:
Every step which jitkr enumerated is explained by sergsinger who made this guide.
Read the complete first post of sergsinger. Also click on show content for full explanation.
If you farther understand nothing please clearly explain what exactly.
"I don't understand" does not help in any way.
Click to expand...
Click to collapse
Next process

If i unlcok bootloader, still recive system updates?

tapunger said:
If i unlcok bootloader, still recive system updates?
Click to expand...
Click to collapse
Yes, as long as you are on stock rom.

I lost my signal forever when I did a nandroid backup from another P2. I've tried it all, but nothing seems to work when it comes to restoring it.
I'm a bit confused by the first posts. OP talks about locking the bootloader and post #2 and #3 say you have to be unlocked to restore the modem? I'd have thought you wanted to lock it in order to flash the modem.

Twrp + magisk on Oreo 8.1 from Windows

If you are on the OTA Oreo 8.1 and dont have root, here's how to do so:
First request: Anyone that knows someone that can help get us WFD (Wireless Display Casting) enabled that would be very helpful. If you edit build.prop you can get it to show wireless displays in the System/Connected Devices/Cast but force reboots for me when I try connecting to my HP Lapdock
Now to TWRP/MAGISK
Make sure you are on 8.1, Android debugging is enabled under developer options and bootloader unlocked (Warning if you're not when you do this it wipes data).
Download TWRP.img & TWRP.zip from https://dl.twrp.me/cheryl
Download the Magisk 16.3 from here: https://github.com/topjohnwu/Magisk/releases/download/v16.3/Magisk-v16.3.zip (SuperSU will not work on 8.1 so magisk is your only option)
Download latest Platform tools from Google here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Windows: In file explorer copy the twrp-installer-3.2.1-0-cheryl.zip to the sdcard of the Razer Phone
Windows: In file explorer copy the Magisk-v16.3.zip to the sdcard of the Razer Phone
Windows: Extract platform tools to any folder
Windows: Open a command prompt window at that directory
Windows: adb reboot bootloader
Windows: fastboot boot twrp-3.2.1-0-cheryl.img (This will boot to twrp without flashing) (DONT CLOSE, need it in a few minutes)
Razer Phone: Once in TWRP install zip twrp-installer-3.2.1-0-cheryl.zip then reboot to system after complete.
Windows: Once the Razer Phone has booted back up, go back to the command prompt window
Windows: Adb reboot recovery
Razer Phone: Once in TWRP install zip Magisk-v16.3.zip then reboot to system
All should be good, have not found any issues yet
I take no credit for any files in above tutorial, give credit where credit is due, donate a beer to those guys.
TWRP credit TWRP Team (https://twrp.me/)
Platform tools credit Google (Watch their ads on Youtube?)
Magisk credit Magisk team (https://github.com/topjohnwu)

It's wornking fine so far. Thanks

Thanks, it works.

Wow that was far easier than before thanks

Hm for me it doesn't work at this step: Windows: fastboot boot twrp-3.2.1-0-cheryl.img
It's just saying "Waiting for device"
Sideloading 8.1 and unlocking went smooth, debugging is enabled

SeriousFlash said:
Hm for me it doesn't work at this step: Windows: fastboot boot twrp-3.2.1-0-cheryl.img
It's just saying "Waiting for device"
Sideloading 8.1 and unlocking went smooth, debugging is enabled
Click to expand...
Click to collapse
I had the same problem, make sure the ADB interface driver is installed under device manager again as i think it clears it after windows reboot.

Had to manually edit it while unlocking the bootloader and it stayed on ADB bootloader interface when I had it reboot to bootloader again.
I'll try again tomorrow
Fixed the "waiting for device" "error" by selecting the older Android Bootloader Interface driver.
Now everything worked and my device is rooted!
Nice guide.

thanks for the quick and dirty guide, worked perfectly

Wondering if I'm missing something. Getting the error "FAILED (remote: BootCMD is not allowed in Lock State)" when attempting to boot the twrp image.
I have USB Debugging and OEM unlocking enabled.
PS: Found out the hard way, don't use the provided USB-C cable that came with your Razer phone, USB-A to USB-C cable recommended.

After installing twrp-installer-3.2.1-0-cheryl.zip mobile booting into TWRP only , can't boot into System!!

Installed the zip and Magisk Manager hangs and crashes. Anyone know what this could be?

Is that work without using boot.img file??

DarkestSpawn said:
If you are on the OTA Oreo 8.1 and dont have root, here's how to do so:
First request: Anyone that knows someone that can help get us WFD (Wireless Display Casting) enabled that would be very helpful. If you edit build.prop you can get it to show wireless displays in the System/Connected Devices/Cast but force reboots for me when I try connecting to my HP Lapdock
Now to TWRP/MAGISK
Make sure you are on 8.1, Android debugging is enabled under developer options and bootloader unlocked (Warning if you're not when you do this it wipes data).
Download TWRP.img & TWRP.zip from https://dl.twrp.me/cheryl
Download the Magisk 16.3 from here: https://github.com/topjohnwu/Magisk/releases/download/v16.3/Magisk-v16.3.zip (SuperSU will not work on 8.1 so magisk is your only option)
Download latest Platform tools from Google here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Windows: In file explorer copy the twrp-installer-3.2.1-0-cheryl.zip to the sdcard of the Razer Phone
Windows: In file explorer copy the Magisk-v16.3.zip to the sdcard of the Razer Phone
Windows: Extract platform tools to any folder
Windows: Open a command prompt window at that directory
Windows: adb reboot bootloader
Windows: fastboot boot twrp-3.2.1-0-cheryl.img (This will boot to twrp without flashing) (DONT CLOSE, need it in a few minutes)
Razer Phone: Once in TWRP install zip twrp-installer-3.2.1-0-cheryl.zip then reboot to system after complete.
Windows: Once the Razer Phone has booted back up, go back to the command prompt window
Windows: Adb reboot recovery
Razer Phone: Once in TWRP install zip Magisk-v16.3.zip then reboot to system
All should be good, have not found any issues yet
I take no credit for any files in above tutorial, give credit where credit is due, donate a beer to those guys.
TWRP credit TWRP Team (https://twrp.me/)
Platform tools credit Google (Watch their ads on Youtube?)
Magisk credit Magisk team (https://github.com/topjohnwu)
Click to expand...
Click to collapse
so i did this and here is my only question. Does flashing twrp and magisk inside twrp, install them into both slot a and b? or no. if no then is there a need to manually switch slots and reflash magisk for example?

iliais347 said:
so i did this and here is my only question. Does flashing twrp and magisk inside twrp, install them into both slot a and b? or no. if no then is there a need to manually switch slots and reflash magisk for example?
Click to expand...
Click to collapse
If memory serves I only flashed to the active Slot.

DarkestSpawn said:
If memory serves I only flashed to the active Slot.
Click to expand...
Click to collapse
I ser

Does this method cause a facotry reset?
This seems alot easier than the other methods.

ItzMar said:
Does this method cause a facotry reset?
This seems alot easier than the other methods.
Click to expand...
Click to collapse
It's that easy because of Oreo and the stuff that comes with it. If your bootloader is already unlocked it won't need a factory reset but if not unlocking your bootloader will erase all data on the phone.

Is it best to do with a SD card in the phone or can you do it without?

So doing this without an SD Card at the mo and I get the waiting on device when trying to do fastboot flash boot twrp-3.2.1-0-cheryl.img
Any help?

askylitangel said:
So doing this without an SD Card at the mo and I get the waiting on device when trying to do fastboot flash boot twrp-3.2.1-0-cheryl.img
Any help?
Click to expand...
Click to collapse
Having an sdcard in the device means nothing unless your trying to boot from sdcard...
You're stuck at that point because your fastboot drivers aren't installed or incorrectly. There have been many posts throughout the forum on troubleshooting the drivers, Google search.

Infinix zero 5g 2023 TURBO X6815C (bootloader unlock/root/system-r/w) Ant-Man and the Wasp: Quantumania Edition

root infinix XOS 12 (Android 12)
Infinix Zero 5G Ant-Man and the Wasp: Quantumania Edition
Easy unlock
1. Enable developer options and turn on/allow OEM unlocking and enable USB debugging
2. Reboot to fastoot
Code:
Code:
adb reboot bootloader
3. Unlock bootloader via fastboot (you will be prompted to accept yes with volume up on phone.
Code:
fastboot flashing unlock
4. Setup and install MTK client Linux (fallow guide)
[GUIDE] [MTK] How to use MTKClient and set it up!
So most of you probably don't know what mtkclient is. It is basically an exploit which is used to boot any (mtk) phone into BROM mode (basically EDL for mtk) I am writing this guide especially for the RM6785 community. This tool is very useful...
forum.xda-developers.com
4. backup all partitions with MTKClient/MTKTool GUI (launch the mtk_GUI with su/root)
in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin
5. copy boot_a.bin to your phone internal for magisk patching manually on phone
(Time of writing latest)
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
6. Rename (magisk renames the default .bin)
patched_boot_a.img to patched_boot_a.bin
7. Copy patched boot_a back to your computer/home folder.
8. flashing.
From fresh started Android reboot to fastboot.
Code:
adb reboot bootloader
DO THE NEXT 2 STEPS AT THE SAME TIME IN FASTBOOT.
(Fastboot commands)
Code: terminal
Code:
fastboot flash boot_a /path/to/patched_boot_a.bin
Code2: (disable verity/secure boot) use vbmeta_a.bin that you backed up from you're phone.
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a /path/to/vbmeta_a.bin
AFTER flashing above you should now have root
############## system r/w#############
If you want system R/W writable (full root) fallow next steps.
1. go to system r/w website and get this version tested here.
Official SYSTEM-RW v1.41 by lebigmac for Samsung Galaxy S23 Ultra and other devices
lebigmac's software
lebigmac
www.systemrw.com
Link to file above
11.21 MB file on MEGA
mega.nz
This must be run on the phone!
Step 1
Decompress (7zip) SYSTEM-RW_v1.41.zip to this directory on device. sysrw_1.41
Code:
/data/local/tmp
Step 2 in Android terminal type
Code:
Code:
su
cd /data/local/tmp/sysrw_1.41
chmod +x sysrw
./sysrw
This will build the new patched r/w super.bin in /data/local/tmp/sysrw_1.41/IMG
Use file explorer (fx-file explorer) to copy patched_super.bin to phones internal/storage and then copy to computer to flash with fastboot.
Step 3
Code:
On computer/PC with adb and fastboot flash super. (Should be around 8gb file)
Code:
Code:
sudo adb reboot bootloader
sudo fastboot flash super /path/to/patched_super.bin
sudo fastboot reboot
########################
Enjoy system r/w[/code]

Lposed

CPU Demensity 1080, can play most emulators (dolphin/athersx2) at 30-60 FPS,a really powerful gaming phone

Phone
Infinix Zero 5G Ant-Man and the Wasp Quantumania Edition

Any help please

Can elaborate this please. Im stuck at this step

Mtk-client has a user interface see photo
Step4 in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin

Still can not change SELinux to permissive or install.... some madgisk modules..?? Assuming because the boot is reed only, wish system r/w worked on boot to as it contains the kennel..

Hi what version is your device? Is it v810? I was wondering if your device can boot into BROM mode.

Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again

notreal456789 said:
Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again
Click to expand...
Click to collapse
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again

Hnojohn said:
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again
Click to expand...
Click to collapse
This is why I don't update things, also it could be the setup Maby I'll post a Linux.iso with mtk client setup correctly

I still use Android apps from 2008 that still work on Android 12 fine