Hey guys,
I'm running a DHD on Leedroid 2.3.4 b2 and was about to format my SD card (the ext3 topic) using ROM Manager 4.1.0.0 (CWM 3.0.2.5). It sent me to CWM after confirmation of SD format, after a few moments I saw the classic CWM screen saying the SD card had been mounted or found (can't remeber 100%), and it seemed to start. A few seconds later it all went black, the phone was out.
I tried to power it on again - nothing happens, the screen stays blank. I tried taking out the SD card and tried again: nothing. I got the battery out and in again: nothing. I plugged in the charging cable: nothing, not even a red/green LED on the top.
I'm really desperate now, because I can't even get into CWM like that, it's just DEAD. Do you have any idea?
You should read stickies before "hacking" the phone:
The first post says in the dev section:
jkoljo said:
As the title says, do not partition SD card using ClockworkMod or ROM Manager.
There has been multiple bricked devices already, all after partitioning SD in CWM. The device suddenly turns off while the partitioning is in progress, and never turns on again. We do not know what causes this issue yet, but I am sure that ClockworkMod team will look into it.
Update:
Update 2:
Update 3:
New ClockworkMod 3.0.2.6 and ROM Manager 4.1.0.0 are out!
Click to expand...
Click to collapse
Sent from my Desire HD using XDA Premium App
Darn, sometimes life is annoying. I was looking in the Q&A-forums not in Dev. "Luckily" I have an old iPhone here for the time while I can hopefully give it back (only a few weeks old, let's see what a store says).
Thx, I'm gonna scream and this thread can be closed.
Maybe someone can duplicate the CWM thread here too for other users, because I was looking here as I thought there might be questions like that.
Thx, at least knowing the enemy is a bit ok.
I am victim too btw hmm luckily i bricked my phone on a saturday(which is yesterday)so i didnt have to suffer 2 days.im gonna go to HTC service center in my country tomorrow after school...
Hi. I have updated my phone to official 2.3 rom by PB99IMG.zip way. It started to bootloop at not going further than htc screen. The only thing that seems to help is removing sd card. Without ir it boots up ok. One more problem. Icqn get bootloader to turn on, but cant get into recovery. What is the solution to my problem. Thank you. P.s my phone is unrooted and s-on
moochinazz said:
Hi. I have updated my phone to official 2.3 rom by PB99IMG.zip way. It started to bootloop at not going further than htc screen. The only thing that seems to help is removing sd card. Without ir it boots up ok. One more problem. Icqn get bootloader to turn on, but cant get into recovery. What is the solution to my problem. Thank you. P.s my phone is unrooted and s-on
Click to expand...
Click to collapse
Uf ur phone works fine without sdcard then ur sdcard could be damaged so try a different 1.
U cant get into recovery because u are s-on & not rooted. To have a custom recovery u have to atleast be rooted.
Sent from my HTC Desire
The card was perfectly fine before flashing
moochinazz said:
The card was perfectly fine before flashing
Click to expand...
Click to collapse
And? I always used sandisk sdcards, i changed to a bigger card and brand then 1 day i put a rom on 1 of the sandisk cards, booted recovery, full wipe and installed the rom and booted fine but after that i got constant reboots so i put the same rom on my new sdcard and it worked fine, no reboots. Strange but true.
Sent from my HTC Desire
jmcclue said:
And? I always used sandisk sdcards, i changed to a bigger card and brand then 1 day i put a rom on 1 of the sandisk cards, booted recovery, full wipe and installed the rom and booted fine but after that i got constant reboots so i put the same rom on my new sdcard and it worked fine, no reboots. Strange but true.
Sent from my HTC Desire
Click to expand...
Click to collapse
really strange, i let my phone sit through the night without the card in it. inserted it in the morning and its working withou problems
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.
omg... I pulled the sim card and just kept holding one of the volumes+power for a loooooong time and it booted!!! Now I'm afraid to turn it back off to put the sim and external cards back. Okay, put it in while powered up and all is fine.
Any reason I should be worried about AdAway?
AdAway updated definitions and asked if I wanted to reboot so I said yes and the phone is now off and I can't get it to boot. What can I try? I don't really know how to troubleshoot this phone. Battery was at around 30%. Nothing happens at all when trying to reboot normally or holding either vol+power. I pulled my external sd card and still no go.
Running Viper.
:crying:
Click to expand...
Click to collapse
Hey there, being a Nexus 5x owner, I always dreaded the ill fated bootloop. But i personally never ran into the problem until yesterday. I am using the Nexus 5x for over 20 months, so repair and warranty is out of question.
Also unlike others it didn't happen after any system update. The last update i did was like a month back. It was running on android oreo.
So 2 days back my sim card stopped responding. So i opened up my sim and tried it on other phone. The sim card was dead. I applied and got a brand new sim card and inserted it on my Nexus 5x, but the new sim never got detected. I waited for a day before trying the sim in other phone, it worked perfectly in other phones, i tried again in my 5x but it always said no sim card detected. But the problem started while trying 3-4 times to re insert my sim, the system went into a boot loop. After leaving it for some time it successfully switched on. But again went back to boot loop after an hour. And now it keeps on happening. It switches on successfully, works for an hour without detecting the sim card, back to bootloop. I am out of wits about what to do next.
I have already unlocked usb debugging and oem.
Any help is extremely welcome and i would be grateful.
Thank you.
There really is no need for a new thread on this topic! Matter of fact the BLOD thread is right at the top of this section!
Also read this for background https://www.xda-developers.com/nexus-5x-bootloop-fix-boot-phone/