Database Info

TrickDroid 4.4 seems to resolve the wifi issue

I just upgrade TrickDroid from 4.3 to 4.4, the wifi issue is resolved, now I'm pretty satisfied with the phone.
Sent from my HTC One S

Didnt need a while thread for this. Did you give some thanks? I don't think I saw your name there...
Close thread.
Sent from my HTC VLE_U using xda premium

Haha cool thread, just for this message
As dooshbag45 said, go to my thread and answer there or hit the thanks there
Really don't need a thread for that ^^

How is the battery life? better then the original rom ?

Of course

torxx said:
Of course
Click to expand...
Click to collapse
The device can hold more than one day ?
And more than 5 hours of screen ?
And how much free memory do you have? In the original rom I can get only 240mb free. :/
(sorry about my English)

It's good just flash it

ya... just flash it already!
can we get this thread stickied?
Sent from my HTC VLE_U using xda premium

I actually glad I saw this thread. Been having issues with the wifi calling since the wifi seems to go to sleep even though it says it isnt. This looks like it will be the reason why I unlock my phone if tmo/htc/qualcom cant get their crap together.

torxx said:
Haha cool thread, just for this message
As dooshbag45 said, go to my thread and answer there or hit the thanks there
Really don't need a thread for that ^^
Click to expand...
Click to collapse
Yes, I really want, but since I'm new to xda, I've no privilege to post in your thread.
Anyway, thanks for the rom and the tweak package.
Sent from my HTC One S

LalyGirl said:
The device can hold more than one day ?
And more than 5 hours of screen ?
And how much free memory do you have? In the original rom I can get only 240mb free. :/
(sorry about my English)
Click to expand...
Click to collapse
Just try it by yourself, if you have unlocked and rooted your phone, it should be very simple, of not, you can find instructions in author's thread.
Sent from my HTC One S

torxx said:
It's good just flash it
Click to expand...
Click to collapse
Ok but before I will flash it, I want you to answer my questions :
The device can hold more than one day ?
And more than 5 hours of screen ?
And how much free memory do you have? In the original rom I can get only 240mb free. :/

yes, the battery stands 1day+
how long with screen an ... don't know.
but when you use the tweakpack you'll save some extra power...
i have 37 apps installed an after one day of use still 217mb free memory.
@ torxx
i have a strang problem since trickdroid 4.0
after start my phone from a night in standby it needs a moment to reconnect with wifi.
but wlan is set to stay online.
any ideas?
mfg
Widowmaker

Widowmaker42 said:
yes, the battery stands 1day+
how long with screen an ... don't know.
but when you use the tweakpack you'll save some extra power...
i have 37 apps installed an after one day of use still 217mb free memory.
@ torxx
i have a strang problem since trickdroid 4.0
after start my phone from a night in standby it needs a moment to reconnect with wifi.
but wlan is set to stay online.
any ideas?
mfg
Widowmaker
Click to expand...
Click to collapse
You are getting ONE day+ with a massive use?

didn't fix it for me
My Wifi connection is solid but every couple of hours the wifi gets disconnected and reconnects. I have trickdroid v5.0 for tmobile. I beleive I tried the v4.4 for the international one s and it had the same issue. I did go thru all of the steps (bootloader unlock, root, fastboot script, and recovery installation of rom). I did it twice for good measure. i still have the same problem.
On a side note I'm not sure if this is related but my friend with the exact same tmo one s and I were doing speed tests. He Consistently got twice my speeds. We both have the same tmobile service and were at the location using the same server. He was using stock ROM and rooted.

androidfever said:
My Wifi connection is solid but every couple of hours the wifi gets disconnected and reconnects. I have trickdroid v5.0 for tmobile. I beleive I tried the v4.4 for the international one s and it had the same issue. I did go thru all of the steps (bootloader unlock, root, fastboot script, and recovery installation of rom). I did it twice for good measure. i still have the same problem.
On a side note I'm not sure if this is related but my friend with the exact same tmo one s and I were doing speed tests. He Consistently got twice my speeds. We both have the same tmobile service and were at the location using the same server. He was using stock ROM and rooted.
Click to expand...
Click to collapse
I tried updating to the latest tmo radio and still no luck. I flashed the LeeDroid rom and I got high speeds, even though I flashed the newest radio on the Leedroid rom too. But I'm getting the same speeds as my friend is on his stock rom.
Also another issue I noticed with the tmo trickdroid v5 is that it doesn't recognise a (wired) headset for sounds or mic. Did anyone else have this issue?
update: the headset works fine on leedroid fyi

