Hi,
I have a Fairphone 2 with the default ROM Fairphone Open 19.08.1.
I am trying to install microG. I red that a good way to get microG working is to install it with nanodroid. And I red also that a good way to install nanodroid is to flash it from TWRP.
So i installed TWRP with the TWRP official installer.
I can boot without any problem on TWRP (btw, I downloaded and installed two times 3.3.1-0, but in TWRP it shows 3.1.1-0).
I downloaded NanoDroid-microG-22.4.20190811.zip and NanoDroid-patcher-22.4.20190811.zip the nanodroid download page.
But when I try to flash those two zips I get an error in red that says: "zip verification failed!" even if the option "zip signature verification" is disabled.
What can I do to be able to flash those zips?
Thx
lalejand said:
Hi,
I have a Fairphone 2 with the default ROM Fairphone Open 19.08.1.
I am trying to install microG. I red that a good way to get microG working is to install it with nanodroid. And I red also that a good way to install nanodroid is to flash it from TWRP.
So i installed TWRP with the TWRP official installer.
I can boot without any problem on TWRP (btw, I downloaded and installed two times 3.3.1-0, but in TWRP it shows 3.1.1-0).
I downloaded NanoDroid-microG-22.4.20190811.zip and NanoDroid-patcher-22.4.20190811.zip the nanodroid download page.
But when I try to flash those two zips I get an error in red that says: "zip verification failed!" even if the option "zip signature verification" is disabled.
What can I do to be able to flash those zips?
Thx
Click to expand...
Click to collapse
I think you would have better luck getting microG to work if you installed lineageOS for FP2.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
I think you would have better luck getting microG to work if you installed lineageOS for FP2.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yes, maybe. I will have a look at it, but first I would like to try width FP OS. I have plenty of things configured on my phone and I would like not to have to configure again everything with another OS.
Isn't it strange that TWRP tries to perform a zip verification even if the zip verification is not activated?
lalejand said:
Yes, maybe. I will have a look at it, but first I would like to try width FP OS. I have plenty of things configured on my phone and I would like not to have to configure again everything with another OS.
Isn't it strange that TWRP tries to perform a zip verification even if the zip verification is not activated?
Click to expand...
Click to collapse
There is FP OS and there is FP Open, which are you using?
And no, it isn't unusual. Sometimes the error is because what you are trying to flash is not compatible, it's a safety measure to prevent flashing something that can harm your device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
There is FP OS and there is FP Open, which are you using?
And no, it isn't unusual. Sometimes the error is because what you are trying to flash is not compatible, it's a safety measure to prevent flashing something that can harm your device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I am using Fairphone Open 19.08.1
lalejand said:
I am using Fairphone Open 19.08.1
Click to expand...
Click to collapse
Everything I'm finding for FP2 TWRP zip signature verification failure applies to LineageOS, I'm not finding anything whatsoever about FP2 Open that applies to TWRP and microG signature failure. This is what leads me to believe that what you are trying to do is not compatible with FP Open and that lineageOS is what you need to be using in order to use what you are trying to use.
Sent from my SM-S767VL using Tapatalk
---------- Post added at 07:03 PM ---------- Previous post was at 06:57 PM ----------
lalejand said:
I am using Fairphone Open 19.08.1
Click to expand...
Click to collapse
I think starting your search in the link below would be a good start for finding info on FP and installing mods.
https://github.com/WeAreFairphone
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Everything I'm finding for FP2 TWRP zip signature verification failure applies to LineageOS, I'm not finding anything whatsoever about FP2 Open that applies to TWRP and microG signature failure. This is what leads me to believe that what you are trying to do is not compatible with FP Open and that lineageOS is what you need to be using in order to use what you are trying to use.
Sent from my SM-S767VL using Tapatalk
---------- Post added at 07:03 PM ---------- Previous post was at 06:57 PM ----------
I think starting your search in the link below would be a good start for finding info on FP and installing mods.
https://github.com/WeAreFairphone
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, thx for your help
lalejand said:
Okay, thx for your help
Click to expand...
Click to collapse
I managed to install TWRP 3.3.1 and I don't have the error anymore.
lalejand said:
I managed to install TWRP 3.3.1 and I don't have the error anymore.
Click to expand...
Click to collapse
Yeah, that should have been the first thing i suggested. You would be surprised what kinds of issues that updating TWRP will fix.
Sent from my SM-S767VL using Tapatalk
Related
Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.
Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror
I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Thanks OP
rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )
It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.
TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img
s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?
Just the first boot after flashing
Sent from my XT1254 using Tapatalk
Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.
TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.
I was using Mokee without any issue. earlier last week i tried Lineage OS and t was not loading it was just showing boot animation.
I tried to get Mokee back but it ended up with the same issue. Also on other OS. I tried with Android 6 OS and it loaded up but without SIM detection and sometimes no WIFI as well. Please Help!! Urgent
Jseven123 said:
I was using Mokee without any issue. earlier last week i tried Lineage OS and t was not loading it was just showing boot animation.
I tried to get Mokee back but it ended up with the same issue. Also on other OS. I tried with Android 6 OS and it loaded up but without SIM detection and sometimes no WIFI as well. Please Help!! Urgent
Click to expand...
Click to collapse
Are you using things that were made specifically for your model number redmi note 3? Or are you flashing things that were made for a different model number than yours?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Are you using things that were made specifically for your model number redmi note 3? Or are you flashing things that were made for a different model number than yours?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I am using the ones specific to my model. Lineage OS, Mokee, RR etc.. All seem to be stuck in boot animation
Jseven123 said:
I am using the ones specific to my model. Lineage OS, Mokee, RR etc.. All seem to be stuck in boot animation
Click to expand...
Click to collapse
Have you tried using the advanced wipes to wipe system partition and data partition before you flash, then flash ROM+Gapps, then do the normal wipes(factory reset, wipe cache and wipe Dalvik/ART cache), then reboot?
The advanced wipes I'm talking about are not the normal wipes (factory reset, wipe cache and dalvik/ART cache) that are usually done when flashing ROMs.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Have you tried using the advanced wipes to wipe system partition and data partition before you flash, then flash ROM+Gapps, then do the normal wipes(factory reset, wipe cache and wipe Dalvik/ART cache), then reboot?
The advanced wipes I'm talking about are not the normal wipes (factory reset, wipe cache and dalvik/ART cache) that are usually done when flashing ROMs.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes i have completely removed even the internal, Copied the zip file to the phone and flashed . Still bootloop. Never had this issue before
U need to unlock bootloader
lululul said:
U need to unlock bootloader
Click to expand...
Click to collapse
I have unlocked bootloader long back. Without that you cant have TWRP to install Custom OS. I need experts please
Jseven123 said:
I am using the ones specific to my model. Lineage OS, Mokee, RR etc.. All seem to be stuck in boot animation
Click to expand...
Click to collapse
What is your model number? Are you sure the ROMs you are flashing are for your specific model number? I'm not asking if they were made for Redmi Note 3, I'm asking if they were built specifically for your specific model number.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
Jseven123 said:
I have unlocked bootloader long back. Without that you cant have TWRP to install Custom OS. I need experts please
Click to expand...
Click to collapse
You will get experts, we just have to establish exactly what you have or haven't done and then figure out what you messed up, then we can help you fix this.
You can't just come and say
"I flashed "this" ROM or "that" ROM but it won't work"
There is a lot more to it than that. We need more information to understand exactly where your issue is, then you'll get an expert answer.
Are you sure that the Gapps you're flashing is the correct ones for your device? Have you tried flashing a smaller Gapps package? The one you used might not be correct for your hardware or might be too big to fit in your system partition. These are common causes of bootloop, especially considering the fact that all of your ROMs so far have bootlooped, are you flashing the same Gapps with each of those ROMs? If so, that could possibly explain your bootloop.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
What is your model number? Are you sure the ROMs you are flashing are for your specific model number? I'm not asking if they were made for Redmi Note 3, I'm asking if they were built specifically for your specific model number.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
You will get experts, we just have to establish exactly what you have or haven't done and then figure out what you messed up, then we can help you fix this.
You can't just come and say
"I flashed "this" ROM or "that" ROM but it won't work"
There is a lot more to it than that. We need more information to understand exactly where your issue is, then you'll get an expert answer.
Are you sure that the Gapps you're flashing is the correct ones for your device? Have you tried flashing a smaller Gapps package? The one you used might not be correct for your hardware or might be too big to fit in your system partition. These are common causes of bootloop, especially considering the fact that all of your ROMs so far have bootlooped, are you flashing the same Gapps with each of those ROMs? If so, that could possibly explain your bootloop.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I have clean wiped everything and downloaded the official custom rom for my Redmi Note 3 and I have tried installing with/without GAPPS. Same issue. If i am not wrong , it boots android v6 and not v7(assuming) since i am using my miui 8 again. and it loaded RR v6 for me but i never had this issue before I was able to to put any Custom Rom. I use Pico GAPP btw.
Jseven123 said:
I have clean wiped everything and downloaded the official custom rom for my Redmi Note 3 and I have tried installing with/without GAPPS. Same issue. If i am not wrong , it boots android v6 and not v7(assuming) since i am using my miui 8 again. and it loaded RR v6 for me but i never had this issue before I was able to to put any Custom Rom. I use Pico GAPP btw.
Click to expand...
Click to collapse
Either you've got something really strange going on or its something in the ROMs. Given that the issue is present with more than one ROM, I doubt it's a ROM issue. Have you looked through the Redmi Note 3 threads to see if anyone has had the same issue? It is probably some setting you changed or some mod that you applied before you tried the new ROMs, what that could be, I don't know.
I know you said you did a full wipe but strangely, sometimes settings/variables that were changed in one ROM causes issues when flashing other ROMs and it doesnt wipe that changed setting. I've exprienced this myself on my Galaxy S3 when going from one ROM to another even with full wipes.
Can I get a link to the ROM or ROMs you're having issues with?
Sent from my SM-S903VL using Tapatalk
https://download.lineageos.org/kenzo
https://download.mokeedev.com/?device=kenzo
If you give me links from unlocking bootloader to installation of OS, I will give a try again for the last time. ( No phone OS=no contacts/calls r= people worried )
Jseven123 said:
https://download.lineageos.org/kenzo
https://download.mokeedev.com/?device=kenzo
If you give me links from unlocking bootloader to installation of OS, I will give a try again for the last time. ( No phone OS=no contacts/calls r= people worried [emoji14] )
Click to expand...
Click to collapse
I'm not finding anything there that would tell me what other users are experiencing with this ROM. Have you tried contacting the developers to see if they understand your issue?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
Jseven123 said:
https://download.lineageos.org/kenzo
https://download.mokeedev.com/?device=kenzo
If you give me links from unlocking bootloader to installation of OS, I will give a try again for the last time. ( No phone OS=no contacts/calls r= people worried [emoji14] )
Click to expand...
Click to collapse
This should be your unlock method
http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader/
Download this TWRP file:
https://dl.twrp.me/kenzo/twrp-3.1.0-0-kenzo.img.html
Use these instructions to flash TWRP (use the TWRP file you downloaded above instead of the one from this guide, also, find and download the newest version of SuperSU.zip and use it with these instructions instead of the SuperSU.zip linked in this guide)
http://xiaomiadvices.com/install-twrp-recovery-root-redmi-note-3/
Then you should be ready to flash your ROMs.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I'm not finding anything there that would tell me what other users are experiencing with this ROM. Have you tried contacting the developers to see if they understand your issue?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
This should be your unlock method
http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader/
Download this TWRP file:
https://dl.twrp.me/kenzo/twrp-3.1.0-0-kenzo.img.html
Use these instructions to flash TWRP (use the TWRP file you downloaded above instead of the one from this guide, also, find and download the newest version of SuperSU.zip and use it with these instructions instead of the SuperSU.zip linked in this guide)
http://xiaomiadvices.com/install-twrp-recovery-root-redmi-note-3/
Then you should be ready to flash your ROMs.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is SuperSu necessary ? I didn't install SuperSu
Jseven123 said:
Is SuperSu necessary ? I didn't install SuperSu
Click to expand...
Click to collapse
It is typical for users to root the device for the first time by flashing SuperSU via TWRP.
I suppose it isn't necessary if you're going to flash a custom ROM that has root built in, if the ROM doesn't gave root built in them you'll have to flash SuperSU.zip to root the device before or after flashing that ROM.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Either you've got something really strange going on or its something in the ROMs. Given that the issue is present with more than one ROM, I doubt it's a ROM issue. Have you looked through the Redmi Note 3 threads to see if anyone has had the same issue? It is probably some setting you changed or some mod that you applied before you tried the new ROMs, what that could be, I don't know.
I know you said you did a full wipe but strangely, sometimes settings/variables that were changed in one ROM causes issues when flashing other ROMs and it doesnt wipe that changed setting. I've exprienced this myself on my Galaxy S3 when going from one ROM to another even with full wipes.
Can I get a link to the ROM or ROMs you're having issues with?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Can I do this?? I want to install Lineage OS
Jseven123 said:
Can I do this?? I want to install Lineage OS
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Jseven123 said:
Can I do this?? I want to install Lineage OS
Click to expand...
Click to collapse
If you do all the steps to get unlocked, TWRP and root installed then there shouldn't be an issue. Have you asked other members that have your device about anything about this? They would know if there were something extra that might have missed.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
If you do all the steps to get unlocked, TWRP and root installed then there shouldn't be an issue. Have you asked other members that have your device about anything about this? They would know if there were something extra that might have missed.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I got the confirmation to unlock but my i am getting COULDN’T VERIFY DEVICE” ERROR DURING BOOTLOADER UNLOCK PROCESS
What to do??
Jseven123 said:
I got the confirmation to unlock but my i am getting COULDN’T VERIFY DEVICE” ERROR DURING BOOTLOADER UNLOCK PROCESS
What to do??
Click to expand...
Click to collapse
I'm not familiar enough with your device to help you with that.
It might be because you've already made an unlock attempt before this and whatever you did then is interfering.
You need to look around in your device forum Q&A or find other users that have your device that have done what you are doing.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I'm not familiar enough with your device to help you with that.
It might be because you've already made an unlock attempt before this and whatever you did then is interfering.
You need to look around in your device forum Q&A or find other users that have your device that have done what you are doing.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
One more thing, Do I need to install different firmware to install Lineage OS?
I have created video guide regarding rooting and TWRP installation on one plus 6 which helps ,specially for noobs.
As this menthod is simple one no A, B partations nothing just simple flash and root and you get permanent recovery which takes backup (except data partition) for safety and become future flashholic person ?
Video guide:
https://youtu.be/SnI_uuNL5sk
REQUIREMENT:
LATEST FIRMWARE OXYGEN OS 5.1.5
(UDATE:IF YOU UPDATED TO OOS 5.1.6 THEN FOLLOW THIS GUIDE AFTER UNLOCKING BOOTLOADER LINKS GIVEN IN VIDEO DESCRIPTION. THIS IS OFFICIAL TWRP AND EASIET ROOTING METHOD
https://youtu.be/frXzBnPsoOs)
DOWNLOAD:
TWRP AND ROOT FILE:
https://googleweblight.com/i?u=http...lbeta-twrp-oneplus-6-t3798439&hl=en-IN&tg=524
Download two files from above thread from two links at top in that thread don't download anything else.
ONE PLUS ADB DRIVERS:
https://drive.google.com/file/d/1ntEb7biGJxenlhJun--i4czQIdNJh8fp/view
After unlocking bootloader phone reboots and it boots in to OOS there you have to again go to
Settings-About phone- build number tap eight times- go back to settings menu- tap developer option enable USB debugging and enable advance reboot
And then long press power button and select bootloader mode again and continue for TWRP flashing and Rooting
[I have not shown this repeated process in video]
Follow procedure exactly as shown in video
1)This rooting process passes safety net check so you can use banking(security) apps on rooted device
2)You can nandroid backup your Rom Except app data
3) It's permenant recovery
We can discuss all things regarding rooting here also
Worst Guide I've ever seen
Why open this thread? There was already another one on rooting and 2 on twrp
Hitman478[emoji769 said:
;76724880]Why open this thread? There was already another one on rooting and 2 on twrp
Click to expand...
Click to collapse
Agreed, the other rooting threads are good enough and it's not exactly difficult.
E.g. root without twrp
1. Download modified boot image
2. Fastboot boot boot.img
3. Install Magisk using using Magisk manager
4. Reboot
Enjoy root
I don't get how people keep managing to break their phones
Sent from my ONEPLUS A6003 using Tapatalk
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
I think the majority is with twrp and people probably swiping to allow system modifications which will cause inability to boot on stock kernel due to dm-verity
Sent from my ONEPLUS A6003 using Tapatalk
This is by far the easiest method. Why use the slot A&B method when that can be very confusing. I know he posted this in one of the other threads but I think it was lost in amongst the threads.
Sent from my ONEPLUS A6003 using Tapatalk
Dude .. I hope to create a video on how to flash stock global ROM through TWRP.
Thanks.
Alex240188 said:
Agreed, the other rooting threads are good enough and it's not exactly difficult.
E.g. root without twrp
1. Download modified boot image
2. Fastboot boot boot.img
3. Install Magisk using using Magisk manager
4. Reboot
Enjoy root
I don't get how people keep managing to break their phones
Sent from my ONEPLUS A6003 using Tapatalk
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
I think the majority is with twrp and people probably swiping to allow system modifications which will cause inability to boot on stock kernel due to dm-verity
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
I used that TWRP from that video and for me at least, It allowed modifications and I could boot back into the ROM no problem.
Sent from my ONEPLUS A6003 using Tapatalk
in stock works? new
emuwar said:
in stock works? new
Click to expand...
Click to collapse
Yes
Sent from my ONEPLUS A6003 using Tapatalk
Will this leave TWRP as permanent recovery and with permanent root? or is it just temporary? Thanks
hallo dare said:
Will this leave TWRP as permanent recovery and with permanent root? or is it just temporary? Thanks
Click to expand...
Click to collapse
I was only on stock rom for a few minutes until I flashed xXX rom. Twrp and root has stuck around a few reboots so I think it is permanent.
Sent from my BTV-W09 using Tapatalk
tdamocles said:
I was only on stock rom for a few minutes until I flashed xXX rom. Twrp and root has stuck around a few reboots so I think it is permanent.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
Its permanent tested
Now the official TWRP is available and you can use this guide to Root Oneplus 6 easily
I wish I could just find a guide how to install oneof those nice ROM's. Looks like this just not to install ROM in TWRP as used to be.
Thank you so much for this guide
Vatumb said:
Now the official TWRP is available and you can use this guide to Root Oneplus 6 easily
Click to expand...
Click to collapse
Can you please tell me if this is still valid for the 9.0.2 (current) build? Everything seems a bit dated right now.
Thanks
Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: twrp-3.3.1-1-guacamoleb.img (from https://twrp.me/oneplus/oneplus7.html)
Magisk: problem started with v19.1 but repeated itself with v20.0
UPDATE: I've found someone else with the same problem https://github.com/topjohnwu/Magisk/issues/1920
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Try to enter TWRP from recovery but boots to stock recovery
Can anyone help me? The feature I need the most is a full system backup
ColOfAbRiX said:
Hi all,
last week I received my new OnePlus 7 and I started playing with it and I'm having a problem. I unlocked it straight away, I installed TWRP and Magisk and all was great.
Then I noticed I coulnd't enter TWRP anymore to take a full backup. I tried everything I found on the net, Volume Up+Pwr, Volume Down+Pwr, Adb and so on but nothing. So I ran TWRP from fastboot and... I f****ed my partition. Some more reasearch and I managed to have the phone back but lost the data of the past week. Why TWRP doesn't start anymore but I only see the stock recovery?
Playing some more I made that happen again and here is what I discovered:
Phone: OnePlus 7 GM1903
OS: Oxygen 9.5.8.GM57AA
TWRP: 3.3.1-1-guacamoleb
Magisk: 20.0
1) Start with factory defaults
2) Install TWRP via adb
3) Install Magisk via TWRP
4) Install MagiskHide
5) Try to enter TWRP from recovery. Doesn't work.
Can anyone help me? The feature I need the most is a full system backup
Click to expand...
Click to collapse
Hello,
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Please use Magisk 19.3 on your pie rom.
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)
Hi!
strongst said:
did you follow this guide https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800 ?
Click to expand...
Click to collapse
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
strongst said:
Is this "3.3.1-1-guacamole" your whole twrp file name? Please use the ones from mauronofrio, you'll find them here(also linked in the guide)
Click to expand...
Click to collapse
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
strongst said:
Please use Magisk 19.3 on your pie rom.
Click to expand...
Click to collapse
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.
ColOfAbRiX said:
Hi!
For TWRP I followed another guide and used the official website. The only thing that differs seems to be the twrp file. For Magisk I followed the XDA thread.
It's almost the entire file name: twrp-3.3.1-1-guacamoleb.img I've downloaded the images following the links in https://twrp.me/oneplus/oneplus7.html. And I've updated my original request
Should I use this file "TWRP 3.3.1-70 Unified Unofficial Installer by mauronofrio"? The download page says it's for "Oneplus 7 Pro" but I have "Oneplus 7"
The problem first started with 19.3 and the second time I tried with 20.0
What I will do now is I'll try to follow step-by-step the TWRP guide on XDA first making sure I'm using the right twrp image, then using Magisk 19.3 and I'll post an update here.
Click to expand...
Click to collapse
Thanks for the update!
Yes, please use the twrp from mauronofrio, it's unified for OP7 and OP7 Pro (check file name like twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip)and and 19.3 magisk.
Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
ColOfAbRiX said:
Done. The partitions didn't break like it happened the first time but I still can't access TWRP. I can only access the stock recovery.
This time I have:
TWRP: twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
Magisk: Magisk-v19.3.zip
It's exactly like these guys https://github.com/topjohnwu/Magisk/issues/1920
Click to expand...
Click to collapse
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.
lvints said:
I can't access TWRP either. Did Magisk 20 cause this? I tried both versions and I can't get TWRP working.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Reading the comments looks like version 20 breaks TWRP.
Possible solution? " I've just factory resetted mine, and installed twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img with Magisk v19.4, now everything is fine."
Click to expand...
Click to collapse
Really? I have the problem with Magisk version 19.3
strongst said:
That's known, that on pie( 9.5.8 for example) magisk 20 has issues, so my recommendation was to use 19.3 Instead.
Click to expand...
Click to collapse
I tried to use 19.3 and nothing.
ColOfAbRiX said:
Really? I have the problem with Magisk version 19.3
Click to expand...
Click to collapse
Hmm, really strange, with 19.4?
lvints said:
I tried to use 19.3 and nothing.
Click to expand...
Click to collapse
Something prevents twrp to stick from magisk side
strongst said:
Hmm, really strange, with 19.4?
Something prevents twrp to stick from magisk side
Click to expand...
Click to collapse
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:
lvints said:
Any idea what it might be or what I did to cause it? No TWRP, no party :crying:
Click to expand...
Click to collapse
Sorry, I'm out of ideas at the moment...
And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP
ColOfAbRiX said:
And I've just realized that the Oneplus Switch application "moves" the files, it doesn't copy them. I've just lost 5 years of pictures... And still no TWRP
Click to expand...
Click to collapse
I'm sad about what happened to you, friend
If you can find a solution put the topic.
I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?
lvints said:
I think somehow I "broke" slot A. When I put in to reboot through this slot it is the phone for TWRP, but I can't access my files.
When I select B, I lose TWRP and can access my files
That makes sense? Is there a way to fix the slots?
Click to expand...
Click to collapse
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
See other thread(cross posting) https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
@strongst
Do you think it's best to answer this topic or the other?
lvints said:
@strongst
Do you think it's best to answer this topic or the other?
Click to expand...
Click to collapse
Where the discussion starts
Otherwise you'll lost the line when switching between threads.
ColOfAbRiX said:
Can you give more details on what you are doing?
I tried to select a different slot: at the moment Slot B is selected, then loading TWRP with fastboot I start Slot A but I can't mount /data anymore. So I restart
Click to expand...
Click to collapse
I have the same problem as yours. I've tried countless scenarios, followed tutorials on XDA and Youtoube but can't make TWRP work.
Out of curiosity I restarted the device through slot A after flash zip from magisk. My phone has accessed TWRP, but I cannot access my files. When I restart from slot B I have the opposite. Twrp doesn't work, but my files are accessible.
So I believe I somehow "broke" slot A. I just don't know how I did it or how to fix it.
obviously pixel 4a doesnt have twrp so,
ive tried all the free apps that let you flash zips but they dont work, and adb sideload gapps isnt working. i have rooted with canary magisk.
im stuck
Most roms for this device are packaged with gapps baked in. What are you trying to flash? Maybe if your more specific, someone here can give the assist.
Sent from my Pixel 4a using Tapatalk
jmtjr278 said:
Most roms for this device are packaged with gapps baked in. What are you trying to flash? Maybe if your more specific, someone here can give the assist.
Sent from my Pixel 4a using Tapatalk
Click to expand...
Click to collapse
I'm trying to flash the Opengapps pico zip on the resurrection remix nogapps build. My device is rooted with magisk canary, but when I use adb sideload, I get an error. So the zip doesn't install.
What's the error you're getting with adb sideload?
IntenseColor said:
What's the error you're getting with adb sideload?
Click to expand...
Click to collapse
error says signature verification failed, error 21.
if that is not helpful I can try sideload it again and get the exact wording of the error