So, I bricked my last A2 and had it replaced and the one they gave me is horrific (bunch of issues...). Anyway, I know I have to unroot, they will most certainly detect that. However, What about bootstrap? Do you think they will notice that when they bring it to the back to do their "troubleshooting"? Because I was just planning on unrooting and then uninstalling bootstrap app (incase they know what that is, i know that that wont remove they bootstrap). So, what are your opinions on that?
Fzx back to stock.
Sent from my MB865 using xda premium
tmease1 said:
Fzx back to stock.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yeah thats never worked out well for me...
okachowwa said:
So, I bricked my last A2 and had it replaced and the one they gave me is horrific (bunch of issues...). Anyway, I know I have to unroot, they will most certainly detect that. However, What about bootstrap? Do you think they will notice that when they bring it to the back to do their "troubleshooting"? Because I was just planning on unrooting and then uninstalling bootstrap app (incase they know what that is, i know that that wont remove they bootstrap). So, what are your opinions on that?
Click to expand...
Click to collapse
Throw it in a microwave to kill it so it wont turn on.
Sent from my MB865 using xda premium
matt99017d said:
Throw it in a microwave to kill it so it wont turn on.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Ever since I bought a Moto phone I feel the need to do that every day
okachowwa said:
Ever since I bought a Moto phone I feel the need to do that every day
Click to expand...
Click to collapse
Lol.
Me too.....
Sent from my MB865 using xda premium
matt99017d said:
Lol.
Me too.....
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Horrible mistake. Live and Learn...unless youre a sophmore who doesnt have any money and is stuck with it for another year...omg.
okachowwa said:
Horrible mistake. Live and Learn...unless youre a sophmore who doesnt have any money and is stuck with it for another year...omg.
Click to expand...
Click to collapse
My case lol
Sent from my locked MB865
Not sure if I'm completely off topic but don't want to start a new thread either: so does AT&T/Motorola salvage the bricked phones returned/exchanged under warranty? I understand if you microwave it, it's gone for good, but otherwise do they have a way to salvage a phone with hosed bootloader or hard bricking? Will it require special hardware setup to recover these phones? I am sure bricking would be a common phenomena in Moto's lab ...
OMG, just took a look at your sign - okachowwa - your smartphone's histories usage so terrible ...
vinamilk said:
OMG, just took a look at your sign - okachowwa - your smartphone's histories usage so terrible ...
Click to expand...
Click to collapse
Dude's also only 15, which it states as well, and to cut the kid some slack!
Launched from my SAMSUNG-SGH-I747 Anti-MOTO Ballistic Missile
vinamilk said:
OMG, just took a look at your sign - okachowwa - your smartphone's histories usage so terrible ...
Click to expand...
Click to collapse
Hey now lol. I try I try. I totally fixed my Captivate...after I bought this AWESOME phone. But I didn't brick this one, it was a bad replacement, and my last one, yeah FXZ confused me so my ignorance overtook my ability to fix it, because I couldnt find the files on the forums (links were down) and flashed wrong ones (live and learn?). But yes, being a sophmore in high school I probably shouldn't being doing this stuff as I don't have any money lol.
kousik said:
Not sure if I'm completely off topic but don't want to start a new thread either: so does AT&T/Motorola salvage the bricked phones returned/exchanged under warranty? I understand if you microwave it, it's gone for good, but otherwise do they have a way to salvage a phone with hosed bootloader or hard bricking? Will it require special hardware setup to recover these phones? I am sure bricking would be a common phenomena in Moto's lab ...
Click to expand...
Click to collapse
Yes, unless the EMMC is corrupted beyond redemption they have special flashing tools to restore phones to a usable condition. Just think about when the phone is made; it is a blank slate. They have to have a way to flash it initially. They can use a similar method to resurrect it if it is not damaged beyond repair.
jboxer said:
Yes, unless the EMMC is corrupted beyond redemption they have special flashing tools to restore phones to a usable condition.
Click to expand...
Click to collapse
Hmmm ... that's exactly is my point; if it is all software, why doesn't it leak like RSDlite? Then users could recover these bricked phones themselves and no need of these warranty calls. It must be some special hardware (to be connected to JTAG?) which even our service centers do not have available. Then we could take our out of warranty phones to them and get it restored for a small fee. Now if I take a bricked phone to them, they change the motherboard and charge ~30% of the phone value.
kousik said:
Hmmm ... that's exactly is my point; if it is all software, why doesn't it leak like RSDlite? Then users could recover these bricked phones themselves and no need of these warranty calls. It must be some special hardware (to be connected to JTAG?) which even our service centers do not have available. Then we could take our out of warranty phones to them and get it restored for a small fee. Now if I take a bricked phone to them, they change the motherboard and charge ~30% of the phone value.
Click to expand...
Click to collapse
That is because there is an efuse that was blown as part of this process, and you can't unblow a fuse/efuse. That is why you are getting new boards. I was at one the AT&T service centers last week and we looked at one of the bricks, and it did throw 2 efuses that I could find. We could connect them to JTAG with the correct connetions, but we could NOT see the phone from the JTAG device/software.
jimbridgman said:
That is because there is an efuse that was blown as part of this process, and you can't unblow a fuse/efuse. That is why you are getting new boards. I was at one the AT&T service centers last week and we looked at one of the bricks, and it did throw 2 efuses that I could find. We could connect them to JTAG with the correct connetions, but we could NOT see the phone from the JTAG device/software.
Click to expand...
Click to collapse
Is it not an inefficient (or dangerous (or suicidal)) design that if you overwrite the bootloader (even by an older version) then a efuse blows somewhere and the motherboard becomes useless. You may refuse to boot if the bootloader isn't trusted but killing the phone in the process sounds too bad to me. Would this happen with phones with unlocked bootloader too?
kousik said:
Is it not an inefficient (or dangerous (or suicidal)) design that if you overwrite the bootloader (even by an older version) then a efuse blows somewhere and the motherboard becomes useless. You may refuse to boot if the bootloader isn't trusted but killing the phone in the process sounds too bad to me. Would this happen with phones with unlocked bootloader too?
Click to expand...
Click to collapse
No, this is a Motorola ONLY thing, as inefficient as it might be. There is no need for anything like is in a unlocked bootloader phone. This happens because these phones are just like iphones in that Motorola does NOT want us "playing" with them, or doing any kind of dev work on them, Moto phones have a HUGE history of being non developer friendly. That is also why certain devs like me find them a challenge and want to "breakthrough" all that.
jimbridgman said:
No, this is a Motorola ONLY thing, as inefficient as it might be. There is no need for anything like is in a unlocked bootloader phone.
Click to expand...
Click to collapse
Well, except their managers we all see how it backfired. It doesn't interfere with people who wants to stay stock, and if it gets bricked doing some dev, they get a warranty call (and maybe they have to swap in 90% cases). Doesn't help anyone.
However I had a Milestone before (why did I buy another Moto afterwards questions my sanity) but even if it had a locked bootloader (and after stock 2.1 no update was given), devs could port froyo and finally CM7 and CM9. I am hoping in spite of the lock, we'll be able to port CM9/10, keeping the kernel same. I am hopeful as LG Thrill 4G, Motorola Droid 3 has CM9 already.
Well I'm offtopic already so don't bother replying
Related
Unfortunately, I've encountered a hardware defect on my phone...
...the dreaded power button is getting stuck and becoming virtually unusable. The VZW Tech Support is sending me a CLNR device which should be here on Friday. (Apparently, they got rid of free overnight shipping.)
I'm unrooting tonight so I can play around with the new OTA over the next couple of days.
Is there anything I need to do to the phone other than un-root it so that VZW doesn't know it was rooted, thereby avoiding any future headaches and $299 charges.
Thanks!
Drew
Just to remember to remove your sd card before sending it back. If left in by accident they can tell some of what you have been doing with your phone.
jett2314 said:
Just to remember to remove your sd card before sending it back. If left in by accident they can tell some of what you have been doing with your phone.
Click to expand...
Click to collapse
Oh yeah. That for me was a given. lol
I'm removing the SIM, SD card, battery and back battery cover.
If that's it then I should be set. Just trying to cover all of my bases. ya know?
CanesDrew said:
Oh yeah. That for me was a given. lol
I'm removing the SIM, SD card, battery and back battery cover.
If that's it then I should be set. Just trying to cover all of my bases. ya know?
Click to expand...
Click to collapse
Just make sure to follow the unroot process in the dev forums so you put your phone back to "stock". You want to make sure its back to "S-ON" but that's about it.
This post is infected with the 3D strain of Gingeritis
capflya said:
Just make sure to follow the unroot process in the dev forums so you put your phone back to "stock". You want to make sure its back to "S-ON" but that's about it.
This post is infected with the 3D strain of Gingeritis
Click to expand...
Click to collapse
Thanks but this is not my first time un-rooting my phone. I got that part covered. Installing the official OTA now.
Good Lord it takes forever over 3G. lol
CanesDrew said:
Thanks but this is not my first time un-rooting my phone. I got that part covered. Installing the official OTA now.
Good Lord it takes forever over 3G. lol
Click to expand...
Click to collapse
You asked
Hope your new phone is better in regards to the power button issue. Mine seems to be OK... Except I keep finding its randomly shut itself off. If its not one thing its something else I guess lol
This post is infected with the 3D strain of Gingeritis
When your next phone arrives, consider using quickboot to restart/turn off the phone. Might help prevent you from going thru the same ordeal again.
Sent from my ADR6400L using XDA App
Wrong thread LOL.
Sent from my HTC Thunderbolt
capflya said:
You asked
Hope your new phone is better in regards to the power button issue. Mine seems to be OK... Except I keep finding its randomly shut itself off. If its not one thing its something else I guess lol
This post is infected with the 3D strain of Gingeritis
Click to expand...
Click to collapse
Actually just got the new phone today and rooted it this evening. Everything works perfectly fine and the power button actually presses down now. lol
The only annoyance is that the speaker seems to crackle if above more than 1/2 volume. Thankfully, I can hear just fine if below that. But if it becomes too bad, I'll have to do another swap.
CanesDrew said:
Actually just got the new phone today and rooted it this evening. Everything works perfectly fine and the power button actually presses down now. lol
The only annoyance is that the speaker seems to crackle if above more than 1/2 volume. Thankfully, I can hear just fine if below that. But if it becomes too bad, I'll have to do another swap.
Click to expand...
Click to collapse
I try to avoid sending in for replacements...they always have problems.
Sent from my HTC Thunderbolt using Tapatalk!
Curious as to why you would bother unrooting software when hardware is the issue? Here's why I ask.
I buy all of my companies pcs and cell phones. If I wipe MSCRAP7 off the machine and it has a MB failure and I call the mfg and they send a new one i don't restore back to 7 why would you on the phone?
rcstilgar said:
Curious as to why you would bother unrooting software when hardware is the issue? Here's why I ask.
I buy all of my companies pcs and cell phones. If I wipe MSCRAP7 off the machine and it has a MB failure and I call the mfg and they send a new one i don't restore back to 7 why would you on the phone?
Click to expand...
Click to collapse
Because rooting voids your warranty...
rcstilgar said:
Curious as to why you would bother unrooting software when hardware is the issue? Here's why I ask.
I buy all of my companies pcs and cell phones. If I wipe MSCRAP7 off the machine and it has a MB failure and I call the mfg and they send a new one i don't restore back to 7 why would you on the phone?
Click to expand...
Click to collapse
Because if I don't, theres a strong risk I'll have to pay full retail for this replacement even though rooting didn't cause the hardware failure.
I'm guessing you're not rooted...
Sent from my ADR6400L using XDA Premium App
CanesDrew-
Love your signature. Care if I borrow it? I am a nursing student too.
emsrider said:
CanesDrew-
Love your signature. Care if I borrow it? I am a nursing student too.
Click to expand...
Click to collapse
Absolutely. Glad to know I'm not the only future male nurse on XDA. Lol
Sent from my ADR6400L using XDA Premium App
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.
Hey guys...
I was unfortunate enough to come across some aroma/twrp bug while updating my kernel and now my phone is bricked. Oh well, life happens. I am going to have to send it in for JTAG repair. I found that mobiletechvideos.com does JTAG repair for $60 so that's not all terrible. Do any of you have experience with them? Is there service good? From what I can tell they look legit..
On their website they also also have numerous "addons" you can choose for your order such as "ROM/Root upgrade service" and "S-off". Now, does that mean that once I get the phone back it will be in a state where I cannot root the device? I have my old bootloader unlock code from before... would that work to root the phone after this procedure is performed? It is my understanding that they (mobile tech videos) modify whatever image they push to your phone to include your IMEI information. Would that give me troubles if I tried to unlock the phone using my old unlock code?
Perhaps I should email them directly.
Anyway, what are your thoughts?
I would ask them, but I believe they can set things up however you want. I recall seeing one person saying they got it back s-off, etc.
iElvis said:
I would ask them, but I believe they can set things up however you want. I recall seeing one person saying they got it back s-off, etc.
Click to expand...
Click to collapse
I sent them an email. Yeah, you can pay extra for S-off etc.. but if I get the phone back in a state that I can do this myself why waste my money, right? I'll let you know when they get back to me.
ECEXCURSION said:
I sent them an email. Yeah, you can pay extra for S-off etc.. but if I get the phone back in a state that I can do this myself why waste my money, right? I'll let you know when they get back to me.
Click to expand...
Click to collapse
They do awesome work they fixed my s3 (borked imei)
Sent from my SGH-T889 using Tapatalk 2
Yea man from what I understand when you get it back you good to go. Unlocked and s-off.
Either which way, I'm sure you'll be glad to have your phone back
Sent from my One X using Tapatalk 2
Never used their service. But from lurking around these forums for a long time now there is nothing but good things to say about them
Sent from my VENOMized HoxL
ECEXCURSION said:
Hey guys...
I was unfortunate enough to come across some aroma/twrp bug while updating my kernel and now my phone is bricked. Oh well, life happens. I am going to have to send it in for JTAG repair. I found that mobiletechvideos.com does JTAG repair for $60 so that's not all terrible. Do any of you have experience with them? Is there service good? From what I can tell they look legit..
On their website they also also have numerous "addons" you can choose for your order such as "ROM/Root upgrade service" and "S-off". Now, does that mean that once I get the phone back it will be in a state where I cannot root the device? I have my old bootloader unlock code from before... would that work to root the phone after this procedure is performed? It is my understanding that they (mobile tech videos) modify whatever image they push to your phone to include your IMEI information. Would that give me troubles if I tried to unlock the phone using my old unlock code?
Perhaps I should email them directly.
Anyway, what are your thoughts?
Click to expand...
Click to collapse
They ask you for your imei before you mail it. They won't change your imei they reload of
Sent from my HTC One X using xda app-developers app
I'm very sad that you have to go through this with your phone
Sent from my SCH-I535 using Tapatalk 2
It will not effect you using your old unlock code.
Sent from my HTC One X using xda premium
I'd really like to buy a riff box. Does every diff brand of phone require a seperate box or does it just push software you load into it
Sent from my HTC One X using xda premium
DESERT.TECH said:
I'd really like to buy a riff box. Does every diff brand of phone require a seperate box or does it just push software you load into it
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
http://www.fonefunshop.co.uk/Unlocking/riff_box.htm
Scroll down and you'll see a huge list of devices supported by the one box. More devices added with firmware updates to the box. Ships from the uk as there is no distributor on this side of the oceans. afaik
But there are distributers on this side. Madusa riff boxes will do the same thing. The JTag site has a list of suppliers that sell riff boxes in the US. Since more devices are becoming usb supported, the need for soldering is limited to certain devices.
Sent from my HTC One X using xda premium
does JTAG'ing void the warranty as they have to open up the phone? I haven't looked in depth at videos of people opening up the phone but I can only imagine that they ahve some stickers inside...
If not, I'd definitely send my phone to them if it meant I could get S-OFF even though I'm on JB
nhshah7 said:
does JTAG'ing void the warranty as they have to open up the phone? I haven't looked in depth at videos of people opening up the phone but I can only imagine that they ahve some stickers inside...
If not, I'd definitely send my phone to them if it meant I could get S-OFF even though I'm on JB
Click to expand...
Click to collapse
I imagine it voids the warranty. But then again, unlocking the bootloader and rooting your phone could also void the warranty...
Thanks Venomtester, I guess I'll start packing up my phone then.
I used mobiletechvideos to fix my HBOOT and S-OFF and they did a fantastic job on both. I would recommend them to anyone looking for that service.
So I kow Mobile Tech does jtag but what if u dont have the IMEI because i got this phone in a trade and it doesnt have a IMEI sticker or whatever. I forgot to even write it down. Anyways I am not going to use the phone on contract so is there any other possible solutions?
AwesomeEvo said:
So I kow Mobile Tech does jtag but what if u dont have the IMEI because i got this phone in a trade and it doesnt have a IMEI sticker or whatever. I forgot to even write it down. Anyways I am not going to use the phone on contract so is there any other possible solutions?
Click to expand...
Click to collapse
Imei can be found in the bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Imei can be found in the bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Oh yeah well The phone is bricked too
Anyone seen this? Wonder of this could help some ppl out..
http://forum.xda-developers.com/showthread.php?p=29996469
Sent from my HTC One X using Xparent Green Tapatalk 2
AwesomeEvo said:
So I kow Mobile Tech does jtag but what if u dont have the IMEI because i got this phone in a trade and it doesnt have a IMEI sticker or whatever. I forgot to even write it down. Anyways I am not going to use the phone on contract so is there any other possible solutions?
Click to expand...
Click to collapse
IMEI is engraved into your simcard tray. Have a look
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 ...
I contacted somebody on craigslist about a nexus 5. He said it was running cyanogenmod 11 and he said that he didn't like it and was going to put it back to stock. He then messages me saying that something went wrong and that the phone is bricked. I ask him a few questions.. Is the bootloader unlocked, was usb debugging checked before it was bricked, can you get into recovery. He said yes to all of them. He then tells me that he was using nexus root toolkit. But run parallels on his Mac. So the commands are never the same. So the question I have do you think that it's fixable before I go and buy it. He was selling it for 250 but after the brick i told him I would buy it for 200.
If he has used a toolkit not meant for the Nexus 5, there's a good chance that his bootloader and other partitions might have got corrupted. Since he's telling you that he can get into recovery, why doesn't he just flash CM11 which might take him out of the bootloop? Sounds fishy.
Besides that, you know there won't be any warranty for this, right??
If I were you, I would stay away from such a deal. It's your call though.
If it turns on in one way or another it's hardly "bricked" lol.
How much is a digitizer worth? If it's truly bricked that's all that it would be worth to sell it as parts. I might risk it for $100
Sent from my Nexus 5 using XDA Free mobile app
Lethargy said:
If it turns on in one way or another it's hardly "bricked" lol.
Click to expand...
Click to collapse
That is what I was thinking. I mean if he can get into recovery then it's hardly bricked!
vin4yak said:
If he has used a toolkit not meant for the Nexus 5, there's a good chance that his bootloader and other partitions might have got corrupted. Since he's telling you that he can get into recovery, why doesn't he just flash CM11 which might take him out of the bootloop? Sounds fishy.
Besides that, you know there won't be any warranty for this, right??
If I were you, I would stay away from such a deal. It's your call though.
Click to expand...
Click to collapse
Yeah I knew that there wouldn't be a warranty for this, I don't think any of my last few phones had a warranty so I am not worried about that. I have a few hours to decide.
It's not bricked I have bricked Nexus trust me it's bricked:crying: I can't get even into any recovery or bootloader.. I do have a new a nexus though i bought from swappa:good:
kidnice15 said:
That is what I was thinking. I mean if he can get into recovery then it's hardly bricked!
Yeah I knew that there wouldn't be a warranty for this, I don't think any of my last few phones had a warranty so I am not worried about that. I have a few hours to decide.
Click to expand...
Click to collapse
Personally I would just buy a brand new one off Google, no risk of "bricked" (lol) phones from other people, and it's not too much more (in comparison to other devices). Plus you get warranty :silly:
yyz71 said:
It's not bricked I have bricked Nexus trust me it's bricked:crying: I can't get even into any recovery or bootloader.. I do have a new a nexus though i bought from swappa:good:
Click to expand...
Click to collapse
Yeah that is what I am thinking, if I can get into recovery I gotta be able to un "brick" it. What I am going to do is make sure I can get into recovery before I buy it.
kidnice15 said:
Yeah that is what I am thinking, if I can get into recovery I gotta be able to un "brick" it. What I am going to do is make sure I can get into recovery before I buy it.
Click to expand...
Click to collapse
Once you could do that your good to go:good:
Could be radio bricked. Could be a bargain. Could be a risk.. Getting into recovery is no sure fire way to say it's repairable.
Whats USB debugging got to do with anything ?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Could be radio bricked. Could be a bargain. Could be a risk.. Getting into recovery is no sure fire way to say it's repairable.
Whats USB debugging got to do with anything ?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have no idea! I was reading up on unbricking Nexus 5 and they all kept saying make sure USB debugging was checked. Like yous aid. Could be a bargain, could be a risk. I am still debating on buying it.
You could meet him somewhere with WiFi, like Starbucks. Then try to flash a stock Rom and see if everything on the phone works. If it were me I'd just buy a new one tho.
Lokke9191 said:
You could meet him somewhere with WiFi, like Starbucks. Then try to flash a stock Rom and see if everything on the phone works. If it were me I'd just buy a new one tho.
Click to expand...
Click to collapse
Yea most likely I am going to head to swappa.
It could have other issues. What if its black listed, and he tried to brick it so no one can test it.
What if it turns on, but it got water damage and something else is wrong.
What if there's a hardware failure for sound or radio or anything.
Can't test much in the state its in. I say you're basically gambling.
---------- Post added at 07:04 PM ---------- Previous post was at 07:03 PM ----------
100 more buys you a perfectly working one.
So I took the gamble and decided to meet the guy.. He worked at AT&T, met him at his store, that was a plus and not in some alley lol. I had my laptop with me and after I bought it. I tried to unbrick it. I unbricked it. It's working flawlessly, checked the ESN on swappa and it's not blacklisted. It was a risky gamble but it did work out. Thanks for all the help on here.
Cool! ?
@kidnice15
That's great. Congrats! Welcome to the n5 gang
kidnice15 said:
story
Click to expand...
Click to collapse
Great story to share with us. Hopefully you'll enjoy using your Nexus 5 and let's hope the phone continues to work for you.
Sent from my Nexus 5
kidnice15 said:
So I took the gamble and decided to meet the guy.. He worked at AT&T, met him at his store, that was a plus and not in some alley lol. I had my laptop with me and after I bought it. I tried to unbrick it. I unbricked it. It's working flawlessly, checked the ESN on swappa and it's not blacklisted. It was a risky gamble but it did work out. Thanks for all the help on here.
Click to expand...
Click to collapse
Its not an "unbrick" if it wasn't really "bricked" in the first place!
Sent from my Nexus 5
yyz71 said:
It's not bricked I have bricked Nexus trust me it's bricked:crying: I can't get even into any recovery or bootloader.. I do have a new a nexus though i bought from swappa:good:
Click to expand...
Click to collapse
How do you brick a nexus device? If you say toolkit I give up.