Visit my support thread for help

LalyGirl said:
You are getting ONE day+ with a massive use?
Click to expand...
Click to collapse
You will never get one day of battery with massive use. Doesn't matter what phone you have.
Sent from my HTC VLE_U using xda premium

xxquicksh0txx said:
You will never get one day of battery with massive use. Doesn't matter what phone you have.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Actually the droid razr maxx might

androidfever said:
Actually the droid razr maxx might
Click to expand...
Click to collapse
I highly doubt it. :cyclops:
Not with Massive use, with heavy use maybe but not MASSIVE lol

how did I brick my phone??

Updated the phone to the latest PA 10/15 build, flashed SU then gapps. After letting everything settled in, boot into recovery and flashed IX kernel 6.3.6 like I always do after every PA updates,but this time my phone won't boot at all, wont even boot into download mode. Stays on the black screen, won't even vibrate. I tried taking off the battery and plugging it in on the computer and outlet. Nothing works. Its hard-bricked. I sure don't have the money to sent it over for JTAG since I don't get paid till next week plus this is my work phone. WHAT TO DO? WHAT TO DO?
Those USB JIG works from Ebay?

Jig probably won't work.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
Jig probably won't work.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
It doesn't hurt to try those usb jigs its only less than 2 dollars plus free shipping. Won't hurt a bit,but knowing those won't ship in for a week or two.
Any other alternative rather than sending it for JTag service?

Z33type said:
It doesn't hurt to try those usb jigs its only less than 2 dollars plus free shipping. Won't hurt a bit,but knowing those won't ship in for a week or two.
Any other alternative rather than sending it for JTag service?
Click to expand...
Click to collapse
Build your own jig with resistors today and find out if it works.
Try taking out the battery and plugging it in and putting the battery back in.

I'm doubting what you did is what bricked It if indeed it is bricked. Doesn't make sense.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

btm fdr said:
I'm doubting what you did is what bricked It if indeed it is bricked. Doesn't make sense.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I honestly don't know. Before I flashed the PA 10/15 build I normally wipe cache, dalvik, format/system then flash the rom/su/gapps then reboot. After that I just installed InstigatorX kernel, rebooted then went on to a blank screen, never to turn on again no matter what I do.
I have never experienced this on the previous PA build with instigator X not saying its new builds fault,but thats honestly what I did.
I've had my faults of flashing roms on wrong devices before,but I greatly learned from that. So don't think I flashed the wrong kernel since I only have one kernel saved up on my computer and saved on on my device sd card.

Had your phone been acting funny beforehand? Seems like you did everything right, and others are running the 10/15 PA build just fine. You might have had one of those wonderful fluke bricks...

Sounds like a bad kernel flash. That's usually what bricks a skyrocket.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

cdshepherd said:
Sounds like a bad kernel flash. That's usually what bricks a skyrocket.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is there a counter for that? Fix? or just JTAG is the only solution?

If you're hard-bricked, JTAG or warranty are the only ways out.

T.J. Bender said:
Had your phone been acting funny beforehand? Seems like you did everything right, and others are running the 10/15 PA build just fine. You might have had one of those wonderful fluke bricks...
Click to expand...
Click to collapse
Never experienced anything unusual and I know I did things right. Only weird funny things that happen to my phone is a few screen flickers on the previous build and I used build.prop to smooth those out. And on PA 2.15 my phone will occasionally randomly shutdown,but gets back on within seconds. I never OC btw. Always keep on stock frequency.
Can I lie to Samsung about the device not being rooted?

