Related
Long story short, I messed up and soft bricked my OG Shield, and I need someone to upload the OEM Image files.
I would also like it if someone would provide download links to a semi stable version of TWRP and a SuperSU binary for 6.0.
Crayman122 said:
Long story short, I messed up and soft bricked my OG Shield, and I need someone to upload the OEM Image files.
I would also like it if someone would provide download links to a semi stable version of TWRP and a SuperSU binary for 6.0.
Click to expand...
Click to collapse
+1 but i think we will have to wait for nvidia to release them.
I'm trayng to downgrade using lollipop recovery image 3.1.1. installation looks ok but tablet get stuck at nvida logo.
lupick said:
I'm trayng to downgrade using lollipop recovery image 3.1.1. installation looks ok but tablet get stuck at nvida logo.
Click to expand...
Click to collapse
Wrong boot image. Need to flash lollipop boot Image
lupick said:
I'm trayng to downgrade using lollipop recovery image 3.1.1. installation looks ok but tablet get stuck at nvida logo.
Click to expand...
Click to collapse
same. got this after flashing supersu
FIXED!!! Found a download link to the update.zip burried in some other forum. Now I just need someone to provide a link to a working SuperSU and xposed framework for OG ST
I had the same problem, I got out of bootloop by flashing the 4.0 update and SuperSU in two steps:
1st flash update zip, clear caches and reboot
2nd flash SuperSU 2.67 and reboot
Of course you will need the experimental twrp for marshmallow
Hope it works for you like it did for me.
Good luck!
Crayman122 said:
FIXED!!! Found a download link to the update.zip burried in some other forum. Now I just need someone to provide a link to a working SuperSU and xposed framework for OG ST
Click to expand...
Click to collapse
Did you flash it through fastboot?
sshep1986 said:
Did you flash it through fastboot?
Click to expand...
Click to collapse
No. I flashed the file through twrp unstable. I didn't flash twrp as recovery, but you can use this to boot twrp without flashing and it still works fine:
Code:
fastboot boot <twrp recovery for shield>.img
Here is the link for the TWRP Recovery. It's a little bit unstable, but it still works ok-ish. UI is REALLY glitchy, that's why I didn't flash, but core functionality is still there.
Crayman122 said:
No. I flashed the file through twrp unstable. I didn't flash twrp as recovery, but you can use this to boot twrp without flashing and it still works fine:
Code:
fastboot boot <twrp recovery for shield>.img
Here is the link for the TWRP Recovery. It's a little bit unstable, but it still works ok-ish. UI is REALLY glitchy, that's why I didn't flash, but core functionality is still there.
Click to expand...
Click to collapse
Thankyou very much. Appreciate the reply. Unfortunately mine hangs on the booting downloaded image. Still got my spare Shield to use for now. I will have to wait for the release of the factory image. Hopefully wont take forever. Cheers
lowsum said:
i had the same problem, i got out of bootloop by flashing the 4.0 update and supersu in two steps:
1st flash update zip, clear caches and reboot
2nd flash supersu 2.67 and reboot
of course you will need the experimental twrp for marshmallow
hope it works for you like it did for me.
Good luck!
Click to expand...
Click to collapse
thank you so much!!!! You saved me from the hell of stock android!!!
Hi all, I have a bit of a strange problem that is I cant update my twrp recovery from twrp, flashify or fastboot the only way I can update is from twrp manager. every time I try and flash it it says it has done but when I try and boot into recovery it just goes to the oneplus screen and no further! had a bit of a look on the forums but couldn't find anything, any help greatly appreciated,
thanks
edit: I can upgrade from twrp itself from 2..... to 3.0.0 but not from 3.0.0 to 3.0.0.1 or 3.0.0.2
matt_simpson said:
Hi all, I have a bit of a strange problem that is I cant update my twrp recovery from twrp, flashify or fastboot the only way I can update is from twrp manager. every time I try and flash it it says it has done but when I try and boot into recovery it just goes to the oneplus screen and no further! had a bit of a look on the forums but couldn't find anything, any help greatly appreciated,
thanks
edit: I can upgrade from twrp itself from 2..... to 3.0.0 but not from 3.0.0 to 3.0.0.1 or 3.0.0.2
Click to expand...
Click to collapse
flash through adb.
krishna442 said:
flash through adb.
Click to expand...
Click to collapse
Just done that, thanks (but still cant understand what the issue is of doing it the easy way.
matt_simpson said:
Just done that, thanks (but still cant understand what the issue is of doing it the easy way.
Click to expand...
Click to collapse
Yes. You installed official twrp 2.8.7.0?? I didn't try updating twrp through twrp. If I did I could've provided assistance.
I can't take anything easily, so if at all I have something new to do, I'll start from the beginning. Lol.
Sent from my ONE A2003 using Tapatalk
hello everyone.. i just updated to 7.0 using ADB. that went smooth. rebooted into the system played with 7.0 for a bit . then i notice i didnt have root any more. i read that we needed to install twrp 3.0.2.3 for 7.0. so i installed twrp 3.0.2.3 with ADB. then i flash superSU v2.78 stable. now my phone stays in the colorfull circles screen. its been that way for 45mins. i am at a lost. what is the next step i should take??
As far as I know there's no TWRP 3.0.2-3 for angler. You should only download from TWRP.
Current version (3.0.2-2) here: https://dl.twrp.me/angler/twrp-3.0.2-2-angler.img.html
Flash current version with fastboot.
Pig Vomit said:
As far as I know there's no TWRP 3.0.2-3 for angler. You should only download from TWRP.
Current version (3.0.2-2) here: https://dl.twrp.me/angler/twrp-3.0.2-2-angler.img.html
Flash current version with fastboot.
Click to expand...
Click to collapse
3023 is a fixed unofficial version
Pig Vomit said:
As far as I know there's no TWRP 3.0.2-3 for angler. You should only download from TWRP.
Current version (3.0.2-2) here: https://dl.twrp.me/angler/twrp-3.0.2-2-angler.img.html
Flash current version with fastboot.
Click to expand...
Click to collapse
Gee, hard to see how bad info gets around. -2 is buggy on large backups. Unofficial -3 is the version to use.
Sent from my Nexus 6P using Tapatalk
ok .. some help please..
Lw00d said:
ok .. some help please..
Click to expand...
Click to collapse
Did you try flashing boot and system again?
istperson said:
Did you try flashing boot and system again?
Click to expand...
Click to collapse
no i have not.. i will try now
This couldn't be a problem with the unofficial TWRP could it? Always some risk involved when trying such new and relatively untested software
ok i updated to the new 7.0.0 (NBD91K) . everything went smooth.. booted up system send some text. bc phone would not boot up.. then i go to flash superUS v2.78 SR3. i thougt maybe that will help. im using twrp 3.0.2-3. i flash> wipe cache/dalvik > reboot. phone will not boot up..
is there another way i could flash superSU. other then twrp.. ????
EDIT:: im going to try installing 7.0.0 (NRD90U) .. see if superSU works
no that didnt work either.
Seems like a familiar issue as in the WETA ROM thread. Can you use cf-auto root instead of flashing SuperSU?
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting.
1. Download the ADB For Windows from here :-
https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k/view
2. TWRP: https://mega.nz/#!v9MmGQ5C!i5VroRopCVz2_Uoc6Mi2U6N4oDa0HK1SxCrkDrc4mwQ
3. SuperSu: https://mega.nz/#!eh13yLiC!3tkx_RkLg-D8T6mi35zDUB8AYEPLliBsL8yO1dmZbI8
Steps:
1.Backup Data
2.Unlock boot loader
3.Flash Recovery
4.Flash SuperSU
ENJOY
Video:
https://youtu.be/wwd31NU7VC0
Rooting OOS 4.0.3 ONEPLUS 3T
https://youtu.be/0QYp5tkBaao
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Simply flash the full ROM.zip manually in recovery, typically 1.4GB.
That means not installing the incremental mini zips. And not installing from the settings menu.
It's up to you whether you want to wipe data or cache.
Midomad said:
Thanks for the nice guide!
What would be the clean method to flash future OOS update when rooted and with TWRP recovery?
Click to expand...
Click to collapse
Download complete zip file n flash using two.
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
yes if u follow the steps you wont have DM verity issuse.
uttam.ace said:
Thanks for nice guide, Just one question so dm verity error would never bother me with this method as I would like to be remain encrypted for some time being.
Click to expand...
Click to collapse
Dm verity zip is not needed when you flash SuperSu.
*winces* Ooh, all the files on file hosts? Why not just link to the legit sites?
Very easy to download the required files. Very simple step-by-step video guide. A+
Thanks for putting this together you made my night!
Thanks, I have unlocked bootloader, Installed TWRP, and Super Su.
one question though, when after setting my account going for nandroid backup there I found SYSTEM as well SYSTEM IMAGE.
what is difference between them, What thing should I backup.
Also there is showing your system is Unmounted, so when I should have to mount it.
Thanks to all Once again.
Hello guys, thanks for the guide!
I was wondering if anyone has faced the same problem as me - while trying to root the Oneplus 3T I constantly get a bootloop after flashing SuperSU. The latest TWRP (3.0.4.0) is installed without any problems in fastboot, the system is mounted as r/w, and I don't see any problems during flashing SuperSU package...
I've tried it before and after OOS 4.0.2, I've tried old and new, stable and beta versions of SuperSU, but either way the phone is stuck on bootscreen after flashing.
P. S. If I flash the official ROM after that - it boots up instantly without any errors... And with no root :/
I'm having the same problem
respectableafrican said:
I'm having the same problem
Click to expand...
Click to collapse
So nice to know I'm not alone!
Did you find a way to root your phone?
Try this SuperSU
I heard only SuperSU SR3 works
Just tried both versions (2.79 and the SR3 beta) - unfortunately, the same bootloop happens.
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
nishant.roy24 said:
I flash twrp 3.0.4 then flashed RR N rom but twrp is not booting to system it boot again to twrp please help
Click to expand...
Click to collapse
Power off and boot instead of selecting reboot from twrp
hrsa said:
So nice to know I'm not alone!
Did you find a way to root your phone?
Click to expand...
Click to collapse
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
respectableafrican said:
Oh yeah actually I did, just use the systemless root guide on r/oneplus (cant link because im new)
Click to expand...
Click to collapse
Oh, finally - thank you so much!
Followed the guide on reddit page, and got the Magisk root, with Android Pay compatibility!
I wonder why it was so hard to find
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good: