Related
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Should verizon replace your phone after you borked it? I think you already know the answer
xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.
Should they? Technically no. Will they? Sure. They would be happy to.
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.
Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?
This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.
If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse
Just say you tried to install the last update and your phone wont boot now. They won't know the difference.
dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.
xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk
Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ
xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.
My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
lkrasner said:
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
Click to expand...
Click to collapse
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
jimbridgman said:
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
Click to expand...
Click to collapse
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Edit: If this does work I owe you something huge, plus I would get my screen problem fixed
EDIT 2: would I be better off just deleting something that would just stop if from booting past the boot logo (big M) so it wouldn't be so obvious that I just killed it with is basically sayins so on the fastboot screen. If so what could I delete that wouldn't prove I had rooted, probably nothing now that I say that.
lkrasner said:
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Click to expand...
Click to collapse
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
jimbridgman said:
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
Click to expand...
Click to collapse
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
lkrasner said:
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
Click to expand...
Click to collapse
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
The secret is to act dumb, pretend like you know nothing bout flashing and this site... just act like it just went nuts and started this, and it will not boot.
Ask for the advanced replacement.
jimbridgman said:
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
Click to expand...
Click to collapse
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
if it is borked when you take it to the store they can't see that it is rooted cause it won't boot... all they are going to do it call their 1-800 number and help you file a support request... then the person the phone will let you know of the "requirements" and ask if the phone has any visible water damage, yadda yadda...
Then they will send you a new phone and you should get it in 3 or so days and you are supposed to send the old one back in the SAME box... so you will already have flashed the fxz and been using the phone the whole time you waited for the new one to show up... just don't forget to send it back... I did and waited until 25 days later, and I was bugged mercillessly by att...
Just make sure you factory wipe and take out your sim and SDcard, and battery door... they do not send anything but the core of the phone, no batt or batt door or anything.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
@jim on playing dumb,hilarious ..i do that when i upgrade my phone.im such an ass when i upgraded to a2 from xperia x10 that i didnt even bother restoring it to stock, i left cm7 on it,custom bootlogo ,said "free xperia team" on boot.i just pretended i didnt know what happend. it was so enjoyable.
service rep - "it appears to be rooted"
My response - "What do you mean rooted? It has roots like a plant?".
@krasner
You worry to much,they cant prove anything.just brick it and youll be fine.u could even play dumb as u crack a smile while doing so and they still really cant do anything to prove u did it and have to exchange it.
Sent from my MB865 using xda premium
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
lkrasner said:
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
Click to expand...
Click to collapse
Maybe 150. It wont be "NIB" you will not get a box, batt, back cover, etc. With the replacement.
Sent from my SAMSUNG-SGH-I747, running CM9, using xda premium
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929
Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?
Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.
iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.
Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300
Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?
If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.
Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.
Hey there,
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked. By the magic operation of Jesus maybe, who knows.
It don't boot, I don't see anything on the screen, I don't know if it is turned on or off… It just won't reply. To anything, fastboot, adb or whatever else. I can't boot in recovery or something else.
I think I have a splendid bricked late-2013 phone… I followed some tutorials to unbrick phones, the power + trick, but nothing.
The only thing I have on a windows computer is a "tadam" when I plug the USB, but that's it, no fastboot or adb, no screen, nada. But this sound of a plugged USB device. Knuh…
What the hell can I do ?
Shall I call Google tomorrow for RMA ?
ps: i saw some threads like me, i followed replies, but after a 4 hours searching, I don't wake up my phone
Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937
esskayy said:
Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937
Click to expand...
Click to collapse
yap, but no more results…
I think I tried all solutions on xda, no one worked :s
Flayks said:
yap, but no more results…
I think I tried all solutions on xda, no one worked :s
Click to expand...
Click to collapse
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.
esskayy said:
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.
Click to expand...
Click to collapse
Damned… why
Please, Google, don't be cruel with me
Flayks said:
Damned… why
Please, Google, don't be cruel with me
Click to expand...
Click to collapse
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader
esskayy said:
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader
Click to expand...
Click to collapse
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
doesn't boot*
*grammar police*
Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA
Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
That would work. Just don't say "send me another" ask "what do I do now"
apristel said:
doesn't boot*
*grammar police*
Click to expand...
Click to collapse
ups, thx.
esskayy said:
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA
Click to expand...
Click to collapse
Yep, I will call the support…
jd1639 said:
That would work. Just don't say "send me another" ask "what do I do now"
Click to expand...
Click to collapse
I would like to…
Thankz!
" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.
apristel said:
" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.
Click to expand...
Click to collapse
How do you know the phone isn't booting due to his bootloader being unlocked? He even said it was fine and it was not booting today....
Sent from my Nexus 5 using XDA Premium 4 mobile app
Because it booted afterwards. Thats how. .
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse
apristel said:
Because it booted afterwards. Thats how.
Quote:
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…
Flayks said:
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…
Click to expand...
Click to collapse
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.
Dude you need to chill a little. Unlocking your bootloader does not completely null warranty. If you brick your phone via software then you are responsible.
By the sounds of what is happening with the op, he has not changed anything to end up in this predicament. As with the other purple with similar problems (unlocking bootloader resulting in brick) can hardly be pointed at them.
Clearly something is happening which is out of user control which is causing these bricks.
If the ROM fails to boot it will throw you back to the bootloader.
If the bootloader fails you have a brick (not 100% true but not going into that now)
The facts are that the op has unlocked the bootloader which is a legitimate task and has for unknown reasons ended up with a corrupt bootloader.
This should still be covered as the op has not fine anything to solicit what had happened.
Sent from my Nexus 4 using xda app-developers app
apristel said:
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.
Click to expand...
Click to collapse
Personally from my own experience, as the disclaimer on the bootloader unlock screen states 'This MAY void your warranty', telling Google the truth would be his best bet. Call Google, advise that the bootloader was unlocked and worked for 3 days and then it suddenly stopped booting.
If you bought a Nexus 5 and don't plan to do anything to it then that's up to you. However some of us buy Nexus devices because of the ease of development on them. Google facilitate this with the ability to unlock the bootloader and have no justifiable reason to refuse an RMA when all the OP has done is unlock said bootloader.
Why don't YOU stop being a **** and get off this thread. Please.
Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others
daniel.kusy said:
Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others
Click to expand...
Click to collapse
Apparently yes, I'm not the only one. It would be great if you try to explain your solution!
Please forgive my ignorance, I'm new to this!
Here's what's going on.
I bought the device, turned it on, and it opens to someone elses LOCK SCREEN. Maybe I shouldnt have but I immediately factory reset.
During reset, says "E:failed to mount / preload (No such file or directory)" - Was it rooted before? When I turn it on, I get the google lockout "please enter an email address previously associated with this device". Obviously, I have no idea what that is. Person who sold it to me says they don't know what i'm talking about. I just want to use the device (Don't necessarily want to root it, but only beacuse I'm afraid of bricking. I'm not opposed to the idea, and I rooted my galaxy nexus way back when) Obviously, because I can't get to the settings, I can't enable debugging or OEM.
BUT - The device DOES enter download mode! Does this mean I can flash a factory image? If so, will my google lockout problem even go away if I do? Note 5 came with 5.1.1, which is when they implemented the lockout; would 5.0 run on a note5 at all?
Any help would be appreciated.
jemisexcitement said:
Please forgive my ignorance, I'm new to this!
Here's what's going on.
I bought the device, turned it on, and it opens to someone elses LOCK SCREEN. Maybe I shouldnt have but I immediately factory reset.
During reset, says "E:failed to mount / preload (No such file or directory)" - Was it rooted before? When I turn it on, I get the google lockout "please enter an email address previously associated with this device". Obviously, I have no idea what that is. Person who sold it to me says they don't know what i'm talking about. I just want to use the device (Don't necessarily want to root it, but only beacuse I'm afraid of bricking. I'm not opposed to the idea, and I rooted my galaxy nexus way back when) Obviously, because I can't get to the settings, I can't enable debugging or OEM.
BUT - The device DOES enter download mode! Does this mean I can flash a factory image? If so, will my google lockout problem even go away if I do? Note 5 came with 5.1.1, which is when they implemented the lockout; would 5.0 run on a note5 at all?
Any help would be appreciated.
Click to expand...
Click to collapse
Sounds like a stock factory image flash via Odin is the best thing you can do. Who knows what is on that phone.
+1. Odin to stock. You can get Odin and the stock image from Tek's sticky at the top of this section.
Here's the thing, if you met face to face you should have tested it. If you purchased it online, should have been reset. Sounds suspicious to me. Either the seller isn't being honest or, not to accuse you, you are not. Let's assume the seller, verify the imei number with swappa or another service and see what that tells you if you haven't. I would be cautious using the phone, hopefully it's not going to be an issue for you.
Ducter said:
Here's the thing, if you met face to face you should have tested it. If you purchased it online, should have been reset. Sounds suspicious to me. Either the seller isn't being honest or, not to accuse you, you are not. Let's assume the seller, verify the imei number with swappa or another service and see what that tells you if you haven't. I would be cautious using the phone, hopefully it's not going to be an issue for you.
Click to expand...
Click to collapse
It is very sketchy. I don't blame you for being suspicious of me, but I will say that before I reset the thing, the person's lock screen had a new email notification, which listed their address, and I did send them a message asking if they lost a phone. I would be fully willing to return it at no cost if they responded to me saying they did indeed lose it, but that hasn't happened, and it's been a while.
You sound like you think I should just dump it? I'd like to either find out if it's missing or use it, but if you think something might happen to me, maybe I will? What do you think could happen?
10-K said:
+1. Odin to stock. You can get Odin and the stock image from Tek's sticky at the top of this section.
Click to expand...
Click to collapse
Do you mean this rom? http://forum.xda-developers.com/tmo...-port-urv1-t3202330/post62846647#post62846647
No. One of the Samsung stock roms that appear at the top of this thread.
http://forum.xda-developers.com/showthread.php?t=3187422
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
I'd try to use it. Worse case scenario it gets blacklisted and they turn it off.
Karakoram2 said:
No. One of the Samsung stock roms that appear at the top of this thread.
http://forum.xda-developers.com/showthread.php?t=3187422
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
I'd try to use it. Worse case scenario it gets blacklisted and they turn it off.
Click to expand...
Click to collapse
Oops, sorry. Well, thanks for your help. It'll take a few hours to download the stock image but I'll let you guys know what happens.
When I'm just flashing stock I don't use a kernel or anything like that, right? I'm usually the one getting irritated at people for not using the search function, but when it comes to CFW/Smartphones I just always want to make 100% sure I know what I'm doing. I don't want a $400 brick.
I really appreciate all the help!
I don't think you can just flash stock and beat this. If you cannot anyway, there's another forum called.. GSM something or other, and I've seen people post they can beat the Google email requirement with a black box.
jemisexcitement said:
Oops, sorry. Well, thanks for your help. It'll take a few hours to download the stock image but I'll let you guys know what happens.
When I'm just flashing stock I don't use a kernel or anything like that, right? I'm usually the one getting irritated at people for not using the search function, but when it comes to CFW/Smartphones I just always want to make 100% sure I know what I'm doing. I don't want a $400 brick.
I really appreciate all the help!
Click to expand...
Click to collapse
Don't do anything with that phone. Go and get your money back and try a different seller. You have been warned.
Sent from my SM-N920T using Tapatalk
Jammol said:
Don't do anything with that phone. Go and get your money back and try a different seller. You have been warned.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Why, what can happen?
I can remove the Google lock
Sent from my SM-N920T using Tapatalk
The failed to mount message is I guess normal because I have a new note 5 from t mobile. I did a factory reset and it gave me that message also.
Sent from my SM-N920T using Tapatalk
jemisexcitement said:
Please forgive my ignorance, I'm new to this!
Here's what's going on.
I bought the device, turned it on, and it opens to someone elses LOCK SCREEN. Maybe I shouldnt have but I immediately factory reset.
During reset, says "E:failed to mount / preload (No such file or directory)" - Was it rooted before? When I turn it on, I get the google lockout "please enter an email address previously associated with this device". Obviously, I have no idea what that is. Person who sold it to me says they don't know what i'm talking about. I just want to use the device (Don't necessarily want to root it, but only beacuse I'm afraid of bricking. I'm not opposed to the idea, and I rooted my galaxy nexus way back when) Obviously, because I can't get to the settings, I can't enable debugging or OEM.
BUT - The device DOES enter download mode! Does this mean I can flash a factory image? If so, will my google lockout problem even go away if I do? Note 5 came with 5.1.1, which is when they implemented the lockout; would 5.0 run on a note5 at all?
Any help would be appreciated.
Click to expand...
Click to collapse
The E failed message always pops up when factory reseting a Samsung phone and the email requirement is part of the previous user activating the reactivation lock. If a hard reset is done with the option enabled the phone is inaccessible till the original email info is entered. Maybe seller forgot to deactivate it b4 selling, happens a lot actually. Many ppl activate it on initial phone set up and forget or don't know exactly how it works and sell without turning it off.
Sent from my SM-N915P using XDA Free mobile app
RayTrue04 said:
The E failed message always pops up when factory reseting a Samsung phone and the email requirement is part of the previous user activating the reactivation lock. If a hard reset is done with the option enabled the phone is inaccessible till the original email info is entered. Maybe seller forgot to deactivate it b4 selling, happens a lot actually. Many ppl activate it on initial phone set up and forget or don't know exactly how it works and sell without turning it off.
Sent from my SM-N915P using XDA Free mobile app
Click to expand...
Click to collapse
Exactly. Odin may not be able to help him either.
jemisexcitement said:
Why, what can happen?
Click to expand...
Click to collapse
You can and will be locked out of the device permanently if Odin fails. It's best to contact the seller and get them to clear it by entering the required info or just get your money back. Next time check your stuff before you buy. And how come you didn't in the first place? Your story doesn't exactly add up or exist.
Sent from my SM-N920T using Tapatalk
Jammol said:
Exactly. Odin may not be able to help him either.
You can and will be locked out of the device permanently if Odin fails. It's best to contact the seller and get them to clear it by entering the required info or just get your money back. Next time check your stuff before you buy. And how come you didn't in the first place? Your story doesn't exactly add up or exist.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
You know what dude, even IF my story didn't add up, even IF I stole it, what are you, the police? Why are you in here picking a fight with me man? You really think I'd STEAL a phone and come to these forums with a made up story? You don't think I'd make up a BETTER STORY? I could say it was a girlfriends and we broke up on bad terms, I could say anything and it would be easy to lie about. You need to calm down and have some common decency, please.
Have you odin'd to stock yet? And, no you don't need to flash a kernel. The stock image comes with the stock kernel.
jemisexcitement said:
You know what dude, even IF my story didn't add up, even IF I stole it, what are you, the police? Why are you in here picking a fight with me man? You really think I'd STEAL a phone and come to these forums with a made up story? You don't think I'd make up a BETTER STORY? I could say it was a girlfriends and we broke up on bad terms, I could say anything and it would be easy to lie about. You need to calm down and have some common decency, please.
Click to expand...
Click to collapse
A lot of people come here after they have stolen a phone. Funny thing you didn't go off on the other person that said the very same thing. I asked you those questions because someone else did and you didn't answer them. And just so you know, no I'm not a cop anymore. I was simply seeing what you would say. You need to calm down and look at it from the end of the spectrum. I don't know you, and I don't know if you would come on here after stealing a phone with a made up crappy story. Not like that hasn't happened before from others.
I was simply trying to help you but whatever. If you didn't steal it, hope it works out and you get to use your phone.
Odin COJ5, boot into recovery and do a wipe.
Sent from my SM-N920T using Tapatalk
Hi. I'm having this same issue. Flashed stock with odin but to no avail. Also tried mounting an otg cable but my n920t won't recognize it. Any ideas?
https://youtu.be/DJ8_qbj1DPQ
Sent from my SM-N920T using Tapatalk