Hey everyone, I have a droid charge that has been bricked for a while now. Here's how it went. I was just sitting on teh couch one day and I felt my charge getting reallly hot in my pocket, and when i took it out, it was stuck at the samsung screen. Before that, I had been having a few random restarts, but after that point, the phone never booted again. I have treid flashing everything. I have tried different roms, and odin'ed like everything. Every time, it is the same thing. It would just boot to stock. After leaving it on my desk for around 4 months without ever touching it, now the phone boots to the droid eye animation and then just bootloops there. Sometimes it has audio, other times it does not. I have looked at countless threads and the only answer I can find is that my internal emmc is damaged. When I use adb in recovery, there are 3 partitions listed as there should be, but the format of the last partition is blank. When I try to use parted to format it, the only thing I get is an I/O error. Now I have accepted that the internal memory is corrupted. Is there any way that I can map an external sd card to the internal memory so that I can install a rom on the sd card and boot off of there instead? If not, can the unbrickable mod help me in any way?
Thanks
Related
I have a strange situation going on with my phone and I could use some advice.
My issues started after loading the "official" IMM76D ROM, the rooted and odexed version. Phone would shut off like it was dead after charging all night. Wont boot back up without a battery pull. It would freeze up while the screen was on forcing a battery pull. Basically unusable for more than 10 minutes.
Here is where I might have messed things up. I tried to wipe the phone completely, including the SD card. Factory Reset multiple times, wiped everything multiple times. I even did a repartition of the SD card thinking it would format it further.
Where I'm at now. The phone still boots into the 4.0.4 ROM and I still have CM recovery. But now no matter what I do, factory reset, format/wipe EVERYTHING including the SD card, use fastboot to load a whole new setup, THE PHONE BOOTS RIGHT BACK INTO THE ROM AND SD CARD STILL HAS EVERYTHING. I dont get it.
I have ODIN 1.87 downloaded but it wont see my phone in download mode. I have all the correct drivers loaded including PDAnet, and my phone is correctly detected as Android ADB Device. Interesting side note: fastboot detects the phone, ADB does not. dont know if that means anything.
Sorry for the long winded post but I have been at this for 4 days now and I really need my phone back! Any ideas??
Maybe flash stock rom or CWM recovery from fastboot would solve the partitions issue. I remember when i had my old HTC magic i would sometimes change the partition layout and to reverse it i would have to reflash my recovery.
But as i said, this is all theory and can work or not.
Recently had a issue with this transformer I got from CL, First had aboot looping issue, called asus and they were going to replace it, but I let the battery drain, hooked it up to my laptop and it just started working.
I updated it, downloaded apps, played around with it up to now where I want to use the mircoSD card slot and it's not working, I have 2 and nothing is being detected, Firmware is update, it's pure stock. It gives no indication of trying to read the SD card, I looked for it in Astro and nothing, it cant even try to make the directory.
I've done restarts and such as well
SD Card is formatted to fat32 (both cards)
Any clues?
Bad port or unlucky software flash, I'd say. Try a factory reset, if that doesn't fix you should RMA borked hardware.
Annnnnnd now I am back to being stuck in the boot loop....Godf'n damnit
Alright, so you're totally stock. I'd say you're mostly screwed, can you Cold-Boot android? If so I'd try rooting and putting cwm on there + a rom and kernel to fix issues.
Otherwise, RMA.
It's getting RMA'd regardless but I'm just not sure why the hell it started working last night out of the blue
it's not being detected by adb devices in recovery. I tried cold booting and just stays in boot loop
Yeah, just RMA it at this pt.
So a couple of weeks ago, I flashed Helly Bean on to my phone. It was a pretty clean flash, and my phone worked fine. I was really enjoying the new OS and everything, but then a few days ago, after sending a text message, I set my phone aside and the phone randomly restarted. But for some reason, it went back to the very old Android boot animation (like 2.1), instead of the regular Helly Bean one. I let the phone sit for a few minutes and it just seemed stuck on that screen. So I did a battery pull and restarted, but the same thing happened again. I did a battery, sim, and sd card pull and left them out for about 5 minutes, and restarted again, and got stuck in a bootloop with the white AT&T screen. So, I did a little research and decided that I should go back to flash because that was the only way to get my phone working again. I re-flashed stock and finally got my phone running again. Since I didn't have a way of doing a backup, my phone deleted everything I had (I still have a back up on my PC from when I flashed Helly Bean, so I didn't make much of it). Then, I tried flashing a different CM10 rom on it, ParanoidAndroid. I followed the instructions, and again, clean flash. Then I set up my Google account and let Google Play restore all my apps, the apps installed without any problems. I mounted my phone onto my PC and realized that only my 4gb external SD was showing up, and that I mistook it for my internal SD when I flashed PA. However, all of my apps were installed on the internal SD card, because the external SD wouldn't have enough space on it to store them all. I figured that I flashed the rom wrong and tried to go back to Gingerbread stock and flash it again. I cleared both caches, did a factory reset, and used one of the Odin OneClicks from xda, just like I did before. About 3/4 of the way through the flash, the phone just restarted and got stuck in another bootloop. But this time, I couldn't get back into download mode using any of the button combos, and the phone got bricked. I decided that getting a USB Jig was my only option and prepared to get one. Then, yesterday, I randomly just decided to try turning on my phone again, and it actually started up. It went all the way back to Eclair. And now this time, it doesn't recognize either of my SD cards. And for some reason, I can't turn the phone on unless my external SD card is in it. Also sometimes I can't make/receive calls and I can't send texts either. I tried doing the OTA firmware update, but it just got stuck at 50% and wouldn't update. So I'm not sure what to do at this point because I don't have access to my internal or external SD cards. Anybody have any ideas as to what may have happened and/or how I can fix it? Should I even bother trying to flash GB/ICS/JB again?
TL;DR: Went from ICS to Helly Bean, was working fine until phone randomly reset itself. Went back to GB, tried flashing ParanoidAndroid, but this time, internal SD card not recognized, but all of my apps were installed on it anyway. Tried going back to GB and got bricked. Phone wouldn't go into download mode, so let it be for a day. The next day, the phone did start up again, but it went back to Eclair 2.1, and now my internal or external SD cards are not recognized by the phone.
Maybe your card is mounted to another mount point now? Have you checked fstab?
SlavaBass said:
Maybe your card is mounted to another mount point now? Have you checked fstab?
Click to expand...
Click to collapse
I haven't, I'm not sure how to do that.
Have you tried both of the possible button combos for DL mode vol up+power and vol down + power?
I have a cappy and a vibe both running hellybean and one thing I noticed is the cappy recognizes external as internal and vice versa.
If your phone will boot up without ext SD, try and format the ext sd card.
Did you lose root?
its peanut butter jelly(bean) time
samsgun357 said:
Have you tried both of the possible button combos for DL mode vol up+power and vol down + power?
I have a cappy and a vibe both running hellybean and one thing I noticed is the cappy recognizes external as internal and vice versa.
If your phone will boot up without ext SD, try and format the ext sd card.
Did you lose root?
its peanut butter jelly(bean) time
Click to expand...
Click to collapse
Well my phone is working now. I can use it just as I would normally. I'm just a bit cautious to go back into DL mode because I don't want to completely brick the phone, and I don't have a backup phone to use if it does. As far as the external/internal SD being jumbled up, I wasn't aware others might be experiencing the same problem or if that was a bug in Hellybean; I don't recall it being listed in the bugs. I don't think I've lost root, but I'm thinking I might un-root and re-root it and that might solve the problem. Do you think that would be a good idea? Or should I just let it be?
Sometimes the phone will "reset" at random times. It does not reboot or show the logo or splash screen. It typically starts by the brightness going all the way up, then it just unmounts/remounts my sd card, reads internal and external storage, and will unmount then remount my sim card (I lose signal completely then get signal back). It does it for no reason sometimes a few times in a row. It's acting like I've reset it, but I am not doing anything at all to it.
I have unlocked it so I can use it on T Mobile. I've upgraded the android version to 2.3.6. It is not rooted.
Please help me fix this problem as I like the phone but this problem is really making me angry.
Help please! :victory:
You could try installing a custom ROM and see if that helps.
Sent from my SGH-I997 using xda app-developers app
cgarrod said:
Sometimes the phone will "reset" at random times. It does not reboot or show the logo or splash screen. It typically starts by the brightness going all the way up, then it just unmounts/remounts my sd card, reads internal and external storage, and will unmount then remount my sim card (I lose signal completely then get signal back). It does it for no reason sometimes a few times in a row. It's acting like I've reset it, but I am not doing anything at all to it.
I have unlocked it so I can use it on T Mobile. I've upgraded the android version to 2.3.6. It is not rooted.
Please help me fix this problem as I like the phone but this problem is really making me angry.
Help please! :victory:
Click to expand...
Click to collapse
sounds like there could be some residual on your sdcard. back up your photos and docs.
do a complete reset and complete wipe a few times or odin or heimdall to complete gb stock and reset
unlocked or tmobile shouldn't be an issue. neither should root or no root
if you're trying to determine hardware or software function, complete stock is the best testing ground
Hi,
First I want to say that although I am not a total newbie, I can be considered as a newbie. I have windows 7 32 bit. I am starting from the beginning.
Until about 1.5 years ago, I was used to connect my phone to Kies and do a "firmware upgrade and initialisation" after feeling that it is time to do so in order to speed up the phone back. Does it speed up the phone back? I'm not sure, but as a guy that still formats his pc from time to time maybe it's a habit.
But about 1.5 years ago when Kies told me that my phone is not supported any more I couldn't do that. Then I made some search and found out cm.
I first installed cwm 6.0.4.3 to my phone by heimdall 1.4.0 then installed cm 10.2.0 and gapps-jb-20130813. I thought it would be good and my phone would be faster since I wouldn't have the unnecessary att apps. It also supported Turkish whereas the stock only supports English and Spanish.
I actually liked it at first except for some parts. Then a few months later the phone switched its language to English itself and started to behave abnormally, so I switched back to latest att stock rom by using odin3-v1.85.
Then about 3 months ago my phone got some water inside when I was under the rain with my phone in my pocket and my pocket not being sealed enough. The phone at first said please insert sim card when it was actually inserted, then I noticed it got wet. I immediately turned it off and removed the battery. Then opened it up and let it dry for a few days.
The phone got back to normal except for a single issue. When I charge the battery the screen behaves abnormally. The abnormality increases with time during the charging, I thought it is related with the phone getting warmer during charging. After the phone turns the screen off after timeout, It does not always turn it on after I press the power button. It starts at first by turning on after a few trials up to not being able to turn on during the charging process. When I unplug the charging cable, I can turn the screen on after a few trials. The phone gets back to nearly normal after 10-15 minutes. Although the screen does not turn on it still responds, for example I can answer a call. And sometimes the screen turns on with being upside down and flickering but responding as if its not upside down.
I hope I could describe the problem well. So this may be a hardware or hopefully a software problem. So I decided to first go back to factory settings. The problem with the screen continued. Then I installed the stock rom by odin. The problem continued but I noticed that the two applications I installed after resetting to factory settings remained in the phone. odin either not installs the rom or installs it by copying files, not formatting the system partition. I thought maybe formatting and reinstalling stock would solve the problem with the screen.
I made some research and noticed that I could actually increase the system partition, which is awesome since I always encounter filled memory problem when I try to install an app so I uninstall some apps to install the new ones. If I manage to repartition the system drive, it also has to format it.
Then I installed the stock rom using the pit file someone uploaded (6GB system partition), I did it but got an error from cwm upon first boot saying something like "unable to mount F", when I ignored the error the phone seemed to turn on but got stuck with att sign. When I pull the battery and turn it back on the phone got stuck at the same place without an error from cwm. Then I installed the stock rom with the original pit file, now the phone turns on but I still have previous apps. I repeated thes a few times (6gb pit file, original pit file) but nothing changed.
Then cm came to my mind, it would format the system drive. I repeated the same procedure I did 1.5 years ago. The phone turned on. I noticed that the internal sd drive had the previous folders,so I wiped the sd drive with cm. Everything was fine but the problem with the screen continued which stated that the it was a hardware problem. There was no reason to stay with cm so I installed the stock rom.
The phone asked a password from me since it had encrypted folders ???. I didn't provide a password, I think it did not recognise the sd drive wiped by cm.
I couldn't install cwm 6.0.4.3 with heimdall, it gave an error at the end. I decided to install a recovery with odin so I installed twrp 2.8.7.0.
I installed cm with 6gb pit, with original pit, installed stock rom with 6gb pit, with original pit with random order and how many times I don't remember that I brought the phone to a state that it won't boot. It turned on with odin mode though. Even the twrp did not recognise the drives. So I wiped all with ext4 format.
Now I have cm with 6 gb system but I want to go back to stock rom. cm drains up my battery. I also noticed that I really got used to the stock rom. I would appreciate it if I have 6 gb system like now. But if I have to reduce it back to 2 gb I don't care.
Can someone please help me?
Sorry for the long post, I wanted to state the problem as good as possible.
Not getting even a single reply probably means I am facing a really extraordinary problem.
I'll try to reformat the partitions. Maybe the OS thinks the unrecognised partition as encrypted. I previously made them both FAT.
Can someone please tell me what should be the filesystems of the system and the internal sd? Are they the same or different?
bloodcurdler said:
Not getting even a single reply probably means I am facing a really extraordinary problem.
I'll try to reformat the partitions. Maybe the OS thinks the unrecognised partition as encrypted. I previously made them both FAT.
Can someone please tell me what should be the filesystems of the system and the internal sd? Are they the same or different?
Click to expand...
Click to collapse
I could be wrong but Ext4 is the most common filesystem so try that