Related
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?
spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.
bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
cmivxx said:
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
Click to expand...
Click to collapse
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
mac796 said:
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
Click to expand...
Click to collapse
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
cmivxx said:
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
Click to expand...
Click to collapse
I usually just use the kernel that comes with the rom im on. And I use magisk. I have used ex kernel. I really like the ex manager app. And I do believe it still passes safety net with just unlocked bootloader. At least it used to. Google updated safety net this month so I don't know if that changes things.
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
cmivxx said:
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
Click to expand...
Click to collapse
You will probably be able to take the OTA with just a unlocked Bootloader, you will just have to boot TWRP and Flash that kernel every month. There also is a stock kernel someone builds for what you're trying to do
You can flash google's factory-image.
Then you can re-lock your bootloader and you can unlock it too.
It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.
Right?
I'm having the same issue. I can't figure out how to root mine either and I've got the same phone and carrier.
nickthekid said:
It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.
Click to expand...
Click to collapse
Details of your current ROM Please..?
Build number etc...
Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB
iamoz said:
Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB
Click to expand...
Click to collapse
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Yes I would be interested in having those files please... Either upload them here or I can give you an email if you prefer... Let me know..
rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.
NonStickAtom785 said:
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.
Click to expand...
Click to collapse
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there
rip21skinz said:
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there
Click to expand...
Click to collapse
I do not have the option to OEM Unlock the phone period. It is not in my developer options unfortunately. If you do find something of that nature please do contact me. Also if you would like a TWRP for your device I'd be up to developing it, although I wouldn't be able to maintain bugs... All I need is the kernel and I can get it done.
Any updates on this?
Long time rooter who has more or less given up in recent years.
Rooted:
HTC hero
HTC desire
Samsung Galaxy s1
Nexus 4
Nexus 5
Nexus 5x
Not rooted:
Pixel 2
Pixel 4xl
Just got a pixel 4 but would be tempted to root the pixel 2 while it's still got some life in it.
Got a few quick questions as to what has changed recently. Would be using magisk to achieve root after installing twrp. (Unless this is old hat and something else is the method of choice). Probably will have to unlock bootloader can't remember if I ever did it on the pixel 2
What's the procedure for monthly updates can they be done via ota or do I need to bring adb into it?
Best guides floating about at the moment? Any other pertinent advice? Muchthx
first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.
IMO the rooting party is pretty much over. I also returned to xda after many flashes years ago. For the Nexus, the great Beanstown dev provided monthly flashes for your custom recovery, but it looks so much more complicated today, to the point it's not worth the effort anymore. I'm sticking with stock till the '2 dies. The risk of unlocking the bootloader and getting root is simply not worth the headache as evident in the Q&A posts. So for now, for my much wanted rootness, I resort to debian linux on the desktop, a command line, and the luxury of typing sudo!!
sudoxd said:
first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.
Click to expand...
Click to collapse
Very impressive signature of the number of many devices you have. Maybe a new wall plaque perhaps?
After riding the HTC and Samsung wagons for quite a while, I have purchased the Oneplus
I have been browsing around the other threads for the 7 and 8 models and it looks like OnePlus typically releases the firmware and/or recoveries right away when a new model is launched. Does anyone know if this will be the case for the 8t?
I want to get root out of the way before setting up the new device when it arrives, so I was hoping a dev already has the boot img uploaded somewhere or it was coming soon.
Does anyone care to elaborate on what expectations should be for this type of stuff?
Thanks in advance!
MNoisy said:
After riding the HTC and Samsung wagons for quite a while, I have purchased the Oneplus
I have been browsing around the other threads for the 7 and 8 models and it looks like OnePlus typically releases the firmware and/or recoveries right away when a new model is launched. Does anyone know if this will be the case for the 8t?
I want to get root out of the way before setting up the new device when it arrives, so I was hoping a dev already has the boot img uploaded somewhere or it was coming soon.
Does anyone care to elaborate on what expectations should be for this type of stuff?
Thanks in advance!
Click to expand...
Click to collapse
If you've around here awhile, you should know that you shouldn't ask about timelines. They'll be available when they're ready.
It's shipping with R out of the box and has new ways of doing things that will take time to figure out. Past availability times shouldn't be used to gauge availability on new phones.
Superguy said:
If you've around here awhile, you should know that you shouldn't ask about timelines. They'll be available when they're ready.
It's shipping with R out of the box and has new ways of doing things that will take time to figure out. Past availability times shouldn't be used to gauge availability on new phones.
Click to expand...
Click to collapse
There is no need to add the useless commentary. I appreciate your reply but I wasn't asking for timelines from a dev or some modification to be done. I wanted to gauge the typical expectations of people have who are current OnePlus users for things like firmware, updates, etc.
For example, HTC is terrible at getting out new updates and has not provided timelines or expectations for firmware updates in like the last year + for their last two flagship models. Samsung is very consistent with software releases and public schedule announcements. These are important to a lot of users and it was tough to determine this when reading the other forums for other OnePlus devices.
Past availability is frankly the only way to estimate when things like this might be available to us. Most companies don't change the way they do everything just because there is a new product being released. If you want to help with that information instead of being negative, I welcome your assistance!
There is typically a monthly update in firmware, with possibly more frequent ones in the beginning if there are issues.
I wouldn't necessarily expect root for at least a week or 2 on any new phone, especially with a new OS.
Superguy said:
There is typically a monthly update in firmware, with possibly more frequent ones in the beginning if there are issues.
I wouldn't necessarily expect root for at least a week or 2 on any new phone, especially with a new OS.
Click to expand...
Click to collapse
Thank you! Good info!
OnePlus phones can be rooted as soon as you have the bootloader unlocked, and you have either TWRP booting (data decryption does not need to work), or stock recovery patched to accept ADB commands.
Once you can pull the stock kernel, you can patch it with Magisk, boot off it in fastboot, then direct install through Magisk inside the OS.
NotATreoFan said:
OnePlus phones can be rooted as soon as you have the bootloader unlocked, and you have either TWRP booting (data decryption does not need to work), or stock recovery patched to accept ADB commands.
Once you can pull the stock kernel, you can patch it with Magisk, boot off it in fastboot, then direct install through Magisk inside the OS.
Click to expand...
Click to collapse
Thanks! You gotta love companies who don't actively discourage or block rooting!
Can you confirm which TWRP version is working on R/11 for Oneplus? I see the instantnoodle version people are using for the 8/pro; will that do the trick? It has been a while since I had to root and I honestly forget if it is the root or unlocking the bootloader which wipes the device, but I at least hoped to get that done before setting up the device.
MNoisy said:
Thanks! You gotta love companies who don't actively discourage or block rooting!
Can you confirm which TWRP version is working on R/11 for oneplus? I see the instantnoodle version people are using for the 8/pro; will that do the trick?
Click to expand...
Click to collapse
I don't know what version is out there right now. My OP8T doesn't come until tomorrow, and I will be at least 40 days out from rooting since T-Mobile won't SIM unlock (generally) until that time, and you need to be SIM unlocked in order to unlock the bootloader.
Superguy said:
If you've around here awhile, you should know that you shouldn't ask about timelines. They'll be available when they're ready.
It's shipping with R out of the box and has new ways of doing things that will take time to figure out. Past availability times shouldn't be used to gauge availability on new phones.
Click to expand...
Click to collapse
What is wrong with you? Why are you being so toxic to someone asking a simple question?
Thanat0s24 said:
What is wrong with you? Why are you being so toxic to someone asking a simple question?
Click to expand...
Click to collapse
Actually, he's not toxic. He's just said the truth.
No sign of stock firmware zips yet, but I'd expect the MSM unbrick tools to be readily available this week.
MNoisy said:
Thanks! You gotta love companies who don't actively discourage or block rooting!
Can you confirm which TWRP version is working on R/11 for Oneplus? I see the instantnoodle version people are using for the 8/pro; will that do the trick? It has been a while since I had to root and I honestly forget if it is the root or unlocking the bootloader which wipes the device, but I at least hoped to get that done before setting up the device.
Click to expand...
Click to collapse
Just to follow up on this so others can avoid it, flashing TWRP does not work. Neither the TWRP vanilla edition nor the isntantnoodle edition worked and went straight to Qualcomm Crashdump mode in both.
I guess it is now a wait for the OTA to download