Database Users

Vibrant USB Connection Issue

Hello XDA Community!
I made a post about this issue before, but have more details so hopefully someone can help me figure out this issue.
My phone even when unplugged from my PC continuously says USB Connected/ USB Debugging in the notification menu.
Also, when I try and reboot the phone, instead of booting even to the Vibrant logo screen, the loading circle continuously blinks on and off, without actually booting.
As I type this, I am not holding down the power button, and the loading circle is blinking on and off by itself....
I used to be able to turn the phone on into recovery mode in the past, but now when I try to reboot into recovery I get a big yellow picture that says "Downloading"
The only way the phone will turn on is if it is plugged in.
I am fairly certain that this reboot issue and the USB issue are correlated in some way.
Did anyone else have this issue with their phones? And if so, how did you solve it?

Another thing I have just discovered...
When the phone is on and idle, the USB Connection notification will constantly blink on and off, which is why I think the phone would do the same when trying to power on!
Is this a hardware issue or a software issue?
I have not flashed anything in a very long time before this issue started happening so I believe a restore is unnecessary .
Someone please help me! This is very annoying, not only do I have NO notification bar because of the constant USB Connection notification turning on and off, I cannot turn on my phone at all unless it is plugged in!
ACK!

Take it back
I carry the insurance, so personally if this was happening to me I would not even mess with it. It sounds like you have a genuine problem with the phone and it needs to be replaced.
If it is possible to do try a nandroid backup of your phone to make getting back to where you are on your new device easier. Then take your phone back to stock with the recovery image here -->
http://forum.xda-developers.com/showthread.php?t=734475 (Thank you justanothercrowd)
One you have a stock device see if you are still having the issue. If you are take it back as defective. Even if you don't have the insurance, that sounds like a factory defect and should be covered by the factory warranty. The insurance just makes the process easier and makes sure they just give you a swap out at the store rather than having to wait for repairs. It also covers things the warranty does not, such as screen breakage - which is the specific reason I carry the insurance.

Ah crap wish I had insurance.... Do I have to do that whole odin procedure or is there a one click un root procedure as well?
Sent from my SGH-T959 using XDA App

Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App

I actually have not had reason to go back to stock, or even use odin yet at this point. My only roms were .zip files that I flashed via clockwork recovery.
I would say that your best best it to just follow the instructions on justanothercrowd's thread very carefully and deliberately. You are already having issues with reboots and your USB port, so this is not the time to deviate into experiments.
So to cut you off and just answer you next three questions:
Q) Can I just . . .
A) No! Just follow the directions exactly.
Q) But can I . . .
A) No! Just follow the directions exactly.
Q) Do I have to . . .
A) Hey look, Just follow the damn directions exactly!
Sorry, I can't help much beyond that. You chose to modify your phone and risk that you would not have issues, just like the rest of us here. In your case you did have issues. Now you have to get it back to stock so they don't have any reason to claim you caused this or that your warranty is void. I hope all goes well and it works out for you. Let as know and keep us posted. Good luck.

Lo N Slo said:
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
We must have been typing at the same time LOL.
There is a thread on unrooting, and basically it is just deleting a few things. After doing this you should not have any non-stock applications on the phone and there would be no reason to think it was rooted unless they went digging on the file system. Personally, I would delete those telltale files just in case, it looks a little suspicious to bring in a phone that looks like it has not been used since you bought it, but they have no proof you did anything and you can claim that you first did a factory reset to see if it would fix the problem.

Just want to keep this thread going, as I am having the exact same issue as the OP as of today. It happened out of the blue, and I haven't flashed anything new to my phone since JI6 was released, other than that, it's just a stock, rooted phone.
Hoping someone has an idea, but I will likely get it replaced under warranty, since the GPS has never worked either.

damnit damnit damnit I really wish I had warranty.
Random question about clockword mod recoveries.
If I were to do a backup right now, and save that file to my computer, could I restore that file later on a different phone after I root my replacement?
I don't have that many mods flashed, and I know all of the apps can be synced, but still it would be sooo convenient .

I believe that is how it works, so yes. It should be no different then when you clone a hard drive to put the image on multiple computers for easy distribution.
It is (just like the cloning metaphor) hardware specific. Just like I could not purchase a upgrade computer and expect a cloned image to work, don't expect to create a Vibrant backup and restore it on a Captivate.
That said, you should be able to restore your backup to new (identical) hardware.
By the way, what is the warranty on these? I thought it was a year for defects. I didn't think the Vibrant had been around long enough yet for anyone to be off warranty.