Z33type said:
Never experienced anything unusual and I know I did things right. Only weird funny things that happen to my phone is a few screen flickers on the previous build and I used build.prop to smooth those out. And on PA 2.15 my phone will occasionally randomly shutdown,but gets back on within seconds. I never OC btw. Always keep on stock frequency.
Can I lie to Samsung about the device not being rooted?
Click to expand...
Click to collapse
Sure, you can do whatever your heart desires.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
Sure, you can do whatever your heart desires.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Lol would they investigate if the phone is rooted?

Z33type said:
Lol would they investigate if the phone is rooted?
Click to expand...
Click to collapse
They can't investigate anything if it doesn't turn on
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
They can't investigate anything if it doesn't turn on
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I pretty much told them I did the ICS update then my phone won't turn on from there. And that I barely bought the phone from Craigslist yesterday.
They believed it just a little scared if they found out that my phone is rooted and starts to charge me restocking fee or whatever they do.
This what they told me
Arwyn: Please hold while check the warranty details.
Visitor: ok
Arwyn: I'm sorry for the delay. I'll be right with you.
Arwyn: Thank you for holding.
Arwyn: I see that device is in warranty till March 5th, 2013.
Visitor: awesome
EDIT: This Arwyn Samsung tech support really something
Arwyn: Are you using the same charger and the battery that came with the device?
Visitor: yes its all oem
Arwyn: Do you see any error message on the device?
Visitor: none
Visitor: Like I said the phone does not turn on at all
Visitor: soft keys don't even light up
Visitor: no vibrations, no boot screen, no boot animations or anything
Arwyn: What do you see on the device screen?
OK NOW THEY ARE TELLING ME TO SEND MY DEVICE FOR SERVICE AND REPAIRS COVERED BY WARRANTY. IS THIS A GOOD IDEA TO DO? SINCE MY PHONE IS COMPLETELY ROOTED, HAS A ROM AND CUSTOM KERNEL. LET ME KNOW PLEASE BECAUSE THIS ARWYN PERSON SAID THEY ARE GOING TO DIAGNOSE WHAT CAUSED IT.

I don't think its a huge deal. Just send it in.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Are they asking you to send it in without issuing you out a replacement device or to send it in once you receive a replacement device? If its the first option it doesn't sound like a good idea to me. Sounds like they might actually check it out.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

RastarNation said:
Are they asking you to send it in without issuing you out a replacement device or to send it in once you receive a replacement device? If its the first option it doesn't sound like a good idea to me. Sounds like they might actually check it out.
Click to expand...
Click to collapse
Samsung never gives you a replacement device. They will just flash a new firmware to it. If they can't they'll give you a new phone. I'd do it if I where you.

Z33type said:
OK NOW THEY ARE TELLING ME TO SEND MY DEVICE FOR SERVICE AND REPAIRS COVERED BY WARRANTY. IS THIS A GOOD IDEA TO DO? SINCE MY PHONE IS COMPLETELY ROOTED, HAS A ROM AND CUSTOM KERNEL. LET ME KNOW PLEASE BECAUSE THIS ARWYN PERSON SAID THEY ARE GOING TO DIAGNOSE WHAT CAUSED IT.
Click to expand...
Click to collapse
1. Stop shouting.
2. Just do it. Worst thing that can happen is they say no. That said, if they can't get the phone to boot, they'll just send a refurb. If they can get it into download mode, they'll just flash the new firmware and wipe your tracks. Even if they do somehow see that it was rooted (i.e., they boot it into the OS), they'll just tell you that the warranty is void, and the repairs will cost X if you choose to go ahead with them.

Well I sent it in this morning and see whats going to happen from here and then. Hopefully it all goes smoothly.

Nexus 5 BRICKED

Ok guise, I'm in some serious need of help here.
Got a new phone, flashed this and that, was trying out new ROMs and stuff, and then I accidentally flashed Faux's MAKO kernel. 028u
Now my Nexus gives no signs of life, isn't recognised via adb, can't get into fastboot with hw buttons or anything at all. What options am I left with?

0rigin said:
Ok guise, I'm in some serious need of help here.
Got a new phone, flashed this and that, was trying out new ROMs and stuff, and then I accidentally flashed Faux's MAKO kernel. 028u
Now my Nexus gives no signs of life, isn't recognised via adb, can't get into fastboot with hw buttons or anything at all. What options am I left with?
Click to expand...
Click to collapse
Sending it to Google.
Next time you should probably be more careful about what you do to a $350-$400 device, eh?

