Database Users

[Q] Real simple. Cash offer to walk me through it by phone or email.

Offer:
I've got a $30.00 PayPal for someone with decent rep here to walk me through the update.
History: This is a new virgin phone, exchanged today. (Sun) The OTA killed my previous phone and I was unable, for whatever reason, to restore nandroid, backup, nada. Until this morning, that was the best phone I've ever had because of this forum and esp the Tips & Tricks thread.
It had: Root, Rom Manager, Titanium Backup, Ryan's OCLF, Autostarts, and MOBILE AP wireless tethering app. (This one is a must for me.)
What I want:
I want the JI6 update installed and the above programs re-installed per the Tips thread... In whatever order you think is best. We verify these things work and I send money immediately. My word is good. (I can re-install my 40 odd apps afterward on my own time.
Background:
I have followed the Tips thread instructions for ODIN. (Open ODIN, press vol up & dn, plug in wire, see COM msg in box, (debug on) mount phone, Pit>...512, PDA>...JI6, START. ..... Nothing! 2 seconds later the message box says something like {All threads complete. 0 succeeded, 0 failed>}
Bottom line:
I've read posts for hours but since I don't really know what I'm doing well, I am also unable to sift through all the advice figuring out which poster's setup is like mine. At this point, I just want it done right.
I will edit this post when it's done. Thanks for reading.
Respond: [email protected]

I'm in the same boat, as far as trying to use Odin. Broken phone, nothing working for me.
So, you took your phone to the store, told them you applied the update and now you're stuck on the vibrant screen, and they just gave you a new one right then and there?

you can drop me a pm and i can try and get you through it. Wont take your money though. Make sure you have odin 1.3 downloaded and the odin flash file for JI6 downloaded. If you can get adb working you get bonus points.
Are you hardware locked? if so you need to download the patch for it also found on here. If not should be easy to get ya up and running with the above mentioned things in place.
If I went to fast or confused you just say so in the pm and we can go as slow or as fast as you need.

adm1jtg said:
you can drop me a pm and i can try and get you through it. Wont take your money though. Make sure you have odin 1.3 downloaded and the odin flash file for JI6 downloaded. If you can get adb working you get bonus points.
Are you hardware locked? if so you need to download the patch for it also found on here. If not should be easy to get ya up and running with the above mentioned things in place.
If I went to fast or confused you just say so in the pm and we can go as slow or as fast as you need.
Click to expand...
Click to collapse
there is alot of us who had bricked our own phones who can help you on this issue i helped someone just the other day unbrick his phone
pm either of us we dont mind helping

hellcatrydr said:
Offer:
I've got a $30.00 PayPal for someone with decent rep here to walk me through the update.
History: This is a new virgin phone, exchanged today. (Sun) The OTA killed my previous phone and I was unable, for whatever reason, to restore nandroid, backup, nada. Until this morning, that was the best phone I've ever had because of this forum and esp the Tips & Tricks thread.
It had: Root, Rom Manager, Titanium Backup, Ryan's OCLF, Autostarts, and MOBILE AP wireless tethering app. (This one is a must for me.)
What I want:
I want the JI6 update installed and the above programs re-installed per the Tips thread... In whatever order you think is best. We verify these things work and I send money immediately. My word is good. (I can re-install my 40 odd apps afterward on my own time.
Background:
I have followed the Tips thread instructions for ODIN. (Open ODIN, press vol up & dn, plug in wire, see COM msg in box, (debug on) mount phone, Pit>...512, PDA>...JI6, START. ..... Nothing! 2 seconds later the message box says something like {All threads complete. 0 succeeded, 0 failed>}
Bottom line:
I've read posts for hours but since I don't really know what I'm doing well, I am also unable to sift through all the advice figuring out which poster's setup is like mine. At this point, I just want it done right.
I will edit this post when it's done. Thanks for reading.
Respond: [email protected]
Click to expand...
Click to collapse
Im pretty sure i know what u are doing wrong man. pm me and i can help u out if u havent already

I gave up on unbricking.
No Trunk, It was more of an escalation from a gentle request (at which point they told me "2 weeks & we'll mail it to ya' ".) through several layers of increasing... uhhh... 'amplitude', ("Okay, We'll do priority mail; 3 or 4 days.") culminating in chaining the duct taped Tmo rep's feet to the back of my hog for a quick ride up the street. ("I think we have one in the back, let me check...")
Cyber, your posted phone 'resume' sig is the scariest thing I've ever seen. (Except for my ex.) Does that thing have photon torpedoes too? Krap!
Okay, just kidding 'bout all that. Thank you guys for responding. Will send PMs tomorrow. (1 more brick & I'm gonna need mortar...) About 3-4 pm pacific time. Again, thanks.
I had root but no roms, no adb, no hardware unlock. I'm not a sophisticated power user. I loved it the way it was, except for the GPS/compass thing. It was fast (with the lagfix) and tethered wirelessly & easy w/ the Mobile AP, & I had some control over the running programs.

phone power off. (remove battery if you think it will help)
ok had my phone brick today took about an hour of googling, reading, downloading etc to get it to work again
Load odin
plug phone into USB (power off mind you) press and hold both volume keys at once, plug into PC, this "should boot you into download mode ( android guy with shovel screens says DOWNLOADING! once it loads into download mode you should see some Com info at the top left of odin, thats your cue to load the PDA and PIt file. check PDA box press start, and wait, installation should take about 5 mins

I was in motion with ODIN finally, when I accidentally pulled the USB cord out of my laptop. Now, all I get when trying to get in download mode is a graphic of a phone, a yellow triangle with exclamation mark, and a computer.
Holy crap this is a learning experience. Anyone know what do do?

adm1jtg said:
... Are you hardware locked? if so you need to download the patch for it also found on here.
Click to expand...
Click to collapse
There is a patch to correct the hardware lock? Please provide a link.
Thanks
Edit Just found the link, hxxp://forum.xda-developers.com/showthread.php?t=802763 (replace the xx's with tt), and can't wait to fix my phone.

trunkstar1 said:
I was in motion with ODIN finally, when I accidentally pulled the USB cord out of my laptop. Now, all I get when trying to get in download mode is a graphic of a phone, a yellow triangle with exclamation mark, and a computer.
Holy crap this is a learning experience. Anyone know what do do?
Click to expand...
Click to collapse
Ok here is your next step by step. First take a deep breath you CAN definitely recover this....
you need to hold down the up/down volume and the power button. The yellow triangle image will go dark and come back. You need to wait till after it goes dark twice then when the image shows up for the third time release the volume side. wait about 5 seconds and release the power. Should jump you back into download so make sure your odin is up and ready

adm1jtg said:
Ok here is your next step by step. First take a deep breath you CAN definitely recover this....
you need to hold down the up/down volume and the power button. The yellow triangle image will go dark and come back. You need to wait till after it goes dark twice then when the image shows up for the third time release the volume side. wait about 5 seconds and release the power. Should jump you back into download so make sure your odin is up and ready
Click to expand...
Click to collapse
Awesome. Thank you so much. What a debacle. I'm stock again. Or at least, it looks like stock again. Now, to get the OTA update and hopefully this time it won't break my phone. I have no idea why it broke the last time I tried it.
My phone was so personalized before, I feel lost, like this is someone else's phone.

Stupid question... Why not just odin the official JI6 file that's posted and be done with it. Even better forget the JI6 and look at one of the awesome roms by eugene or bionix as they both use JI6 as their base?

Dude....where in OC are ya ?
I'm in Seal Beach,if you don't get it fixed before your stated 4pm pst time...gimme a holler and I'll even bring my laptop and cable.
Save the 30$, but you're buying the beers

adm1jtg said:
Stupid question... Why not just odin the official JI6 file that's posted and be done with it. Even better forget the JI6 and look at one of the awesome roms by eugene or bionix as they both use JI6 as their base?
Click to expand...
Click to collapse
Not sure if that was for me or not, but I don't even know what JI6 is... flashing stock was the first time I ever Odin'd anything before.

I don't have much of a rep here, but here's how I did things. I installed OCLF from the market, and rooted (and only rooted). Then I installed ROM manager and did a nandroid (and I did one after each change I made to my phone as well). Then I updated to JI6 through odin. After that, I gave myself MobileAP. Then (because I was hardware locked), I used odin to fix that. As far as I know, you can install everything else you got from the market from there (all root apps not already installed included). I can't really tell you how that lag fix from OCLF works with JI6, as I never actually used that part of the app (I only used it to root).
As a side note, you may get an error with odin if you aren't in download mode (but you may still get a com message). For a sure fire way to get into download mode, open odin, and then plug in your phone (completely booted). Use the adb command "adb reboot download" and you'll be in download mode and ready to use odin. Also, if you mess up, as long as you can get into download mode, you can use odin to flash back to how your phone originally shipped.

Update
Hey guys,
I HAVE JI6!!!
I'm the OP & I just logged on to send the PMs to be rescued. I saw the mini-kies method of installing JI6, tried it, and it worked. I'm re-rooted, oclf'ed, clockworked, & have re-installed many apps.
The MOBILE AP seems to be my last major hurdle. I forgot how I did it last time but it worked great! Now the instructions I think are different??? I don't remember any "flashing" with CW though. I've never flashed anything. I've read every post HERE but I'm gunshy now. Is there a "for dummies" way to do this?
Also, I have lost my Haptic feedback. It seems to be set correctly, but it's just not there. Even when I adjust the intensity up to full, nada. It may have happened after the OCLF install, or playing with Swype, not 100% sure. It definatelt was working an hour ago... Any ideas on this? Thanks.
Thanks for the "PM me" responses. You guys are slowly curing my ignorance. (very slowly...)

Member character...
Yep. The Brickmaster is back. After a 3 day long recovery process from a new phone, I had somehow done it again...
This is to say thanks to the multiple members who offered personal help but in particular, to the one who gave it. After a PM, this man called me back and for 2 straight hours on a Friday night, with no request for, or guarantee of payment, patiently led me through the technicalities of an Odin recovery. Somehow, he fixed my phone. And I got a little more education.
During the course of this call, it turned out he is an Iraq war veteran with a new baby who is re-enlisting in the military to serve his country even more! Thank you so much for your help, and my gratitude for your service to our country.
.................................................................................................
As for me, being a natural born electronics genius is rough. Last night I elevated the art of brickification to a new high. (2 clicks gentlemen. Beat that!!!) The poison pill was OCLF, then Voodoo, BTW.
Oh yeah, PS... If anyone needs their phone converted into a shiny black paperweight, get in touch. I'm among the best out there.

stuck at asus spinning circle

Stock tablet, no root or super kernel etc..
Last update done. still the RR on effects, excepts, now it wont start again.
I'm stuck at the spinning circle.
How can i fix that ?
Or i'm seriously thinking of throwing that &*@# back to asus.
Anyone on the same boat ?

So when you power it off and power it on again, it freezes sometime during the ASUS boot animation every time?

ssl123 said:
So when you power it off and power it on again, it freezes sometime during the ASUS boot animation every time?
Click to expand...
Click to collapse
Yes, always the spinning circle, not freezed, always spinn,nothing more.. until battery die i suppose.

What are the first few characters of your serial number, because you're probably going to have to NVFlash that, if your device will allow it.

ssl123 said:
What are the first few characters of your serial number, because you're probably going to have to NVFlash that, if your device will allow it.
Click to expand...
Click to collapse
It is one of the first, i don't have it right now, i'll have to look at the box, cause the sticker is not there anymore.
If i have to do something out of the usual, i'll just send it back to asus.. this is a non working unit that need to be repair, or replaced, or they can put it where i think.

karlr30 said:
It is one of the first, i don't have it right now, i'll have to look at the box, cause the sticker is not there anymore.
If i have to do something out of the usual, i'll just send it back to asus.. this is a non working unit that need to be repair, or replaced, or they can put it where i think.
Click to expand...
Click to collapse
Try Vol down plus power button
Wait till you see the options of cold boot linux or wipe data,
try wiping data to see if it help

baseballfanz said:
Try Vol down plus power button
Wait till you see the options of cold boot linux or wipe data,
try wiping data to see if it help
Click to expand...
Click to collapse
ok i'll try this at home, i'll plug it before to be sure.
and i'll came back to you.

If you have one of the early units, it should definitely be NVFlashable. The symptoms sound like a system file or system files have been corrupted. NVFlashing the unit with a "known good" image should correct that. Unless there are hardware problems as well, I would not send it in for warranty repair, because there is always a chance that it comes back with more hardware problems than it currently has, whether due to bad technical work or due to transit. With an NVFlash-capable device, almost all software problems can be resolved on our own.
---------- Post added at 09:37 PM ---------- Previous post was at 09:34 PM ----------
Yes, try baseballfanz suggestion first. It's worth a shot, and it's easy. With any luck, that'll be all that's needed.

karlr30 said:
ok i'll try this at home, i'll plug it before to be sure.
and i'll came back to you.
Click to expand...
Click to collapse
I've tried the wipe data, and it is working now.
All apps are being re-instaled right now.
Thanks a lot.
As for my satisfaction of the asus tablet, it is getting worse, let's just say if they don't fixe the RR and vpn soon.. well, you know, when the time will come to buy another one, the choice will be made easier by elimination.
I was this close, to either throw it back at them, or just crush it with a hammer... i don't care for the cost, we have to pay for our error. Mine might just have been to pick up that tablet from asus.
Future will tell us.

Have you tried holding down the power button for at least 10 seconds? Sounds like one of the reported problems lots of people are having.
Edit - ignore me, I didn't read your posts properly :-(
Sent from my Transformer TF101 using xda premium

simonr43 said:
Have you tried holding down the power button for at least 10 seconds? Sounds like one of the reported problems lots of people are having.
Edit - ignore me, I didn't read your posts properly :-(
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Yes i did that too.
I had to do that several time before.
The wipe data did work this time,lets hope it stay that way.

power button broke and need to revert back to stock

I'm sending my a500 into acer to get the power button fixed and i have to revert it back to stock before I do. Is there any way of doing this automatically without using the recovery method and needing to select options with a power button. I tried using this EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 from here http://forum.xda-developers.com/showthread.php?t=1113878 and it detected my custom rom but nothing showed up under new image version and wont let me continue.
any help??
btw I'm on honeycomb lightspeed 2.1 with honeyvillain 3.7 kernal right now.

My power button broke a few months back. I just popped it open and soldered it back onto the board and I used a glue gun to fill the gap behind the power button casing so it won't get pushed back anymore (I guess one too many hard pushes screwed mine up.) Haven't had problems with it since.
Hope this helps.
http://www.techrepublic.com/photos/...16&tag=thumbnail-view-selector;get-photo-roto

starkiller86 said:
My power button broke a few months back. I just popped it open and soldered it back onto the board and I used a glue gun to fill the gap behind the power button casing so it won't get pushed back anymore (I guess one too many hard pushes screwed mine up.) Haven't had problems with it since.
Hope this helps.
http://www.techrepublic.com/photos/...16&tag=thumbnail-view-selector;get-photo-roto
Click to expand...
Click to collapse
too scared to open my iconia , did a ps3 the other day to fix the YLOD that was piss but yeah feel if i open the iconia a little gremlin with 9 arms will fall out lmao

Just send it in to Acer. They probably won't even say anything about it. Especially it being a PWR button.
The thing about "if you root you lose warranty", is hogwash more or less. In your case, you can stand your ground as it's a physical defect.
I haven't heard a whole lot of stories from anybody who returned their device, even if it was rooted and such, and got a hard time from the service center. In fact, I have read cases where people got a replacement tab, and not only was it rooted, but already had a custom rom installed!!!!
Just send it in and don't worry about it. The thing is, with your older version of CWM, and not the touch version, you're pretty well up the creek. Unless you want to go the NVFlash way. Now that we can definately help you with. You should be able to NVFlash a stock recovery image. In fact, I believe the Acer Recovery Installer on the market, may be able to flash a stock recovery. Might want to check it and see if it will boot your tab to APX mode automatically. I haven';t used it before, as I prefer the old fashioned way (involves the PWR button)
MD

starkiller86 said:
My power button broke a few months back. I just popped it open and soldered it back onto the board and I used a glue gun to fill the gap behind the power button casing so it won't get pushed back anymore (I guess one too many hard pushes screwed mine up.) Haven't had problems with it since.
Click to expand...
Click to collapse
when the button broke my first instinct was to tear it apart and fix it myself. but then i found out I'm still under warranty so i didn't see any point when acer will fix it for me for free. if it happens again i will definitely do this. Thanks.
Moscow Desire said:
Just send it in to Acer. They probably won't even say anything about it. Especially it being a PWR button.
The thing about "if you root you lose warranty", is hogwash more or less. In your case, you can stand your ground as it's a physical defect.
I haven't heard a whole lot of stories from anybody who returned their device, even if it was rooted and such, and got a hard time from the service center. In fact, I have read cases where people got a replacement tab, and not only was it rooted, but already had a custom rom installed!!!!
Just send it in and don't worry about it. The thing is, with your older version of CWM, and not the touch version, you're pretty well up the creek. Unless you want to go the NVFlash way. Now that we can definately help you with. You should be able to NVFlash a stock recovery image. In fact, I believe the Acer Recovery Installer on the market, may be able to flash a stock recovery. Might want to check it and see if it will boot your tab to APX mode automatically. I haven';t used it before, as I prefer the old fashioned way (involves the PWR button)
Click to expand...
Click to collapse
That's great to hear. i wasn't sure how acer was about being rooted. i know with my sprint phone if the service guys wanted to be dicks they can black flag it and it will void the warranty on that phone entirely, and I've read cases of this happening to people. I'm just gonna do a factory reset and send it to acer. I'll update this thread when i get it back.
also, i did install the stock recovery and tried to flash a stock update.zip but every time I'd get the android guy with the exclamation point next to him, then it would reset (i think it's cause its from the wrong rom?). i had a real hard time finding a stock rom with a good DL link. almost everyone i tried from that link in my first post (and from google) had bad download links. i only got like 2 to actually download and neither worked. but it don't matter now cause I'm sending it in rooted anyway. thanks for the info.:highfive:

lemywinks said:
when the button broke my first instinct was to tear it apart and fix it myself. but then i found out I'm still under warranty so i didn't see any point when acer will fix it for me for free. if it happens again i will definitely do this. Thanks.
That's great to hear. i wasn't sure how acer was about being rooted. i know with my sprint phone if the service guys wanted to be dicks they can black flag it and it will void the warranty on that phone entirely, and I've read cases of this happening to people. I'm just gonna do a factory reset and send it to acer. I'll update this thread when i get it back.
also, i did install the stock recovery and tried to flash a stock update.zip but every time I'd get the android guy with the exclamation point next to him, then it would reset (i think it's cause its from the wrong rom?). i had a real hard time finding a stock rom with a good DL link. almost everyone i tried from that link in my first post (and from google) had bad download links. i only got like 2 to actually download and neither worked. but it don't matter now cause I'm sending it in rooted anyway. thanks for the info.:highfive:
Click to expand...
Click to collapse
Yeah, some of the "update.zips" are a little ify-ify on whether they will work or not. One that works well is an EUU rom. But this requires you enter your UID number for it to continue (a good idea to copy yours down when you get the tab back). Of course it's for a a500, but will install on an a501 also. Usually we use this to reset partitions from a failed NVFlash.
Keep us posted. Sprint folks can be real peckerheads sometimes.
MD

*UPDATE*
So I got my tablet back from acer today. I sent it in rooted on a honeycomb lightspeed rom and I got the same a500 (I put a little mark on it) back on a stock 3.2.1 rom. So they don't really care about root as they still fixed the power button. Thanks for the heads up on that one Moscow Desire. It's funny cause my 1 year warranty would have ended on August 15, 15 days from now lol.
I think its time for some ice cream sandwich.

Black Screen Of Death (New OPT just out of the box)

Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,

Rest in peace. Contact Oneplus support m8 and send that **** back
Sent from my ONE A2003 using XDA Free mobile app

Small Update: I just wish you all to never wait for the OP customer service / technical support. (waiting time is really outrageous for a company which support customers online).
In addition, the technical support team sent me files to download (while i'm explaining her that i tried all of those already) + sending me ROM for OPO (Cyanogen........)
I was in a kind of a shock, while i'm correcting her and telling her there's no CM for OPT and the files she sent me (CM11s?!) are not the correct ones, she sent another mail.
Anyways, i guess you have to go for that "entire process" until they allow you to get a refund.
Hate to type it, but for me it's probably "Never Again" instead of "Never Settle".

CS is the same for most companies, someone in a call centre with little knowledge and a book of instructions to follow. There's no point you saying "I did this already" because they get in trouble if they don't follow the script they have.

I have got the black screen of death too and im a couple of mot=nths into using it
[/COLOR]
Tricepz said:
Hello Guys,
I am posting this thread with a great deal of frustration and of course i'll try to leave the emotions out of this, although it's pretty hard (since that's NOT how i imagined i'll unbox the OPT which i was waiting for, for so long).
Anyways,
I'll cut to the point, I received my OPT package and happily went a head opened the box (hoped not to get a broken phone or anything (like someone who posted a thread here), and indeed the package looked okay and the device looked good (physically speaking).
I started the phone, and i can see the black background white android logo, and then.. Black Screen... I'm telling myself "Ahh that's probably nothing.. let's wait a bit or worse case another restart" waiting didn't help and as you probably know restarts did not help as well.
Okay, since i am not newbie to the android troubleshooting, i said to myself, probably a bad OS boot or some sort of OS issue, let's enter the RECOVERY to reset / wipe / factory reset.
Volume Down + Power Button, can't enter recovery just a Black Screen showing.
Starting the phone again regularly shows the Black Screen but the buttons are glowing blue and if i click on the volume buttons i can hear the sound tick.
Okay, at that point i was getting a bit worried, no recovery, several reboots and Black Screen when going to recovery or normal mode.
So now, i knew i had to go over and search the forums (XDA | One Plus) for more solutions on soft bricked / hard bricked devices.
I found the restoration thread of:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Including the QualCom driver method and 2 FULL restoration kits (1 Hidro OS 1 Oxygen).
I followed the steps (trying first the lighter Hidro Kit (without .img's of system etc') finished the process but when it should logon to recovery SAME result.
Then i went ahead and tried the OxygenOS recovery kit, same procedure it finished, phone restarting but same Black Screen.
This is where i am at right now, very frustrated, i raised a TT to the one plus support, i will update how it goes, i assume i passed most of the troubleshooting phases but if anyone has ANY ideas on how to proceed or assist i would be glad to try it out.
In addition i will use this stage to also update on the OnePlus support (refund wise, and TT dealing wise) as i think it's also important to report on the support when actual problems occur and how they handle it.
In any case guys, thanks for reading this, i really hope you will receive your products WORKING as they should, there's not much worse things when it comes to getting a NEW device starting it for the first time and not being able to use it, after waiting for so long for it.
--Video is also attached below.
https://dl.dropboxusercontent.com/u/33088939/20151005_132402.mp4
I will keep you updated.
Thanks & Regards,
Click to expand...
Click to collapse
So the phone should be responsive even if you cant see the screen. SOOO forget letting it drain, but instead, connect it to pc and install latest twrp. Or crm. Unlocking the bootloader may be difficult as you have to use the power and volume buttons to choose yes or no but i think it starts on yes so just press the power button. Now copy over any rom and gapps (i used exodus and lollipop gapps). Flash them and the phone will boot up surprisingly quickly. This will hopefully stop you from wasting time with support teams that are already overloaded with queries. I hope this helped

I have the same problem I dont know what to do! please someone help !

This is really old news, I'll just add that I've sent the device back and got my money back,rocking a new lg v10 and happy a hell.
Sent from my LG-H960 using Tapatalk

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