Hello to all the people of the world who share this amazing interest in their electronics.
Please let me begin by saying that this is my first post and have searched for hours over the last five days to try and find the answers and learn more about my situation, and I thank anyone who takes the time to respond ahead of time.
I am the owner of a what I believe to be a hard bricked verizon sch-i535.
I started with the stock phone and I decided to try the update I found on this wonderful site.
http://forum.xda-developers.com/showthread.php?t=1974114
"[GUIDE] Jelly Bean Factory Image (Root/Recovery/Unlocked Bootloader) *UPDATED 12/6*"
I followed the directions perfectly, installed TWRP Recovery, added SuperSU, and went with both Root and Unlocked Bootloader option.
Everything went perfect. The phone rebooted, opened loaded android jelly bean perfect and I was able to make a recovery back up, by entering TWRP recovery mode, three button combo, vol up, power, home. This all went perfectly according to plan.
My problem arose when I pushed my luck and lack of research which I rightly admit and decided to try and then upload one of the modified roms.
I decided to go with the latest AOKP milestone, that i downloaded from the AOKP site.
aokp_i9300_jb_milestone-1.zip
I had spent some time researching and was pretty sure I understood what to do.
I entered TWRP with the three button recovery mode option (vol up, home, power), made a second back up, did the factory reset swipe, cleared both caches, then tried to install "aokp_i9300_jb_milestone-1.zip" from sd card which was on the list. The phone reloaded, the screen went black and enter what i now believe to be hard brick status.
I have tried all the simple fixes, ordered and used a download jig, removed battery, no button responses, not recognized by odin on xp, computer chimes but does not recognize phone. This is where I'm at and how I have gotten here. If only
I have been researching JTAG and the RIFF box, and now also the ORT JTAG box. There are people who are supposidly doing JTAG repairs on the sch-i535 even though all of the sales sites for these boxes do not show the Snap dragon msm 8960 chip set is supported. I realize I could just send this phone to them but I would really like to repair it myself if I can purchase the correct tools. I have searched high and low and would just like to know if anyone on here has any experience with this type of repair if you think its an option in my case. I have also read that people who have had hard bricks with the same symptoms have had to replace the motherboard. If JTAG repair with RIFF box is possible, can I use the same JTAG jig as the one designed for the i747 version which is also based on the same chipset? I realize that the actual programing is different between carriers but if the RIFF box has the correct verizon software can it be used with i747 JTAG jig?
I have also read about the option to use a good SCH-I535 to make a boot sd card and then short the resistor on the bricked phone. There really hasn't been much written about success with this option. I am a person who believes I can fix anything, and would like to be able to repair it in the future if I can find the right tools and also help others in my area. Is it really dead or can I still resurrect my phone?
Thanks a lot to all of you at XDA.
Are you able to reach download mode from
vol d + home + power?
Sent from my SCH-I535 using xda app-developers app
jam.i.s0n said:
Are you able to reach download mode from
vol d + home + power?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No, my phone is completely unresponsive. Neither of the three button press options nor the download jig I ordered do anything.
your problem lies in the fact that you flashed an i9300 (international variant) rom onto your us variant rom. unfortunately they're not compatible and most probably bricked your phone unless you are somehow able to go back into download mode and use odin to flash the appropriate stock rom for your verizon s3.
Sent from my GT-I9300 using xda app-developers app
OP see sticky top of page for correct forum.
jje
Sent from my GT-I9300 using xda premium
This is wrong forum mate
Sent from my GT-I9300 using XDA Premium HD app
mputtr said:
your problem lies in the fact that you flashed an i9300 (international variant) rom onto your us variant rom. unfortunately they're not compatible and most probably bricked your phone unless you are somehow able to go back into download mode and use odin to flash the appropriate stock rom for your verizon s3.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response. A question about the variants. Was it the No wipe version, or the AOKP version? I'm thinking the AOKP due to the fact that the phone booted up perfect after the no-wipe Jelly bean. Or am I wrong, and would it appear to operate fine at beginning only to crash after?
fscxide said:
Thanks for your response. A question about the variants. Was it the No wipe version, or the AOKP version? I'm thinking the AOKP due to the fact that the phone booted up perfect after the no-wipe Jelly bean. Or am I wrong, and would it appear to operate fine at beginning only to crash after?
Click to expand...
Click to collapse
The problem is you flashed the I9300 AOKP on your Verizon S3. Guaranteed hard brick every time.
Glad to see you've been researching and you're on the right path, is gonna need JTAG. here is the link everyone uses. You may be able email and ask what method they use to determine if you can do it yourself. I'd guess it's expensive, but it may be something you want to do.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Sent from my SCH-I535
My guess is that I7 box will do no good. There has to be more to JTag. In the beginning Josh at Mobile Tech could JTag the other Variants but not the I535. He now can so apparently there is more needed than just the box.
kintwofan said:
The problem is you flashed the I9300 AOKP on your Verizon S3. Guaranteed hard brick every time.
Glad to see you've been researching and you're on the right path, is gonna need JTAG. here is the link everyone uses. You may be able email and ask what method they use to determine if you can do it yourself. I'd guess it's expensive, but it may be something you want to do.
Sent from my SCH-I535
Click to expand...
Click to collapse
Thanks for your response. I have spent at least 5 hours a night since Monday to try to figure this all out. I am learning a lot about this phone and the processes here on xda, and all it has done is peak my interest even more. I'm definitely in the camp that believes its wrong to take back a perfectly good phone that is technically only "asleep." :fingers-crossed:
add another one to the jtag tryouts!
fscxide said:
Thanks for your response. A question about the variants. Was it the No wipe version, or the AOKP version? I'm thinking the AOKP due to the fact that the phone booted up perfect after the no-wipe Jelly bean. Or am I wrong, and would it appear to operate fine at beginning only to crash after?
Click to expand...
Click to collapse
sorry the late response since apparently this got moved to the appropriate forum.
it's the i9300 rom which if i remembered correctly, is the AOKP. You need to somehow get back to download mode and use odin to flash the proper stock rom into it.
Good luck
Success!
Well not exactly but my phone is completely fixed thanks to Josh at MOBILE TECH VIDEOS! After extensively searching for answers and figuring out what I had done there was only one option. JTAG. I realize I could have just brought it back to Verizon and exchanged it but I wasn't willing to risk getting a refurb when I knew there was nothing physically wrong with my phone. I called the Mobile Tech Videos number last Tuesday afternoon to make sure I could speak to a person before just placing my phone in the mail. The person who answered was actually Josh the owner. I explained what I had done to the phone and he explained exactly what I did internally to the phone and that he could definitely help me. He even told me of a notebook program that would let me read the code before had and I would have seen that I had an international ROM. He was very easy to talk to and took the time to explain to me information that he has probably said 1000s of times all with patience and a genuine desire to help me understand.
I packaged my phone up on Tuesday and mailed it the way his very well designed website said to. He told me exactly what would happen and it did. I received an email Friday stating that they had received my phone and that because I had paid the additional 15$ for the expedited service, that the phone would be fixed and shipped within 2 business days. Monday I received another email that my phone was fixed and shipped with a tracking number. I had also paid for the expedited shipping so I received my phone today! 4 day turn around...Awesome! :victory:
It was packaged in a small bubble wrap envelope inside a larger bubble wrap envelope inside of the outer shipping envelope safe and sound.
Came home put sim card, battery in and it came to LIFE! I went back over all the correct steps I had done and reinstalled Jelly bean with TWRP and both the superuser and root unlock option. SO glad to have my phone working again thanks to MOBILE TECH VIDEOS and Josh but also everyone here at XDA! Thanks Again!
I hard bricked mine following a soft brick. Followed the guide to the letter, or so I thought. Anyway I ended up with a paperweight. I didnt know about jtag repair so I talked with samsung and explained what happened and even told them it as a rooted bad flash. They advised to send it in to them and they would fix. Sent off on friday and got it back yesterday. Samsung replaced the motheboard and did it under warranty. I should have had to pay something but did not have to. I learned my lesson on paperweights. Phone was rooted as quickly as possible, installed ota rootkeeper and took the ota this morning. So far everything is golden.
Sent from my SCH-I535 using xda app-developers app
Cheap 100% working jtag
Hey I found a guy that has very good service and is almost guaranteed to fix your hard bricked Samsung. Go to jtagmyphone.com
Its the best guy and he has very good service and he's very quick also you can give him a call at 518.847.7473. This is the best option for your bricked phone I promise.
Related
Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL
jhong91 said:
Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL
Click to expand...
Click to collapse
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.
qkster said:
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.
Click to expand...
Click to collapse
Hello,
thanks for the reply!
if the problem really is, as you may have kindly pointed out, with the circuit board or bad battery terminal, do you think it's unrecoverable even by the AT&T technicians (or mobiletechvideo's jtag service)?
Also, this is my first time dealing with warranties on smartphone.
If they happen to find out that I have voided the warranty by rooting the phone, the worst thing that could happen is not getting a replacement device right? they can't charge me or penalize me right?
Thanks in advance!
You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5
eZdubzitmk4 said:
You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
did you go to a retail store? or an official device support center?
thanks!
A retail store
Sent from dr0id using Tapatalk 2 beta 5
eZdubzitmk4 said:
A retail store
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
ok, i thought I was supposed to go to device support center..
i guess i'll go to retail first and then device support center if they should redirect me there..
anyways,
thanks man!
Yeah it all depends on the person, most are pretty cool and try to help.
But others just send you away to support
Sent from dr0id using Tapatalk 2 beta 5
I had CM9 On my rooted Samsung Galaxy S3, and my phone would crash randomly in the middle of changing songs on playerpro or in the middle of phone calls, so I tried to download SiyahKernel hoping it would add some stability to my ROM. Well I had 2 different versions of the kernel somehow. One was SiyahKernel 3.something, and the other was 2.5. I assumed the 3.something would be for the S3 and the 2 something was a false download that I got on accident and was made for the S2 or something, but when I tried to flash the 3.something it didn't work, versus when I tried flashing the 2.5 it installed perfectly fine. So, here's the fun part...when I went to reboot my phone it died COMPLETELY. I can't start the phone in download mode to odin it, can't get into recovery to flash an old nandroid. Phone won't turn on, won't charge, will do absolutely nothing, and I know for sure the battery was charged to 90% when it crapped out. I've done battery pulls, I actually did a 3 hour battery pull at one point...I don't have insurance, and I don't have the $$$ to go buy another phone, so if anyone has some ideas on how I could either get my phone back operational, or a cheaper solution (like a jigg) it would be MUCH appreciated. I wasn't just a noob jumping into it on my S3, I've been rooting, romming, and flashing **** since 2009, and it's my 10th smartphone, but my first brick ever. Please help!
search jtag.
If you can't get into odin mode or recovery then your phone is deffo hard bricked n will be costly to repair mate. Be careful flashing kernels n use odin to do it not recovery mode
Sent from my GT-I9100 using xda premium
I had the gs2 and I was trying to unroot it and I couldn't even get Odin to work because it didn't recognize the phone. So I called samsung and told them that got an update, but after it finish updating it cut off and never came on, and the battery was fully charged. So, if I was you I'll go that route. And good luck
droidstyle said:
search jtag.
Click to expand...
Click to collapse
Could I do the JTAG process MYSELF, or is paying them 60 dollars the only way to solve my problem?
That seems like the only way to fix this, because as of right now I seem pretty much screwed.
Atreux said:
Could I do the JTAG process MYSELF, or is paying them 60 dollars the only way to solve my problem?
That seems like the only way to fix this, because as of right now I seem pretty much screwed.
Click to expand...
Click to collapse
I think you need equipment to do it.
Sent from my SCH-I535 using Tapatalk 2
Note for the future: always a good idea to carry the cheaper (just asurion) insurance if your gonna root and flash. It's $5.18/month. A quick "oops I drove over my phone, or its on the bottom of the Atlantic", and boom.. New phone for a C note.
Sorry for no solution, it's more for others reading post.
Sent from my SCH-I535 using xda premium
mustbepbs said:
I think you need equipment to do it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
annoyingduck said:
Note for the future: always a good idea to carry the cheaper (just asurion) insurance if your gonna root and flash. It's $5.18/month. A quick "oops I drove over my phone, or its on the bottom of the Atlantic", and boom.. New phone for a C note.
Sorry for no solution, it's more for others reading post.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This post is ridiculous. Asurion blows, never have had a good experience with them over using 5 phones insured by them. Only ever had 2 crap out on me (hardware-wise. If it was ever software related I did it, and knew exactly how to handle it, but the 2 that were done were spidered screens). They gave me a broken refurbished evo back for the very first phone I ever had that I rooted, rommed, and hacked on for DAYS trying to learn the entire process...all those manhours and they send me a refurbished phone with nothing on it, and a screwed up LCD digitzer...do NOT recommend asurion whatsoever, and will never use them again no matter what carrier I go with.
mikey banner said:
If you can't get into odin mode or recovery then your phone is deffo hard bricked n will be costly to repair mate. Be careful flashing kernels n use odin to do it not recovery mode
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Why would you use odin to flash a kernel? I use cwm all the time for roms and kernels alike. Odin for radios or to return to stock. Cwm does everything else I need it to do. Same mistake could have been made on a computer guy downloaded two kernels and flashed the wrong one.
OP I am sorry for your loss.
Sent from my SCH-I535 using xda app-developers app
annoyingduck said:
Note for the future: always a good idea to carry the cheaper (just asurion) insurance if your gonna root and flash. It's $5.18/month. A quick "oops I drove over my phone, or its on the bottom of the Atlantic", and boom.. New phone for a C note.
Sorry for no solution, it's more for others reading post.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
imo insurance fraud is not the right answer. the right thing to do is research then flash, dont flash then research. ofcourse its now standard in america to be bailed out for every mistake we make, so perhaps your right.... I have yet to cave in and accept this kind of mentality.
The profit margins these companies make is ridiculous to begin with. It's not fraud, the only thing that may be considered even close to it is claiming that the phone is missing or damaged beyond repair due to something that was out of your control. Non the less your insurance covers all these avenues twice a year.
In reality, a bricked phone should be covered under insurance, and I'm sure if you have the proper legal knowledge you could argue that further and make them cover it without having to tell a white lie. Insurance is simple, covering a loss. And a loss is technically a brick (that's not open for debate either, that's correct), but there is a loophole they use where they can refuse to honor a claim if they feel to do so (hence modifications).
F that. I pay for insurance, I do my part. Not to mention when I actually signed up for the insurance, I asked the vzw rep if a rooted phone is covered, and his response was exactly this: don't take a chance, smash it up and send it back, or disappear the device.
I do not abuse or condone anything of what I said, I have yet to make a claim, but be assured, if I brick my device after 5 years of carrying ins. I am getting my money's worth out of it.
Sent from my SCH-I535 using xda premium
I've bricked my GS3. I got it rooted, custom recovery installed and bootloader unlocked then proceeded to flash the Foxhound rom. Now after the Foxhound flash, it is completely unresponsive. All I can guess is that I downloaded the wrong version of the rom.
When I plug it in, device manager recognizes it as QHSUSB_DLOAD. searching on this gives very disheartening results.
Is there any hope? I've found some references that certain phones are recoverable if a Linux machine is available to perform the operation. I do use Linux so if something is available, please clue me in.
Thanks,
Quintin
QU3U3 said:
I've bricked my GS3. I got it rooted, custom recovery installed and bootloader unlocked then proceeded to flash the Foxhound rom. Now after the Foxhound flash, it is completely unresponsive. All I can guess is that I downloaded the wrong version of the rom.
When I plug it in, device manager recognizes it as QHSUSB_DLOAD. searching on this gives very disheartening results.
Is there any hope? I've found some references that certain phones are recoverable if a Linux machine is available to perform the operation. I do use Linux so if something is available, please clue me in.
Thanks,
Quintin
Click to expand...
Click to collapse
a brick is when the phone does nothing, like a brick.
your phone is in DLOAD MODE.
google is what id do, if i knew how to get out id tell you
I'm not 100% up to date on all roms, is that rom even for the Verizon galaxy s3?
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
I'm not 100% up to date on all roms, is that rom even for the Verizon galaxy s3?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Apparently not.
Can you boot into down load mode or recovery?
Sent from my SCH-I535 using xda app-developers app
barrackOBAMA said:
Can you boot into down load mode or recovery?
Click to expand...
Click to collapse
Nope ... I press any button, or combination thereof, and nothing happens. Well, not nothing. If I'm plugged into the computer it dings in recognition of a device being plugged in but there is zip displayed on the screen of the phone.
At this point, I've done enough reading to come to the understanding that the phone is dead ... may as well bury it in the back yard next to the cat for all it matters.
QU3U3 said:
Nope ... I press any button, or combination thereof, and nothing happens. Well, not nothing. If I'm plugged into the computer it dings in recognition of a device being plugged in but there is zip displayed on the screen of the phone.
At this point, I've done enough reading to come to the understanding that the phone is dead ... may as well bury it in the back yard next to the cat for all it matters.
Click to expand...
Click to collapse
Foxhound? Did you flash an international ROM?
Sent from my SCH-I535 using Tapatalk 2
TXI Kaze said:
Foxhound? Did you flash an international ROM?
Click to expand...
Click to collapse
Yes, I'm guessing so. I ran across it when working with CM last weekend on the Nexus that the GS3 replaced. That was the fist I've worked with ROMs. I knew Foxhound was out of Italy but the light never went on.
Good thing I still have the Nexus.
JTAG is the only fix for the QHSUSB-DLOAD mode. Unless someone has very recently found a way to recovery from it which is doubtful.
Mobiletechvideos.com can fix you up for about $60 (plus shipping I believe) and a couple weeks.
JBO1018 said:
JTAG is the only fix for the QHSUSB-DLOAD mode. Unless someone has very recently found a way to recovery from it which is doubtful.
Mobiletechvideos.com can fix you up for about $60 (plus shipping I believe) and a couple weeks.
Click to expand...
Click to collapse
Hey, man ... thanks! Everything I have read about JTAG was that I had to send it back to Verizon but it wold cost me so much that I may as well buy a new one.
Ya know ... when I started out with computers ump-teen years ago, you'd tweek the machine till it was fubar, wipe it and start over. Now you tweek this stuff till it's fubar, fork out a chunk-o-change and don't do it again. They've taken all the joy out of it.
I did the same exact thing about a month and a half ago.
it would make a noise when i plugged into the computer, but couldnt boot into download or recovery. and i also flashed an international version on accident!
Found a guy that does it for 45, and got it back 7 days later. just google brickedmyphone and his is the first link. I tried talking to the mobiletechvideos guy and he didnt respond for about 6 days which is a long time with a bricked phone! :laugh: Could've been a fluke, but this guy and brickedmyphone got back to me quick and was cheaper than mobiletechvideos. But the fact that he did it quicker than mobiletechvideos for me was because he's not as popular(i think) and lives closer. mobiletechvideos is in texas (as was 60 bucks before shipping) brickedmyphone is in michigan(45 before shipping), michigan being much closer to ohio, i chose him.
whoever you choose, it is well worth the month because it teaches you a very good life lesson to triple check everything before flashing a rom
yay for runon sentences and sounding like a poorly written testimony! oh well :b
good luck mang.
I recently bought a Samsung Blaze from my friend who upgraded to an Iphone 5 for $50.
I really enjoyed the phone, but being the autist I am I couldn't handle the bloaty pink addons that tmobile had provided. In addition I had numerous prompts about how my phone couldn't complete wireless calling due to my dated prepaid sim card.
I decided to use keyes to upgrade to ICS, which provided no new differences.
I then decided to go to my local library to root my phone on a windows machine.
During my first attempt I was rushed, and ended up soft bricking my phone.
My second attempt was sucessfull in rooting and installing the clockwork mod.
I tried downloading liquid smooth and installing it, like a moron ( i assumed all roms would work with any device considering that I really couldn't find a specific set of roms for the device). I ended up hard bricking it.
Now, what do I do?
Can I go to tmobile and play dumb, despite the fact that I do not have a contract with them and just a prepaid sim? Would they offer a replacement even without a receipt (its got TMOBILE plastered all over the front in that respect).
or
Should I just play dumb with Samsung? Say that my power went out when installing ICS on kies and my phone wont turn on? Will they send me a refurbished one?
or should I just sent it here mobiletech videos .mybigc om merce.co m/s amsung-gala xy-blaze-4g-jt ag-bric k-repa ir/
It might be nice to have it unlocked and rooted, and I guess I could have them install a rom I want in that event.
Any insights are much appreciated.
I've hard-bricked my Blaze once. All I did was send it back(not in store) and get a new replacement one.. As some people suggested, have you tried getting in download mode? ROMs as you've learned don't work with any device. That's why we have a separate forum for our device . Which LiquidSmooth did you use? In the Dev forum(for the Blaze) we have a LiquidSmooth ROM..
Neither T-Mobile nor Samsung are obligated to replace the phone for a number of reasons, but you could give calling them a try if all else fails. Samsung might be willing to replace it if it has been less than a year since it was purchased, but my experience with them is that they wont honor a warranty without a receipt if you're not the original owner.
First try getting the phone into download mode and using ODIN to reflash the stock rom tar, following the directions of course: http://forum.xda-developers.com/showthread.php?t=1591601
You really can't hard brick this phone... I've even wiped all partitions abd got it back..
Get it to download mode and you are good
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
chjema said:
You really can't hard brick this phone... I've even wiped all partitions abd got it back..
Get it to download mode and you are good
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Its very difficult to hard brick that's for sure.
Sent from my Nexus 4 using xda app-developers app
im_awesome_right? said:
I've hard-bricked my Blaze once. All I did was send it back(not in store) and get a new replacement one.. As some people suggested, have you tried getting in download mode? ROMs as you've learned don't work with any device. That's why we have a separate forum for our device . Which LiquidSmooth did you use? In the Dev forum(for the Blaze) we have a LiquidSmooth ROM..
Click to expand...
Click to collapse
To specify, it is not reacting to any button presses at all. The soft brick that I previously did just made it freeze at the tmobile spash screen, which I fixed by returning to stock.
I cannot currently turn on the phone, nor get it to download mode. I will not indicate if it is charging, and plugging it into the computer brings up "improppertly removed media" prompts on my computer screen.
I only have osx and linux, so I kind of rushed when the library was closing and downloaded a stable version of liquid smooth, turned on usb storage on my phone, then launched the zip file from clockwork rom manager, just as some random web page told me to.
When you said you returned it back, did you mean tmobile or samsung? Did they ask for receipt or for your sim card to still be in the device; or did they just take it and give you a new one because it was clearly marked as a tmobile device?
Bulbousmicrobe said:
To specify, it is not reacting to any button presses at all. The soft brick that I previously did just made it freeze at the tmobile spash screen, which I fixed by returning to stock.
I cannot currently turn on the phone, nor get it to download mode. I will not indicate if it is charging, and plugging it into the computer brings up "improppertly removed media" prompts on my computer screen.
I only have osx and linux, so I kind of rushed when the library was closing and downloaded a stable version of liquid smooth, turned on usb storage on my phone, then launched the zip file from clockwork rom manager, just as some random web page told me to.
When you said you returned it back, did you mean tmobile or samsung? Did they ask for receipt or for your sim card to still be in the device; or did they just take it and give you a new one because it was clearly marked as a tmobile device?
Click to expand...
Click to collapse
Well I had a warranty. I talked to the T-Mobile guy over the phone and they said they would send me one.. Just call them. But make sure you don't say anything about trying to get a custom ROM lol.
Sent from my Provisioned Galaxy S Blaze
So I see this seems to be working for Sprint users... Anyone tried this for verizon?
I have a second stock Verizon GS3 sitting here and all the other required bits to try it if someone can give me a little help on how/what to extract from the working phone.
BTW I bricked my stock ROM rooted phone by plugging in a usb flash card adapter I have used in the past. I'm wondering if the paragon ntfs mounter app is partially to blame... SuperSU had recently started giving notifications paragon had been granted SU access ever time the screen was enabled.
Thanks
_sadpanda said:
So I see this seems to be working for Sprint users... Anyone tried this for verizon?
I have a second stock Verizon GS3 sitting here and all the other required bits to try it if someone can give me a little help on how/what to extract from the working phone.
BTW I bricked my stock ROM rooted phone by plugging in a usb flash card adapter I have used in the past. I'm wondering if the paragon ntfs mounter app is partially to blame... SuperSU had recently started giving notifications paragon had been granted SU access ever time the screen was enabled.
Thanks
Click to expand...
Click to collapse
Are you able to boot into recovery or download mode? Doesn't sound like a hard brick.
If you can't then the only way to recover from it is jtag, that method stated in the thread you linked wouldn't work.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Are you able to boot into recovery or download mode? Doesn't sound like a hard brick.
If you can't then the only way to recover from it is jtag, that method stated in the thread you linked wouldn't work.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
its a hard brick. no lights even while charging, no response from buttons or usb jig
I went ahead and cracked it open anyway and sure enough... if a similar solution does exist, we would definitely need another leaked document. boards are completely different.
JTAG it is.
_sadpanda said:
its a hard brick. no lights even while charging, no response from buttons or usb jig
I went ahead and cracked it open anyway and sure enough... if a similar solution does exist, we would definitely need another leaked document. boards are completely different.
JTAG it is.
Click to expand...
Click to collapse
This is the second thread I've seen where a device was bricked by plugging in a peripheral device. This definitely shouldn't happen.
I would call up Samsung and tell them what happened, they might fix your phone or give you a new one for free. This isn't your fault this happened.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
This is the second thread I've seen where a device was bricked by plugging in a peripheral device. This definitely shouldn't happen.
I would call up Samsung and tell them what happened, they might fix your phone or give you a new one for free. This isn't your fault this happened.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Are the situations occurring from the same ROM and/or Kernel?
DubleJayJ said:
Are the situations occurring from the same ROM and/or Kernel?
Click to expand...
Click to collapse
That's a good question, the user in the other post used Cyanogenmod 10.1.
Either way, I don't see how a peripheral device could overwrite a bootloader and hard brick a phone. But it's definitely happened twice.
http://forum.xda-developers.com/showthread.php?t=2374046
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's a good question, the user in the other post used Cyanogenmod 10.1.
Either way, I don't see how a peripheral device could overwrite a bootloader and hard brick a phone. But it's definitely happened twice.
http://forum.xda-developers.com/showthread.php?t=2374046
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I was on no-wipe jelly bean.
Being that its hard bricked is there any reason they would not replace it? (ie no way to tell it was rooted etc) The top right corner of my frame has a dent in it (dropped while removing a difficult clam shell case) but other then that, no wear or damage.
_sadpanda said:
I was on no-wipe jelly bean.
Being that its hard bricked is there any reason they would not replace it? (ie no way to tell it was rooted etc) The top right corner of my frame has a dent in it (dropped while removing a difficult clam shell case) but other then that, no wear or damage.
Click to expand...
Click to collapse
If your phone honestly got bricked by a peripheral device, I'd call Verizon and they will send you a refurbished phone. But if it was your fault I'd pay the 60 bucks and get it jtag. My phone had lots of dents but Verizon still didn't charge me for a replacement but then again I could have gotten lucky
Sent from my SCH-I535 using xda premium
Watoy said:
If your phone honestly got bricked by a peripheral device, I'd call Verizon and they will send you a refurbished phone. But if it was your fault I'd pay the 60 bucks and get it jtag. My phone had lots of dents but Verizon still didn't charge me for a replacement but then again I could have gotten lucky
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
took it to verizon store today. told the guy what I did, he played with it for a few minutes, looked at his screen for a while, checked to make sure there was no obvious damage to the usb port then told me my new phone would be arriving at my home tomorrow. warranty claim through samsung, NOT assurian insurance claim.
That is a lot better then what samsung told me via the live chat... They tried to have me load recovery, then said I would have to mail them the phone (usually 2 days) wait for repair (usually 5 days) then wait for return shipping (usually another two days).
I'm glad it worked out and I didn't have to pay for JTAG. I wonder what rom the replacement will ship with...