So any kind of hardware intervention wont really help me?
I won't be sending it to Google, since I'm not from the US
What can a qualified service provider(not really sure if that's the correct translation) do for me?

0rigin said:
So any kind of hardware intervention wont really help me?
I won't be sending it to Google, since I'm not from the US
What can a qualified service provider(not really sure if that's the correct translation) do for me?
Click to expand...
Click to collapse
Your best hope is jtag. It's a new device so it may not be available yet. Google mobiletechvideos

Wow. I didn't even think a Nexus 5 was brickable.
That's a feat right there.

Bring it to a cell repair shop.
Sent from my Nexus 5 using xda app-developers app

Han Solo 1 said:
Wow. I didn't even think a Nexus 5 was brickable.
That's a feat right there.
Click to expand...
Click to collapse
You can brick most devices by flashing an incompatible kernel, same as prior nexus phones.
Sent from my Nexus 5 using Tapatalk

Introducing the new Nexus Paperweight
No jtag available yet
If anyone has another idea, please, do share!
Sent from my Nexus 4 using xda app-developers app

hotleadsingerguy said:
Sending it to Google.
Next time you should probably be more careful about what you do to a $350-$400 device, eh?
Click to expand...
Click to collapse
There are smart people out here hooking up their car coolant hoses to transmission breather ports and you expect forethought from street level smart phone users? What backup?

No hate in the thraed plz
Was flashing stuff on Nexus 4 the day before, had everything in the same folder and because of this accidentally flashed a mako kernel... Yeah **** happens. N4 is still an awesome phone though, running 4.3.1 custom makes it much more usable than N5 atm, so I can wait a bit more with ease... Any kind of suggestions/solutions won't hurt no one though

I'd rma it to Google. I wouldn't lie to them or anything. Google is pretty cool about this kind of stuff.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Take a screenshot of what your computer picks the device up as in my computer. I think your bootloader might be toasted (pre- Android bootloader). We might be able to get some kind of bootloader repair going...
Sent from my Nexus 7 using Tapatalk 4

devoureddreams said:
I'd rma it to Google. I wouldn't lie to them or anything. Google is pretty cool about this kind of stuff.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
0rigin said:
I won't be sending it to Google, since I'm not from the US
Click to expand...
Click to collapse
danifunker said:
Take a screenshot of what your computer picks the device up as in my computer. I think your bootloader might be toasted (pre- Android bootloader). We might be able to get some kind of bootloader repair going...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
pc does'nt recognize te phone at all. Can't get into fastboot. Can't get it to budge at all.

0rigin said:
pc does'nt recognize te phone at all. Can't get into fastboot. Can't get it to budge at all.
Click to expand...
Click to collapse
Are you in Windows or Linux? If Windows, is there nothing listed under "Other" devices? Also, can you try running Linux and doing an lsusb to try and find the device?

This guy (http://forum.xda-developers.com/showthread.php?t=2347060 flashed the wrong image on his n4 and was able to recover using the process he outlines in the post. Perhaps this would work for you too (it might be a long shot since your computer does recognize fastboot), but hey, worth considering. Good luck.

After a gazillion tries, managed to get my phone into fastboot.... Don't ask how, because I simply don't know...
Seems like that at least some of the time my phone was also in some sort of bootloop or sth, because 60% of my battery is gone.
Whatever it may have happened, the issues are sorted out and I can continue with flashing....the right kernels hopefully.
EDIT: tried it again and can confirm - I can only get into fastboot when all these criteria are met:
- phone is turned off
- press and hold down the both VOL buttons
- continue holding them down and plugging the phone to a PC(ADB installed of course)
Hope this might be helpful to someone.

[Q] Can someone explane the high amount of bricked Nexus 5

Hey,
I come from the HTC One section and so I know the basics about Android rooting. But there are still some differences I wanna know before buying a Nexus 5.
Compared to the HTC One I found here a amazingly high amount of people having the random bricks:
[Q] what is qhsusb bulk ?
[Q] Bricked Nexus 5 doesn't boot + no access adb/fastboot/recovery (corup. bootload)
Have I bricked my N5?
So I don't wanna spam you
Ok, AFAIK these bricks happend randomly and not after flashing something. So their phones just randomly died after working correctly for a long time. Can someone tell me if these bricks could also occure when having an unrooted/locked N5 ?
Or does it only appear to be a high amount of bricks and it actually isn't ?
Thanks for helping me

my 2 cents: if you do your homework the likeliness of bricking the phone (no matter of what you flash) is very small.
all other "random" bricks could be just defective hardware or random issues. that's why all devices have warranty.
advice: keep your phone stock for a few days / weeks. just to test it (in case some unfortunate hardware failure appears you will have a better poker face for RMA). after that you can document / read / learn and decide weather you want to tweak it.

LibertyMarine said:
Compared to the HTC One I found here a amazingly high amount of people having the random bricks:
Click to expand...
Click to collapse
Hi,
Ah...? It's not what I called an "amazingly high amount of people having the random bricks"...
Plus people claim they "bricked" their device when it's not a "brick"...
I don't think the number is like you describe.
A real bricked device without doing anything is minor for me and all the rest is by doing something wrong, at user level. It's always the same thing for all the devices (I agree some are more concerned than others) but the Nexus 5 does not suffer more...
LibertyMarine said:
Can someone tell me if these bricks could also occure when having an unrooted/locked N5 ?
Click to expand...
Click to collapse
It could happen, whatever if you are rooted, unlocked, stock or not.
LibertyMarine said:
Or does it only appear to be a high amount of bricks and it actually isn't ?
Click to expand...
Click to collapse
For me it's this, but it's just my opinion.

kraven001 said:
my 2 cents: if you do your homework the likeliness of bricking the phone (no matter of what you flash) is very small.
Click to expand...
Click to collapse
Ok, I generally like having everything under my control... that's also why I try to learn first many things about the phone and so on... and that's also why I don't use toolkits... eventhough I think their creators did an awesome job !
kraven001 said:
all other "random" bricks could be just defective hardware or random issues. that's why all devices have warranty.
Click to expand...
Click to collapse
Ok, yeah... I had 3 damn hardware faults on my HTC One... everytime rooted and everytime got it replaced on warranty... :victory:
kraven001 said:
advice: keep your phone stock for a few days / weeks. just to test it (in case some unfortunate hardware failure appears you will have a better poker face for RMA). after that you can document / read / learn and decide weather you want to tweak it.
Click to expand...
Click to collapse
Ok, that sounds like a very good idea... Will do that when I got the HTC One refunded !
Thanks!
viking37 said:
Hi,
Ah...? It's not what I called an "amazingly high amount of people having the random bricks"...
Click to expand...
Click to collapse
Yeah... I exaggerated a bit.. you know surely.. some people may agree and some others disagree with this statement... and because of the fact that it's exaggerated there are more people answering this thread because it's kinda provocative
Nothing against the people agreeing or disagreeing, I just wanna get answers and this is one way of getting them If you think this isn't a good way, I'm always open for better options :good:
viking37 said:
Plus people claim they "bricked" their device when it's not a "brick"...
Click to expand...
Click to collapse
Yeah... I experienced that on the HTC One section too About 90% of people telling that they have a brick actually didn't have a bricked device and we could fix these devices .. and 9% bricked their device doing something stupid... flashing a wrong hboot and 1% did have a hardware fault... poor guys... I had 3 times one
viking37 said:
I don't think the number is like you describe.
Click to expand...
Click to collapse
Thanks, that's a relief (or however it's called in English.. sry)
viking37 said:
A real bricked device without doing anything is minor for me and all the rest is by doing something wrong, at user level. It's always the same thing for all the devices (I agree some are more concerned than others) but the Nexus 5 does not suffer more...
Click to expand...
Click to collapse
even more relieved :victory:
viking37 said:
It could happen, whatever if you are rooted, unlocked, stock or not.
For me it's this, but it's just my opinion.
Click to expand...
Click to collapse
Thanks !!! Thanks to both of you 1!
Have a great weekend !

Count me in as one of the "hard bricked" phones with just normal use and seems to be a hardware failure. I have seen a few similar post recently but doesn't see like a very big number of instances. Mine had the show up in device manager as "QHSUSB_BLUK" issue. I was not flashing anything or using the phone at all. Just picked it up and it was off.

crazycd1 said:
Count me in as one of the "hard bricked" phones with just normal use and seems to be a hardware failure. I have seen a few similar post recently but doesn't see like a very big number of instances. Mine had the show up in device manager as "QHSUSB_BLUK" issue. I was not flashing anything or using the phone at all. Just picked it up and it was off.
Click to expand...
Click to collapse
Yep, it stinks but does happen. I had it happen on a different device and have seen about the same amount of instances on a number of devices I've followed. The n5 is no different.

One thing you must take into account is that many people buy the Nexus 5 because it is very much a developer friendly phone; so the percentage of Nexus 5 users who post on XDA Developers and who do things that increase the chance of bricking (such as installing a custom ROM) is probably much higher than the percentage of HTC One users who do the same things.

Charlular said:
One thing you must take into account is that many people buy the Nexus 5 because it is very much a developer friendly phone; so the percentage of Nexus 5 users who post on XDA Developers and who do things that increase the chance of bricking (such as installing a custom ROM) is probably much higher than the percentage of HTC One users who do the same things.
Click to expand...
Click to collapse
The n5 is a difficult device to truly brick by flashing things. The ones I've seen that are bricks are failure of the emmc, imo.

a far majority of bricked nexus 5 are not really bricked, its just users doing stuff to their phone without knowing how to recover from their own errors. sure, a few are defective and get bricked on their own, but thats very rare. but the far majority are just user error.

I saw another device kernel flash brick. I assume incorrect bootloader would brick too.
Bricks are caused by 2 things.
1) defects
2) idiots
Sent from my Nexus 5 using Tapatalk

