The current version of TWRP will not accept your pin/password on 8.1. Until we get an update to TWRP there are a couple of work arounds.
One option is totally wipe your phone and root it before you set up a pin/password/fingerprint.
The other option is to get a thumb drive and a USB to C adapter from Best Buy or elsewhere. Put SU on the thumb drive, boot to TWRP img with fastboot as you normally do and then plug in the thumb drive to the phone. In twrp you will see an option to select storage, select the OTG USB Drive and you can install SU from there.
Our phones came with a USB a - c adapter in the box... Unless you bought it used or lose it... You shouldn't need to buy one unless you lose it
two_cents said:
Our phones came with a USB a - c adapter in the box... Unless you bought it used or lose it... You shouldn't need to buy one unless you lose it
Click to expand...
Click to collapse
Lol, you are right. Forgot all about that. Now I have two.
Fyi, just took the ota to Android 8.1 beta on my stock Pixel and Magisk 14.3 survived. Now have 8.1 rooted and all my modules up and running:laugh::good
Sent from my Google Pixel using XDA Labs
Guys I just bought a new pixel which turned out to be Verizon, anyway I'm just wondering if 8.1 has any major bugs or bugs at all ? Since the bootloader is looked and I will not be able to flash factory images if anything goes wrong with this beta.. help appreciated.
Alaadragonfire said:
Guys I just bought a new pixel which turned out to be Verizon, anyway I'm just wondering if 8.1 has any major bugs or bugs at all ? Since the bootloader is looked and I will not be able to flash factory images if anything goes wrong with this beta.. help appreciated.
Click to expand...
Click to collapse
I seems rock solid to me, and not seeing any major complaints.
Before I update can anyone confirm if ARISE will run on this?
quinejh said:
Before I update can anyone confirm if ARISE will run on this?
Click to expand...
Click to collapse
NVM I figured it out!! Lol
What i did to root the 8.1 Dev Preview was
1. As i didn't get the OTA Notification, i used the factory image, deleted the -w command
2. flashed the Factory Image
3. done, reboot back to bootloader
4. boot into the official twrp using the fastboot boot command
5. adb sideload magisk
6. Profit?
Well still can't flash anything but it's better to have root, and my previously installed modules are still there as well.
mflow said:
What i did to root the 8.1 Dev Preview was
1. As i didn't get the OTA Notification, i used the factory image, deleted the -w command
2. flashed the Factory Image
3. done, reboot back to bootloader
4. boot into the official twrp using the fastboot boot command
5. adb sideload magisk
6. Profit?
Well still can't flash anything but it's better to have root, and my previously installed modules are still there as well.
Click to expand...
Click to collapse
What version of Magisk are you using? I'm on 14.0 rather than 14.3.
ss4rob said:
What version of Magisk are you using? I'm on 14.0 rather than 14.3.
Click to expand...
Click to collapse
i'm on 14.3 now, i haven't tried 14.0 yet but i got problems with 14.0 on Android 8.0, so i moved to the beta channel.
Black crush
Would anyone be willing to do a test for me?
Can you restore the stock boot image, boot to system then look at the top right corner of this wallpaper with brightness on high, and in a dim room. You should see banding like the middle phone in this picture.
Then root with SR5-SuperSU-v2.82-SR5-20171001224502.zip and look at the same wallpaper. Let me know if the banding is gone and the transition is as smooth as the right phone in the picture.
You have to do the steps exactly as laid out, though. Having a modified boot image before flashing SuperSU does not produce this result, and neither does being on 8.0 or 7.1.2. It only happened in 8.1, and only after I flashed this SuperSU over the stock boot image...Magisk did not do the same thing.
Will it be necessary to wipe my phone or flash with -w command?
I have a card reader which is type c port. But I dirty flash SuperSU zips using different TWRP images. One is TWRP 3.1.1-0 from this forum, and another one is 3.2.0 from TWRP official website. SuperSU zips are 2.8 stable and 2.82 RC5. Any zip installed by TWRP 3.2.0 was failed, stable on 3.1.1-0 shows successful but not getting root after boot into system, RC5 shows patching sepolicy failed and gets the same result after boot.
I don't want to wipe actually, because I have lot of important data especially game data on it. It's easy to copy and paste personal files but since I can't use Titanium Backup I hate getting clean wipe.
Should I get a Magisk for completeing this one?
bbs3223474 said:
Will it be necessary to wipe my phone or flash with -w command?
I have a card reader which is type c port. But I dirty flash SuperSU zips using different TWRP images. One is TWRP 3.1.1-0 from this forum, and another one is 3.2.0 from TWRP official website. SuperSU zips are 2.8 stable and 2.82 RC5. Any zip installed by TWRP 3.2.0 was failed, stable on 3.1.1-0 shows successful but not getting root after boot into system, RC5 shows patching sepolicy failed and gets the same result after boot.
I don't want to wipe actually, because I have lot of important data especially game data on it. It's easy to copy and paste personal files but since I can't use Titanium Backup I hate getting clean wipe.
Should I get a Magisk for completeing this one?
Click to expand...
Click to collapse
The sepolicy abort is happening to others. I don't think keeping the -w in place is going to help.
https://forum.xda-developers.com/pixel/how-to/platform-tools-windows-zip-12-5-2017-t3715120/page2
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
sliding_billy said:
The sepolicy abort is happening to others. I don't think keeping the -w in place is going to help.
https://forum.xda-developers.com/pixel/how-to/platform-tools-windows-zip-12-5-2017-t3715120/page2
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
Click to expand...
Click to collapse
Yeah, and after boot I even don't got any supersu app, manually install from play store and it will tell me my phone isn't rooted
---------- Post added at 03:27 PM ---------- Previous post was at 03:07 PM ----------
Finally, I've successfully rooted by following steps from here: https://forum.xda-developers.com/pixel-xl/how-to/how-to-root-android-8-1-devpreview-1-t3696278
But notice we don't have to keep -w command to do a clean wipe, just boot into TWRP and flash TWRP installer, then flash magisk it will be done.
Shortcoming is I cannot use SuperSU anymore instead of Magisk, but it also doing things great.
I used Magisk 14.5 (1456) to root the Pixel with no issues. I left SuperSU on the XL, and might put it back on the Pixel when the issue is resolved.
---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------
bbs3223474 said:
Yeah, and after boot I even don't got any supersu app, manually install from play store and it will tell me my phone isn't rooted
---------- Post added at 03:27 PM ---------- Previous post was at 03:07 PM ----------
Finally, I've successfully rooted by following steps from here: https://forum.xda-developers.com/pixel-xl/how-to/how-to-root-android-8-1-devpreview-1-t3696278
But notice we don't have to keep -w command to do a clean wipe, just boot into TWRP and flash TWRP installer, then flash magisk it will be done.
Shortcoming is I cannot use SuperSU anymore instead of Magisk, but it also doing things great.
Click to expand...
Click to collapse
Try Magisk.
I've successfully rooted 8.1 by following steps:
1. boot into TWRP 3.1.1-1
2. install the latest Magisk 14.5 zip from external storage (DOK)
without wipe and/or installing twrp installer
Really wish we could get SuperSU to work. Rooting with Magisk doesn't allow me to use Titanium backup to get rid of Google bloat. Is there some other way to achieve this using Magisk? My understanding is that rooting through Magisk will not allow one to modify the System partition in any way?
pavanmaverick said:
Really wish we could get SuperSU to work. Rooting with Magisk doesn't allow me to use Titanium backup to get rid of Google bloat. Is there some other way to achieve this using Magisk? My understanding is that rooting through Magisk will not allow one to modify the System partition in any way?
Click to expand...
Click to collapse
I removed approximately 500 MB of bloat via Titanium Backup. I'm rooted with Magisk 14.5. Flashed Magisk 14.5 via TWRP using usb-otg. No issues except the contacts sync issue.
phaino00 said:
I removed approximately 500 MB of bloat via Titanium Backup. I'm rooted with Magisk 14.5. Flashed Magisk 14.5 via TWRP using usb-otg. No issues except the contacts sync issue.
Click to expand...
Click to collapse
Huh! It didn't work for me when I tried it. It seemed to uninstall, but on rebooting, all the apps were still there. Is that not the case for you? Also, do you have a list of the apps you uninstalled?
Thanks.
Related
Hello,
I have a big problem. I don't know what to do.
I wanted to make a clean install of OxygenOS 4.5.8 and so i downloaded it, did it on SD card together with Magisk and no_verity_op5.zip (because i read that this decrypt the data).
So i cleand data and installed no_verity_op5.zip via TWRP, but when i wanted to reboot it takes way to long (i waited 30minutes but it stays on boot circle)
After that i booted into TWRP and decided to made a factory reset and to install OxygonOS 4.5.8 in a clean version. But it was not possible anymore!
When i want to install the .zip it says Patching system image unconditionally... and it loads. after the blue is full it says:
writing static_nvbk image...
patching firmware images...
script succeeded: result was [1.000000]
And when i want to boot into system it says no OS installed.
I tried also to flash this rom or even any other custom rom through ADB Sideload but it does not work. Same like above..
What can i do? I do not know what to do
I hope my phone is not bricked.
Thank you for any suggestion.
Go to oneplus 5 official download page, download stock recovery and latest stock firmware and follow instructions on the download page.... But first with TWRP take a backup of all your data because restoring stock firmware will ERASE everything... Don't panic it will works
First off, don't panic! you're not bricked as long as you can reach your bootloader and recovery.
This happened to me as well and luckily the fix is easy!
You probably tried to flash the OxygenOS build from the Oneplus downloads right?
Somehow these won't flash properly through TWRP and you must therefore also flash the Oxygen recovery image listed in the downloads.
Here are some steps that'll fix your problem.
1 - Backup all of your private data from internal storage because flashing OxygenOS will WIPE/ENCRYPT all data on your device.
2 - Go to the Oneplus download center and download both the latest OxygenOS and it's appropriate recovery:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.8
3 - Boot into your bootloader and flash the stock recovery you just downloaded. (fastboot flash recovery <recovery>.img)
4 - Boot into the Oxygen recovery and flash OxygenOS.
This should get you up and running again.
Once you get tired of OxygenOS simply reboot back into your bootloader and flash TWRP and any rom of your liking.
In the future if you want to flash OxygenOS from TWRP you have to grab a build from XDA I guess. I'm not entirely sure why flashing from within TWRP won't work with stock OOS but I believe it expects to be flashed from withing the stock recovery.
I'm pretty confident this will solve your problems.
Please backup your data first though, don't want anything to get messed up in there!
Good luck!
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
manuelbvb said:
Ok thank you.
i will try it.
So you are right, i tried to install OxygenOS with TWRP.
So is it not possible to have official OxygenOS with TWRP, Magisk and Root?
So i cannot backup OxygenOS with TWRP?
Click to expand...
Click to collapse
It is possible to have both OxygenOS and TWRP for sure!
Only a clean flash from a non-encrypted state in TWRP seems to break stuff. You can use a modified OOS build from the forums.
TWRP can indeed backup your OOS install so that shouldn't be a problem.
The only exception seems to be flashing a clean install of OxygenOS (from Oneplus Download center) through TWRP.
Other than that everything works as expected.
Ok thank you.
So i will follow you instructions and i hope it will work.
And i think so.
And after it i will install TWRP again (because i need the backup tool), i will install magisk. will this work?
So i can use everything as in a custom rom, but cannot make a clean install? So official Oneplus OTA will work with TWRP or not?
Thank you soooo much!
Also, Magisk/root works just fine on OxygenOS.
Once you flashed OOS from the stock recovery and have everything set up simply boot into your bootloader and flash TWRP.
From there you flash Magisk and everything should be fine.
OTA's from Oneplus also install fine through TWRP as long as you go into Magisk and uninstall 'root' first. When OxygenOS tells you there's an update simply remove Magisk as I said above and it'll update fine.
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
manuelbvb said:
Ok thank you!
It worked!!!!! I am very happy!
So i will now install TWRP, and then magisk (newest version).
I have a question, because the last time i installed magisk it did not fully work.
If i install it i have root or? But how can i get saftynet in magisk?
Click to expand...
Click to collapse
First off! YAY!! glad it worked out!
Be sure to use the TWRP build from the twrp.me website. The one listed on these forums are 'unofficial'. Not saying those are bad, but the official one has a pretty impressive track-record.
After flashing Magisk you are root-enabled so yeah, congrats you are now root! In order to pass safetynet you must enable 'magisk hide' in the magisk manager (the app that should now be installed on your phone).
If you do not have an app called 'magisk manager' then you can download this app from the magisk forums. It should however install itself while flashing the Magisk zip. So assuming you have it installed find the 'magisk hide' service and enable it.
From my experience you sometimes need to reboot in order for it to pass safetynet check.
Glad it all worked out for you!
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
manuelbvb said:
Everything worked!
Now i have OxygenOS 4.5.8 (with OTAs in future), magisk + root + saftynet and i can install something throug TWRP and backup.
SO PERFEKT.
You are a hero
Click to expand...
Click to collapse
That's great to hear!
Enjoy and take care!
no os
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
xda___ said:
sideloaded zip for rom in twrp, says successful but then no os installed and I can't find the zip anywhere in twrp. help :]
Click to expand...
Click to collapse
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Zocker1304 said:
Can't you just connect your phone to your PC and use MTP for the file transfer? Make sure to have MTP disabled under TWRP-> Mount -> Enable MTP
Click to expand...
Click to collapse
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
xda___ said:
I tried, windows recognizes my phone, but when I try to transfer files it it says device is not available or has been disconnected (something like that...)
Click to expand...
Click to collapse
Well just flash a different twrp via fastboot flash recovery *path to file*
Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version
Ss
joeeboogz said:
Ss
Click to expand...
Click to collapse
Too late , topjohnwu released magisk v16.1 here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 Magisk manager isn't flashing for some reason so you have to go into the actual file path inside the zip. /common/magisk.apk and install it manually. The module devs need to update their code, but mine should still work.
Just noticed well If u need apk still it's in my drive along with zip
How do access your drive? I tried to go the Magisk route and it hung on the Google boot screen with the loading bar and eventually rebooted itself
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
I did the same thing. I couldn't get it to boot back to my phone but I could boot back into TWRP. So I just wiped then restored a backup I had. Try that. Or worse case scenario just boot to bootloader and flash the factory.img again. That should over write anything you have on there now and allow you to boot successfully.
Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
This may be a little late, but go back into twrp and flash the magisk uninstaller located in the official forum. Then reboot. Then reinstall magisk again
This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?
petiolarissean said:
This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?
Click to expand...
Click to collapse
You need to use Xposed for P, which isn't even the roadmap I'm sure lol
If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?
x31234 said:
If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?
Click to expand...
Click to collapse
No.
are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*
AlPoo said:
are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*
Click to expand...
Click to collapse
Also waiting for this. Just searched for it but it seems the full image files are not online yet. And I don't know if twrp or the ability to root will still be there if I just uninstall magisk via the uninstaller zip in twrp, and then install the OTA from today?
EDIT:
fastboot the full dp2 image
do set-up process (don't set a PIN)
fastboot twrp 3.2.1.2 img
install twrp 3.2.1.2 zip
reboot recovery
install magisk 16.4 (16.0 won't work)
done
Tested with adaway and it works fine. I expected it to be harder to be honest but I'll take it.
joeeboogz said:
Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version
Click to expand...
Click to collapse
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.
Jerreth said:
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.
Click to expand...
Click to collapse
I did the same but booted to 3.2.1-2 and it worked as well
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
sometimes it takes a second or more reboots to get into the OS.
madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
Same here
Try flashing boot.img to both slots and redo the process
Sent from my Pixel XL using Tapatalk
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Did you do this from Pie or from Android Q beta? Also, did you uninstall Magisk from the manager before you did the OTA?
Anybody know if this worked smoothly with their Viper4Android app?
This worked form me going from Android 9 with Magisk to Android 10
I'm glad I waited and saw this before moving to Android 10. This worked like a charm for me as well.
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and installed it.
---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
kmry said:
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Click to expand...
Click to collapse
Is your recovery stock? It may not be clearly stated as I haven't read the thread in its entirety, but the OTA will fail with TWRP installed. It likely will also fail if the system partition is modified.
EDIT: I re-read your post. You clearly note using TWRP.
Nightf0x_007 said:
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
Click to expand...
Click to collapse
How do you flash it, with flash fire, trough TWRP or from fastboot?
kmry said:
How do you flash it, with flash fire, trough TWRP or from fastboot?
Click to expand...
Click to collapse
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Anyone know how to get the native led configuration without using a custom rom or the lightflow app?
Should I update Magisk and manager before I do this?
My Magisk installed is 18.1 and it lists 20.1 as available
Magisk Manager installed is 7.0 and 7.4 is listed as available
If you wanna follow the official instructions :
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Nightf0x_007 said:
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Click to expand...
Click to collapse
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
kmry said:
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
Click to expand...
Click to collapse
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Nightf0x_007 said:
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Click to expand...
Click to collapse
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
Just the flash-all.bat if your using Windows. :good:
kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
.bat file only
October Security Patch has been posted.
What is the size of this update? I received only 7.1mb update ?
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
I don't know. Flashed the full image from Google.
in Germany, the update is also so big
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
Yes, it is 7.1 MB. Strange.
Wow huge update! My WiFi couldn't cope up with 7.1mb update. Awesome Google ?
Nothing here yet, T-Mobile, Houston.
Edit: received OTA last evening 10/08. I believe the size was 7.4mb.
Sent from my [device_name] using XDA-Developers Legacy app
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
Dude sometimes this phone just needs a little extra... Lol glad you kept your cool and hung in there.
Sent from my Pixel 2 XL using XDA Labs
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
How did you "reflash magisk and kernel?" Did you boot to system first?
astaineakash said:
What is the size of this update? I received only 7.1mb update ?
Click to expand...
Click to collapse
Me too
jlokos said:
How did you "reflash magisk and kernel?" Did you boot to system first?
Click to expand...
Click to collapse
Yes after flashing factory image without wiping, i booted up to system then checked magisk wasnt installed (only manager app), then i fastbooted to twrp recovery flashed custom kernel then flashed magisk and reboot, thats it, and all my magisk settings returned back to what it was like before all this
Can anyone please post the fingerprint for the October build from build.prop?
Much thanks!!
Any easy way to install this on a rooted phone without wiping data?
Dylan.4 said:
Any easy way to install this on a rooted phone without wiping data?
Click to expand...
Click to collapse
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Since October patch (rooted) I have massive problems my pc/my phone detecting my phone/my pc. I dont know why, its just charging, one time it worked (I need USB-Tethering) I was just restarting and restarting the phone, turning debugging on/off...
Any idea how to fix this?
edit: It just says unknown usb-device, I manually uninstalled and installed the latest android usb drivers. If I try to use an adb command it just says "error: no devices/emulators found"
Probably the worst security patch. My sensors aren't working properly, phone doesn't go off while i talk. It hangs at odd occasions. Battery is weak. Auto brightness isn't working either
hawkjm73 said:
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Click to expand...
Click to collapse
Perfect, it worked. Thank you!
What I need to do to upgrade and root version 11.1.1.1, I'm currently on a 9.0.16 rooted twrp magisk
Wheres the download link for the full OOS 11.1.1.1.1.1.1? Does OTA mean the full stock rom download or zip file just for update????
The way I did it from 10.3.8 and 10.3.12:
1) Boot into TWRP
2) Flash latest TWRP (twrp-installer-3.5.2_9-0-fajita.zip from official TWRP site) and Reboot to recovery
3) Flash the full OOS11 zip file. It will flash one of the two A/B slots - DO NOT YET REBOOT!!!
4) Directly after flashing the OOS11 zip flash twrp-installer-3.5.2_9-0-fajita.zip again
5) Reboot into recovery
6) Flash OOS11 zip again into the other slot - Again: DO NOT YET REBOOT!!!
7) Flash twrp-installer-3.5.2_9-0-fajita.zip again
8) Flash Magisk-v23.zip
9) Reboot
Looks more complicated than it really is. You just have to do everything twice to flash both slots. At least that's how I did it a couple of times and it worked without any issues.
!!!You could also Flash directly from the updater app without rebooting. Go into Magisk and install twrp A/B retention script and reinstall Magisk. I never did it that way because I always made a Nandroid backup before flashing everything.!!! See edit comment!!
Hope that helps.
Edit: I just read in another thread the Magisk route (A/B retentio...) leads to a Qualcomm Crashdump which needs unbricking via the MsmDownloadTool!!!
@ptuner: I usually go tp Settings -> System -> System Updates. Don't install, just but put the phone aside for some time. It will download the full zip into Internal memory/.Ota.
You download the full zip from any of the places you find via your search engine of choice.
MrBrainstorm said:
The way I did it from 10.3.8 and 10.3.12:
1) Boot into TWRP
2) Flash latest TWRP (twrp-installer-3.5.2_9-0-fajita.zip from official TWRP site)
3) Flash the full OOS11 zip file. It ill flash one of the two A/B slots - DO NOT YET REBOOT!!!
4) Directly after flashing the OOS11 zip flash twrp-installer-3.5.2_9-0-fajita.zip again
5) Reboot into recovery
6) Flash OOS11 zip again into the other slot - Again: DO NOT YET REBOOT!!!
7) Flash twrp-installer-3.5.2_9-0-fajita.zip again
8) Flash Magisk-v23.zip
9) Reboot
Looks more complicated than it really is. You just have to do everything twice to flash both slots. At least that's how I did it a couple of times and it worked without any issues.
!!!You could also Flash directly from the updater app without rebooting. Go into Magisk and install twrp A/B retention script and reinstall Magisk. I never did it that way because I always made a Nandroid backup before flashing everything.!!! See edit comment!!
Hope that helps.
Edit: I just read in another thread the Magisk route (A/B retentio...) leads to a Qualcomm Crashdump which needs unbricking via the MsmDownloadTool!!!
@ptuner: I usually go tp Settings -> System -> System Updates. Don't install, just but put the phone aside for some time. It will download the full zip into Internal memory/.Ota.
You download the full zip from any of the places you find via your search engine of choice.
Click to expand...
Click to collapse
all data is deleted yes?
ELAD098 said:
all data is deleted yes?
Click to expand...
Click to collapse
No, if you upgrade via TWRP as I described your data will NOT be wiped. But I always advice to make a full backup (nandroid and internal storage) before flashing anything!!
Are you satisfied by 11.1.1.1 generally ?
I was on 11 and rollback to 10 cuz battery issues. Can anyone give some info, are you satisfied with 11.1.1.1 ?
I am only using since last Wednesday but so far I am happy with it. The battery usage is identical to 10.3.12 with 0.7%/h (according to AccuBattery). Screen usage is probably the same. Can't really tell as I am not a heavy user.
Unfortunately I tried to install and got a brick
i can unlocked bootloader on 11.1.1.1
now i on 10.3.8 lock bootloader
i want to upgrade
I bricked mine too and used MSM tool to get to android 9, I installed TWRP 3.3.1-31 (pie version) and last version of Magisk, after that, I wiped all but internal storage, download OOS 11.1.1.1.1.1..1 and flashed with TWRP, done after like 5 min, I clean Dalvik cache and flash the same TWRP (3.3.1-31 pie version) + Magisk 23
Booted the system and noticed that Magisk wasn't installed so I got back to recovery, flashed once again Magisk and all Good until I fok up again in the future.
Messing around with rooted oos 11 only for 1 day so far and I already noticed the battery drain on this system is more (agressive)
I used adb to shut off the update notification posted by Sachin09.
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.oneplus.opbackup
exit
I have issues with phone after though. Phone says not online WiFi but I can watch youtube but I cannot open or view any attachments in gmail. I had Hotpot on when I ran the adb script. I'm wondering if that was a problem.
Question: If I repeat the adb script but swap install for uninstall, will it revert to normal? Any suggestions? I'm still on 10.3.12 and happy with it.
Jim44 said:
I used adb to shut off the update notification posted by Sachin09.
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.oneplus.opbackup
exit
I have issues with phone after though. Phone says not online WiFi but I can watch youtube but I cannot open or view any attachments in gmail. I had Hotpot on when I ran the adb script. I'm wondering if that was a problem.
Question: If I repeat the adb script but swap install for uninstall, will it revert to normal? Any suggestions? I'm still on 10.3.12 and happy with it.
Click to expand...
Click to collapse
Try to do a local update with full zip file. Maybe it help.
edited: try thiis command and see if it work
Code:
1. adb shell
2. cmd package install-existing com.oneplus.opbackup
3. exit
After that restart the phone.
Thank you! That worked. I'm back with the unwanted OS 11 update again.
I tried the "pm -k uninstall..." again which removed the update but the wifi and gmail issues returned.
I fixed it though. I rooted my 1+6T long ago. I have the TWRP and MAGISK zip files in root.
I booted into recovery, uninstalled Magisk with the uninstaller zip, installed TWRP..zip then installed Magisk..zip. I rebooted and now everything works.
I tested out OS 11.1.1.1.1 on my buddy's phone and I don't want that OS. Thank again for the help I needed. Jim44