Related
Sd card stopped reading on g2 and I've tried the following:
Used different sd cards, still nothing detecting.
And sd card reads fine on my computer via card reader
Tried a master reset
My question is since its still under warranty and this model I have has been rooted with s off, will they charge me for the full replacement fee? I've already called tmobile to get a replacement. Phone works fine its just not reading the sd cards I place in the slots.
Its not under warranty if you rooted it....that being said its up to you. I dont think they have time to check. they just wipe em check hardware and see if they should refurb or trash.
Sent from my HTC Vision using XDA App
That sucks, you can use fastboot to apply update.zip files so I would try that(maybe get a brick and say it was from the update)
Sent from my T-Mobile G2 using XDA App
I understand that its against warranty if the phone is rooted but the cause of the SD read isn't a software issue its a hardware issue. With that being said I've been doing some research and it seems that its better if i somehow brick the phone, but I did call them up today, or well the tmobile sales rep did and told them that the sd card wasn't being read. Has anyone used warranty on a rooted phone?
Also is there a way to unroot without being able to use the SD card?
Not wanting to postwhore, but I turned off the phone and left it there off for a good 15 minutes, then rebooted and somehow the sd card's reading atm so now going to follow these steps to unroot the phone before returning it.
http://www.addictivetips.com/mobile/how-to-unroot-t-mobile-g2-htc-desire-z-complete-guide/
One could argue that the non approved software broke the hardware.... just sayin......
Sent from my HTC Vision using XDA App
nguyen925 said:
Also is there a way to unroot without being able to use the SD card?
Click to expand...
Click to collapse
fastboot has a command to apply an update.zip(as i posted above)
g_grey said:
fastboot has a command to apply an update.zip(as i posted above)
Click to expand...
Click to collapse
is this going to update the phone through zip file? Will that turn on S off?
shortlived said:
One could argue that the non approved software broke the hardware.... just sayin......
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
True but seems like i'm the only one with this particular issue. I don't see how rooting my phone would lead to an SD card reading malfunction. Both of which are unrelated..
i have not tried it since i don't have a problem with my sdcard reader, but the fastboot binary has an option to apply a zip file via the terminal on your computer. so as long as you can read and do a little research you should be ok to try it(worst case you brick your phone and you're done)
update*
I sent in my phone even though it was perma-rooted, and got tmobile to replace it free of charge. Not sure how that worked out but phone's been fully functional since.
Ok, I rebooted into recovery last night and I got a 5 vibrates and a green blinking light.
I can get my phone to go into android if i have it pluged into usb but sd support is disabled. If i unplug at any time, it reboots into 5 vibrates. Battery pull.
I can get it ino recovery sometimes but nothing from sd card can be accessed.
I can get it into bootloader but it says s-on for some reason and nothing is flashable from bootloader including ruu's or radio upgrades etc...
The phone is not communicating with pc or pc with phone
Adb is not functional either.
Ive tried everything that i can think of to unroot etc..
Any help would be greatly appreciated. Im desperate.
Thanks,
Incubus
Your sd card may be corrupt. First, back it up, then format it to fat32 in windows. Then put the PB31IMG.zip file on the root of your sd: http://www.megaupload.com/?d=9Q4CNAGX
Put the sd card back in the phone and do a battery pull. When you put the battery back in, hold the volume down key for a few seconds if the phone is plugged in. If it isn't plugged in, hold the power button and the volume down key until the bootloader comes up. It should eventually ask you if you want to update, and press volume up.
If you can't get to the bootloader, then you are most likely bricked. Talk to verizon about a replacement.
Also, before this happened, were you flashing any radios via bootloader?
Well if you got S-ON, I would just take it to VZW and say this **** is messed up get me a replacement, unless you didnt originally buy the phone from them.
I'd try a different SD card formatted to Fat 32 with the RUU on it, unless you already tried that.
but i cant even flash an ruu from my pc either. That has nothing to do with the sd does it? Also, if i put anything on my sd card to flash in bootloader. It just says its checking file and never asks me if i want to install it like it used to.
Does an sd card have to be in the phone in order to flash a ruu from the pc?
incubus26jc said:
but i cant even flash an ruu from my pc either. That has nothing to do with the sd does it? Also, if i put anything on my sd card to flash in bootloader. It just says its checking file and never asks me if i want to install it like it used to.
Does an sd card have to be in the phone in order to flash a ruu from the pc?
Click to expand...
Click to collapse
Don't think so, but I think it has something to do with HBOOT or Radio version that's in the RUU, so if the one that is on the phone now is higher then the RUU, it wont update. Maybe if its the same version as well it wont update. Dont think you need the SD card to run RUU from PC.
So I assume that since you are trying to fix it, there is no way you can get a warranty replacement?
TNS201 said:
Don't think so, but I think it has something to do with HBOOT or Radio version that's in the RUU, so if the one that is on the phone now is higher then the RUU, it wont update. Maybe if its the same version as well it wont update. Dont think you need the SD card to run RUU from PC.
So I assume that since you are trying to fix it, there is no way you can get a warranty replacement?
Click to expand...
Click to collapse
didnt I ruin my chances of a warranty by rooting it?
incubus26jc said:
didnt I ruin my chances of a warranty by rooting it?
Click to expand...
Click to collapse
Totally, if there is any trace of root or customizing of the software in any way your warranty will be voided.
Sent from my SPH-P100 using XDA App
incubus26jc said:
didnt I ruin my chances of a warranty by rooting it?
Click to expand...
Click to collapse
Well if it says S-ON then you are OK. Does it have stock recovery or clockwork on it, if even accessible? If you call in, they will send you a new/refurb model, then you send it back in. They wont even bother checking. I would suggest calling over going to a store. You get better service and more convenient. All I would say that your phone does this and that and wont boot and they will probably try to tell you to do a few things, but if you can't get into the OS, I don't see your phone call being long.
AlpineM3 said:
Totally, if there is any trace of root or customizing of the software in any way your warranty will be voided.
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
Only if he goes to the store. If he calls and gets it taken care of, they will send him a phone, then he sends it back. I believe all they check is that there was no water damage and cracked screen and other physical damage.
can i just say i lost it?
incubus26jc said:
can i just say i lost it?
Click to expand...
Click to collapse
If you got insurance on your policy,then yes, you can say it was lost/stolen. You just pay the $90 deductible or whatever for the new phone.
But if you don't have insurance then you're screwed on that approach, also if you call for warranty replacement they just check for any physical damage, but they do try to boot it
Sent from my HTC Incredible
yeah, it looks like im going to pay the fee
incubus26jc said:
yeah, it looks like im going to pay the fee
Click to expand...
Click to collapse
Oh well at least its cheaper then paying full price.
you should be ok. try flashing stock rom through hboot (pb31img file). you can find one posted in the get back to stock thread. if you can't find it let me know and i'll get it for you.
did you try flashing recovery through hboot as well? i can send you a pb31img with clockwork 2.5.0.5 if you want to try but i think you need a signed image.
incubus26jc said:
Ok, I rebooted into recovery last night and I got a 5 vibrates and a green blinking light.
I can get my phone to go into android if i have it pluged into usb but sd support is disabled. If i unplug at any time, it reboots into 5 vibrates. Battery pull.
I can get it ino recovery sometimes but nothing from sd card can be accessed.
I can get it into bootloader but it says s-on for some reason and nothing is flashable from bootloader including ruu's or radio upgrades etc...
The phone is not communicating with pc or pc with phone
Adb is not functional either.
Ive tried everything that i can think of to unroot etc..
Any help would be greatly appreciated. Im desperate.
Thanks,
Incubus
Click to expand...
Click to collapse
Verizon will cover this under the one year warranty. Thankfully I thought I was the only one, this happened to me twice.
Inc,
What were you doing at the time? Did you flash an incorrect hboot? I'm really surprised it can't be recovered if you can access the bootloader. Did you try another card just to rule it out?
SGH-I747 (4.1.2 i747's please)/ SGH-i747m( If you have a official 4.3 i747m, please post a debrick.img) only:
Hi, I recently hard bricked my phone into QHSUSB DLOAD and I am going to attempt repairing it through the SD Card boot method.
http://forum.xda-developers.com/editpost.php?do=editpost&p=47431259
I need a debrick.img to flash to the SD card in a Linux OS.
I would have gotten it myself but my phone is obviously dead. I found one before on XDA, but it did not work on my device and it gave me an error in the Linux terminal when it should not have.
-snip-
The end of the 3rd boot-loader stage in mmcblk0 is at 77.3 megabytes. If you are going to help out using your device, try to refrain from uploading an image with a different ROM other than root.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=2m count=81054925
The count is the amount of bytes. I am not sure if it is meant to be 1000 bytes=kilobyte or 1024 bytes=kilobyte. The count above is for 1024.
I need someone to install the Galaxy S III unified toolkit, and pull the first 7 partitions from mmcblk0 ,which is where the third bootloader stage ends.(Don't upload a heavily modified device please) http://www.skipsoft.net/?page_id=213 Once you get the files, PM me.
If anyone has a link to a working one, please post that. If you want to get your own image to help me, go ahead.
Thanks guys.
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
what happened?
winosxbuntu said:
what happened?
Click to expand...
Click to collapse
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
99ytrewq9111 said:
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
Click to expand...
Click to collapse
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Thanks for that link! It looks very promising, and I can probably find a stock boot.IMG in there. I will work on tomorrow. If I succeed, I'll edit the OP and make a debrick guide for this drvice forum. A word of advice, try not to mess with your bootloader or you end up like me
winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Hi, the toolkit didn't fix my phone, but its defiantly a step up. Since I'm assuming you have the toolkit installed that you suggested it, could you do me a favor?
It will be a bit easier using the toolkit to extract the partition files. If you could pull the first 7 partitions from "mmcblk0" of your device through the toolkit, it will probably set the next step to fix my phone. (Assuming you have a 16g i747... I don't really know)
You don't have to do this of course.
Thanks man.
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
99ytrewq9111 said:
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
winosxbuntu said:
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
Click to expand...
Click to collapse
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
99ytrewq9111 said:
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
Click to expand...
Click to collapse
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Bradkirk said:
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
Click to expand...
Click to collapse
Did you use an i747 or a i747m device?
If a i747m image works on an i747, it will basically fix all of my problems.
spensa said:
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Click to expand...
Click to collapse
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bradkirk said:
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately that's the download I found that didn't work.
Thanks for trying though
damn! the only other help I can offer then, is that there is a pretty good thread on this over in the d2tmo section. someone there wrote a little tool to easily download the relevant data. might help you on your quest. or at least make it so you could ask someone that doesnt know ADB. best of luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
99ytrewq9111 said:
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
Click to expand...
Click to collapse
when connected to the computer written QHSUSB-DLOAD,
spensa said:
when connected to the computer written QHSUSB-DLOAD,
Click to expand...
Click to collapse
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
99ytrewq9111 said:
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
Click to expand...
Click to collapse
I took it to a service to repair
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?
jack man said:
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?
Click to expand...
Click to collapse
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.
omeadsthename said:
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.
Click to expand...
Click to collapse
Yea tried with a class 10 16g micro sd like a million times and it wont work.and i think its because i dont have the 4.4.2 img if some one could help me out by uploading it. u et the img via busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70
So the phone won't power on at all? Can't get into download or recovery?
are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?
audit13 said:
So the phone won't power on at all? Can't get into download or recovery?
Click to expand...
Click to collapse
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
yowski said:
are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?
Click to expand...
Click to collapse
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken
omeadsthename said:
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken
Click to expand...
Click to collapse
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?
yowski said:
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?
Click to expand...
Click to collapse
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.
omeadsthename said:
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.
Click to expand...
Click to collapse
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?
yowski said:
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?
Click to expand...
Click to collapse
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.
yowski said:
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.
Click to expand...
Click to collapse
Unfortunately kids at my high school are afraid of rooting, so xda is basically my only bet. Im just surprised that some sr member hasnt added a debrick img to their threads. I mean its 4.4 and this is android central!
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.
yowski said:
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.
Click to expand...
Click to collapse
Cant they find out that you are root and hard bricked? like doesnt that void warranty. and if its a 4.3 h brick cant u just use the sd method?
omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.
yowski said:
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.
Click to expand...
Click to collapse
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?
omeadsthename said:
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?
Click to expand...
Click to collapse
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.
yowski said:
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.
Click to expand...
Click to collapse
hmm i wish i could do that to my phone too. i mean, i dont even know how i would unroot without getting my phone on. but if im this hard bricked they probs cant tell anyways. im guessing?
uz unlock HARD BRICKING S3'S
omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
I DID THE SAME THING ! but i used debrick (i535 vzw 4.3 ) and it pattially worked at least it will recovery and odin but i think it needs to be the 40 mbps type card the black micro would not work for me , then i flashed the wrong recovery and am starting all over but the debrick still getting me into odin thats ware you will sideload the right recovery and firmware ,rom what ever hope ( i even paid for cdma work shop and it aint did jack ) debrick then odin sideload look it up thats the best i got
Hey all, Was wondering if anybody had some time to help me troubleshoot why I cannot for the life of me get this method to work and maybe explain to me a few things that are confusing to me...
Basically my phone is hard bricked:
Samsung Galaxy S3 SGH-i747 (AT&T)
- Began with Stock 4.1.2 (almost %100 positive)
- Attempted flash to 4.4.4 Task650's AOKP ROM (Flashed ok but stuck at boot animation) via CWM
- Attempted reverting back to stock with the file below via Odin but I must have missed a step...
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
Now I am hard bricked and don't know where to go from here. I've tried several solutions:
- Homemade Jig (didn't work)
- 3 button combo / download mode (doesn't work)
- Odin does not read phone
- Connected to a pc (red power light appears but nothing else)
- SD card method - Using Win32DiskImager to write images to a 16gb class 10 micro sd
- Debrick images used: 4.1.2, 4.1.1, (should i try 4.0.4, 4.3, or even 4.4?)
- How do I tell if the image is writing correctly and partitioning the drive right?
- When the sd card is seen in the computer I see a folder on it named "image" with several files inside it but I don't know how to see partitions
I have screenshots too if you'd like to see them. Let me know if you have any suggestions or have seen anyone with this same issue able to fix it. I'd appreciate it. Thanks.
- Chris
not very knowledgeable about this stuff , but here is a thread (hardbricked 4.1.1) with link to debrick images 4.3/4.4.
http://forum.xda-developers.com/showthread.php?t=2880002
thanks to @DocHoliday77
hopefully someone will come along with some real help.
good luck.
err on the side of kindness
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok thanks. I'm going to attempt this again tonight using an SD card adapter instead of using another mobile device as the adapter to see if that makes a difference. If that doesn't do the trick I will try the LinuxLiveCD method. I'm using a Lexar 16gb Class 10 micro sd card so I don't think it that is the issue but I guess it wouldn't hurt to try a different brand.
Just curious, has anybody here successfully debricked their phone using another mobile device as the sd card adapter?
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Good to know, but just to clarify when you say it "fails"... what exactly fails - writing the image file, partitioning the card, or does it write everything to the card ok and then just not boot up? I'm just asking so I know what to look for if it ever happens.
Thanks for the responses as I'm still new to this process and this phone and every little thing helps!
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So, it appears that the issue was using the mobile device as the sd card reader. After writing the debrick file to the same sd card with an actual sd card reader, I am able to boot into the stock recovery. From here, I should just be able to flash a stock ROM to it correct or no?
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok, after playing with the phone for awhile I have found out that I can boot into download mode now. After rebooting, I was able to boot into the stock 4.3 ROM but I noticed I lost root access. Now the problem is I cannot enter the recovery to even flash the file you mentioned above (I flashed CWM via Odin but I can't boot into it). The phone can be seen in Odin now as well. I've done a little bit of research on achieving Root access again but I came across a post that mentioned I could ruin my IMEI number by flashing a "CF-Autoroot" file, should I be worried about doing this now that I'm on 4.3 or am I ok since I didn't use the OTA 4.3 ??
Again, thank you so much for the advise! I'm so glad this phone isn't a brick anymore.
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
CornfedChris said:
.... I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs.
... although I might try to upgrade again tomorrow and see what happens.
Click to expand...
Click to collapse
I've seen reports of this more than once where someone going back to stock initially receives the no updates available msg and then after 24 hrs or so it becomes available. So, your plan sounds good.
CornfedChris said:
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
Click to expand...
Click to collapse
Right on! Glad to hear you got it all fixed up! If that update does become available later, please let us know. I've been telling several people to wait a day, but I haven't heard if it actually came through for any of them yet.
If you do decide to root in the future, just don't forget about that backup!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
So tonight while I was watching TV I looked down at my phone and noticed it decided to just go ahead and update itself to 4.4.2, haha. So apparently there's an auto-update defaulted in the settings somewhere. I haven't really noticed too many differences yet but I'm liking it so far. :good: