yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
Preliminary results from using e2fsck

#[B][COLOR="Blue"]e2fsck[/COLOR][/B]
e2fsck
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
#[B][COLOR="blue"]e2fsck /dev/block/mmcblk0[/COLOR][/B]
e2fsck /dev/block/mmcblk0
e2fsck 1.41.12 (17-May-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0
Filesystem mounted or opened exclusively by another program?
#[B][COLOR="blue"]e2fsck -p /dev/block/mmcblk0[/COLOR][/B]
e2fsck -p /dev/block/mmcblk0
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0
Filesystem mounted or opened exclusively by another program?
#
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
You can't run a filesystem check on a device level as there's no partition data there. To check /data or /cache you need to run:

e2fsck /dev/block/mmcblk0p1 for /data and

e2fsck /dev/block/mmcblk0p2 for /cache

Try to add -f to the list to force check such as e2fsck -pf /dev/block/mmcblk0p1

Edit:

I don't know if you'll be able to check /cache if it's mounted. What do you get from adb shell in recovery when you type umount /cache or try to unmount it from the recovery options?

Anyways, you should be able to run mkfs even with the partition being dirty.

I just thought of something. What if you type:

parted /dev/block/mmcblk0

then

rm 1 to delete the first partition?

Then rebuild the partition with mkpartfs primary ext2 8192B 797MB

Then exit out of parted with quit.

Then convert to ext3 with mke2fs -j /dev/block/mmcblk0p1

This process will wipe /data.

I tested this with partition 2 with a similar command.

If the phone still bootloops, do the following:

parted /dev/block/mmcblk0

rm 2

mkpartfs primary ext2 797MB 1007MB

mke2fs -j /dev/block/mmcblk0p2

The above steps will wipe /cache.

Hopefully you should be able to mount and unmount /cache after rebooting recovery.
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
My results :eek:
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Do a print from parted and tell me what you get.
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
Same results :silly:

C:\Program Files (x86)\Android\android-sdk\platform-tools\DINC>adb shell
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext4
2 797MB 1007MB 210MB primary ext3
3 1007MB 7944MB 6937MB primary fat32 lba
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Did you try the ruu from cmlusco? Also theres a link someone gave for fixing their partition issues.

Edit: here is a detailed guide and the one I'm talking about. I'm sure you're up to trying anything.

http://blog.swiftpassage.com/2013/02/03/htc-incredible-jelly-bean-nearly-bricked/
[Droid Incredible Q&A, Help & Troubleshooting] CalvinAMi:
I didn't see any particular RUU posted by Cmlusco. I have run the stock RUU for Froyo & Gingerbread multiple time. No dice.

Also, that blog went through the same stuff i have tired. Result = /cache & /data are still mounted and not available to alter.

I did find an old back (stock+) for this phone. When I try to restore the backup I get:

Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
Error while formatting /data!

I am at my wits-end with this thing.

Shame the stock RUU can't remove the partitions entirely and recreate them.

Oh well. It might be time to just put this old Dinc on the shelf. :crying:
[Droid Incredible Q&A, Help & Troubleshooting] GnatGoSplat:
Did you ever fix this?

I think I am having a very similar problem. I had originally flashed convert2ext4_no_data_limit_normal_dalvik.zip on stock ROM a long time ago.

I have /cache, but no /data. It was the opposite earlier.
[Sprint HTC EVO 4G LTE] Lonewuhf:
I'm not sure what's causing this. It seems to have started when I first rooted the phone. Voice recognition isn't working. When I try to use google search the circle around the microphone icon will move, but the icon doesn't turn red as it does when it recognizes voice. If I cup my hands around the microphone on the phone and pretty much yell, sometimes I can get it to work. Other times I can't. Tried another test, downloaded a voice recording app and when I recorded, I could hear my voice but it was INCREDIBLY quiet. I couldn't make out what I was saying at full volume. I have had no complaints about my voice when on phone calls. Does anyone have any idea what this is, or what a fix would be? I'm rooted currently, have tried multiple different roms with the same outcome. Am I just missing a setting somewhere?
[Huawei Ideos X6] drmanishtaneja:
hi my spice mi 410 touchscree behaves weirdly like pseudo touches everytime i install a new rom it goes away but after sum days it comes back searched forum but cudnt find anything reasonable tried almost all roms including stock plz help
[Huawei Ideos X6] reversegear:
yes the phantom touches are weird behaviour of all roms including stock ones

temporary solutions

sol 1 : lock and unlock the phone with power button (risk of power button life)

if you are in ics, enable show touches in settings>>development. with this ull know where the touches happening.(little battery consuming)

sol 2 : when u find pseudo touches happening,with two fingers swipe across the screen.(since Max touch points are 2 the device forgets the pseudo touch)
[Nexus 4 General] Censura_Umbra:
Just ordered two.

Sorry if this gets closed but seemed relevant and important due to recent back orders.
[Nexus 4 General] Manoboy:
Re: Nexus 4 back in stock!

How many days is delivery?
[Nexus 4 General] neo6776:
Not in the UK they aren't!!
[Nexus 4 General] justinangil:
1-2 weeks
[Nexus 4 General] natedroid:
I think it will be in stock in 1-2 weeks, then 2 day delivery after that. Google charged me $13.99 for 2 day shipping on my order.
[Nexus 4 General] Manoboy:
What model did you buy?
[Nexus 4 General] big gulps huh?:
I ordered the 16gb version at 10:25am Mountain Time. They quoted me 1-2 weeks shipping with an estimated shipping date of February 13th. FINALLY able to order one. I almost dropped twice the money on a Note 2 because I was tired of waiting.
[Nexus 4 General] Censura_Umbra:
I bought two. My wife didn't answer quick enough if she wanted one, so a bought two. Will cancel or sell the second one if she wants something else
[Nexus 4 General] mclain1:
woot woot... just ordered my 16 Gigger...!
[Nexus 4 General] crachel:
Nexus 4 Back in US Play Store

Closed
[HTC Wildfire S] icu64:
MIUI

INTRO

This is a port of MIUI 2.10.26. i have tried my best to make this a clean MIUI rom. For the list of changes look around on on miuiandroid.com

BUGS

-those in cm10

-you tell me

DOWNLOADS:

ICS

1/29/2013 http://www.mediafire.com/download.php?y48jrsqa435w8rp

2/5/2013 http://www.mediafire.com/?deesx31por2rurb

JB

5/11/13 http://www.mediafire.com/?xadra4re7rt79s7

CHANGE LOG

1/29/2013

-test rom

2/5/2013

-cleaned things up

-removed cpu settings script

-new boot screen

5/11/13

FIRST JB PORT

*I recommend flasing this kernel after the ROM* http://xdaforums.com/showthread.php?t=2010083
[HTC Wildfire S] icu64:
will be updating this thread and rom tomorrow
[HTC Wildfire S] pensador1:
Re: [ROM][Marvelc][MIUI]

This is. the same as Henry's rom?
[HTC Wildfire S] icu64:
Re: [ROM][Marvelc][MIUI]

Not! Lol this one is more up to date with less bugs
[HTC Wildfire S] demi_fiend:
Re: [ROM][Marvelc][MIUI]

Do you have that mms issue I mentioned earlier with other cdma carriers?
[HTC Wildfire S] pensador1:
Re: [ROM][Marvelc][MIUI]

GPS work on this room?
[HTC Wildfire S] icu64:
i wouldnt know because my phone is out of service lol. need a metroPCS user to test. SN: can you help me make a better post?
[HTC Wildfire S] icu64:
Re: [ROM][Marvelc][MIUI] UPDATE 2/5/2013

Of course not. Its based off of cm9
[HTC Wildfire S] pensador1:
Re: [ROM][Marvelc][MIUI][UPDATE 2/5/2013]

Thank-you man
[HTC Wildfire S] icu64:
welcome, sorry it doesnt work :/
[HTC Wildfire S] Tarrnation:
Finally had some spare time last night to test out this ROM. Installed fine and runs smooth. The theme selection and the ability to mix and match portions of several different themes to create a custom theme really makes this ROM shine. Many of the themes are designed for an Asian market but they are still pretty cool nonetheless. One of my favorite features of this ROM is the ability mass-kill recent apps from the popup menu when you hold down the home button.

As far as bugs go, the only one I've found so far that's not already mentioned in this thread is broken video playback (no surprise there though). I really hope to see this ROM get updated to a newer version. I'm sticking to BlackBean for the time being but this is a nice toy to play around with for sure! :cool:
[HTC Wildfire S] icu64:
so i got miui jb to work.... will post after testing :)
[HTC Wildfire S] demi_fiend:
Good job dude. It's crazy how far this device has come...gonna try and get mine on so I can try it out when you upload.
[HTC Wildfire S] icu64:
Its up
[HTC Wildfire S] nysokheng:
It's only for Marvel C ? Marvel is incompatible? Really want to test this on my marvel.
[HTC Wildfire S] icu64:
there is another thread by another dev for the marvel version of this rom :)
[HTC Wildfire S] nysokheng:
Ok. I found it, but that was a little bit old. so need to wait for the update. thx.
[Nexus 4 Q&A, Help & Troubleshooting] Goog1e Phone:
What's the best method for removing clockwork recovery for twrp? I've heard twrp is better than the outdated clockwork recovery. Any help would be appreciated. Thanks.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] CMNein:
You don't remove the old recovery, you just flash a new recovery image. Do it via fastboot, or using the Goo Manager app (in the case of TWRP).
[Nexus 4 Q&A, Help & Troubleshooting] ksavai:
yes TWRP is definitely user friendly never looked back. Just flash it over that .img file.

