Related
How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.
subvapor said:
How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
Flash like every other factory image and all should be good.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Is it do able without a computer my laptop quit on me? If its not I'll have to wait till I'm around my moms house to do it. Ive only ever flash custom roms before so im not sure if it can be done with TWRP. Thanks for the help.
You need to use the fastboot tools, so you need your PC.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
phaino00 said:
You need to use the fastboot tools, so you need your PC.
Click to expand...
Click to collapse
Okay thanks for the help.
Whats the difference between the files?
9.0.0 (PPR1.180610.009, Aug 2018)
9.0.0 (PPR1.180610.010, Aug 2018, Telus)
The Telus one is for people who have Telus for cell service. If you don't have Telus use the 009 if you have telus use 010. Google tends to do this from time to time.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Does this apply if you have custom recovery (TWRP) and modified boot.img (Magisk)?
I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Sent from my SHT-AL09 using Tapatalk
Butch1326 said:
I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Click to expand...
Click to collapse
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.
Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.
SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
For me it did not take long for the Pixel to start after boot. Maybe a minute or two. It did take 5-10 minutes to run the Pie update.
Maybe it was because I originally installed Magisk 16 before going to version 16.7.
I agree with post-mortem's suggestion. It will be easier for you to reinstall Magisk before reinstalling the OS.
I've been starting out by flashing the factory image with adb. Then once it boots I can fastboot the twrp.img and get twrp into the recovery slot with no issues. I didn't get a chance today, but tomorrow I'll try with Magisk again.
post-mortem said:
Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.
Click to expand...
Click to collapse
I did end up doing that, though I don't know if this itself solved my problem. I'll explain more below
daver68 said:
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.
Click to expand...
Click to collapse
I ended up fixing my problem. After posting this, I repeated my exact steps a few more times to make sure I wasn't doing something wrong.
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk 16.7
8. reboot into Pie
These steps didn't work, and I would always get into a bootloop that takes me straight to recovery
What I ended up doing that fixed my problem was the following
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk uninstaller
8. reboot recovery
9. flash Magisk 16.6
10. set boot partition to B
11. reboot into rooted Pie
Specifically, I used the Magisk Uninstaller, used an "older" version of Magisk (16.6, not the later 16.7), and I also changed my boot partition from A to B after flashing Magisk. This worked for me, and until I know specifically why, I'm going to just re-use this procedure on the next factory image update.
Hopefully this can help someone else having the same problem!
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Not sure what to do at this point. Any ideas?
Thanks!
mobbdeep said:
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Edit sorry I updated magisk and now I don't have twrp
Not sure what to do at this point. Any ideas?
Thanks!
Click to expand...
Click to collapse
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
SirFronts said:
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
Click to expand...
Click to collapse
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
mobbdeep said:
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
Click to expand...
Click to collapse
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
I'll give that a try tonight.
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
alex.coffen said:
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
Click to expand...
Click to collapse
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Boot TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
I tried something and soft bricked my phone...
Anyway, lucky that I did a backup with twrp for boot when magisk was 19.3, then i can get into twrp by "fastboot boot" the twrp boot img temporarily and restored the boot.
Now everything works fine.
Ps: fastboot boot is not 100% safe...
mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
My TWRP is gone too. But I can temporarily get in TWRP using my computer.
How do I flash OOS firmware? I am currently on PIE 9.5.13 intl. version. Should I download the full zip OOS and then flash it via TWRP ?
Then flash TWRP ?
And then flash Magisk 19.4 ?
Another question: DO you think uninstalling magisk via magisk uninstaller and installing the canary version of it would allow TWRP to stick ? There's threads that mention that the canary version doesn't erase TWRP.
mobbdeep said:
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
redpoint73 said:
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
Click to expand...
Click to collapse
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh?
Dogstarlooma said:
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh
Click to expand...
Click to collapse
I just read that Magisk 20 has a bug, that prevents TWRP from "sticking", and to use 20.1 (or in your case, looks like 19.4).
Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex
dr.zikzak said:
Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex
Click to expand...
Click to collapse
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.
soihuvuontrang said:
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.
Click to expand...
Click to collapse
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.
dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
boot in to fastboot mode and your fone is not brick,so msm tool isn't used .
you can download newest driver for oneplus on google.
and you can find on forum. hope you will be successful
Kurtinaitis said:
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.
Click to expand...
Click to collapse
I'll have a try..,.thanks for that!
Regards,
Alex
The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
I also tried fastboot flash recovery twrp.img -> no such partition..... don't know why it worked the first time I did it, root and custom ROM without any issues...
Thanks,
Alex
dr.zikzak said:
The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
Thanks,
Alex
Click to expand...
Click to collapse
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash
Kurtinaitis said:
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash
Click to expand...
Click to collapse
I downloaded latest twrp-3-3-1.2 (I think) for my OP6, copied the belonging .zip file to my phone... started cmd as admin, typed fastboot devices....the device showed up, then fastboot boot twrp...........img.....enter, and afterwards the "1+" logo showed up, below it read Fastboot Mode...and nothing ever happened... till i switched the phone off again after 10 minutes...
Wrong version you think?
Thanks,
Alex
If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img
Flash a patched boot image of your rom via fastboot and than flash twrp installer through magisk manager. Done.
Kurtinaitis said:
If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img
Click to expand...
Click to collapse
Yes that worked for me last time I attempted root.
TWRP update - no boot into system
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex
dr.zikzak said:
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex
Click to expand...
Click to collapse
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.
Kurtinaitis said:
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.
Click to expand...
Click to collapse
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex
dr.zikzak said:
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex
Click to expand...
Click to collapse
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before
Kurtinaitis said:
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before
Click to expand...
Click to collapse
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)
Kurtinaitis said:
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)
Click to expand...
Click to collapse
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex
Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex
dr.zikzak said:
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex
Click to expand...
Click to collapse
Did you try to install the Update since the app Oxygen Updater?
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
dr.zikzak said:
Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex
Click to expand...
Click to collapse
I think there's some thread in Guides and News in which OP uploads some patched boot.img le something like that to have root but i never tried.
Hey, after installing android 11 on my Oneplus 6 I have servere issues on getting root back.
Both methods I used result in a stuck boot.
Method 1: fastboot boot twrp, then install magisk.zip (tried with both 21.4 (last with a zip) and the renamed 23.0 (from apk to zip)
Method 2: Extracted boot.img from my OTA update, then patched with magisk 23.0.
Flashed the new boot.img -with fastboot -with twrp both result in a stuck boot.
Suprisingly flashing the extracted boot.img from the OTA boots fine, but that image is without magisk
Update: I have extracted the boot.img directly from the phone, patched it and it still doesn't work
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Thratchen said:
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Click to expand...
Click to collapse
twrp actually works, but after flashing magisk or flashing a magisk boot.img it breaks. I have a working version here
Ping me if you get magisk working
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
To remember!
Thratchen said:
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
Click to expand...
Click to collapse
Which installation method of magisk did you use?
How long did you wait after first boot?
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Thratchen said:
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Click to expand...
Click to collapse
Thanks for the reply, as a last question: Which magisk version did you use (could you link i?t). I assume you took the magisk v23 apk and renamed it to .zip? or what did you do?
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Thratchen said:
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Click to expand...
Click to collapse
Hmm, I perfectly copied your instructions and still get a bootloop. Even reflashed 11.1.1.1 again. Might be time for a reset
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
vkass said:
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
Click to expand...
Click to collapse
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp latest zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
tacohell said:
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp lat est zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
Click to expand...
Click to collapse
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
UraniumDonut said:
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
Click to expand...
Click to collapse
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
vkass said:
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
Click to expand...
Click to collapse
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
UraniumDonut said:
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
Click to expand...
Click to collapse
Thhank @UraniumDonut - that worked - I have never before used that method and honestly didn't even know about it. I use the official documented twrp way which is to first fastboot in to twrp and then install the zip file which has to be located on the phone file system. This method seems a lot easier!
As to magisk, I usually flash that from twrp using the zip file method and never have had any issues. But with all the issues surrounding oos 11 I am playing it safe as I don't want to get in to a boot loop. Will do some more research before I try something. But thanks to you I have made 1 step forward progress!
UraniumDonut said:
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
Click to expand...
Click to collapse
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
vkass said:
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
Click to expand...
Click to collapse
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Just for reference here
UraniumDonut said:
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Click to expand...
Click to collapse
I posted detailed steps if you want to give this a try @UraniumDonut: https://forum.xda-developers.com/t/how-to-root-op6-11-1-1-1.4344269/#post-85765879
Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp
MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.
No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop
RIP
Started ranting instead
TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY
Pics
RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while
Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.
the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp