I noticed that in the screenshots and the attached guide the phone was running OxygenOs version 3.1.2 and the one I just recieved is running 3.1.3. (and I also have a update available) will the toolkit still work for my system version? I read many pages but couldn't find my answer.
Also, if possibe i'm looking to find if the toolkit works with the subsequent updates? Im assuming eventually the OTA's would take me to 3.2.1?
Thank you in advance!!!!!!!!!!
If you're talking about this toolkit, although I don't see any screenshots, I have used it yesterday to root my OnePlus 3. For me worked just fine except the "[1] Backup data" function.
Familotel said:
If you're talking about this toolkit, although I don't see any screenshots, I have used it yesterday to root my OnePlus 3. For me worked just fine except the "[1] Backup data" function.
Click to expand...
Click to collapse
Thank you for the reply! Yes, I was looking at that toolkit as well as others (with screenshots hahahaha) What Oxygen os version were you running when you rooted?
DanRyan85 said:
Thank you for the reply! Yes, I was looking at that toolkit as well as others (with screenshots hahahaha) What Oxygen os version were you running when you rooted?
Click to expand...
Click to collapse
The phone arrived yesterday.. so I got to work
OxygenOS version 3.2.1 (through OTA yesterday)
I rooted yesterday with that toolkit, Systemless root SuperSU 2.76.
Familotel said:
The phone arrived yesterday.. so I got to work
OxygenOS version 3.2.1 (through OTA yesterday)
I rooted yesterday with that toolkit, Systemless root SuperSU 2.76.
Click to expand...
Click to collapse
Thank you! I wasn't sure if it would work with the newest OxygenOS, and i didn't want any problems right off the bat, so that's awesome. I guess I'll just update and root then
DanRyan85 said:
Thank you! I wasn't sure if it would work with the newest OxygenOS, and i didn't want any problems right off the bat, so that's awesome. I guess I'll just update and root then
Click to expand...
Click to collapse
BTW, If you're interested in Xposed as well, I have just installed the Unofficial Systemless one by topjohnwu. The latest version 86.2, works like a charm
You really don't need a toolkit. Rooting this phone is childsplay...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Related
I installed the update today absent-mindedly.
I had rooted my device previously with Stumpy. No TWRP was present, and my recovery was the stock one.
Now, after the update, I have the update installed but have lost root yet Stumpy thinks I am rooted still.
What is the best way to fix this?
newbcake said:
I installed the update today absent-mindedly.
I had rooted my device previously with Stumpy. No TWRP was present, and my recovery was the stock one.
Now, after the update, I have the update installed but have lost root yet Stumpy thinks I am rooted still.
What is the best way to fix this?
Click to expand...
Click to collapse
Use PurpleDrake
mrfeuss said:
Use PurpleDrake
Click to expand...
Click to collapse
Agreed. PurpleDrake works for root still.
Recently I got a nexus 7 2013 5.1.1 LMY48I which I tried to root with NRT. Long story short like many other people I cant get TWRP to mount the files it needs(I get to the automated step that is suppose to open TWRP and install some files from a ZIP archive and it hangs up). First off I have a USB OTG cable coming within a couple days. I have looked for the past couple hours for a solution and keep coming up empty. Basically I have two questions, 1. what files do I need to have transferred so that I can get my Root permissions installed properly and 2. should I wait for the USB OTG calbe or should I try to use abs push
I'm in the same boat, really would like to get this thing rooted. I have been all over the WugFresh Forum, as well as Android Central and this one too of course. I have not found an answer to this problem yet. If I come across one I will post here, please do the same.
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
https://www.reddit.com/r/AndroidQue...e_to_mount_partitions_after_flashing_twrp_on/
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
gorilla p said:
Dude. this is infuriating. Apparently the alst batch that was made, they changed the mmc chip. These all went out on Groupon and stuff on sale.
The only recovery that I got to work was the TWRP for Multirom because they actually addressed the issue. The bug has been brought up on the TWRP flo github they just have yet to fix it.
This is infuriating
Click to expand...
Click to collapse
So what version of Android are you running now. I am on 6.0.1 and want to root it. Did you apply this to to Lollipop or Marshmallow? Thanks for the info.
UPDATE: This worked for me I am now on MM 6.0.1 and rooted. Thank you for the find.
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
sgtfoo said:
Yea we already have a thread for this..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Click to expand...
Click to collapse
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
AngryPotato said:
Thank you I was able to downgrade and root my device using that method. Now I just need to figure out how to flash to purenexus or just upgrade my device to 6.+ and root it.
Click to expand...
Click to collapse
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
diggitydogg said:
You can root 6.0.1 using the beta SU from Chainfire. I am running the new one from Groupon using the multirom TWRP and I flashed SU 2.65 and it worked perfectly.
Click to expand...
Click to collapse
so update to 6.0.1 stock then root or flash a rooted rom?
AngryPotato said:
so update to 6.0.1 stock then root or flash a rooted rom?
Click to expand...
Click to collapse
I did a clean flash of stock 6.0.1. Then flashed the multirom version of TWRP since I have one of the newer chipsets of the Nexus 7. Then I flashed the beta SU. All was good. The issue I am having now is that I can't get the restore from within TWRP to work. I backup fine, but when I restore it gets partway through the system part and then just says Failed. Not really sure what the deal is there. I am guessing it has to do with this multirom version of TWRP, but I'm not really sure...
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
cantsingh said:
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
Click to expand...
Click to collapse
That update permanently block root for your device
cwalker0906 said:
That update permanently block root for your device
Click to expand...
Click to collapse
Even if I have an unlocked bootloader already?
cantsingh said:
Even if I have an unlocked bootloader already?
Click to expand...
Click to collapse
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
cwalker0906 said:
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
Click to expand...
Click to collapse
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
cantsingh said:
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
Click to expand...
Click to collapse
Fastboot boot twrp alpha 2, flash the su zip, and reboot
cwalker0906 said:
Fastboot boot twrp alpha 2, flash the su zip, and reboot
Click to expand...
Click to collapse
Got it. Thanks, buddy. I'll post back here to confirm.
Confirmed. If you lost root when updating to NMF26O (or after installing TWRP RC1), then hot-boot TWRP Alpha 2 (fastboot boot twrp-alpha-2.img), flash supersu and reboot. Thanks!
confirmed - worked for me!
cantsingh said:
Got it. Thanks, buddy. I'll post back here to confirm.
Click to expand...
Click to collapse
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
miker2069 said:
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
Click to expand...
Click to collapse
You fastboot twrp rc1 but then flash the twrp rc1 zip and then it should be fine and then flash SuperSU 2.79 sr3.
Hi guys,
When nougat first came out, there was this huge hassle to update from a rooted op3. You needed a modified twrp etc etc. Is this still the way to update? Or can I just flash it through normal twrp? (And i suppose I have to flash supersu as well?)
Thanks!
Deleunes254 said:
Hi guys,
When nougat first came out, there was this huge hassle to update from a rooted op3. You needed a modified twrp etc etc. Is this still the way to update? Or can I just flash it through normal twrp? (And i suppose I have to flash supersu as well?)
Thanks!
Click to expand...
Click to collapse
The 'normal" TWRP is not fully compatible with Nougat and OP3. So you still need the modified ones. And SuperSU as well.
tnsmani said:
The 'normal" TWRP is not fully compatible with Nougat and OP3. So you still need the modified ones. And SuperSU as well.
Click to expand...
Click to collapse
Okay, thanks for the quick answer!
Any chance to post links to the modified TWRP and SuperSU? I can't seem to find those...
Squishy1991 said:
Any chance to post links to the modified TWRP and SuperSU? I can't seem to find those...
Click to expand...
Click to collapse
Here is TWRP: https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
For SuperSU, I am using 2.79: http://www.apkmirror.com/apk/chainf...79-release/supersu-2-79-android-apk-download/ If you need other versions, search with Google.
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
ttocs99 said:
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
Click to expand...
Click to collapse
Not yet. I'm on T-mobile.
mrpink10 said:
Not yet. I'm on T-mobile.
Click to expand...
Click to collapse
Same I spoke to Google support and they claim it's Al read available via ota
Haven't got it yet I bought my phone from Google.
Sent from my Nexus 5X using Tapatalk
Are you rooted? If so just get the ota from google and flash it with flashfire
jd1639 said:
Are you rooted? If so just get the ota from google and flash it with flashfire
Click to expand...
Click to collapse
Flashfire doesn't fully support Oreo yet so that's a no go, same with TWRP. ADB sideload might work.
I just flashed it this morning and had no problems.
I flashed a couple of hours ago official OTA package via ADB. No problems till now.
I took the plunge and flashed the 8.0 stock factory image the done a factory reset after to make sure and it been great ever since turned off animation and it's nippy just wish battery was about better but I'll give it a few days see if that goes
jd1639 said:
I just flashed it this morning and had no problems.
Click to expand...
Click to collapse
Did you use Flashfire?
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
jd1639 said:
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
Click to expand...
Click to collapse
Well then, I guess it's just when coming from the beta that it doesn't work. Thanks for the heads up.
ttocs99 said:
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Click to expand...
Click to collapse
Enable dev options and disable always keep mobile data on.
I just noticed that for some reason that is checked in oreo and it shouldn't be unless you are never on WIFI.
ttocs99 said:
Same I spoke to Google support and they claim it's Al read available via ota
Click to expand...
Click to collapse
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
I can confirm that jd1639's method works for people rooted with TWRP.
- download OTA (https://developers.google.com/android/ota)
- run Flashfire 60.0 (free version is OK)
- when asked "A system update has been detected", cancel
- Flash ZIP or OTA
- uncheck "restore boot and recovery images"
- press "EverRoot" and select "Inject SuperSU" and "Preserve recovery"
- Flash
- wait patiently
I tried flashing the modem FW using "Flash firmware package" on the OTA zip file. It rebooted and the screen went black for many minutes. I had to hard reset.
Can anyone confirm the 8.0 baseband? I have M8994F-2.6.39.3.03. I know that's the baseband for the 8.0 developer preview, but I wanted to make sure it was the final.
Billys20 said:
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
Click to expand...
Click to collapse
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
Nope
Sent from my Nexus 5X using Tapatalk
tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Billys20 said:
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Click to expand...
Click to collapse
6p here, downloaded ota (NOT factory), ran Tibu, ran Flashfire 7.0 pro as described and after three reboots and a while of booted finishing, was cleanly updated to 8.0.0. took < 20 min. [emoji2]
Sent from my Nexus 6P using Tapatalk