jd1639 said:
The n5 is a difficult device to truly brick by flashing things. The ones I've seen that are bricks are failure of the emmc, imo.
Click to expand...
Click to collapse
Yes, but you're still more likely to brick it by messing with the root system than if you just keep the phone stock forever and never even go into fastboot. I'm not saying that the Nexus 5 is easy to brick, I'm just saying that it probably has a much higher percentage of users who are into modding than other phones, I guess you could counter this argument by saying that many people buy the Nexus 5 for the "stock Android" experience though. Your point does stand though, many of the bricked Nexus 5s I've heard of sound like it was due to a hardware fault and not caused by something done with software, you can't expect this not to happen with anything manufactured in mass production though.

Charlular said:
Yes, but you're still more likely to brick it by messing with the root system than if you just keep the phone stock forever and never even go into fastboot
Click to expand...
Click to collapse
Yes but only if you're an idiot or clumsy.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Yes but only if you're an idiot or clumsy.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, and you find these people with every device :silly:

Charlular said:
Yeah, and you find these people with every device :silly:
Click to expand...
Click to collapse
This is true
Sent from my Nexus 5 using Tapatalk

The only real manufacturing fault that seems to cropping up is the emmc failure.
But I'd say the most part it is user error.
Many of the bricked threads are actually just soft bricks which can be fixed.
Others are often caused by cross flashing things for a different device.
I've seen people flashing kernels for different phones.
Restoring efs partitions from old to new n5s.
All result in bricks.
The nexus is more open than many other devices.
Unfortunately this gives those who don't know what they are doing the ability to do things they really shouldn't be doing.
As first stated. Failed emmc seems to be the only thing that is a genuine brick. Pretty much all others I think are either not actual bricks or user created bricks.
Sent from my Nexus 5 using xda app-developers app