it should be a year, but there was also the option for a purchased warranty. I did not purchase a warranty, so I should be good on just my manufacturer's defect warranty

Being discussed here:
http://forum.xda-developers.com/showthread.php?t=817643

Real TRUE Brick this time

[PROBLEM SOLVED]
Ive been flashing back and forth to different builds trying which is better. I made sure I took the cautions not to flash builds that would brick my phone. There were 4 times that I soft bricked my phone but I was able to revive it. However, my little game has come to an end with this last one. The fault was this guide: http://forum.xda-developers.com/showthread.php?t=817186.
Little did I know, by doing a repartition and not loading anything to the NAND resulted in the bootloader not being installed. (Devices like this should have a ROM programmed to recover from these errors, think Gigabyte) Upon reset, the phone went out and didn't turn back on. ODIN reports success. Now the phone cannot turn back on, no matter what battery pull method I use, I get nothing on the screen. So much for fail-safe protocols Samsung has implemented, if there are even any. Poorly engineered!
EDIT:Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
EDIT 2: I am wrong about the bootloader being hardware. Some say it is flashable, so it is possible you can get a real TRUE brick and must need JTAG to revive it. Fortunately for me, I was able to use the USB JIG method to get it back up and running. Too bad, a new phone would've been nice.

Not poorly engineered, just poorly made user input.

Yes true, but samsung should have taken into account accidents like this will happen then they dont have control over who administers their update. People have bricked their phones by doing the factory update. When I design systems like these, I always make sure there is a fail safe backup that the user cannot modify. I am sure samsung has one and maybe they just dont let us access it.

I sometimes encounter the same error message but I never repartition. Luckily, i never clicked on it in Odin.

But you have to realize that most of those bricks are because people modified their phones from factory (ie. Voodoo and OCLF). Odin, a program used by internal Samsung engineers, was never meant for the public and shouldn't be used unless you know how to use it.
I agree, there should be an absolute fail safe if worse comes to worse, but the point I am making here is Samsung isn't wrong in this case.

