I have a T999, 1.5 years old used on Tmobile's 30$/month plan and love it, but recently hard bricked. History: It's been rooted for more than a year, flashed with a rooted stock via ODIN, keeping the flash counter at zero. Accepted one OTA update and kept root using a rootkeeper app. About two months ago I installed clockwork recovery to start messing with roms, but didn't do anything other than flash the recovery.
A week ago, I was frustrated with random freezes and wanted to update, either to stock 4.3 or a custom rom. I tried cyanogen 1st, downloading the most recent stable rom- 10.1.3 from mid September, for the Tmobile s3. When I flashed, via CW recovery, the phone rebooted very quickly, with a frozen SGS3 plus the cyanogen logo screen. 30 minutes later, I pulled the battery and tried to get into recovery and go back to the nandroid backup I created earlier. Button combos, jig, nothing worked. I've tried KAsp3rd's debricking method using external SD boot image (on two different sd cards, both using a win32diskimager), but that hasn't worked. All I can get is an unrecognized device when I plug into a PC, and sometimes a red LED light when I plug in both with and without the battery. I've used an external charger, so the battery shouldn't be the issue. Would a next step be sending it out for JTAG wipe or new motherboard?
Thanks for any replies.
auguststuart said:
I have a T999, 1.5 years old used on Tmobile's 30$/month plan and love it, but recently hard bricked. History: It's been rooted for more than a year, flashed with a rooted stock via ODIN, keeping the flash counter at zero. Accepted one OTA update and kept root using a rootkeeper app. About two months ago I installed clockwork recovery to start messing with roms, but didn't do anything other than flash the recovery.
A week ago, I was frustrated with random freezes and wanted to update, either to stock 4.3 or a custom rom. I tried cyanogen 1st, downloading the most recent stable rom- 10.1.3 from mid September, for the Tmobile s3. When I flashed, via CW recovery, the phone rebooted very quickly, with a frozen SGS3 plus the cyanogen logo screen. 30 minutes later, I pulled the battery and tried to get into recovery and go back to the nandroid backup I created earlier. Button combos, jig, nothing worked. I've tried KAsp3rd's debricking method using external SD boot image (on two different sd cards, both using a win32diskimager), but that hasn't worked. All I can get is an unrecognized device when I plug into a PC, and sometimes a red LED light when I plug in both with and without the battery. I've used an external charger, so the battery shouldn't be the issue. Would a next step be sending it out for JTAG wipe or new motherboard?
Thanks for any replies.
Click to expand...
Click to collapse
Try KAsp3rd's debricking method again. You have to be pretty precise with the process i.e need the correct debrick image, the correct SD memory, etc.
Daoiod said:
Try KAsp3rd's debricking method again. You have to be pretty precise with the process i.e need the correct debrick image, the correct SD memory, etc.
Click to expand...
Click to collapse
Thanks for the reply! I've imaged SD cards 4 or 5 times, both with the first image mentioned, SGH-T999 ***NOT FOR 4.3*** and, just because I suppose it's possible CM10.1.3 is running 4.3 bootloaders or something, the second 4.3 image. In each instance, I get a successful write, ending up with a 63 mb partition visible to windows, about 24 more partitions on the SD card itself. I've done it with a 16gb class 4 card and a higher quality samsung 32gb class 10 card. Granted, each image write has been in windows, using win32diskimage, and not their linux imager, but lots of folks in the thread have done it with windows. Is it worth making a linux bootdisk and running the code on that system?
auguststuart said:
Thanks for the reply! I've imaged SD cards 4 or 5 times, both with the first image mentioned, SGH-T999 ***NOT FOR 4.3*** and, just because I suppose it's possible CM10.1.3 is running 4.3 bootloaders or something, the second 4.3 image. In each instance, I get a successful write, ending up with a 63 mb partition visible to windows, about 24 more partitions on the SD card itself. I've done it with a 16gb class 4 card and a higher quality samsung 32gb class 10 card. Granted, each image write has been in windows, using win32diskimage, and not their linux imager, but lots of folks in the thread have done it with windows. Is it worth making a linux bootdisk and running the code on that system?
Click to expand...
Click to collapse
I was pretty successful with using Windows to write the image. It didn't work at first because I wrote the wrong image. (I needed to use the 4.3 debrick image.)
Also, keep in mind that the memory capacity of the micro SD card has to match the memory capacity of the phone (i.e if your S3 is 16GB, you have to use a 16GB micro SD card).
I used a Polaroid 16GB micro SDHC card (my S3 is a 16GB) and it worked fine.
Thanks for the second tip. The class 4 card might not have been up to snuff. I used a Top RAM class 10 16gb card and managed to get some vibrations, eventually into factory mode, but my battery must have given out while I was opening ODIN. I'll try again tonight.
Sent from my SGH-I897 using xda app-developers app
auguststuart said:
Thanks for the second tip. The class 4 card might not have been up to snuff. I used a Top RAM class 10 16gb card and managed to get some vibrations, eventually into factory mode, but my battery must have given out while I was opening ODIN. I'll try again tonight.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Nice! I'm glad to hear! The follow up after you get it into download mode is to flash a stock firmware via Odin.
Daoiod said:
Nice! I'm glad to hear! The follow up after you get it into download mode is to flash a stock firmware via Odin.
Click to expand...
Click to collapse
So I was able to get into factory/ODIN mode, but two PC's with the proper drivers, that have both flashed ODIN wouldn't recognize the phone. About a month ago, some wine got spilled near the USB port and it's acted squirrely ever since. It would charge, but most cords wouldn't allow PC's to recognize it. Just pulled the motherboard, cleaned out the port with rubbing alcohol and a pipe cleaner, compressed air dried, and will let it sit overnight before putting everything back together. We'll see if this works. That or a $100 new motherboard on ebay, I guess.
Related
I rooted and installed the leaked OTA. After hearing about the possible 2.2 I tried to downgrade the radio. Something messed up along the way and now I'm stuck with an incredible that is showing no internal memory (won't even let me save a picture), will not read an SD card and keeps rebooting when I remove the usb cable. I'm stuck in a real hard place. If anyone can assist me in restoring my phone and how to go about it, it would be appreciated. Also it is now showing my phone as an unknown device when I connect to the pc and I can not get into adb.
Can you reboot into recovery? (power off, then hold volume down while powering back on) then select recovery?
If you can get into clockworkmod recovery, we can get you back up and running.
do a hard reset. if that doesnt work, take it back to vzw and make up a story on how it got the way it is.
TIP: i dont think you can downgrade the radio.
Sent from my Incredible using XDA App
I started following this tutorial http://www.youtube.com/watch?v=eeuiURZZZds and after trying to run 'flash_image misc mtd0.img', it said I did not have enough memory so I just unplugged the phone and tried to reboot, but it brought me to the recovery console and it's the stock one. So the stock img was able to install. I don't even have clockwork now. I should have left it alone. I have a constant sd card icon with a ?.
just hard reset or ruu . if this doesnt work, then i think you bricked your radoio. do you have 3g?
Sent from my Incredible using XDA App
Jd is right. Just ruu back to the leaked ota. If you can get to stock recovery you should be able to ruu. Once your back up and running we might be able to help you downgrade. First things first.
Just tried the hard reset it was a no go. I have 3G service and I made some calls to make sure it worked. After the hard reset it is still showing the sd card icon with ?. For the RUU do I need any drivers because the phone is showing up now as an unknown device.
Just give it a shot.
ruu is the way to go. your problem is more sever than hard reset fixijg.
Sent from my Incredible using XDA App
P.s. If you follow the downgrade tutorial by "IncredibleDoes" you can use an sdcard adapter and put the card into your pc (since your phone usb drivers aren't working), copy the "pb31img" file over, then reboot back into hboot, and it will put you right back to the original stock in one step.
If you have a card reader on your pc, turn the phone off, put the card in the pc and make sure it's formatted properly. Then put the ruu file on the card. (Follow the instructions in the unroot sticky topic.) Then put card back in phone and boot into stock recovery. It should apply the update.
Sent from Incredible using Tapatalk.
[email protected]
hows the ruu going?
Sent from my Incredible using XDA App
I'm still trying. It's not looking good. Hboot is still version .79 after I flashed the stock img. I'm probably going to have to call it a night for now though. I'll be back tomorrow to trouble shoot it some more. I'll write more after I try it again. Thanks for the help tonight!
of you need additional help feel free to pm me anytime.
Sent from my Incredible using XDA App
Hboot is NOT going to downgrade....no matter what you do. The stock (pre-ota) rom will run fine with the newer hboot version.
samwathegreat said:
Hboot is NOT going to downgrade....no matter what you do. The stock (pre-ota) rom will run fine with the newer hboot version.
Click to expand...
Click to collapse
Yes it will downgrade, as the ota leak is a newer version of .79. that is, if you follow the procedure right.
Also, yes you can downgrade the radio, in response to an earlier post.
If you got out of memory type messages running through that method, then you did it wrong. Maybe you tried it outside of clockwork? I haven't watched the video to do it, but seeing how I made the original post for it, I know it works.
Interesting! I wasn't aware of that breakthrough (hboot downgrade).
In that case, I suggest ruu'ing back to the leaked OTA (so that your USB and SD are both working again), then try following the instructions that adrynalyne referenced.
Good Luck.
http://forum.xda-developers.com/showthread.php?t=727263
I ruu'ed the img. The phone starts up and works normally. Except it still shows the internal and SD card memory as unavailable and the usb restarting after removing the cable. I tried to reload the leaked OTA through recovery, but it gets an error saying the file is not on the SD card.
I purchased a used droid incredible off of ebay to fix. The phone powers on but doesn't get past the droid incredible splash screen. It is able to boot into HBOOT but when the recovery option is selected it just goes back to the white splash screen. There is no sd card but I have put one in myself..it's not formatted and it's empty. Any help would be greatly appreciated!
What info is detailed in hboot? S-on, s-off, etc; provide any relevant info that you see once you boot into hboot. Do you know what os the phone is on: froyo, GB? Did the seller provide info on how the phone got in this situation?
Here's a photo of hboot. The owner said one day it just turned off and went to the splash screen. It was not rooted.
Sent from my Galaxy Nexus using XDA
Aight, you may have to perform a factor reset. Have you done that yet? If so, you may have to download an RUU from here:
pvillecomp.com
It is under "Stock images." One download link is for the froyo RUU and the other is for Gingerbread. Place the file onto the root of your sd card in no folders and then boot into hboot. Hboot should prompt you to upgrade using the volume buttons.
Factory reset did not work. I will try the second option and get back to you
thanks!!
Sent from my Galaxy Nexus using XDA
I would not do the gingerbread ruu as that will upgrade the radio making it harder to root. I would try the froyo ruu first, if that works run unrevoked.
When I boot into hboot nothing happens. I'd this because the RUU is an exe?
Edit: I'm downloading the PB31IMG file now
Edit 2: The PB31IMG didn't seem to work. It said SD checking ..loading PB31IAG.zip: no image. And the same for PB31DIAG.nbh, PB31IMG.zip and .nbh
Sent from my Galaxy Nexus using XDA
Is your sdcard fat32?
Yes it is. PB31img didn't work and RUU says I have under 30% battery so I'm just charging the phone. If the phone wasn't even rooted in the first place what could the cause of the problem be?
jared, did you ever get this to work? I have one that is doing the exact same thing.
I did not! I tried to use the RUU through the computer and it seemed to restore everything but the radios but then failed. I was then prompted to do a recovery and try again but the phone went black and would not power on no matter how much I charged it.
That sucks....thanks for the reply though.
So I figured I would give you an update.
I ended up trying several micro SD cards (ones that I had laying around the house), started with SanDisk 2GB, then a Transcend 1GB, and finally a generic 4GB HC. When I used the generic 4GB, the Inc was able to see the PM31img file and downloaded and did the upgrade. Only problem is that I used the gingerbread image, and not sure what happened (my guess is slcd issue) but the radio failed everything else passed. When it rebooted I have nothing, no display and it doesn't look like it will even power up.
So I figured I would let you know, since I was having basically the identical issue you were, that it might be your micro SD card. But make sure you have the correct image on it too before you start swapping SD cards.
My at&t Galaxy S3 appears to be hard bricked. I tried using the method of using an .img file to the external SD card, yet now I'm unable to boot using that image.
Previously I was able to boot using the .img file, I did a factory reset, and now I'm stuck.
Are there any options available to me or anything else I can try?
thanks for all your help.
Obsessive said:
My at&t Galaxy S3 appears to be hard bricked. I tried using the method of using an .img file to the external SD card, yet now I'm unable to boot using that image.
Previously I was able to boot using the .img file, I did a factory reset, and now I'm stuck.
Are there any options available to me or anything else I can try?
thanks for all your help.
Click to expand...
Click to collapse
You would need to provide more information to let us know what went wrong and what fix to apply. What caused the brick in the first instance? After you booted the first time using the recovery image, did you do a firmware restoration which is the sure fix to getting your phone back in working order? The recovery image only lets you get the phone back into booting mode. Thereafter, you need to work your way up the rest of the food chain via full firmware restoration. If you did a factory reset/wipe without first restoring your firmware, it's possible you may have wiped the recovery image card clean. If that's the case, you would need to create a new image and repeat the process all over.
I bricked my dad's phone a while back. Couldn't get to recovery or anything. Just a blank screen, couldn't tell if it was even on or off. We ended up sending it to a guy on Ebay that has a JTAG and he was able to fix it for us. I think we only paid $25 too. Got it back working within the week.
If you would like the guys name I can find it.
ZS
ZehelSitchel said:
I bricked my dad's phone a while back. Couldn't get to recovery or anything. Just a blank screen, couldn't tell if it was even on or off. We ended up sending it to a guy on Ebay that has a JTAG and he was able to fix it for us. I think we only paid $25 too. Got it back working within the week.
If you would like the guys name I can find it.
ZS
Click to expand...
Click to collapse
I believe an JTAG will be my only option if the USB jig doesn't work any magic. The only life I get out of my phone when plugged into my computer is the USB driver and if I pull the battery while plugged in the red light shines.
Yep. That is exactly what mine did.
Debrick
I got mine unbricked by making a dedrick sd card. I used a 32gb sd and partitioned it and it worked!
So i tried flashing a new recovery and rom. here's how the process went down.
flash recovery
reboot
flash rom
clear cache - failed to mount /cache uh oh
try to boot - fail
reboot to recovery - flash old .zip of twrp 2.6.x
reboot followed by boot loops and no known to turn off device. Can't reach recovery now.
i do NOT have a windows computer which makes using odin hard. is there any way for me to fix this or do i need to locate a windows computer and use ODIN? does anyone know how i can at least get it to stop rebooting in the meantime?
Edit: i can reach download mode, that's all i can do at the moment as far as i know.
Pc and odin is my best solution or check this
http://www.xda-developers.com/android/need-a-samsung-usb-jig-build-your-own/
may help havent tried it
I had the problem myself.
Keep trying VolUp+Home, you must hit it in the right moment between screen cycles. Try pushing and releasing Pwr button too while you hold VolUp+Home, releasing it right before a screen cycle.
I was about to open my tablet to remove the battery but decided to try the last time. Finally I pressed Pwr+VolUp+Home and the right moment when the screen cycled, then released Pwr, and I was in recovery.
Try pulling external sd card to see if it boots up, just in case the card is causing the problem.
Sent from my LG-V500 using XDA Premium 4 mobile app
You need PC ODIN... The bootloader wasn't flashed, hence the problem. Flashing another JB recovery won't fix this...
You need to flash the whole rom in PC ODIN, this may require a factory reset.
Find TWRP2.7.0.1 and flash that, it's KK friendly, then flash the latest supersu (I believe its 1.99r3)using TWRP.
You should now be OK to go, Android KK with root and a custom recovery.
Th only drawback is that if you're external sd is formatted exFAT you can't make backups to it. though you can transfer the file to a PC then the Appropriate file on the external sd afterwards...
bootx1 said:
Try pulling external sd card to see if it boots up, just in case the card is causing the problem.
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know if this helps but my Note3 used to have this issue and heated up a lot around the SD card slot right after booting up and would reboot and reboot. Pulling out the sd card helped a little, but to get it to NOT reboot, I would put it in the fridge or put a cold can of drink on top of the sd card area with the battery cover off. The phone would reboot every second day or so and I would need to fridge boot it again.
This was shi77ting me heaps and I was close to giving up on my Note3 when the 4.4 OTA update came thru.
After the update, the Note 3 became rock solid and I was getting 500+ hr up times without itself rebooting. it only reboots now because I shut it down and I cant remember it rebooting by itself since the kitkat update. I love my Note3 now and run it rooted (Kingo Rooted), with SDfix, and dont wish for any update that might upset this rock solid stability.
My note3 is the N900 Exynos 5420 version.
My Note10 is the N605 SD800 version and it runs 4.3 very solid and I'm not keen to upset it with a kitkat update as im happy with the way it is.
actually, you CAN use a Mac
smac7 said:
So i tried flashing a new recovery and rom. here's how the process went down.
[...i do NOT have a windows computer which makes using odin hard. is there any way for me to fix this or do i need to locate a windows computer and use ODIN? does anyone know how i can at least get it to stop rebooting in the meantime?
Edit: i can reach download mode, that's all i can do at the moment as far as i know.
Click to expand...
Click to collapse
I was faced with the same problem when I upgraded to KitKat and needed to enable writing to my external SDcard by rooting. I have a late 2011 MacBook Pro running an i7 chip. I was running OS X 10.8x at the time, but have since upgraded to 10.9 since Apple reenabled local syncing of contacts--all these big companies play the same games trying to own your data.
I used Parallels Desktop 9 and installed Windows 8.1. Once I did that, I was able to get Odin running on the Windows side to see my Note 10.1 (2014). After that, rooting was straightforward, just as if I was on a PC. You may not want to go to the expense (about $200 for Parallels and Win 8.1) but I wanted it to run the latest version of Office. Being able to root was a nice bonus for me.
Thanks guys. I ended up finding a windows 8 iso and installing in boot camp. It was a slow process but I eventually got it to work
Sent from my HTCONE using Tapatalk
I noticed that when I restart, or power off and on my HTC 10, sometimes it will bootloop 2 to 3 times at the white HTC logo. Eventually, the green boot animation will load, Android will start and the phone will behave normally.
Except for this anomaly, my phone has been rock stable in everyday use. It's a Taiwan set with the latest 1.30 firmware.
Anyone else having this issue?
Nobody?
Same issue. It started with the most recent OTA update. After installing, it was stuck in a boot loop until I hard powered it off. Then it boot correctly, but asked to send a bug report.
Now when i restart my phone, it typically always asks to send a bug report.
mine does the bootloop with xposed installed on bell's 1.21 firmware.
Just chiming in - US unlocked on ATT, have seen this issue on the stock 1.53 ROM as well as Bad Boyz. It is indeed transient in nature.
Installed 1.80 Taiwan firmware and it's still there...
Just booted up from power off, and it rebooted 4 times by itself before the green HTC circle logo finally appeared! Coming from an LG G4 with the infamous boot loop of death, this is scary stuff!
There is another thread on this a few threads below this one. As I mentioned there, I had this issue on a fully stock U.S. Verizon 10. I formatted my SD card, which I had transferred over from my m8, and have not seen the issue since then.
Parakaleo said:
There is another thread on this a few threads below this one. As I mentioned there, I had this issue on a fully stock U.S. Verizon 10. I formatted my SD card, which I had transferred over from my m8, and have not seen the issue since then.
Click to expand...
Click to collapse
Did you format the microSD card using the 10, or using a PC?
chong81 said:
Did you format the microSD card using the 10, or using a PC?
Click to expand...
Click to collapse
PC. It cleared the card, I put my music back on it and nothing else. And that seems to have solved it.
Had this issue too
After some tests i found, that my microsd-card was the fault! had a samsung 128gb evo+ card.
with a different card this issue doesnt occur.
put back my samsung card and the issue occured again.
after low-level formatting the card the problem is solved
Parakaleo said:
PC. It cleared the card, I put my music back on it and nothing else. And that seems to have solved it.
Click to expand...
Click to collapse
Well, I take this back. After formatting my SD card, I had 4-5 days with no problems, then this morning when I powered on the phone, it did the bootloop/send error report thing again
It does seem to be related to the microSD card - I removed my microSD for a few days, rebooted plenty of times and encounter a single boot loop.
Mine is a Lexar 128GB UHS-I 633x microSD.
Folks, please share the microSD card you're using, and whether you have encountered the transient bootloop.