Database Users

AT&T Samsung Galaxy S7 G930A Root Install Instructions?

If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated

There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk

twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay

OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks

thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can

Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.

thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?

Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33

twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?

Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.

I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar

P9 Lite booting lock

Hi all, i'm new to Android Phones, so i started a few days with this phone. But now i think i've done a big mistake, i tried to erase everything from the phone, in a hope to "restore" to the factory state. Instead, i think i've deleted everything from the phone, and now, it only says "Your device is booting now..." and it doesn't boot. It's unlocked and rooted, i've deleted it from the TWRP menu.
So, is there anything that i can do, to restore it back? The model i think it's the VNS-L31, i'm downloading a firmware from the L21, can it be replaced or something like that? Thankx in advance.
*Edit* I found stock rom for my phone here in the fórum, but it says i need to have stock recovery but i have the TWRP recovery. Is there any way that i can do it, with that recovery?
*Edit 2* In Erecovery, when i try to download it says "Getting package info failed"

First of all... Why don't you have a backup in TWRP? ALWAYS back up your stuff before doing ANYTHING in TWRP.
Second: there is an option for factory reset within the EMUI system itself. Absolutely no need to mess around in TWRP for something like that. Of course you can "factory reset" in TWRP but this can also wipe your system which then requires you to flash something.
To your problem:
Since I luckily was not forced to flash a stock firmware yet, some more information would be nice.
In which format does the firmware come (link to where you downloaded it)? TWRP can handle .zip files. So if it comes as a .zip file, you can try flashing it through TWRP (really depends on what you downloaded!)
If you only need stock recovery, try accessing TWRP with your phone plugged into a PC.
This way it normally fires up the stock eRecovery.

Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.

iDeadSmack said:
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
Click to expand...
Click to collapse
Hmm maybe best way is to send the user that made it work a PM and maybe he can provide you a guide on how to do it.
And maybe he or you can then provide a guide here on how to do it.
This device is rather new and the forum is building up so there is a lot of work to do and a lot of things have to be worked around.
Hope you can fix it, like I said, I cannot really help you properly since I never had the problem and therefore do not really understand what's happening on your device.

hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You

iDeadSmack said:
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
Click to expand...
Click to collapse
Could you help me with this problem i have the same problem on Huawei l-21 ??

Always have a backup of your fresh system on TWRP. Then whatever happen just restore it whenever you think you messed up your device and you should be fine ALWAYS.

Is there any ROM/Root method for G360T1?

Hello everyone actually I have a G360T1 with the latest system update (G360T1UVU1AGP2) and I want to customize my phone, root it and/or install a custom ROM but it's my first time messing around with a Samsung phone and I need some help because I don't want to do something wrong with my phone

BEFORE YOU DO ANYTHING ENABLE DEVELOPER OPTIONS AND ENABLED OEM UNLOCKING AND USB DEBUGGING! Use Chainfires auto root method. Google cf auto root and find the page. Use ctrl-f to search for sm-g360t1 and download the appropriate file (it will be .zip) Extract it (make sure you have USB drivers from Samsung) Put you phone in download more (turn it off, then turn it on while holding home, power, and volume down buttons at the same time. Press the volume up bottom to continue) Run the Odin program and then plug your phone in while in download mode. Make sure it says connected. Next click the AP button in Odin and select the cf auto root .md5 you extracted earlier. Click start. The phone will reboot and root itself. If it seems to restart more than 3 times just pull the battery out and pop it back in. TADAH! YOU'RE NOW ROOTED!

syran123 said:
BEFORE YOU DO ANYTHING ENABLE DEVELOPER OPTIONS AND ENABLED OEM UNLOCKING AND USB DEBUGGING! Use Chainfires auto root method. Google cf auto root and find the page. Use ctrl-f to search for sm-g360t1 and download the appropriate file (it will be .zip) Extract it (make sure you have USB drivers from Samsung) Put you phone in download more (turn it off, then turn it on while holding home, power, and volume down buttons at the same time. Press the volume up bottom to continue) Run the Odin program and then plug your phone in while in download mode. Make sure it says connected. Next click the AP button in Odin and select the cf auto root .md5 you extracted earlier. Click start. The phone will reboot and root itself. If it seems to restart more than 3 times just pull the battery out and pop it back in. TADAH! YOU'RE NOW ROOTED!
Click to expand...
Click to collapse
That sounds pretty easy, but do I need a custom recovery? Also, does this method have any consequences?

Auraburst said:
That sounds pretty easy, but do I need a custom recovery? Also, does this method have any consequences?
Click to expand...
Click to collapse
With this method you do not need a custom recovery. However, I would suggest that you still get one so you can perform backups and restores. There are a few consequences but nothing major. When the phone boots it will have a small line of text that said "set warranty bit: kernel" and also with all rooting processes your warranty will be void.
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
If you have any more questions keep them coming. I've bricked this phone a few times so I know how scary it can be so if I didn't explain something well tell me and I will do better. I would hate for you to brick yours because I said something poorly

syran123 said:
With this method you do not need a custom recovery. However, I would suggest that you still get one so you can perform backups and restores. There are a few consequences but nothing major. When the phone boots it will have a small line of text that said "set warranty bit: kernel" and also with all rooting processes your warranty will be void.
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
If you have any more questions keep them coming. I've bricked this phone a few times so I know how scary it can be so if I didn't explain something well tell me and I will do better. I would hate for you to brick yours because I said something poorly
Click to expand...
Click to collapse
Well, now I understand a little more, just a few questions, which custom recovery should I use? I've read about TWRP is available for this phone, also, what should i avoid to install or do with the stock ROM and don't brick my phone? As I said, it's my first time messing around with a Samsung phone and it's my main and only phone atm