Easiest way to do it download goo manager from playstore and apply it from there.
[Nexus 4 Q&A, Help & Troubleshooting] lyall29:
Just do it! You won't regret it. :)
[HTC One X] Arcaneex:
I've broken my screen, to be accurate not me but some dude, he paid for the new screen. Ofcourse, he picked the most ****ty store he could to fix it to pay less money for it, it was horrible. Light from the side of the phone was leaking, the buttons didn't light up well, the front camera lense was missing and most importantly the screen itself wasn't like before. First of all, it fell off from the phone all the time ( with just the two connectors connected ), it was horrible pale and etc.

Being the social akward I am, I was silent about it, and got used to the screen after I glued it.

Anywho, yesterday without any warning or anything screen stopped working. Sound is playing, digitizer is prolly working, screen? nah. Black screen. I opened it up few times before as the LCD connector disconnected, it was okay. Now the connector was inside still, connected and I opened it and tried to tighten it up, thought it was loose or something. Nope, still no screen.

Now I come to you, xda, with the need of help.

Where can I buy a REAL. LCD2, like stock screen?

And if its possible, how can I identify if the screen I got earlier IS lcd2 original screen? ( the seller said it was, obviously it wasn't )

Thanks! ( Really hope for fast answer )
[HTC One X] sandm4n:
http://xdaforums.com/showpost.php?p=26408110&postcount=3799
[Sony Xperia P, U, Sola, Go] angus1996:
Hi everybody!

I installed the rom and it's really great,

except the font, which reminds me of Samsung's first touch smartphones.

I searched a bit in the forum and I think the best way to change font with CM9 could be via console,

but I can't find it on the current ROM, maybe it's not included...

How do I get the terminal? IS changing the font by deleting and replacing the font folder in /system SAFE?

Thanks

Angus :)
[Sony Xperia P, U, Sola, Go] psyionx:
Have you tried font installer *ROOT* found in market?
[Sony Xperia P, U, Sola, Go] angus1996:
In the forum using apps was discouraged because they could be incompatible with CM9.