Alex240188 said:
Many of the bricked threads are actually just soft bricks which can be fixed.
Click to expand...
Click to collapse
That's another truth right there.
Personally I prefer not to acknowledge the existence of "soft bricks" though. It ain't a brick if its fixable.
Sent from my Nexus 5 using Tapatalk

Yes, most are fixable and not close to a hard brick!

Too many people modding their phones, when they don't know how to properly.
sent from my Hammerhead Nexus

Users with minimal to zero knowledge start rooting and modding cause its hip and cool and preferably use a toolkit to mess up their phones and then scream that the toolkit killed their phone

gee2012 said:
Users with minimal to zero knowledge start rooting and modding cause its hip and cool and preferably use a toolkit to mess up their phones and then scream that the toolkit killed their phone
Click to expand...
Click to collapse
yeah, I know... on the HTC One section (I have the impression) this is even more popular... they unlock the bootloader mod their device... relock the bootloader and then they can't unlock it again and they are stuck on custom firmware ...

BUY or NO BUY?

i'm realy in a need to have a new phone.
oneplus one is still the best price for a new phone.
but like i see every where. BAD GROUNDING issue when its in a car stand or table so u cant use more than 2fingers. and ghost touches.
i dont want that.
cause i write very fast smses. so if the touchscreen is not folowing me im gonna go mad.
and that grounding would be anoying also cause i always internet in my bed. so.
help IS THIS A PROBLEM WITH ALL PHONES? i cant seem to find a awnser any where