As far as I know TWRP is the only available custom recovery at this time. I would suggest getting the unofficial one created by shinyside because the official one has a few issues. Some things you should not do with this phone is use a reboot app to reboot to things like boot loader and recovery. If you need to access special boot modes such as those I would recommend just using the correct button combo. Also if at some point you want to get xposed make sure you check and double check that it is the version for Samsung phones and your arm version. If you do successfully install the xposed framework make sure the modules you download are for touchwiz/Samsung.My two major pieces of advice though would be to have the stock ROM and Odin on your pc at ALL times. And if you plan on changing any thing on the system (such as build.prop) make sure you do a backup with TWRP. If something goes wrong first try using twrp recover and if that doesn't fix it use Odin. I've bricked this phone several different ways and Odin has always fixed the issues. Mostly just be careful when you see something you want to change. Samsung does a lot of modifications to android so not everything works correctly. However, once you get everything running nice and smooth it is the best thing EVER!
---------- Post added at 03:37 AM ---------- Previous post was at 03:34 AM ----------
To summarize the above post stay away from xposed till your 100% sure of what your doing. Don't use a 3rd party app to restart the phone, you WILL get stuck in a bootloop(this includes xposed modules) Make sure to have a TWRP backup before you change anything. And finally have the stock ROM on your PC at all times (including Odin) so that you can restore at any time. It may suck to reset but it's a lot better than a bricked phone.

I forgot one last thing. When you are leaving the TWRP recovery to go back to android DO NOT let it install supersu. If you do it will brick the phone. Other than that it should work perfectly.

syran123 said:
As far as I know TWRP is the only available custom recovery at this time. I would suggest getting the unofficial one created by shinyside because the official one has a few issues. Some things you should not do with this phone is use a reboot app to reboot to things like boot loader and recovery. If you need to access special boot modes such as those I would recommend just using the correct button combo. Also if at some point you want to get xposed make sure you check and double check that it is the version for Samsung phones and your arm version. If you do successfully install the xposed framework make sure the modules you download are for touchwiz/Samsung.My two major pieces of advice though would be to have the stock ROM and Odin on your pc at ALL times. And if you plan on changing any thing on the system (such as build.prop) make sure you do a backup with TWRP. If something goes wrong first try using twrp recover and if that doesn't fix it use Odin. I've bricked this phone several different ways and Odin has always fixed the issues. Mostly just be careful when you see something you want to change. Samsung does a lot of modifications to android so not everything works correctly. However, once you get everything running nice and smooth it is the best thing EVER!
---------- Post added at 03:37 AM ---------- Previous post was at 03:34 AM ----------
To summarize the above post stay away from xposed till your 100% sure of what your doing. Don't use a 3rd party app to restart the phone, you WILL get stuck in a bootloop(this includes xposed modules) Make sure to have a TWRP backup before you change anything. And finally have the stock ROM on your PC at all times (including Odin) so that you can restore at any time. It may suck to reset but it's a lot better than a bricked phone.
Click to expand...
Click to collapse
syran123 said:
I forgot one last thing. When you are leaving the TWRP recovery to go back to android DO NOT let it install supersu. If you do it will brick the phone. Other than that it should work perfectly.
Click to expand...
Click to collapse
I did it without problems, thanks a lot! :victory:
Something i've noticed after i rooted my phone: Sometimes the system freezes randomly, but is only a issue that happens a few hours after i've rooted, now works as usual

Check out this thread. It has everything you need for this device
http://forum.xda-developers.com/gal...des-faq-one-stop-shop-metropcs-t3266173/page1
I can confirm almost all of these working perfectly as I have this device and it is my daily driver
Hope this helps

HardBricked OP5, plz help! :(

Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(

Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine

I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse

Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.

bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.

cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.

bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.

I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?

Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol

Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.

Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.

I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro

Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff

Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only

After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?

cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )

Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.

I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.

david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out

Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!

Attempting to root and install Android 10 on Nexus 6P. Noob needs help!!!

Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you

xa3phod said:
Hey folks. I am seriously stumped and I can't figure this out.
I want to install Android 10 on my 6P. I figured I would have to root it first. I installed TWRP 3.3.1.0-FBE-10-angler.
I successfully did OEM Unlocking.
I Pushed Beta-SuperSU-v2.67-20160121175247 and it seemed to install fine.
I reboot and its not there. It should be in the apps, but its not. What am I missing? Should I do Magisk? This is new for me and once I get it, I won't have to ask again.
I also have the PixelExperience_angler-10.0-20200101-0925-OFFICIAL. I have not installed this yet, but this is the image I want, I believe.
Any advice is appreciated.
Thank you
Click to expand...
Click to collapse
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?

Ata Ur Rehman said:
Hey, Did you follow the instructions mentioned in Pixel Experience thread one by one as they are?
Click to expand...
Click to collapse
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?

xa3phod said:
I was still stuck on the earlier problems. Before I went in and completely destroyed this phone, I wanted to make sure I was not missing something fundemental.
Also, for some reason the phone always pops out of data transfer mode. Do you think its my USB C cable that's losing the connection?
Click to expand...
Click to collapse
Probably It is losing connection to PC try another cable and reinstall and drivers on your PC.
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
You can follow this video for detailed installation ( keep in mind if you aren't a BLOD user so you just skip flashing 4 core files )

Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!

xa3phod said:
Another issue: I installed TRWP and I was able to get into TRWP just fine. But, if I reboot and go into recovery I get the robot on his back with the triangle over it. I have reinstalled TWRP 3 times, but this keeps happening. Before I install a new ROM, I think I should know why this is happening and how to fix it.
Thanks again!
Click to expand...
Click to collapse
Did you Turn OEM unlocking on?
Did you have flashing and downlaod mode unlocked?