Anyway thanks for the answer I'm gonna find out myself if those apps work :)

Finally I got an efficient and easy to use solution: http://xdaforums.com/showthread.php?t=1959019
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
My SG3 replacement is only days old after a long battle with the old one. I thought a new phone would be the end of this but it too is doing the exact same thing with one new wrinkle. I will outline the symptoms and hope someone can help me out.

The problem is the phone will lose the ability to send or receive sms messages nor can the phone receive phone calls. The only way to restore the phone to working order was/is to reboot. I only become aware of the situation when family members would email me asking why I am not answering them. The phone always appeared normal to me, had bars of service etc. Only while waiting on a replacement phone from AT&T did I discover by accident that if I tried to make an outgoing call, 90% of the time would also fix the condition.

In my many call sessions with AT&T, I went through all the steps you would expect. New SIM card, made sure I was upgraded to 4.1.1 Jelly Bean, reset, they said they checked to make sure phone was provisioned correctly etc. Finally they said they would send me the warranty replacement.

The new fone came and for two days worked perfectly but I noticed it was running ICS so I upgraded to JB. The symptoms returned the same day. This could be coincidence or not as the old phone would sometimes go for days without an issue. Are the problems from JB or from an app I am running?

That one new wrinkle I mentioned is that in the middle of last night, the phone rebooted on it's own.