When you violate warranties and experiment you tacitly accept responsibility for your actions. To not do so is not an act of rebellious ire...it is an act of denial.
Manufacturers do not, nor can not prepare for all scenarios because the possible number of scenario's to cover are legion. I don't see it as realistic especially for them to prepare for brick scenario's created by using a leaked internal engineering tool that the community has figured out largely through trial and error either. OTA and Mini Kies bricks they are responsible for, for obvious reasons, and Samsung and T-Mobile have taken responsibility for these scenarios because they are ones of their making.
XDA is not a place where people file warranty complaints (though some do complain). It is a place where people experiment, hack, and customize smartphones. Though some manufacturers do a better job than others at getting out of our way here (Samsung hasn't done so bad here relative to say Motorola), I don't think any of them particularly "care" about such community efforts in any meaningful sense. And why should they?
By modifying our devices aren't we quite clearly saying we're taking matters into our own hands? You have to balance your strong desire to tinker with the reality of where responsibilities lie.
These phones are some of the most difficult Android phones to brick. Anecdotally and statistically shown to be. Not impossible of course, but quite difficult. I feel for your bad experience but at least consider shouldering some of the blame.

Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?

I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?

Have you tried the jig method of getting into dl mode?

engineer14 said:
Thank god i am too scared to use odin. The deepest i go is clockwork recovery, but good luck with your paperweight.
Too bad the SGS is so light, it wouldnt make a good paperweight, or even a brick.
but seriously, the warranty is there to protect users which this happens to, assuming it wasnt voided by hacking the phone. Are you asking samsung to take into account that you would hack the phone and provide a way back after you have a bad hack and probably make themselves liable by providing that way back in case it does not work properly?
Click to expand...
Click to collapse
Keep on flashing, and eventually Odin will probably save your butt
Don't be scared of it, it works great. And it is safe to use.
========================================
I'm really sorry about your phone man, I didn't know that you had to NAND before re-partition, thank god I've never checked that but I might have in the future had you not shared this with us, so thanks a lot!
I guess your loss is everyone elses gain

No I havent tried the Jig method. The thread says that I need to have at least the samsung screen, so some kind of activity. This phone is just off, nothing comes on, no buttons, no screen...just dead. I think when I followed that guide, it told be to repartition and then reboot with the "PDA" field empty. So the phone rebooted when it finished formatting without installing anything. Now the NAND is at a "blank" state and I do not have any bootloader on there. Anyone know of a method to install a bootloader without the phone turning on?

I might be a little too far out of my element here but I think I found a guide to remove the sdcard and format it via pc one time when I was in a similar situation. I am at work currently and I also cannot remember if I have the link saved.

Maybe some phone expert in your city may help you to install the bootlaoder. I think it's called jtagging, I'm not sure though.
Sent from my SGH-T959 using XDA App

trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Just call Tmobile and tell then that you were upgrading to froyo 2.2 using Kies mini and it froze...

I had a black screen once. I was flashing in odin and knocked the cable loose. I think I had to remove the battery, open odin, plug the usb cable in, then install the battery and possibly hold a key down on the phone. I believe the download screen then came up. Otherwise the phone would not respond nor would any lights come on

trdexalbee said:
I want to be clear that I am not blaming samsung for this but I thought samsung could have done a better job. Ill admit, this phone was the first phone that impressed me in years and as an engineer, I am hardly ever impressed; other engineers will get my point. I wish they had some soft of fail safe mechanism. For us who like to tweak things, I get we get what we deserve. But what about those who dont like to tweak and still brick their phones? i.e. those who use Kies Mini and still brick. I still have warranty on the phone and I'll try to take it up with Tmobile, hope they don know much about flashing. BTW, I tried using the other program but no go. All the drivers were installed, rebooted computer...nothing. I think it is because I have W7 64 and not 32?
Click to expand...
Click to collapse
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.

masterotaku said:
Depending on which drivers you installed (and there seem to be quite a few floating around) you might need to disable Driver Signature Checking in 64bit Windows OS's if the drivers are not signed. The easiest way I've found to do this is with EasyBCD . Install it, run it, click Advanced Options and enable loading of unsigned drivers. Do this before loading a potentially unsigned driver and you're good to go.
Just a tip, and my lengthy diatribe on responsibility was more to stem the potential tide of trolling such a thread is likely to generate than dump on you. I know what it's like to brick things. I've been bricking stuff for 30 years lol.
Click to expand...
Click to collapse
To disable driver signing, you ONLY need to run a single command and then reboot. And this applies to both Windows 7 and Vista.
Also to the OP.
You say you have no bootloader, but can't find ANYWHERE in this thread that says you were attempting to flash a bootloader. In fact, you can **** up partitioning, and your bootloader is still in tact. Been there, done that.
Do this. Plug the phone in, and leave it charging for about 30 minutes. Pull the phone off, hold the volume buttons, and plug the phone into a computer. See what happens. I had a ****ty situation end up happening to me, that I couldn't get the phone on for about 30 minutes. I had already even called T-Mobile for a replacement.

Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.

trdexalbee said:
Thanks for all your suggestions guys. So yes this phone was definitely bricked beyond any software repair. I was going to JTAG it but I figured there MUST to be some hardware bootloader implemented. I went ahead and did the USB JIG and surprise, it booted from the hardware bootloader. I used ODIN to flash JFD and it works now. So my guess is samsung did implement a fail safe, which is the USB trick and forces the phone to boot from hardware. If that is true, this phone is brick proof, provided that all electronics still work.
Click to expand...
Click to collapse
This "hardware" bootloader as you are calling it, is the exact bootloader that you can flash and TRULY brick your device. It is NOT a failsafe in the way in which you are referring. Please, please don't call it this. There are plenty of users on this forum that are clueless. The jig method, is a hardware jump point that Samsung has built in to allow you to get to download mode situations where the button method does not work.
As I mentioned earlier, you didn't flash a bootloader. Nor did you full on brick your device. Glad your device is back to normal now though.

my apologies then, it would be easier if samsung gave us the schematics, but that would never happen. So when we use odin to flash, we are not flashing the bootloader as well? Is the bootloader located on another ROM that is not easily accessible? I guess ROM would be the incorrect term since you stated you can "flash" the bootloader.

Need Help with APX Mode Brick.

Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app

I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app

I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986

You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!

I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.

Bricked beyond repair?

So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.

Just to rule out the obvious, have you tried different cable and computer?

gabriwinter said:
Just to rule out the obvious, have you tried different cable and computer?
Click to expand...
Click to collapse
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.

godraistlin said:
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
Click to expand...
Click to collapse
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.

How did you brick your OP in the first place? Does it still charge?

Z-Blade said:
How did you brick your OP in the first place? Does it still charge?
Click to expand...
Click to collapse
It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.

gabriwinter said:
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
Click to expand...
Click to collapse
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.

The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.

godraistlin said:
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
Click to expand...
Click to collapse
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.

Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.

Did you try holding power button for >40 seconds?

godraistlin said:
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Click to expand...
Click to collapse
If it's totalled then one plus will have no idea what is wrong either, send it back mate.

After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.

dladz said:
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

GAMIT PRUTHVI said:
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

gabriwinter said:
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

jhs39 said:
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

Cannot use Google PAY

I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.

chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
Did you convert your tmobile to international ? I guess you did. So either root it and install magisk or livr without Google pay.
Sent from my [device_name] using XDA-Developers Legacy app

chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.

Krzysiek_CK said:
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Click to expand...
Click to collapse
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?

chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
Well you can't do really anything but if you have not had it too long you could return it.

chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
You have 3 options:
1. DO nothing and hope OnePlus will fix it down the road. I actually lost hope with this one.
2. Load T-Mobile version, and loose dual sim capability. Google Play will pass certification and Google Pay will work.
3. Use Magisk, at your own risk, to trick SafetyNet check.

I have one of those scammy "no warranty" T-mo -> Intl. OnePlus 6T and, with enough work, it is possible to convert to the most recent Intl. android 10, and get root and Google pay working. I don't think at this time it's possible to watch Netflix in HD while having your cake and eating it too, sadly. The A/B situation on this phone is painfully confusing and leads to brick after brick as you learn the ropes of this phone. Not sure that's TMo's fault. Thankfully the bricks are fixable. You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
So that gets you to an equivalent to a locked Global 9.0.11 rom with no OTA updates. From there you can do developer mode -> unlock bootloader instantly from fastboot -> (loose all your data) -> TWRP; now the a/b stuff gets really confusing AF but if you do TWRP from fastboot->flash 10.3.2 -> TWRP from fastboot again (it's like ms windows!) -> flash TWRP .zip installer -> TWRP from fastboot yet again -> Magisk, you can finally boot system.
To pass CTS profile you'll need to use the command-line signature changer Magisk module and Magisk Hide. Once the play store says it's "Certified" (certifiable more like...) and Magisk is giving you two green checkboxes, you are ready for more suffering. Now you need to freeze the Google Pay/Play apps and Google Play services and blow away all their data. At least that's what I did. Then make sure Magisk hide has all the Google play/GMS/AR/pay stuff hidden in Magisk, one more reboot for good measure, and you're off to the races. This gets Google Pay working and even lets you watch DRM at Widevine L3 level... it's still not all your cake and all your eating I suppose... hopefully you're not a big Netflix guy. Otherwise you kinda bought the wrong phone.
GL! Oh btw I have not found any way to restore an encrypted TWRP backup on this device. Starting to suspect it's literally impossible at this time -- but, if I'm honest, probably I just haven't gone through enough suffering, yet, to figure it out.

anonywimp said:
There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
Click to expand...
Click to collapse
Nope. Just completely dis-confirmed the above recipe. I am clearly still well in the cargo-cult phase of my OP qdl client tools education
All I can say for sure is randomly frobbing with the buttons and the phone-side usb-c cable for long periods of time will usually eventually start the process. And one sure-that-I'm-not-sure---but-still-fairly-confident correction: It probably helps to /un-/plug the phone from the PC, once it starts giving the meaningless red "Sahara quintessence frobnitz poop" error message (or whatever equally meaningful thing it actually says). If you find yourself in TWRP, you can use the "Reboot edl" button. Likewise, I believe the stock recovery has an interface to jump to qdl mode... could be making that up though Anyhow I think from there you want to turn the phone entirely off, which I believe can only at this point be achieved through continuous, uninterrupted mashing of the power button. So just after your get the error and disconnect, is your opportunity to impress the phone by bleeding all over it.

anonywimp said:
You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..."
Click to expand...
Click to collapse
OK, I think I figured out an actual recipe now, or the beginnings of one. It is still a bit fuzzy in places. It goes like this:
If you're not in qdl mode, or you are there but it won't talk to the proprietary flasher software, get the phone completely turned off. Often this is the hardest part. I have sometimes managed to brick my phone where it will Boot and insta-freeze at the infuriating-yellow-triangle screen¹. Then it will just sit there, indefinitely, and never bring up any sort of USB or wifi connectivity (nor does it show any sign of boot-looping, judging by dmesg output on my computer. It's just cold, and dead. Probably a bootloader bug/secure boot fail). In every semi-brick-like circumstance like this, I've found the following enables me to get the phone to turn itself off reasonably quickly, in fact, in just a couple of seconds, usually: unplug any USB-C cable (so I'm running on batteries), hold down all the buttons* until fingers bleeding or something happens -- if nothing happens, release all the buttons briefly and try again; once off, release all the buttons immediately.
Now get the phone back on, and in qdl mode. Somehow. Usually, if the phone is unplugged and off, I can get it there by holding all the buttons and plugging it into usb. If I'm soft-bricked, I'm already there, so nothing to do. From TWRP I can easily "reboot edl" to get there. Maybe there's ways to do it from fastboot, stock recovery, and system as well, via adb/fastboot commands.... My preferred way is holding "all the buttons" for about 1 second, and plugging in the usb cable, which will cause it to enter qdl mode "just one time" without actually bricking anything.
Now, finally, we run the proprietary flasher tool. Press start and it will go until it gets to the "sahara bingo yip-a-dee-ha" error (or whatever it really says... definitely not exactly what I wrote ).
Now turn the phone off again. Same recipe, but this time it seems to almost-always suffice to keep the phone connected to USB, while holding all-the-buttons. If that isn't working, then I go ahead and unplug, power cycle, and get into qdl mode like above. During this, the computer software is maybe completely disconnected from your phone, *****ing and moaning the whole time about Sahara or whatever. Ignore that, it's fine.
If the phone was fully powered off (rather than power-cycled in place), be sure to next release all the buttons, so that the phone has no usb or button-press input of any kind for at least a fraction of a second. Then press "all the buttons" again (nb: I suspect just vol+ and vol- suffice here, and the power button is superfluous? Maybe even detrimental depending on ordering? If I screw this up (sometimes it winds up booting into recovery or bootloader), then I find a way to ask it to reboot from there into qdl mode, if I can, or else power off from there and try again to use the three buttons.
pro tip said:
It is possible to hold all the buttons for too long. In which case, you may find yourself booting system. From there you may need to start this guide over from the beginning, sorry. The correct period of time to hold all the buttons down is about a second. Two seconds is probably too long.
Click to expand...
Click to collapse
Using your fourth hand, Plug in a USB-C cable, what leads from your computer, to the phone, while continuing to hold down all the buttons with your other three hands (or, if you entered qdl via software, just plug it in, now).
That's it, done. Kick back and enjoy as the tool's progress bars go wild and unbrick your phone tut suite. The qdl process should be able to go all the way to the end where it says "100%" (although when you close the program it will still treat this like you are interrupting it in the middle; I think that's because it does multiple phones at once, and you only ever fed it the one phone, so it is alerting you that, hey, phone #2 never got processed).
I am doing the above in a non-FOSS emulator under desktop linux, using the patched client referenced from xda threads.
I imagine qemu would work, as well. Obviously native Windows is going to be your best bet. I def. wouldn't trust Oracle (VirtualBox) USB emulation with my qdl flashing needs, if I were me -- which I am. Phones tend to look like huge USB hubs, full of an ever-changing kaleidoscope of peripherals. Which I don't think the VirtualBox USB stack is really ready to cope with right now. (Not even with the proprietary USB add-on pack or whatever that is -- I simply don't trust Oracle not to hard-brick my phone; VirtualBox has seemingly perma-bricked one device for me, already. That was some time ago but I'm not going to feed it any more devices and I doubt the USB was fixed in vbox. It think it's paravirtualized, or something, so as to be super-fast, but unreliable when the bus topology changes in meatspace.
-- rants / footnotes ---
¹ You know, that warning screen for "security." Which, currently, happens to be punishing me for trying to put the newest stock security updates onto my phone that I just purchased a month ago¹*².
* Not an "All the things" meme -- by "all the buttons" I literally mean all the hardware buttons: [vol+], [vol-], and [power].
¹*² I imagine the person who made the decision to require this in Android would explain it something like this:
straw man said:
(California accent) "Um, like, why? Are you a criminal or something? You know, you could just buy a new phone for like $899 US. Oh, you're, like, poor, or something? Well, OK, I guess there's no way for us to stop you from doing that. But we, like, won't be able to support you in any way. Also, sorry, but we're just going to need to put a brief warning screen on your phone, as a safety measure? No, it's not really a warning for you. More, like, in case other people might be around you for some reason? It just says, 'Hey, no judgement, but it seems like maybe a poor person owns this phone? And they're definitely doing some really weird stuff with it. So just be careful. Like maybe tell a friend where you're going, if you're going to spend time with them.' What? No, I'm sorry, there's no way to remove it. We paid millions to have it fused into the microchips or something? If you could just remove the warning, that would defeat the purpose. So, I'm sure you'd want the people around you to be safe, right? And, like, so do we! So we, like, locked that down pretty tight, yehh-...!'
Click to expand...
Click to collapse