Related
The story goes like this:
I have a Desire and today saw a local Ad where a guy sells a Htc Desire Z stuck at boot after upgrading. Thats the only info provided.
Now, the price is around 160 euros or 222 us dollars.
I have lots of experience with root/s-off from the Desire and anything with that shouldn't be a problem.
My questions are:
Is there a way to brick this phone?
Can it be somehow unbricked?
If the guy tried to update the phone to the latest one, can i root it then or downgrade it perhaps and root then?
Thank you very much whoever answers this.
Well hopefully some brighter folks than I can ellucidate whether it is possible to get out of a bootloop.
What I can offer however is my opinion on the purchase overall. $222USD is a good chunk of change. If there's a chance that it is not recoverable, I don't think it would be worth the gamble. Now if it were the nearly unbrickable Vibrant or something, I'd say go for it.
I bought my G2 in near mint condition for $275.
It all depends, Is it S-off? Does he have a custom recovery installed? Can you boot into Hboot and then into recovery(Clockworkmod Recovery)? If so then you probably can install a rom on the sdcard and flash them from recovery.
If its in a boot loop with S-on I would not touch it.
Boot loop with S-ON means it still has Nand protection which means you can't do shiz with it. I do have a little story though.
Bought a G1 off craigslist and shortly after the screen started acting wonky so I said what the hell and called Tmo. Explained the problem and hoped theyd have some pointers since the G1 was new and resources like this didn't exist at the time. They ended up being able to look up the phone and determined it still had warranty time left on the device so they exchanged it for me. Sometimes warranty carries over with phones. I'd call Tmo before I bought though and have them go ahead and send me a refurb then go buy the bootlooped one and send it back.
Supposedly he tried to install a different ROM which implies that he's rooted.
That should be fixable then, right?
Or is s-off really necessary for the Z?
UPDATE:
he just lowered the price to around 100 euros.
hiko36 said:
Boot loop with S-ON means it still has Nand protection which means you can't do shiz with it. I do have a little story though.
Bought a G1 off craigslist and shortly after the screen started acting wonky so I said what the hell and called Tmo. Explained the problem and hoped theyd have some pointers since the G1 was new and resources like this didn't exist at the time. They ended up being able to look up the phone and determined it still had warranty time left on the device so they exchanged it for me. Sometimes warranty carries over with phones. I'd call Tmo before I bought though and have them go ahead and send me a refurb then go buy the bootlooped one and send it back.
Click to expand...
Click to collapse
I actually just did something similar. I bought a used G2 that was in perfect physical working order but with physical blemishes etc. and was about 3months old. About a week later dust started to accumulate under the screen. Even though the phone was used and I was on a EM+ plan with no contract and I didnt purchase the phone from a T-mo store, they still replaced it for free. More of a statement about how great T-mo support is than anything, but I think its interesting that they will support the device even though its used.
Now anything more than this is quite borderline not very ethical depending on who you ask, but I wouldn't really feel like buying a bootlooped phone just to try and send it back to T-mo and claim you don't know what happened. If that was very possible then the guy that currently has the phone would probably have done that already...
Yeah, i bought it.
The problem is/are it won't boot or turn on at all.
I'll send it to the repair shop to see if anything can be done.
And guess what.
Do you remember when the HTC vision/g2/desire z got leaked?
This picture here
It turns out, it's the same phone
THE SAME PHONE, Look at the serial numberl
DanijelDesire said:
Yeah, i bought it.
The problem is/are it won't boot or turn on at all.
I'll send it to the repair shop to see if anything can be done.
And guess what.
Do you remember when the HTC vision/g2/desire z got leaked?
This picture here
It turns out, it's the same phone
THE SAME PHONE, Look at the serial numberl
Click to expand...
Click to collapse
PLEASE tell me you kept that. That would be like getting that first iphone that homeboy lost in the bar.
I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)
Sent from my SGH-T989 using Tapatalk 2
LuniZ916 said:
I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)
Click to expand...
Click to collapse
Same thing happen to me the dreaded QHSUSB error when I bricked my exhibit2. I know how you feel.
Sent from my SGH-T989 using XDA Premium App
Lol. I bricked mt very first phone (the T989) the very first day i got it. I got it replaced for free with that 14 day gap thing that Tmo has. Got lucky. Ive never had a bad flash since.
Sent from my SGH-T989 using xda app-developers app
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Stupid kies mini hard bricked my trusty vibrant... Luckily, t-mobile replaced it for free, but it was the horrible exhibit 1.
supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Yeah most people went through regular warranty exchanges, but from what the OP was explaining he's a very honest person and would have said that he rooted the phone therefore he would not be able to exchange it.
That's good that he's honest, but it would have been a lot easier to just do that and get the phone next day because TMobile is just going to send that phone back to Samsung and they'll do the exact same thing they're doing to his phone now
Sent from my SGH-T989 using xda app-developers app
This sounds exactly like something I would! Especially buying parts thinking I could fix it!!
I feel so at home on xda!!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
U could a saved a ton of time and money by just saying ur phone stopped working. Cuz technically it did
Sent from my SGH-T989 using xda app-developers app
LOOOOOOL this made my day^^
I have my phone till two years now and i bricked it once by disconnecting by mistake while unlocking bootloader (yes i fell with my phone in the hand and lukily it only disconnected and didnt pull my laptop with it.
I had it fixed in a half hour^^
Greets
Sent from my Xperia X10 using xda app-developers app
Good to know thanks
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
My very first device was the Mytouch 3G on T-Mobile. Back then, it was maybe the 2nd Android phone to have even existed at that point.
Me, never being satisfied with anything stock and coming from a heavily modified blackberry, wanted to tweak the hell out of it.
Back then, it took a LOT more to root and flash, ESPECIALLY HTC Devices. There were no custom tools yet to root, and the only easy part was using CWM. You HAD to use adb commands to exploit to get root and even get CWM on the device at that point, but only AFTER downgrading it back to Android 1.5, but after that it was easy.
(I couldn't believe how fast and easy it was to root and flash on the T989 after having HTC devices up until last year)
Anyways, I somehow managed to get it CWM to boot (you had to boot into normal recovery after replacing update.zip with a CWM zip, and then flash the new update.zip file back then) and went to flash a ROM, and instead I flashed a zip, but the wrong ROM was uploaded by the OP, and what I had flashed as for the G1. It was literally only uploaded for all of maybe 2 minutes before he pulled the post down and uploaded the correct version.
I was the ONLY one who downloaded and flashed it within that 2 minute window.
Needless to say, I hated my life.
Now the funny part:
I was so paranoid back then about not letting T-Mobile know that I was rooted, that I literally bought a BRAND NEW Mytouch 3G (because you couldn't even find broken ones on ebay yet) and sold the broken one, which I bought the day before mind you, for $20. I wish I would have known that, back then, there were no counters on the MT3G. T-Mobile would have never known as it wouldn't boot.
:crying:
Flash forward to today, and IDGAF.
Hi, i'm thinking about taking out a contract to get a HTC One X, seems like the best phone that's in my price range, however i'm seeing this offer with my network for a refurbished HTC One X that I get free on a low-pay contract. (meaning I won't have to pay the £100 to get the phone to keep the low-pay contract.) It says it's as good as new, but I was wondering will the refurbishment change any HTC settings or what not that will not allow me to root? I currently have a HTC Desire Z, and like the freedom to flash custom ROM's and change phone settings etc. So will a refurb affect this?
Note: This is what the website says for the refurbishment.
It's a used phone that's been restored to its original state, so it's as good as new. You'll receive a phone, battery and charger. You can start using it straight away!
It'll be same as a new one, except refurbished. Wont be any differences software wise.
You will still be able to root.
Some people are reluctant to take refurbished handsets. The reality is you still get your 12 months manufacturers warranty (can be 24 months in some places) and if anything your refurbished phone has actually gone through more testing than a new handset.
nookcoloruser said:
It'll be same as a new one, except refurbished. Wont be any differences software wise.
You will still be able to root.
Some people are reluctant to take refurbished handsets. The reality is you still get your 12 months manufacturers warranty (can be 24 months in some places) and if anything your refurbished phone has actually gone through more testing than a new handset.
Click to expand...
Click to collapse
Yeah that's what I thought, I have to say to begin with I was one of those as you so put it reluctant people just because of the refurbishment, but the more I think about it the more appropiate it seems... I need a contract anyway to be honest, at the minute i'm on Pay as you go, which is alright but more often than not I forget to top up, plus it's my birthday in 8 days D) so this could go to that Plus I already have a fine rooted G2 running CM9, so if it does go bad after the warranty always got a backup phone Looks like i'll be the proud owner soon of a refurbished rooted HTC One X Thanks a lot
I'd like to share with you all my tale of rom flashing gone horribly wrong. It's really only important for 2 pieces of misinformation that I've seen kicking around the forums. First, the story.
I had already rooted my Telus Galaxy S3 (SGH-i747M), but was still running stock. I started looking around for compatible roms running JB, but didn't have much luck (finding ones that support the Canadian version is not easy). At the same time, I had to update and reset my old Galaxy S2 for a relative who was taking it off my hands. I found a JB rom that was available for both the S2 and S3, from the same dev. I decided to try both out, downloaded them and copied the respective files to the S2 and S3, but quickly realized that the S3 version didn't support my Canadian phone. No problem, I'll leave the S3 as rooted stock.
I proceeded to flash and install the rom on my S2. Everything seemed to be going fine until the first reboot after flashing. The phone appeared to be completely dead. I tried putting the phone into download mode but it was completely dead and would not even show signs that it was plugged into a power outlet. Then, horror. Both my S2 and S3 are in Otterbox Commuter cases. They look very similar. At 1 in the morning in a dimly lit room, they look identical.
Yes. Like an idiot, I had installed the incompatible S3 rom to my Canadian S3. I had, in fact, hard bricked my phone. I set aside my grief for 10 minutes and got the S2 done, as that was the original goal of this adventure. That worked fine. Of course.
For the next several hours and most of the following day, I searched and searched. I ended up on the posts talking about QHSUSB_DLOAD and how I'd screwed myself. No hope. Only option is either JTAG service or, and this brings me to misinformation #1, sending it back to Samsung. Why send a rooted and screwed phone back to Samsung? Well, the argument was that in all likeliness they wouldn't be able to tell and would probably just get it up and running anyway, perhaps with some nominal fee. Also, and here comes misinformation #2, there was a good chance that they would have to fix the problem in order to verify it.
Thankfully, in my only intelligent move in the last year, I had opted to choose the extra device protection offered by my carrier. Which meant, if it wasn't covered under warranty, I could get a brand new phone at a significantly reduced rate. But it did mean I had to send it in to Samsung first. And so, I walked into a carrier store and simply stated that it wouldn't power up. I neglected to mention the whole "I'm an idiot and accidentally installed an incompatible rom at 1AM". At the end of the day, they don't care anyway.
So I waited for almost 3 weeks before getting an update from my carrier. Samsung had looked at it and had a quote. I called the store to find out the cost. The phone needs a new mainboard. $350+ (I remember it being more than $350 but less than $400). Ah, no thank you. I politely declined and contacted the company providing the device protection. No problem, phone would be in my hands in 2-3 business days. I just need to send the damaged phone back when I get it from Samsung.
When the phone did get back from Samsung (within 24 hours, I might add), it came with a note to the carrier indicating that the phone had been rooted. The store manager actually made a good point too. If they were able to get it up and running to figure out it was rooted, why did it need a new mainboard? In all likeliness, they just wanted to teach me a $350+ lesson in voiding the warranty. So, what did I learn from this experience?
1) If you are rooting multiple phones, don't leave them all laying around in identical cases in a dimly lit room at 1AM.
2) Don't root phones in a dimly lit room at 1AM.
3) If you royally mess up your bootloader and it won't boot up, Samsung can still boot up that phone.
4) If that same phone is rooted, Samsung can not only tell, but ensure that the phone remains in it's screwed state for return.
5) They might just try and teach you a $350+ lesson; my guess is this ultimately depends on who looks at it (just like walking into an Apple store and walking out with a replacement, prior to Applecare+).
If anyone is curious why I didn't JTAG service the phone, it's simply because I can't afford to wait that long without a phone and the cost difference between JTAG and my device protection plan is not significant.
I think the are full of it.. I bet they did not even boot it up.
It would be possible for them to boot into download mode using a JTAG device, flash a working bootloader and at the very least load up a recovery environment terminal to check for root access. This is assuming of course they couldn't do this directly from their JTAG skipping having to fix the bootloader. Even so whats to stop them flashing a non working bootloader back to the device after they found what they are looking for. Not only would this not take very long, for the chance at turning 350 bucks work of profit vs a warranty fix im sure the techs are required to do this. This of course doesn't justify the obvious fact that a replacement motherboard is completely ridiculous. I'm of the opinion that it isn't right to cheat the manufacturers by getting warranty replacements on user created errors, however if they are attempting to gouge the end user instead of just charge them to fix the problem then i say all's fair. Lets face it, its not as if they don't take these warranty devices, especially the hard bricked ones, and simply fix the software, repackage and sell them again.
Exactly. I sent it in and fully expected some kind of charge, like labor, to get it working again. But not almost $400.
Yea, that is pretty lame. Its no different than a damaged led lens, which they charge the full LED assembly price of $175 instead of just fixing the problem. I just did this today on my phone for $20 and an hour or so of my time.
Wow that sucks. At least your other phone still works.
sent from my rooted galaxy 3.6
Noob question:
Did you use Triangle Away? If they can just boot up the device and find if you have root access, is the point of Triangle Away just aesthetics?
I think that is more or less an easy give away the uneducated rep at the sales counter can look for.
i must confess i've rooted my phone dozens of times, and i can say that over 80% of those were in the dark after midnight.
Yeah, me too. It only takes one mistake though ...
yes rooting is such another .apk on the phone and certainly does not void the hardware warranty... Obviouisly they should charge you for software issues which you did.. did you get the phone back and have someone else jtag and fix it?
No. I have to send it back in to the company I have device protection through. But I have a new S3 already. JTAG would probably work, but it would take too long and isn't much cheaper than getting the new one.
Sent from my SGH-I747M using Tapatalk 2
And yeah your full of it lmao. I had a galaxy s3 that just stopped working after being left in charger a night. Took it.to a rsi (Samsung official customer service and service center here in dallas Texas) and they said the motherboard was ruined. And it was stock non rooted. And it was covered under warranty and they had to create a new imei for the phone. So $350? Yeah right
Sent from my SGH-I747 using xda premium
Sorry, I'm full of it? Your phone is non rooted, so your point is completely moot. Your phone legitimately died. Mine was screwed because of my own fault of flashing the wrong rom. There was and is nothing wrong with the motherboard on this phone. They were just trying to teach me a $350 lesson in rooting/voiding my warranty. But thanks for your insightful comment.
JTAG
bionemesis said:
Sorry, I'm full of it? Your phone is non rooted, so your point is completely moot. Your phone legitimately died. Mine was screwed because of my own fault of flashing the wrong rom. There was and is nothing wrong with the motherboard on this phone. They were just trying to teach me a $350 lesson in rooting/voiding my warranty. But thanks for your insightful comment.
Click to expand...
Click to collapse
happened to be last night,only option was to JTAG it so sent it to MTV Mobile Tech Videos,sucks ass....will se how long i am in Texas and sent it to Bryan Texas.Hopefully Get it back albeit in one piece by Wednesday Meanwhile i have no Phone.
This is not to offend anyone or cause a flamme war.
But I don't think people should be lying to Samsung or any carrier, that 1. Your phone isn't bricked/rooted and 2. That you have no idea of what's going on and it just wouldn't turn on.
You as a user should hold all responsibility for a bricked device. Should they charge you 400$? Damn right they should.
That's one of the many reasons why Samsung and many other carriers either ship their devices with locked bootloaders or don't release source code. And don't say the whole "I played 500$ for my phone I get to do what I want," yeah you're completely right. But let's say you're changing your cars oil and the person being the n00b that they are decides to mix synthetic oil and convention oil in the engine. Oh no you're screwed. You dont take your car to the dealership saying "I don't know what happened the engine just won't turn on," THEYRE GOING TO KNOW lol, and expect to get a free car or not get charged for your miss hap. C'mon. If you screw up at least be responsible to pay some kind of fee to get it fixed. I despise folks who "try to play the system" because of them phones will be locked down in the near future. Now its illegal to carrier unlock your device unless its paid for because of folks like that. I understand the OPs mistake. Yeah I've done it. But I paid to fix my mistake. Be responsible people. We're grown ups here. Same with flashing stuff. Do a little reading before you start a thread on how you "bricked your phone" but its really stuck in a boot loop.
Just my 2¢
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I couldn't read all of that I must have a terrible attention span these days.
But I did read that you were with telus, not at&t; but of course its morally wrong to lie to at&t but the way I see it is I pay them $2000+ over the course of my contract for this phone and if I want to take advantage of their warranty system to save $300-400 (a small fraction of what they're making off of 1 customer) and try my best to get a free replacement you can bet your ass I will.
Heisenberg420 said:
I couldn't read all of that I must have a terrible attention span these days.
But I did read that you were with telus, not at&t; but of course its morally wrong to lie to at&t but the way I see it is I pay them $2000+ over the course of my contract for this phone and if I want to take advantage of their warranty system to save $300-400 (a small fraction of what they're making off of 1 customer) and try my best to get a free replacement you can bet your ass I will.
Click to expand...
Click to collapse
I see were you're getting at but you pay ATT for a service, not a phone. Those 300-400$ are for Samsung, which is different. They're kind of giving you a discount. Phone cost 700$ but they'll kindly replace it for 300$ they're being lenient about it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
bionemesis said:
If anyone is curious why I didn't JTAG service the phone, it's simply because I can't afford to wait that long without a phone and the cost difference between JTAG and my device protection plan is not significant.
Click to expand...
Click to collapse
JTAG costs $50 and has a two day return.
Did you try a jig to force the phone into download mode.?
Hi, I have a hard-bricked Samsung Galaxy S2 (device shows up as QHUSB_DLOAD) from Telus (same model as from T-Mobile).
I already have a different phone so it's not pressing, but I would be curious about having it repaired.
Interestingly, aside from the hard-brick state - the phone has another issue. I honestly think the phone has bad memory or some hardware issue because the thing would crash routinely regardless of using stock rom or custom roms. Since day #1 with stock rom it would crash routinely. Flashing a custom rom seemed to make no difference; phone still would crash routinely in the same places. Of course, this was before I bricked it (accidentally installed wrong kernel)...
So I guess my question is, is this phone worth anything? I might be willing to spend up to $75 for repair. Seems like a better option than just collecting dust or thowing it away. Can I send this directly to Samsung? Or another service provider?
Your tips are appreciated.
well, a working phone is worth $200-300 on eBay depending on condition.
Otherwise, I find old electronics make for good target practice
[/COLOR]
Redsmurf said:
Hi, I have a hard-bricked Samsung Galaxy S2 (device shows up as QHUSB_DLOAD) from Telus (same model as from T-Mobile).
I already have a different phone so it's not pressing, but I would be curious about having it repaired.
Interestingly, aside from the hard-brick state - the phone has another issue. I honestly think the phone has bad memory or some hardware issue because the thing would crash routinely regardless of using stock rom or custom roms. Since day #1 with stock rom it would crash routinely. Flashing a custom rom seemed to make no difference; phone still would crash routinely in the same places. Of course, this was before I bricked it (accidentally installed wrong kernel)...
So I guess my question is, is this phone worth anything? I might be willing to spend up to $75 for repair. Seems like a better option than just collecting dust or thowing it away. Can I send this directly to Samsung? Or another service provider?
Your tips are appreciated.
Click to expand...
Click to collapse
www.mobiletechvideos.com/
I highly recommend this site. I cost $50 to fix it and they are pretty fast getting it back to you.
Just got off live chat with Samsung. The device is still under warranty so I guess I'm going to try my luck with that. Going to UPS to send it now...
Redsmurf said:
Hi, I have a hard-bricked Samsung Galaxy S2 (device shows up as QHUSB_DLOAD) from Telus (same model as from T-Mobile).
I already have a different phone so it's not pressing, but I would be curious about having it repaired.
Interestingly, aside from the hard-brick state - the phone has another issue. I honestly think the phone has bad memory or some hardware issue because the thing would crash routinely regardless of using stock rom or custom roms. Since day #1 with stock rom it would crash routinely. Flashing a custom rom seemed to make no difference; phone still would crash routinely in the same places. Of course, this was before I bricked it (accidentally installed wrong kernel)...
So I guess my question is, is this phone worth anything? I might be willing to spend up to $75 for repair. Seems like a better option than just collecting dust or thowing it away. Can I send this directly to Samsung? Or another service provider?
Your tips are appreciated.
Click to expand...
Click to collapse
Did you try to reflash it with Odin? and if nothing works--that phone is still worth a couple hundred dollars bricked.
You can use it as a nice fancy paperweight. Or you can drop it from a 10 story window and see what happens... our you can send it to Samsung for repair. Your decision.
Sent from my SAMSUNG-SGH-T989 using xda premium
Just got it back! Luckily they just went ahead and replaced the mainboard
It appears to have solved the frequent crashing issue as well - phone works perfect.