does anyone have any cm13 for asus zenfone selfie? i can't find the rom in my pc. can anyone upload it?
Deleted, wrong link
24imelqui said:
Deleted, wrong link
Click to expand...
Click to collapse
i see you're on Z00T nougat, how did you install? does it need cm 14?
If you are still on LL firmware and have the latest TWRP 3.1.0-0 flash the fix found on post #2 in this link ---->> https://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698
After flashing you can now flash LOS 13/14 base ROMS.
Z00T - Selfie
24imelqui said:
If you are still on LL firmware and have the latest TWRP 3.1.0-0 flash the fix found on post #2 in this link ---->> https://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698
After flashing you can now flash LOS 13/14 base ROMS.
Z00T - Selfie
Click to expand...
Click to collapse
oh i have an unofficial version of a cm13 i found online. it has some bugs but usable. downside is the battery drain. so even tho i have the cm 13 i need to flash the fix? then i can flash LOS 14?
TrstnKndrk said:
oh i have an unofficial version of a cm13 i found online. it has some bugs but usable. downside is the battery drain. so even tho i have the cm 13 i need to flash the fix? then i can flash LOS 14?
Click to expand...
Click to collapse
You're already on a MM firmware? Then you don't need to flash the fix.
24imelqui said:
You're already on a MM firmware? Then you don't need to flash the fix.
Click to expand...
Click to collapse
i think i need to because when i flashed the RR nougat rom an error occurred. the same exact error the post mentioned. thanks for the help
24imelqui said:
If you are still on LL firmware and have the latest TWRP 3.1.0-0 flash the fix found on post #2 in this link ---->> https://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698
After flashing you can now flash LOS 13/14 base ROMS.
Z00T - Selfie
Click to expand...
Click to collapse
The error I was just getting before flashing this fix was something like
ASSERT FAILED: ASUS TRUSTED.......... Error code 7
Then flashed this and now on lineage ROM 7.1.1 got that error cause I couldn't update from my 5.0.2 stock os on my Z00TD
Yup, the fix was just a flashable MM firmware.
Related
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.
I m having redmi 2 prime... it was running lineage 14.1 official... i backed up the full rom and thought of flashing new android 8.0 aosp unofficial rom... i clean flashed the rom successfully... then i thought of reverting back to lineage and clean flashed it but it was stuck at ''patching system image unconditionally and the bar was full.... then i downloaded the miui 8.5 flash file and again clean flashed it through fastboot and then after flashing twrp again... i tried to flash lineage again but again it was stuck at patching system image unconditionally..... pllllzzzzzsz....... heeeellllllpppppp....
smart123123 said:
I m having redmi 2 prime... it was running lineage 14.1 official... i backed up the full rom and thought of flashing new android 8.0 aosp unofficial rom... i clean flashed the rom successfully... then i thought of reverting back to lineage and clean flashed it but it was stuck at ''patching system image unconditionally and the bar was full.... then i downloaded the miui 8.5 flash file and again clean flashed it through fastboot and then after flashing twrp again... i tried to flash lineage again but again it was stuck at patching system image unconditionally..... pllllzzzzzsz....... heeeellllllpppppp....
Click to expand...
Click to collapse
which build date u used????
Latest of 25 date
I could flash it earlier easily... but after installing aosp error came
smart123123 said:
I could flash it earlier easily... but after installing aosp error came
Click to expand...
Click to collapse
use same twrp or clean flash rom again
btw which los version is stable enough and less heating?
Los 14.1 build date 25..... i had used same twrp and same rom package
Issue not solved
i got same problem , try another rom like dot os , lineage os but when i flash miui rom its normal.. please help
Read the op.... even after flashing fastbootmiui rom.... the problem is not solved... the problem raised when i installed aosp rom
Hlo guy...i found the error... my sysrem.new.dat file is corroupt.... can someone send me full lineage os 14.1 date 25 build... plz
Yeah found the link to date 25 build....
https://www.mediafire.com/?4kyv2az89n8ec28
Or you can download it from my drive...
https://drive.google.com/file/d/1DOpZyGQ7fCZjT--PlAWbmCJsWD4PEiC1/view?usp=drivesdk
Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.
pissgoat said:
Looking to install a stock kernel somehow but i'm not sure how exactly. is there any guide on how to install a stock kernel? I've already looked arrount the forums but didn't really find any usefull information.
I'm rocking a xxx41 model and I'm planing to install Invicta OS onto it.
Thanks for any help in advance.
Click to expand...
Click to collapse
I have already replied same thing on older thread, [ https://forum.xda-developers.com/moto-g4-plus/help/quick-questions-kernel-installations-t3794980 ]
if you flash ROM, it will also install kernel which is considered stock for that installed ROM. You need to flash kernel only if you have modified it (by flashing custom kernel or SU zips).
If you want to flash different ROM, you can flash without doing anything else, just wipe and flash.
PS invictaOS is discontinued long ago, invictaOS-Nougat is stable, Oreo will be more bugfull than current available ROMs..
Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?
veikaas11880 said:
Experience "failure to load kernel" issue after flashing lineage 17 OS and OpenGapps 10 stock... please share the solution.. do i need to load a stock kernel?
Click to expand...
Click to collapse
Though these forums are for the Moto G4 Plus, that does suggest an issue with the build of Lineage OS that you're using. Can you confirm with the developer that this build is successfully running on their device? Do you have a compatible Lineage 17 OS based kernel you could try to flash?
Was your device working with other stock or custom ROMs before flashing Lineage 17?
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
+1
ajeteja said:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
Click to expand...
Click to collapse
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
NZedPred said:
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Click to expand...
Click to collapse
Yes I was on soak test. Pls help Moto g5s plus
@NZedPred Can you pls help? I am also facing the same issue.
#shubham Bane/- said:
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Yes I was on soak test. Pls help Moto g5s plus
Click to expand...
Click to collapse
kiranbala003 said:
@NZedPred Can you pls help? I am also facing the same issue.
Click to expand...
Click to collapse
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
@NZedPred thanks man. It worked
kiranbala003 said:
@NZedPred thanks man. It worked
Click to expand...
Click to collapse
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
ugander1989 said:
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
Click to expand...
Click to collapse
Step by step instructions are in my post above... Do you have a more specific question?
Does this work with moto G5s plus [sanders]
Will the above method work with moto g5s plus sanders
sarath6622 said:
Will the above method work with moto g5s plus sanders
Click to expand...
Click to collapse
Yes, if you did the same thing, i.e. flashed stock Oreo and then went to an Oreo custom rom, then yes the same approach will work. I have a flashable build and persist fix for sanders here:
https://www.androidfilehost.com/?w=files&flid=280579
Clean flash/Dirty flash?
@NZedPred I am facing the same problem. I own the Indian Moto G5 Plus (retin)
Here's what I did -
1. I unlocked my bootloader
2. I updated to Oreo (soak test) using the OTA capture.
2. I somehow rooted my phone after flashing TWRP.
3. Just after I flashed TWRP i.e. before rooting, I took a complete backup including the persist and EFS partitions.
4. After rooting, I clean installed MSM-Xtended ROM (8.1.0)
5. Everything is fine, but the fingerprint feature doesn't work/appear anywhere. Even the gesture support is gone.
What do I need to do?
If I follow your steps mentioned above i.e. flashing the persist-fix first, flashing the Nougat ROM you provided and then flashing any custom ROM, how should I proceed?
I am really confused whether I should clean flash (Wipe Data, System, Cache) after every step or dirty flash everything.
Please guide me.
Before you go back to custom ROM from stock Oreo ROM you have to flash stock nouget ROM if not fingerprint , NFC will not work.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
@sinchan_nohara
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
U wrongly flashed firmware, try Oreo custom rom
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
dhinesh_cool said:
U wrongly flashed firmware, try Oreo custom rom
Click to expand...
Click to collapse
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
navinsingh said:
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
Click to expand...
Click to collapse
ask in telegram grp
I've flashed the latest TWRP 3.2.2 on my Zenfone max pro m1 3/32.
I was previously on completely stock rom. I unlocked the bootloader and then flashed latest TWRP 3.2.2.
Next when I went to flash HAVOC PIE ROM OFFICIAL, I wiped data, dalvik,cache and system but then when I flashed,I got Zip treble compatibility error saying illegal zip format.
Please help, I'm unable to flash any pie roms.
Deeptesh Basak said:
I've flashed the latest TWRP 3.2.2 on my Zenfone max pro m1 3/32.
I was previously on completely stock rom. I unlocked the bootloader and then flashed latest TWRP 3.2.2.
Next when I went to flash HAVOC PIE ROM OFFICIAL, I wiped data, dalvik,cache and system but then when I flashed,I got Zip treble compatibility error saying illegal zip format.
Please help, I'm unable to flash any pie roms.
Click to expand...
Click to collapse
OKAY GUYS I'M REALLY SORRY. I KNEW ABOUT TWRP 3.2.3 ,BUT IT WAS NOT THERE IN THE ORIGINAL TWRP THREAD. NOW I'VE FOUND IT ,my problem is solved! :laugh:
Deeptesh Basak said:
OKAY GUYS I'M REALLY SORRY. I KNEW ABOUT TWRP 3.2.3 ,BUT IT WAS NOT THERE IN THE ORIGINAL TWRP THREAD. NOW I'VE FOUND IT ,my problem is solved! :laugh:
Click to expand...
Click to collapse
Can u provide the link for the official twrp u got??... Because im too facing the same error
Vicky_2409 said:
Can u provide the link for the official twrp u got??... Because im too facing the same error
Click to expand...
Click to collapse
Here it is TWRP FOR PIE
ALL of @SagarMakhar
Vicky_2409 said:
Can u provide the link for the official twrp u got??... Because im too facing the same error
Click to expand...
Click to collapse
Here you go buddy!
https://androidfilehost.com/?fid=3700668719832241089