I have since deleted most apps on the phone trying to see if this is the cause. Only a dialer app is left on the phone and that too will go if the issue reoccurs. (EDIT: Also am still running Apex launcher)

My questions:

Is it possible an app intermittently can cause a phone to lose sms and incoming call ability?

Could the upgrade of JB be the cause by itself or an incompatibility between an app and JB?

If this reoccurs, do you see any merit in a reset with zero apps brought back?

Any other suggestions are most welcomed.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
I would try flashing another ROM. Something de-bloated, or if you dont need the Samsung stuff use AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
It is possible that it's coming from a app that you have/had. Knowing which one though is hard and can only be tested by you (often uncommon apps).

I highly doubt it's from the upgrade to JB as more people would complain about this.

Usually, problem like this comes from either a bad SIM or on the carrier's side. Could be good to check your APNs as well (make sure they match your carrier's).

As for the phone rebooting, what exactly happened?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
I will check the APN's, never did that before.

The rebooting is new. The phone was over 50% battery power and as usual, sat on a table along side my bed. 1:12am, I woke up to the AT&T tones you hear when it reboots and phone was lit and just finishing up rebooting. Hasn't done it since. So far today, the phone has lost sms/call ability once and the rest of the apps save Apex and Dialer1 were removed, all widgets etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
All my APN settings are grayed out and I cannot change any of them so I thought I would post pics of same hoping they are correct.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Odd that you can't change them, althought, haven't been on stock in a very long time so dunno if they allow it.

They did make you do a factory reset in recovery right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
No, they had me to do it from an internal menu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar.ioo:
You said while running ICS you didn't encounter with that problem, run ICS for a couple more days to see if JB is your problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
On this new phone which came with ICS, I had only ran that for two days before upgrading to JB which I am currently running. How do I go back to ICS?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Know that this will make your phone like it was out of the box (data wise), therefor, you will lose your apps, texts, call logs and such. A backup is suggested before going through with this, which can be done in recovery as well (called nandroid, under backup).

Recovery mode: Hold vol up+home+power button until you see the recovery screen. There will be a factory reset option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar.ioo:
Flash through ODIN a Stock ICS ROM or another option is try to find an ICS ROM in the development thread/original development.