Bad grounding? No idea.
Ghost touches? Fixed as of yesterday. Was a problem with the drivers which is up to Synpatics to resolve, not Cyanogen/OnePlus.

zephiK said:
Bad grounding? No idea.
Ghost touches? Fixed as of yesterday. Was a problem with the drivers which is up to Synpatics to resolve, not Cyanogen/OnePlus.
Click to expand...
Click to collapse
if readed that if you put it on a pillow the phone wont work (touchscreen) something with the bad grounding. don't know if its the right word
atleast last month like july some where. i asked a XDA developer "carburano" ex developer from my LG O2X
he got the phone in july and didnt recomand me it and that he won't use it and give it to his dad. but now 2 months later i wanna know if there are things fixed
cause 300€can't find a other goood phone. lg g2 is 300€ from ebay new. but without douane TAX.. so i need to add 20% to the price. and that doesnt make me happy.
this what he said. to me in august
"It is a great device but with an awful touchscreen... It has a bad grounding issue (hardware) that cannot allow more than 2 touches when you will use your phone in car stand or on a table... Also it has a bad software bug regarding touch driver"

reggiexp said:
if readed that if you put it on a pillow the phone wont work (touchscreen) something with the bad grounding. don't know if its the right word
atleast last month like july some where. i asked a XDA developer "carburano" ex developer from my LG O2X
he got the phone in july and didnt recomand me it and that he won't use it and give it to his dad. but now 2 months later i wanna know if there are things fixed
cause 300€can't find a other goood phone. lg g2 is 300€ from ebay new. but without douane TAX.. so i need to add 20% to the price. and that doesnt make me happy.
this what he said. to me in august
"It is a great device but with an awful touchscreen... It has a bad grounding issue (hardware) that cannot allow more than 2 touches when you will use your phone in car stand or on a table... Also it has a bad software bug regarding touch driver"
Click to expand...
Click to collapse
It's hard to comprehend what you are saying, I've had my phone for a few days now and it is great. Coming from a Nexus 5 it seems like it is a good update and for the price I think it would be worth getting this over a LG G2.

reggiexp said:
if readed that if you put it on a pillow the phone wont work (touchscreen) something with the bad grounding. don't know if its the right word
atleast last month like july some where. i asked a XDA developer "carburano" ex developer from my LG O2X
he got the phone in july and didnt recomand me it and that he won't use it and give it to his dad. but now 2 months later i wanna know if there are things fixed
cause 300€can't find a other goood phone. lg g2 is 300€ from ebay new. but without douane TAX.. so i need to add 20% to the price. and that doesnt make me happy.
this what he said. to me in august
"It is a great device but with an awful touchscreen... It has a bad grounding issue (hardware) that cannot allow more than 2 touches when you will use your phone in car stand or on a table... Also it has a bad software bug regarding touch driver"
Click to expand...
Click to collapse
I have heard absolutely nothing about grounding problems. As far as the touch problems, they weren't that bad and have been resolved as of yesterday.
I can tell you for sure that you won't be disappointed with the device. If you have a invite, buy the phone. I'm typing on my phone right now and am typing as fast as I can and have problems. Although you will need to flash a custom kernel to get the newest fix until the Ota is released but it should be very soon.
Sent from my A0001 using Tapatalk

