Database Info

[Q] Device hangs and cannot format /data

Hi,
Today during a call my Inspire 4G froze with no apparent reason. I rebooted and I always had freezes, so I decided to do a factory reset.
I'm rooted and have Virtuous Unity 1.24 installed (never upgraded because it had been working fine).
When I try to format /data it hangs for a while and I get an error saying "error formatting data".
I'm just downloading latest version of the ROM hoping this way it'll get fixed.
Just before messing more with the phone, has anyone had this experience with the Inspire 4G?
Regards

Try doing a full wipe/factory reset in recovery, if same error, your sd card could be trashed. There's a recall on some newer sd cards that came with inspire. Google it.
Sent from my Inspire 4G using Tapatalk

Well,
Now it won't even reboot into recovery. I only can boot into HTC white screen, but clockwork died, seven vibrations when I try to go into recovery.
Now I'm trapped, tried installing PD98IMG.zip that comes with the rooting files, seems to install well but doesn't work.
Any other suggestions before I assume my Inspire died?

Take out your SD card. Then trybooting Into recovery. Once in recovery you can insert SD card. Wipe and flash. I saw that this worked for a couple of people in another thread somewhere
no hay de queso no mas de papa

No luck, just 7 vibrations when I go into recovery, with and without SD card, even tried without SIM card which should not have anything to do...

I had the same error with motorola atrix. I have flashed the firmware again to resolve this issue
Sent from my MB860 using XDA App

Maybe try a different pd98 or maybe the ruu.
no hay de queso no mas de papa

Tried with the RUU but it cannot detect the phone, will see if I can do something else, just strange thing, never had this kind of issue with any Android Phone...
Is there a way to extract the PD86IMG.zip file from the RUU?
Well, after alot of trying out, I'm pretty sure the device is hard-bricked due to some HW problem, will still do some attempts to recover the phone, but it is strange:
1. It worked great a few days ago, I installed no updates, radios or anything other than Market apps.
2. In the last days, I've had some random hangs on the phone, just pulled battery and rebooted.
3. Today it hanged during a phone call, pulled battery and every time I rebooted it would just hang again.
4. Went into CWM Recovery, was able to ADB and everything, but any attempt to format /data or /cache would cause an error.
5. After playing around with CWM, suddenly I wasn't able to see the menus anymore, when I rebooted, any attempt to go into recovery from the HBOOT screen would result in seven short vibrations, a wile after that screen would go black.
6. Downloaded various PD86IMG.zip files, all of them install and give no errors, but the phone always keeps sending those 7 vibrations when trying to boot or go into recovery. HBOOT screen still works, any PD86IMG.zip file apparently installs fine (no errors), but when I reboot it is dead.
I am thinking that something bad happened to the internal storage, the symptoms show in that direction and I can't find any post that seems a bit related to this issue. This might be my 6th or 7th Android phone and I often root other phones for friends, in fact I have rooted 4 or 5 Inspires and have had no issues.
I just want to see if there's anything else I can do...
Thanks and regards...

Have seen the 7 vibrate occurrance mentioned a few times. It is hardware related and there is not much you can do about it. Sounds like the solder connections between the processor and the motherboard are separating. By chance has the phone been real hot in the recent past?

Real hot not, but I dropped it once a few weeks ago, I was really surprised that nothing broke, it was not a nice drop...
Well, will see how much I get for the phone listing it as "for parts"...

[Q] NS4G is possesed

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.

Captivate not recognizing either internal or external SD cards

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?

[Q] Nexus S (wind mobile) can't factory reset! (jellybean)

Hi, first post here.
So I bought a Nexus S that was rooted and updated to Jellybean. It's an unlocked phone originally locked to Wind Mobile.
So it's been having issues with getting stuck on the google logo after reboot, so I decided to sell it. Problem is when I go to factory reset the phone it shows the reset bar but then that turns into a big triangle with an exclamation mark on it with a little android guy next to it. The phone gets stuck there. All I can do from there is remove the battery.
From there I tried going on bootloader using power and volume up (says unlocked btw), and from there I load recovery. On recovery there is an option to factory reset and I click on there, however it doesn't do it. This is what I says:
"--wiping data...
formatting /data...
E:format_volume: make_extf4fs failed on /dev/blo/ck/platform/s3c-sdhci.0/by-name/userdata
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/ .android_secure!
Skipping format...
Data wipe complete."
So I think the error might be accociated to the sd card because the Nexus S doesn't come with an sd card, it has built in memory? Also on recory when choose "mount sd card" it says"Error mounting /sdcard!".
So how do I go about fixing my problematic phone? I have a dude that wants to buy it but I can't even reset the damn thing, let alone fix the freezing at start up issue. I am also totally new to this.
Extra info: When the phone freezes at the google logo at start up I get passed that by using a blow dryer on the phone. That's the only way I start up the phone after the battery comes out. This is the gt-i9020t model.

Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!

gunner49 said:
Are you using a custom recovery? If not, that might be the reason your phone is behaving like that as I had the same issue like yours when I first started flashing things!
Click to expand...
Click to collapse
I don't know if it's a custom recovery because the previous owner installed everything/rooted.
When I press power and vol. up, It looks identical to the uploaded picture's bootloader/recovery.

Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.

gunner49 said:
Its a custom recovery (Clockworkmod) ok. I'm not familiar with it but there should be a setting somewhere - maybe in "advanced" - where you have the option of restoring default settings for the recovery. Do that and then try doing factory reset again.
Click to expand...
Click to collapse
In advanced there is no option that worked.

*Solution*
Ok so for those having this problem this is what I dug up:
Internal SD card error causes the boot freeze/factory reset error. When you try mounting SD card it fails, this is also what makes me think it's a fault with the phone's internal SD card.
I do not know how to "fix" this fault, however I'll tell you what I did to get passed this issue.
1) Heating up the phone helps bypass the frozen screen. On Boot it goes to the google logo and freezes, but you can get passed this by heating up the phone (using a blow dryer) before hand and it's relatively successful.
2) I believe that before factory resetting the phone (whether using recovery or the actual reset option on settings), if you heat up the phone, it might work the same way it works when booting up.
I did not try 2) because I managed to "reset" my phone manually by uninstalling all apps, deleting all files/cache/photo's/accounts, and by clearing all app data. This works just as fine if you ask me.
Overall this solution has not been "fixed", I encourage people to find a real fix, but for now using the blow dryer and manually resetting is one way around the problem.

Help needed to install the stock rom back

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