Tip: I always make a stock backup through recovery as soon as I root my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
stock firmware: http://xdaforums.com/showthread.php?t=1968625
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
Thanks for the help guys! The phone has not had any issues since yesterday morning when I deleted all widgets and almost all apps. This is hardly definitive as it has fooled me in the past but another couple days will tell. If not, I will have to put your suggestions into play.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mty msi:
Last Wednesday I became aware that some incoming calls were receiving error messages (typically "the phone call can not be completed at this time" and not able to ring my phone. I have tried to call my S3 and received the error messages about 6 times on different days as have several callers. There are at least 3 different error messages one in English only with no error codes, one in English/Spanish with the error codes MI01ML & MI01EE or GE and one in English/Spanish with the error codes MI01GL & MI01EE.

At least 8 calls to AT&T tech support have resulted in different completely answers and no resolution. I was told today by an individual at the Costco wireless kiosk where I purchased the S3 that a friend of hers with an S3 has the same problem and her friend's husband knew someone at AT&T who told him this issue is a known problem and is caused by a mistake AT&T made in the programming and that it will take 1-2 months to resolve. Further, AT&T will not admit there is a problem and the level of tech support we can reach as consumers have not been made aware of the issue. This would explain why every time I called I got completely different responses and no resolution. The problem is only with S3's, no other phone AT&T uses.

My cellphone is my main business line thus I can not afford the luxury of having potential clients and current clients unable to call me on an intermittent basis for the next 1-2 months. Fortunately I bought my S3 on Black Friday and Costco has a 90 day exchange policy so I am picking up a new LG Optimus G today because the $20 I will have to pay to upgrade to it is a sale price that ends today.

There is a possibility rooting the S3 may resolve the issue and I spoke with a very technically savvy individual who also works at the Costco kiosk who offered to root my phone but said he could not guarantee it would resolve the issue. Thus I have no choice but to get the LG and I would much prefer keeping the S3 because I spent 35+ hours finding a case/holster combo that allows outward screen placement in the holster (BodyGlove ToughSuit) and probably won't be able to find one for the LG (BodyGlove doesn't offer the ToughSuit for the Optimus G).

I've spent at least 10 hours trying to resolve this issue and am really disappointed that I can't keep my S3 but I must have a phone that receives incoming calls so the LG is my resolution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
Question, did it ever effect text messages to your phone, both outgoing and incoming? This sounds like what I have concluded also. Thank you for the info. My phone failed yesterday afternoon again and I was going to do a factory reset from recovery but am pondering root/rom to see if that might be a better solution. My only worry is that if the phone also fails with a rom, I will have issues going back to AT&T for help with the boot counter thing (not sure exactly what is called) but they will know the phone was rooted/rommed.

The customer service techs are no help as you mention, they just put you through steps from a trouble shooting book. I dred having to call/deal with them again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
Just did the reset from recovery mode as you list above and did not restore or bring back ANY apps but I suspect this is not going to be the solution. Next step will be to try a rom I guess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s60convert:
Ok long phone call with AT&T yesterday afternoon after yet another failure. At first, the guy wanted to put me through the usual diagnostic hoops but I stopped him and told him to just listen to what's been done and what the symptoms are. After a while he stopped me and said he knew exactly what the issue is and will fix it for me right now! Now I do not know what all the terms he threw at me mean but I will list them here for reference. I told him that the phone was reset yesterday morning and zero apps were installed so it had to be a network issue or something wrong with my account. He told me there were "routing number mismatches" and my "LRN" was incorrect. Also said they had me on the wrong network and moved me to the Cingular wireless network. Don't know where I was previously. He also mentioned that the SOA was updated with LRN to the proper SPID. I was told the changes could happen immediately but for sure within 24 hours. No failure yet but this phone has fooled me before and gone for a couple days without failing.

One thing I didn't think was related is that I talk with my wife a lot during her long work commutes and we are constantly loosing the ability to hear one another. There are periods of silence then it pops back in. This literally happens in every call we have and we attributed it to either a tower issue or her car's Bluetooth etc but since the tech made these changes, not one call issue in the three conversations we have had. Also it seems that text messages are received and send instantly unlike they used to sit for a bit before going. Hmmmm.

I hope I do not have to post in the next couple days that the phone has failed again, it is really getting to me.
[AT&T Samsung Galaxy Note II] LordOfSin:
Could a ps2 emulator be possible on the Galaxy Note 2? if not could someone help me understand why because I know that the Galaxy Note 2 has a 1.6 quad core processor but I don't know what that compares to a ps2 processor I tried looking it up but I don't understand what they said really 300mhz seems really low dose not comput
[AT&T Samsung Galaxy Note II] mrevankyle:
No there is no PS2 emulator mainly because of the complexity of the system you would need to emulate and not the raw power needed to run the games