zephiK said:
I have heard absolutely nothing about grounding problems. As far as the touch problems, they weren't that bad and have been resolved as of yesterday.
I can tell you for sure that you won't be disappointed with the device. If you have a invite, buy the phone. I'm typing on my phone right now and am typing as fast as I can and have problems. Although you will need to flash a custom kernel to get the newest fix until the Ota is released but it should be very soon.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
so u have problems with typing fast or u just missed word "not"???

gerciolisz said:
so u have problems with typing fast or u just missed word "not"???
Click to expand...
Click to collapse
I have no problems with the newest firmware that was released yesterday

zephiK said:
I have no problems with the newest firmware that was released yesterday
Click to expand...
Click to collapse
OK thanks. i wasnt sure because u said:
zephiK said:
I'm typing on my phone right now and am typing as fast as I can and have problems
Click to expand...
Click to collapse
THX. See people he has no more problems! :highfive:

okay yeah sorry i write fast on pc always. and never read back what i write.
will see than. invite shouldnt be that hard. got invite like 20 times kept saying no for all that problems.
but thanks. if realy the touchscreen is fixed, its worth the shot. (now that i learned that the lg g2 isnt 299€ like i tought... stupid import tax 20%more on the buy price, not cool) i acualy dont want to spent more than, 300€ on a phone. so yeah.

The grounding issue you speak of is the exact issue i had. If the device was lying flat on a pillow for instance not plugged in the screen wouldn't register more than two fingers simultaneously. This has by a large degree been fixed with the latest available update 33R. Now there is already a new firmware on its way,think around next week, that is going to completely fix the issue and @zephiK just mentioned in another thread that there was another update added just over an hour ago so this issue seems to be well on its way to be done and dusted.

zephiK said:
I have no problems with the newest firmware that was released yesterday
Click to expand...
Click to collapse
can you tell your update build number ?

avetny said:
can you tell your update build number ?
Click to expand...
Click to collapse
Its based on the newest kernel, build number has nothing to do with it.
The commits for the touchware firmware update is not in the latest OTA just yet.

zephiK said:
Its based on the newest kernel, build number has nothing to do with it.
The commits for the touchware firmware update is not in the latest OTA just yet.
Click to expand...
Click to collapse
What.. People on the thread keep saying fixed with the new firmware.. WHERE. I haven't gotten anything yet and the ghost touching is driving me crazy- along with not being able to type quickly..

You_got_owned123 said:
What.. People on the thread keep saying fixed with the new firmware.. WHERE. I haven't gotten anything yet and the ghost touching is driving me crazy- along with not being able to type quickly..
Click to expand...
Click to collapse
Its in the kernel, you need to flash Franco r17. Otherwise, you'll have to wait for the official OTA to be released with the new kernel which contains the new firmware. All firmware/drivers are in the kernel.

hum, still not sure.
i don't want a phone that anoyes me....

Don't buy it then. But you need to realise that only a small percentage of these phones actually have any problems. The vast majority of these phones are perfectly fine. Don't just listen to the loud people complaining, they're always the most vocal.
Transmitted via Bacon

zephiK said:
Its in the kernel, you need to flash Franco r17. Otherwise, you'll have to wait for the official OTA to be released with the new kernel which contains the new firmware. All firmware/drivers are in the kernel.
Click to expand...
Click to collapse
Thank you so much

You_got_owned123 said:
Thank you so much
Click to expand...
Click to collapse
r18 is out if you didn't see it includes the one that was released today on top of yesterdays.

timmaaa said:
Don't buy it then. But you need to realise that only a small percentage of these phones actually have any problems. The vast majority of these phones are perfectly fine. Don't just listen to the loud people complaining, they're always the most vocal.
Transmitted via Bacon
Click to expand...
Click to collapse
ah finaly some sort of awnser.
look that helps me a little bit. i tought every oneplus had this anoying problem.
than i will maybe start looking around again on the forum for the phone. and cross my fingers that i will get a good one.

To make it short, buy it and ignore those people digging everywhere just to find a hair in the soup.
Send from OnePlus One using Tapatalk