Hard Bricked Phone: A Phone that won't turn on by any means. Booting to the OS or even opening the Custom/Stock recovery or Download Mode simply won't work.
I've searched plenty of forums regarding Android phones that are "Bricked". But it seems to me that most of the instructions laid out by the "replyer" require the phone to be opened up using special combinations of buttons that would either lead to the Custom/Stock recovery mode or the Download mode which is basically a definition of a "Soft Bricked Phone". A phone wherein it would still turn on and simply has problems with how the OS/Kernel/whatever runs.
Problem: I toyed with my Samsung Galaxy S4 in such a way that it would deal with underclocking my phone. I know that underclocking is a risky thing to do. But I was lowering it to the point where My phone would still run stable... until one day it just suddenly gave out. My phone would still turn on but for about 2 seconds and it would turn itself off immediately. That means that even if i was fast enough to go into the download mode or to my Custom Recovery mode, it would still shut off completely as if I pulled my battery out of my phone.
I'm not really in an INSANE need of help to repair my phone, but a good "Fixing a Hard-Bricked Phone is impossible." or something would definitely help as it would give me a sense of peace around all the threads claiming that they can fix such said phones that are in the same working condition as a brick.
thank you for any help.
:Bump:
Yeah, if the device doesn't turn on through any manner of key press combinations, you're pretty much screwed. I assume when you connect the device to the PC you get nothing?
If I use some type of flashing program from my pc that detects my phone on download mode, it sort off detects it for half to a full second until my phone will give in.
Thanks for the reply.
:Bumping:
- Just to keep dusts away.
friend is totally repairable but you have to disarm and perform jtag will return as magic JTAG samsumg you team only will be damaged the initializer in 95% of cases is so
larrywilson said:
friend is totally repairable but you have to disarm and perform jtag will return as magic JTAG samsumg you team only will be damaged the initializer in 95% of cases is so
Click to expand...
Click to collapse
JTAG? As in that Jtag brick repair where in you disassemble the back part of your phone and you have to connect the Riff/Jtag box to the 6 small pins and use a software on the computer to use the "resurrection" button? . Looking at that process, it does make it possible to unbrick insanely bricked phones. However I do need a device for that and a bit of electronic skills in which I have no background on. Not to mention that buying such device almost costs the same as buying another Samsung galaxy s4 from where I come from. Seems like overkill at this point haha.
Thanks for the reply as it did answer my question, but I think I'll try sticking to other possible alternatives if any. :fingers-crossed:
@gobbler6000: Not to mention owning one of those devices is questionable legality, depending on where you are.
To be honest, after five years, it's not worth trying to resurrect a dead S4. Sell it for parts and purchase a newer device. Used devices should be easy to come by, and I'm sure you could get a good bargain that way.
Strephon Alkhalikoi said:
@gobbler6000: Not to mention owning one of those devices is questionable legality, depending on where you are.
To be honest, after five years, it's not worth trying to resurrect a dead S4. Sell it for parts and purchase a newer device. Used devices should be easy to come by, and I'm sure you could get a good bargain that way.
Click to expand...
Click to collapse
Thanks! It's the hard and cold truth but I guess s4 is definitely not worth the trouble now. I thought I could probably use my old phone without spending a few bucks. I'll just use my 13 year old appeal and lotsa chores to get my parents' appeal for a new phone.
In one way or another, the questions were answered. How do I lock this thread? :fingers-crossed:
gobbler6000 said:
In one way or another, the questions were answered. How do I lock this thread? :fingers-crossed:
Click to expand...
Click to collapse
You don't. Report the thread to a mod and ask them to close it.
harry779 said:
I have faced the same situation once and one of the blog has helped me that I have mentioned below.
Click to expand...
Click to collapse
Link seems kinda scammy. It's also of no help to the OP. Besides the fact this thread is from last year, the OP's device was hard-bricked. Your link spends most of its bandwidth on soft-brick solutions, devoting only a single paragraph on hard bricks. That one paragraph on the page can be summed up in two words: you're screwed.
Related
I recommend to set a reward to thoses who find a solution for this problem.
Before continue lets say a Bricked HTC C1 is a phone who stay no matter what in the T-Mobile G1 screen.
I put 25.00 USD in a paypal account
Dude, when a phone is bricked it means its DEAD like a BRICK.
If you can get into recovery or bootload mode, it isn't bricked.
So back to my first statement, there is no coming back from a bricked phone.
Agree with Mikey, dead means dead. Unless you want to bend the rules of life then its not possible.
There's must be a way to fix it.
And i'll give more U$50 (on paypal) of reward
Does anyone know what board is replaced by HTC when they fix bricked SPL's and such?
axion68 said:
Does anyone know what board is replaced by HTC when they fix bricked SPL's and such?
Click to expand...
Click to collapse
I dont think they replace the board, they must only reflash (somehow) the correct flash.
That must be using a JTAG way, or some battery (pandora), who knows...
The reward is 75U$
UNITED NATIONS Brick HTC G1 Thread?!
Lol sorry, but isn't there already one of these threads? But, when you guys say dead... isn't it just dead software wise? It's all physically intact.. why is there no coming back?
Dead doesn't necessarily mean not recoverable. Think about developers who are writing radio and SPL parts - if they mess badly with something, put it on their dev devices, and phone can't boot, only solution will be order next dev device...? I don't think so...
In general, there are several ways used by phones/electronic devices producers, one is to have simple spare bootloader which can write part of SW which can take unbricking process further, or device's heart can be operated with JTAG. Unfortunatelly there is not much documentation about Dream's, and producer of the processor isn't known as a cooperative one... (or i missed something
come on guys.... someone from inside HTC or Android dev. Surely you can give us the details on how to build a ROM flasher and how to flash without the damn device switched on?
Its basic electronics, it is for sure possible, the catch is only you guys know how. Please share some details...
From what I know you would require a JTAG cable at least but then having the right flash tools to bring it to life. Even if software or chips die on a motherboard, there are always a way to either clear it, short it, re-flash or to replace the chip in question.
Happens a lot if you work on laptops, computers or any other electrical device, however the hardware required is often specialised and expensive...
I also think the Jtag will be the solution, reward 75.00 keep it up guys!
HTC G1 Service Manual
http://mikechannon.net/PDF Manuals/HTC Dream SM (A04).pdf
its time to give up :'(
Hell no!, i think i find a solution... please provide me 10 days. Thanks in advance!
@cuore_alfa: woah... that now sounds very promising... why 10 days? you take 20 days and if you come up with a solution, then the forum members with bricked devices will rain all their blessings and favours on you.
Cuore_alfa said:
Hell no!, i think i find a solution... please provide me 10 days. Thanks in advance!
Click to expand...
Click to collapse
Buying a new one?! =)
Btw, U$30,00 paypal reward for a solution to my bricked G1 (spl).
Now we have U$ 105 of reward
Yes please!
My HTC Magic has just passed away
I think I applied the HARD Spl meant only for G1.
me idiot (but page not clear http://code.google.com/p/android-roms/wiki/SPL)
where theres a will there a way come on people... its america anything is possible ill add 15$ to the highest offer ... the must be a way...
p.s i just brick my g1 so im waiting...
I'll add $25, solve and tell me how to pay...
I'm interested in buying an android based phone. I found a cheap one, the seller says it doesn't have any scratch at all or anything. The only problem is that he tried to flash a ROM and now it stops at the boot logo that says "Android G1 (TIM Italy)" and reboots. Do you think it's possible to flash another ROM and make it work again? I have an iPhone 3GS so I don't know anything at all, I know it has to be rooted to flash but that's all.
Proabably bricked, that is one of the tell tale signs, but it could be soft bricked as well... hard to say without knowing exactly what he did to it before hand, and likely has such a lack of knowledge doesn't know any of the proper button combo's to find out if it is truly bricked, and it would be kinda dumb to tell him how to fix it.
How much is he asking? If it isn't much at all, get it, worst case scenario you sell it off to someone in need of a new screen or case or something.
pjcforpres said:
Proabably bricked, that is one of the tell tale signs, but it could be soft bricked as well... hard to say without knowing exactly what he did to it before hand, and likely has such a lack of knowledge doesn't know any of the proper button combo's to find out if it is truly bricked, and it would be kinda dumb to tell him how to fix it.
How much is he asking? If it isn't much at all, get it, worst case scenario you sell it off to someone in need of a new screen or case or something.
Click to expand...
Click to collapse
He's asking 450RON(about 150$). He says a service thing can repair it for 200-250RON(60$). I don't really know what to say..
freemini said:
He's asking 450RON(about 150$). He says a service thing can repair it for 200-250RON(60$). I don't really know what to say..
Click to expand...
Click to collapse
That sounds way too steep for a device that easily could be a brick... the fact it loops makes it sound like just a bad flash, but not getting past the G1 screen is also the main sign of a brick.
I would ask him to see what happens when he holds down the camera and power button at the same time on power up, that is the combo to take him to fast boot... if he can get it there, it is worth it, if not for that price not worth the risk.
pjcforpres said:
That sounds way too steep for a device that easily could be a brick... the fact it loops makes it sound like just a bad flash, but not getting past the G1 screen is also the main sign of a brick.
I would ask him to see what happens when he holds down the camera and power button at the same time on power up, that is the combo to take him to fast boot... if he can get it there, it is worth it, if not for that price not worth the risk.
Click to expand...
Click to collapse
He said he can't get in recovery mode. I don't really want to help him, though.
freemini said:
He said he can't get in recovery mode. I don't really want to help him, though.
Click to expand...
Click to collapse
I wouldn't take the chance. The service to fix it likely just sends you a refurbished device, and uses the one you send them for parts. Not worth that much money, you can get a near perfect condition working device for $200 on a good day... seen some good condition with light wear go for as low as $175 as well when I bought mine off eBay.
pjcforpres said:
I wouldn't take the chance. The service to fix it likely just sends you a refurbished device, and uses the one you send them for parts. Not worth that much money, you can get a near perfect condition working device for $200 on a good day... seen some good condition with light wear go for as low as $175 as well when I bought mine off eBay.
Click to expand...
Click to collapse
I was thinking the same thing.
I thought that bricks just hung.
If it is rebooting itself, doesn't seem like a brick to me. More likely just borked the /boot or /system partition.
lbcoder said:
I thought that bricks just hung.
If it is rebooting itself, doesn't seem like a brick to me. More likely just borked the /boot or /system partition.
Click to expand...
Click to collapse
So basically how do you reflash it?
The same way you would if it wasn't goofed up... with an NBH file.
You wouldn't ever see a reboot on the first screen, if the system or boot partition is nailed it'll just stay there and do nothing. He's probably lying to get you to buy a brick. Don't touch it.
Today would be a good day for me to start making treads. Been around long enough to still brick my phone. Not a noob nor yet a pro but I know when my phone is fully brick! "Black sreen with no led lights when charging." Ease touble shoot right; Its a gonner."
I myself know bricking is a lot more common now then every. With that said, How about a group or just someone do some research on how to bring back tri-color screen so that we have a chance to re-rom. Maybe post up what are the process to bring the phones back to life after death.
Its a start but this is just as important as us being able to flash custom rom. Maybe even more important if you ask me because, its a mobile device you spent money on to make your life seem alittle bit more fulfilling.
Like many out there in XDA, Roms are always fun to flash even if we had a good one running. The fact of the matter is: Having freedom to customize your little buddy seem just alittle bit more then just a passion. Its personal I will donate $500 US dollars to anyone who cracks this issue. Im returning my solid brick HD2 as defective to tmobile today!
good luck
Sorry, you have posted in the wrong section.
Ask someone in the HD2 section.
thanks
flyboy
MOD EDIT - Moved to HD2 forum.
No need to off $500 to unbrick device, just search in HD2 forums for guidance and you can unbrick it yourself. Alternative a lot of users on this site would guide you for free....that's what this site if for!!
let me guess... t mobile us meets incorrect radio version... won't power on, black screen, no charging light.
sorry, but this isn't one of those chance bricks, this is user error.
take it back to tmo and pretend it was like that when you woke up.
Yeah Im getting it in a few days. How funny that you mention user error. because it sure wasn't a user error. the user was just hard-headed to not believe that such a thing would not be repairable. lol! I hope someone could find out ways to unbrick. maybe upload a dummy software to upload open roms? any idea on how htc fixes these refurbish devices?
babydreamer1520 said:
the user was just hard-headed to not believe that such a thing would not be repairable. lol!
Click to expand...
Click to collapse
Even if the relevant sections of the forums is full of big warnings that it really isn't? Wow, you were feeling lucky...
babydreamer1520 said:
Yeah Im getting it in a few days. How funny that you mention user error. because it sure wasn't a user error. the user was just hard-headed to not believe that such a thing would not be repairable. lol! I hope someone could find out ways to unbrick. maybe upload a dummy software to upload open roms? any idea on how htc fixes these refurbish devices?
Click to expand...
Click to collapse
Chances are that if there is a way to unbrick these black screen bricks (tmous only, no other hd2 has shown this type of brick) then it will require a jtag connection to reinstal the bootloader. Certainly not something 99.999% of xda dev users would be advised to try.
I'm getting worried with all these people flashing wrong ROMs and bricking their phones and then taking it back to Tmobile and blaming htc for making a crappy device that just died when it's actually their fault. This makes both htc and HD2 look bad. People need to be more careful and read before flashing
Svegetto said:
I'm getting worried with all these people flashing wrong ROMs and bricking their phones and then taking it back to Tmobile and blaming htc for making a crappy device that just died when it's actually their fault. This makes both htc and HD2 look bad. People need to be more careful and read before flashing
Click to expand...
Click to collapse
hehe, dont worry, the people that count (us!) know whos fault it is.
I've got my RIFFbox, and I've been able to connect to the device just fine. I can send the resurrection to the dead body, but I can't get it to boot to Odin mode still. When connecting to PC, it still shows the QPST download mode (QDL mode). I'm currently trying to flash individual partitions to the device.
Any help or suggestions to get this thing out of QPST mode? :/
Thanks!
I've tried 301k & 619k JIGs also, and several known combinations of keys to boot Odin mode.
UPDATE [7-23-13]:
At this time, I've determined that this device is permanently bricked until I can get my hands on the Kies MF3 Odin package and manually load these files via JTAG. However, even this is not guaranteed to fix it. For the time being, I've replaced the device. I'll hold onto the carcass for a little while longer to see if I can get MF3 to boot on it. If I can, I will use this as a test bed for developers to attempt to unlock bootloaders or develop an MF3 root. Otherwise, I eventually plan to part it out, selling things like the screen, etc.
Aou said:
I've got my RIFFbox, and I've been able to connect to the device just fine. I can send the resurrection to the dead body, but I can't get it to boot to Odin mode still. When connecting to PC, it still shows the QPST download mode (QDL mode). I'm currently trying to flash individual partitions to the device.
Any help or suggestions to get this thing out of QPST mode? :/
Thanks!
I've tried 301k & 619k JIGs also, and several known combinations of keys to boot Odin mode.
Click to expand...
Click to collapse
Did you PM my tech?
TheAxman said:
Did you PM my tech?
Click to expand...
Click to collapse
Yup. No reply yet.
Currently flashing the whole 1GB image. Takes forever, so I will let you all know how it goes in a couple hours. I haven't tried flashing the whole MF3 boot chain but it's looking like that's what I will end up needing to try.
Aou said:
Yup. No reply yet.
Currently flashing the whole 1GB image. Takes forever, so I will let you all know how it goes in a couple hours. I haven't tried flashing the whole MF3 boot chain but it's looking like that's what I will end up needing to try.
Click to expand...
Click to collapse
I have no doubt you will get it straightened out.
Sent from my GT-I9505 using xda premium
TheAxman said:
I have no doubt you will get it straightened out.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
No go on the full 1GB flash. In a last-ditch effort, I threw the MF3 version of SBL2, SBL3, ABOOT, TZ, and RPM at it.
Still boots to QHUSB_DLOAD mode.
This is unbelievably frustrating. No matter what I throw at this thing, it refuses to boot. Also, it seems that the only people that know how to JTAG one of these things are not responding.
Try getting a hold of Josh over at mobile tech videos. I believe he goes by connexion2005 here on XDA.
Sent from my SAMSUNG-SGH-I337 using xda premium
Red_81 said:
Try getting a hold of Josh over at mobile tech videos. I believe he goes by connexion2005 here on XDA.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Thank you, but he was the first person I tried contacting. Seems to ignore my PMs, or just doesn't have the time?
He's pretty busy most Days. His business takes up most of his time.
Sent from my SAMSUNG-SGH-I337 using xda premium
Aou said:
Thank you, but he was the first person I tried contacting. Seems to ignore my PMs, or just doesn't have the time?
Click to expand...
Click to collapse
Have you tried contacting @AdamOutler? If I remember from the early Captivate days he worked with Josh to get the JTAG stuff working. He's definitely very knowledgeable when it comes to Samsung hardware.
I'm pretty sure you need a JTAG flash with an up to date firmware. There was someone else who's device refused to boot and he managed to unbrick with software. I take it that this is due to messing with bootloaders and trying to revert? btw... quote or mention usually gets my attention.
Devo7v said:
Have you tried contacting @AdamOutler? If I remember from the early Captivate days he worked with Josh to get the JTAG stuff working. He's definitely very knowledgeable when it comes to Samsung hardware.
Click to expand...
Click to collapse
... - didn't try - last I knew he didn't accept PMs.
AdamOutler said:
I'm pretty sure you need a JTAG flash with an up to date firmware. There was someone else who's device refused to boot and he managed to unbrick with software. I take it that this is due to messing with bootloaders and trying to revert? btw... quote or mention usually gets my attention.
Click to expand...
Click to collapse
Yes, this is from flashing MF3 Sbl2 and Sbl3 (without aboot and tz). I've tried flashing the whole MF3 bootchain, and it still doesn't like it. Still boots to QPST mode.
EDIT/ADD:
At this point, I've flashed these:
PGPT (and SGPT) from the 1GB "full dump" provided by riffbox (assuming MDB or MDL - it was released 7/3/13)
PIT from the forums around here somewhere (seems identical to one from dump)
MD5 from dump
(empty area) from dump
apnhlos (aka non-hlos) from MF3
MDM from MF3
sbl1 from AdamOutler's MDB dump
sbl2 from MF3
sbl3 from MF3
aboot from MF3
rpm from MF3
tz from MF3
Yeah, tried it all again, for good measure. Starting to wonder if this thing is completely and utterly bricked? It makes no logical sense. Something is still triggering it to enter QPST mode. Again, I've tried using 301k (and a few other) Ohm resistance JIGs to try booting immediately the flash. Nada. Using the 4.2v power supply from the Riffbox, tried USB power (kinda difficult to flash things solderless when the daughterboard is attached, but possible), tried battery power only... All appear to work fine in Riff, all allow me to read and write any address I want.
I'm about to the point where I'm going to scrap this for parts to help get a new one. :/
Aou said:
Yeah, tried it all again, for good measure. Starting to wonder if this thing is completely and utterly bricked? It makes no logical sense. Something is still triggering it to enter QPST mode. Again, I've tried using 301k (and a few other) Ohm resistance JIGs to try booting immediately the flash. Nada. Using the 4.2v power supply from the Riffbox, tried USB power (kinda difficult to flash things solderless when the daughterboard is attached, but possible), tried battery power only... All appear to work fine in Riff, all allow me to read and write any address I want.
I'm about to the point where I'm going to scrap this for parts to help get a new one. :/
Click to expand...
Click to collapse
Could sell for parts for around 300 or so ?
Adam is right, you did get the newest firmware they have online right?
Did Derek get hold of you? I had him busy at work today, he had to load 50+ laptops with win 7, big money involved, I will IM him for you.
@AdamOutler @Aou
same exact thing happened to me i did the same thing with the verizon update and sent it out to josh @ mobiletechvideos.com
just got my device back today and its still Bricked !?!?!?!? either josh and his guys just failed to test it or there is no way to fix these phones
1. this really pisses me off i sent it to the most reputable guy in the buisness and got it back in this condition.
2. for the odd case that its just a complete loss i have one thing to say to samsung, vzw, att....
basically moral of the story is i wouldnt sell your phone for parts to get another wait until i/we hear back from mobiletechvideo then sell you device and never buy a samsung device again as long as it is locked
beanstown106 said:
@AdamOutler @Aou
same exact thing happened to me i did the same thing with the verizon update and sent it out to josh @ mobiletechvideos.com
just got my device back today and its still Bricked !?!?!?!? either josh and his guys just failed to test it or there is no way to fix these phones
1. this really pisses me off i sent it to the most reputable guy in the buisness and got it back in this condition.
2. for the odd case that its just a complete loss i have one thing to say to samsung, vzw, att....
basically moral of the story is i wouldnt sell your phone for parts to get another wait until i/we hear back from mobiletechvideo then sell you device and never buy a samsung device again as long as it is locked
Click to expand...
Click to collapse
I've been a diehard Samsung supporter since the GS1 came out. The hardware quality is awesome. Unfortunately, their policies are beginning to become unfriendly for developers. The issue you're having is due 100% to Samsung's desire to lock people out of custom kernels.
Isn't it AT&T and VZW who are locking it?
TheAxman said:
Adam is right, you did get the newest firmware they have online right?
Did Derek get hold of you? I had him busy at work today, he had to load 50+ laptops with win 7, big money involved, I will IM him for you.
Click to expand...
Click to collapse
I got the latest firmware that I could find - but it's dated 7-3-13 (a week before the MF3 patch). Does Kies have MF3 yet? I might be able to live with MF3 if I were able to retain a custom recovery and therefore root (via injection). It'd mean no custom ROMs until a new "Loki" (or equivalent) is made, or we get these blasted bootloaders unlocked.
beanstown106 said:
@AdamOutler @Aou
same exact thing happened to me i did the same thing with the verizon update and sent it out to josh @ mobiletechvideos.com
just got my device back today and its still Bricked !?!?!?!? either josh and his guys just failed to test it or there is no way to fix these phones
1. this really pisses me off i sent it to the most reputable guy in the buisness and got it back in this condition.
2. for the odd case that its just a complete loss i have one thing to say to samsung, vzw, att....
basically moral of the story is i wouldnt sell your phone for parts to get another wait until i/we hear back from mobiletechvideo then sell you device and never buy a samsung device again as long as it is locked
Click to expand...
Click to collapse
I would REALLY like to hear what the deal was with mobiletechvideos.com & @connexion2005 has to say about our situation here. My plan was to cut my losses on Monday if I am not able to get it fixed this weekend. This is really crazy news for me - Josh is indeed the most reputable JTAG guy in the industry (afaik). For them to send that back still bricked is a really bad sign! (Makes my situation look pretty much hopeless!)
AdamOutler said:
I've been a diehard Samsung supporter since the GS1 came out. The hardware quality is awesome. Unfortunately, their policies are beginning to become unfriendly for developers. The issue you're having is due 100% to Samsung's desire to lock people out of custom kernels.
Click to expand...
Click to collapse
Indeed, I've had the Infuse, S2, and now the S4. I love Samsung's handsets, and I traditionally loved how much modification you could do to these handsets to customize them. However, with locked bootloaders and such, this is becoming quite the joke - and the joke's on us, it seems.
----------
As an update to my situation, I haven't tried anything new since my last post. Still waiting to find new ideas or hear some suggestions.
beanstown106 said:
@AdamOutler @Aou
just got my device back today and its still Bricked !?!?!?!? either josh and his guys just failed to test it or there is no way to fix these phones
1. this really pisses me off i sent it to the most reputable guy in the buisness and got it back in this condition.
2. for the odd case that its just a complete loss i have one thing to say to samsung, vzw, att....
basically moral of the story is i wouldnt sell your phone for parts to get another wait until i/we hear back from mobiletechvideo then sell you device and never buy a samsung device again as long as it is locked
Click to expand...
Click to collapse
I screwed up my S4 recently and it was being fixed (hopefully) from MobileTechVideos. Josh is really a good guy and back in my S1 Cappy days I had to send one to him. We chatted on the phone about android stuff quite a bit back then.
So I screwed up the kernel I believe trying to make a kernel splash screen, flashed in recovery and when it rebooted I just got a vibration every 3-5 seconds. Tried Odin MDB and MDL firmware with both always passing. But still same results when it went to reboot.
Now seeing this comment you made has me actually worried now. Have you contacted them about it still being bricked yet? Or did they send it back with refunding the charges since it wouldn't work? Crap it I f'ed it over after only 1 week of having it and it cannot be resurrected. Now I know my situation is different as I have NOT messed with anything from MF3 at all. But if something else is going on inside that MobileTechVideos couldn't fix has me worried.
Also @Adam, I feel the same way about the quality of the Galaxy lines as I have had the S1,S2, S3, and now S4. But I am seeing the writing on the wall with Samsung and ATT showing me this COULD BE my last of them.
Sent from my SCH-I800 using xda premium
Hey guys.
So, the worst case scenario seems to be playing out with my phone, and Samsung & the retailer are turning into villains. I've had my phone maybe 8 months, I flashed root to it in the first week. This is the stock firmware, just with root access so I could run Titanium Backup. The phone was working fine, had recently started to become a little bit chuggy due to lots of apps & data, though yesterday I opened a link from a friend which looks like it's killed my phone. I was in the middle of doing my Japanese lessons with Duolingo... received a Whatsapp message from a friend with a link to a sale ( I could post the link, but spam filters might block it)- the moment I opened the link in Chrome my phone had a heart attack. Froze, rebooted... but worse, the boot animation also froze. I tried the power reset (volume down + power button), and managed to get as far as the lock screen. Upon entering my PIN, the phone went black and it has been a brick ever since. I took my phone to the shop I bought it from this morning and regret being honest about having root access. I cannot possibly fathom how having full access to MY DEVICE could possibly kill any hardware or disable the device to this degree, and as such think this warranty voiding angle is a giant scam.
This post is seeking a few things... 1) sympathy (lots please).... 2) advice about warranty (are they within their rights to deny my warranty? I'm in Australia, imported phone) ... 3) How could this happen?!?!?!
Please, thanks, and woe is me....
:-/
loudboy77 said:
Hey guys.
So, the worst case scenario seems to be playing out with my phone, and Samsung & the retailer are turning into villains. I've had my phone maybe 8 months, I flashed root to it in the first week. This is the stock firmware, just with root access so I could run Titanium Backup. The phone was working fine, had recently started to become a little bit chuggy due to lots of apps & data, though yesterday I opened a link from a friend which looks like it's killed my phone. I was in the middle of doing my Japanese lessons with Duolingo... received a Whatsapp message from a friend with a link to a sale ( I could post the link, but spam filters might block it)- the moment I opened the link in Chrome my phone had a heart attack. Froze, rebooted... but worse, the boot animation also froze. I tried the power reset (volume down + power button), and managed to get as far as the lock screen. Upon entering my PIN, the phone went black and it has been a brick ever since. I took my phone to the shop I bought it from this morning and regret being honest about having root access. I cannot possibly fathom how having full access to MY DEVICE could possibly kill any hardware or disable the device to this degree, and as such think this warranty voiding angle is a giant scam.
This post is seeking a few things... 1) sympathy (lots please).... 2) advice about warranty (are they within their rights to deny my warranty? I'm in Australia, imported phone) ... 3) How could this happen?!?!?!
Please, thanks, and woe is me....
:-/
Click to expand...
Click to collapse
It depends on how you rooted but guessing as you rooted when you first got the device it probably tripped knox and voided your warranty... either way by the sounds of things you can fix this yourself by flashing official firmware with odin do you know how to do this?
In fact can you get into recovery mode?
while the phone is off try holding power button + home button + volume upfor around 10 seconds (this does not require the boot animation to load)
If you can do that use the volume keys to navigate down to "wipe data and factory rest" then navigate to yes and after that reboot your phone (might take 10 mins to boot) but should fix your problem
EasyAndroidPro said:
It depends on how you rooted but guessing as you rooted when you first got the device it probably tripped knox and voided your warranty... either way by the sounds of things you can fix this yourself by flashing official firmware with odin do you know how to do this?
In fact can you get into recovery mode?
while the phone is off try holding power button + home button + volume upfor around 10 seconds (this does not require the boot animation to load)
If you can do that use the volume keys to navigate down to "wipe data and factory rest" then navigate to yes and after that reboot your phone (might take 10 mins to boot) but should fix your problem
Click to expand...
Click to collapse
For a moment I was excited to get a reply, and then I read yours. Please read my post before replying. If I could flash anything or get any kind of response do you think I would have taken my phone in for repairs??! It's DEAD. They changed the battery, the display (so they tell me) and they like to refer to the remainder as "the motherboard" but they mean the whole damn phone... Can anyone report if this has happened to them? Seems so thoroughly weird.... and to blame it on the fact I have root access.... the same as thousands of others.... it's really dodgy.
loudboy77 said:
For a moment I was excited to get a reply, and then I read yours. Please read my post before replying. If I could flash anything or get any kind of response do you think I would have taken my phone in for repairs??! It's DEAD. They changed the battery, the display (so they tell me) and they like to refer to the remainder as "the motherboard" but they mean the whole damn phone... Can anyone report if this has happened to them? Seems so thoroughly weird.... and to blame it on the fact I have root access.... the same as thousands of others.... it's really dodgy.
Click to expand...
Click to collapse
Wow good look getting help with an attitude like that :good: i was offering beginner advice because from your post you sounded like an newbie. Good luck i won't be helping further.
EasyAndroidPro said:
Wow good look getting help with an attitude like that :good: i was offering beginner advice because from your post you sounded like an newbie. Good luck i won't be helping further.
Click to expand...
Click to collapse
Oh no... you're going to keep that awesome advice to yourself? Maybe someone else can suggest I try turning it off and on again?
Seriously- it's frustrating enough being put through the wringer of losing a device like this, and even moreso being held over a barrel by Samsung & the retailer. I'm doing my best to be clear and spell out my situation, in the interests of not only myself, but the whole Samsung community. When you're locked out of a device by design, and all you can do is press buttons in certain combinations, please assume that I meant it when I said I already tried pressing the buttons.
More frustrated. Thanks. =)
loudboy77 said:
Oh no... you're going to keep that awesome advice to yourself? Maybe someone else can suggest I try turning it off and on again?
Seriously- it's frustrating enough being put through the wringer of losing a device like this, and even moreso being held over a barrel by Samsung & the retailer. I'm doing my best to be clear and spell out my situation, in the interests of not only myself, but the whole Samsung community. When you're locked out of a device by design, and all you can do is press buttons in certain combinations, please assume that I meant it when I said I already tried pressing the buttons.
More frustrated. Thanks. =)
Click to expand...
Click to collapse
Come on, dude. I/we know the frustration of things like this but that's completely uncalled for. He offered genuine advice from the information given in your post.
I hope you get it sorted but I doubt you'll get much in the way of helpful responses if you are this rude.
It is completely within their rights to deny you warranty. You rooted the thing. The very act of rooting voids warranty. And yes, complete access to the device can do that to your phone because any rogue app can delete system files/programs that are essential to running the phone, or even turning it on. As it is, suck it up and accept you lost warranty and pay for the repair or get a new phone.
Sent from my SM-T231 using Tapatalk
what whatsapp message could do that much harm and has that done any harm to your friends (rooted) phone?
I think that after the freeze the phone has become damaged in software
Could be that it happens with any application that filled the memory.
If nothing can be saved with any trick and you have done everything I'm afraid there is nothing more possible than all the "tricks" here on XDA that are available after a good search.
Succes
loudboy77 said:
Hey guys.
So, the worst case scenario seems to be playing out with my phone
Click to expand...
Click to collapse
If u cant get into Download mode, then the people at service centre also cant
Go to a different service centre and play dumb. Just say that 'The phone stopped working when I was travelling. I dont know what happened. The phone just died'
Dont give anymore info than this. If u do then they might pin it on you
Just play dumb and deny everything lol
They cannot prove that the phone is rooted just by looking.
In your case the motherboard might be fried (IDK maybe) and if they replace motherboard then ur knox flag will be reset.
Visit another Service centre. Dont go to the same place again.
chanchan05 said:
It is completely within their rights to deny you warranty. You rooted the thing. The very act of rooting voids warranty. And yes, complete access to the device can do that to your phone because any rogue app can delete system files/programs that are essential to running the phone, or even turning it on. As it is, suck it up and accept you lost warranty and pay for the repair or get a new phone.
Sent from my SM-T231 using Tapatalk
Click to expand...
Click to collapse
There was recently a ruling in the States that returned some rights to consumers to unlock their devices while keeping warranty. In Australia we have some pretty decent consumer protection laws. http://ausdroid.net/2012/10/22/warranties-and-bootloaders-what-you-should-know/
You're not showing an awful lot of compassion to the community of developers who spend their time trying to root phones... too bad if your phone dies? nice.
I suggest you read this.
http://www.samsung.com/au/support/warranty/
From the read of it. You have already violated 2 things.
1.Your phone was imported.
2.Modification(in this case root)
Also, if you think software can not kill hardware then you are wrong. Some hardware are also being controled by software. Of course something like the glue holding the display together come off is definite not caused by software but something like fried mainboard/electronic is possible.
Of course, this seem very unlikely in this case but still not impossible. If you still want warranty, you must prove yourself innocent enough for them to accept your claim which seem nearly impossible.
Also being honest about rooting when claiming your warranty will instantly have your warranty rejected, no question asked.
Well, you can still try using the customer right law or something like that to help you, if you don't mind wasting time.
Sent from my SM-G935F using Tapatalk
loudboy77 said:
There was recently a ruling in the States that returned some rights to consumers to unlock their devices while keeping warranty. In Australia we have some pretty decent consumer protection laws. http://ausdroid.net/2012/10/22/warranties-and-bootloaders-what-you-should-know/
You're not showing an awful lot of compassion to the community of developers who spend their time trying to root phones... too bad if your phone dies? nice.
Click to expand...
Click to collapse
Unlocking and rooting are two different things. Compassion? What are you talking about? Just accept that rooting voids warranty. Rooting opens the phone to exploits which may or may not cause problems. The manufacturer has every right to deny you service because they cannot prove if it is a fault on their part or yours. If you a friend bought an unrooted phone from you and roots it and bricks it, would you take back the phone and give him a new one free of charge? Or would you shoulder repair fees for your friend? No. Same thing. If you accidentally drop your chicken on the floor, KFC won't take it back.
There is consumer protection, and there is abuse.
And I appreciate the rooting community, but understand and accept the fact that doing so voids my warranty.
If my phones dies? I pay for the repairs. Simple.
Sent from my SM-T231 using Tapatalk
EasyAndroidPro said:
It depends on how you rooted but guessing as you rooted when you first got the device it probably tripped knox and voided your warranty... either way by the sounds of things you can fix this yourself by flashing official firmware with odin do you know how to do this?
In fact can you get into recovery mode?
while the phone is off try holding power button + home button + volume upfor around 10 seconds (this does not require the boot animation to load)
If you can do that use the volume keys to navigate down to "wipe data and factory rest" then navigate to yes and after that reboot your phone (might take 10 mins to boot) but should fix your problem
Click to expand...
Click to collapse
So I take it that there's a way around knox to root the phone without tripping it? I've got the Exynos variant of this phone, would you mind putting me in the right direction on rooting it? I've looked everywhere but never found a way that does not trip knox.
Alaa Joseph said:
So I take it that there's a way around knox to root the phone without tripping it? I've got the Exynos variant of this phone, would you mind putting me in the right direction on rooting it? I've looked everywhere but never found a way that does not trip knox.
Click to expand...
Click to collapse
I've not tried it myself nor have I looked into it myself I rooted the normal way as I don't care about Knox related apps I just remember seeing the reports around.
Here is a related thread https://forum.xda-developers.com/ga...ot-method-via-engkernel-t3423438/post68204186