-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Is my phone dead? (single tear...)
- Thread starter The_Horak
- Start date
-
- Tags
- htc droid incredible
iowabowtech
root@android:/ #
Yeah when it shows the file size like that you're good. Without being mounted, you were effectively in read only mode. Now you can write.
Cool, I'm making progress!!! Currently fixing the partitions through adb shell...
Wait! Is this right? It says "parted: invalid token: ext2"
I'm gonna wait a couple minutes. If no one replies, I'm going for it.
Wait! Is this right? It says "parted: invalid token: ext2"
Code:
/sbin # parted /dev/block/mmcblk0 mkfs ext2
parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
[B][I]parted: invalid token: ext2[/I][/B]
Yes/No?I'm gonna wait a couple minutes. If no one replies, I'm going for it.
iowabowtech
root@android:/ #
Don't know. This is where I ended up with the last guy that i worked with on this and he either decided not to proceed or he did and i never heard the result.
uhh....
Can I run chmod 0755 on the 6 files again?
Code:
~ # parted /dev/block/mmcblk0 mkfs ext2
parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]? ext2
ext2
ext2
[B][I][U]Error: File system was not cleanly unmounted! You should run e2fsck. Modifying
an unclean file system could cause severe corruption.
Ignore/Cancel?[/U][/I][/B]Can I run chmod 0755 on the 6 files again?
iowabowtech
root@android:/ #
Actually THAT is the point he ended up at. So again, idk. What i do know is i went through this procedure many months ago with another user and it fixed a near brick BUT I don't recall any of these errors and warnings. Honestly I don't have a great feeling about it and I cant put my finger on what is causing this to happen to several phones recently. Seems like possibly a function of the formatting multiple partitions from the cwm menu is about the only common thread. And im not even positive of that link. I will try to contact the guy quick and see what happened if/when he pushed ahead at this point.
No, don't worry about it. I'm gonna cancel, run chmod 0755 again, and see from there. I never, EVER, formatted partitions in Mounts and Storage before, but the tread said to. I figured, 'Huh... never thought about that." Figures... I wonder if it was my process. I never really know what to flash first, when to boot up before flashing again, and when not to.
iowabowtech
root@android:/ #
Good luck. We had the same results after repeated efforts. Also, you may find that you have to re-push the binaries (maybe). We then moved onto this:
Error formatting /data when restoring - CyanogenMod Forum
And we got the exact same results as the OP, no real solution in the end. Which leads me to believe that the partitions aren't just formatted incorrectly, but they are corrupt in some way. However, as mentioned earlier, a diagnostic check on the partition(s) shows perfect operating order. Makes no sense and one of the most PIA situations I've run across in the history of this phone. And now it's happened to at least 3 people that I've seen in the last few weeks.
Well, my give up... my give up.
I feel like this is a whole other process just to find out that I have bad hardware. I may mess with it a bit more tonight, though. I just want to say THANK YOU to everyone who helped me out!! Maybe we didn't fix my baby, but we gave it a fighter's shot. I learned a lot from this, and really look forward to my next phone's critical failure so that I can learn even more, haha!
Special Shout Outs:
-Scotty85!!!
-sdrawkcab25!!!
-iowabowtech!!!
BTW, I ended up using someone else's upgrade and grabbed myself an Incredible 2. All the new phones are too much for me, and apparently the batteries, too. Instantly noticed an increase in phone speed, got the highest speedtest.net score yet (1420 kbps DL/817 kbps UL), and still had a phone that feels familiar. It's all of the Original, with some nice improvements all the way around (like battery life).
Code:
[B][I][U]Error: File system was not cleanly unmounted! You should run e2fsck. Modifying[/U][/I][/B]
an unclean file system could cause severe corruption.
[B][I][U]Ignore/Cancel? ignore[/U][/I][/B]
ignore
ignore
[B][I][U]Error: File system has an incompatible feature enabled. Compatible features are
has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.
[/U][/I][/B]
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
/sbin #I feel like this is a whole other process just to find out that I have bad hardware. I may mess with it a bit more tonight, though. I just want to say THANK YOU to everyone who helped me out!! Maybe we didn't fix my baby, but we gave it a fighter's shot. I learned a lot from this, and really look forward to my next phone's critical failure so that I can learn even more, haha!
Special Shout Outs:
-Scotty85!!!
-sdrawkcab25!!!
-iowabowtech!!!
BTW, I ended up using someone else's upgrade and grabbed myself an Incredible 2. All the new phones are too much for me, and apparently the batteries, too. Instantly noticed an increase in phone speed, got the highest speedtest.net score yet (1420 kbps DL/817 kbps UL), and still had a phone that feels familiar. It's all of the Original, with some nice improvements all the way around (like battery life).
scotty85
Extreme Android User
i wouldnt give up just yet 
it may be worthwhile to download the newest version from the link it gave,then start the process over. delete all the old files from your tools folder,and put the ones from the new download in place of them.
run thru the commands again,and if you get the same "Error: File system was not cleanly unmounted! You should run e2fsck. Modifying an unclean file system could cause severe corruption" error,then try running e2fsck:
e2fsck /dev/block/mmcblk0 mkfs ext2
and see what happens definately nothin to lose if you got a new phone 
it may be worthwhile to download the newest version from the link it gave,then start the process over. delete all the old files from your tools folder,and put the ones from the new download in place of them. run thru the commands again,and if you get the same "Error: File system was not cleanly unmounted! You should run e2fsck. Modifying an unclean file system could cause severe corruption" error,then try running e2fsck:
e2fsck /dev/block/mmcblk0 mkfs ext2
and see what happens
definately nothin to lose if you got a new phone I know, I know, I'm pathetic... I agree with you, but I do not know what I'm looking at when I paste that link in Crome's address bar. Can you tell me which file to download? Also:
-1) When you say to erase the files in tools, you mean just those 6 key files I keep using, right?
-2) When I run e2fsck, I get this:
Code:
~ # e2fsck /dev/block/mmcblk0 mkfs ext2
e2fsck /dev/block/mmcblk0 mkfs ext2
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-3) how do I run tunefs and debugfs? what command do I type?
scotty85
Extreme Android User
I know, I know, I'm pathetic... I agree with you, but I do not know what I'm looking at when I paste that link in Crome's address bar. Can you tell me which file to download?
the newest looks tobe all the way at the bottom of that list. heres the direct link: http://ftp.gnu.org/gnu/parted/parted-3.0.tar.xz.sig
Also:
-1) When you say to erase the files in tools, you mean just those 6 key files I keep using, right?
correct
-2) When I run e2fsck, I get this:
Is that correct? What do I do with that?Code:~ # e2fsck /dev/block/mmcblk0 mkfs ext2 e2fsck /dev/block/mmcblk0 mkfs ext2 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
is it waiting for an input? if so you could try -p,and see if it automatically fixes things. if it just wants a command,it may want the -p at the end. example: e2fsck /dev/block/mmcblk0 mkfs ext2 -p or maybe e2fsck /dev/block/mmcblk0 -p
-3) how do I run tunefs and debugfs? what command do I type?
try just changing out the front part: tunefs /dev/block/mmcblk0 mkfs ext2 or debugfs /dev/block/mmcblk0 mkfs ext2
sorry i can be a lil more helpful about the operation of parted. dont feel you have to rush thru this right now,we can always try and research a lil more and try again later.
iowabowtech
root@android:/ #
I believe you want to insert the paramater after the e2fsck something like this:
e2fsck -p /dev/block/mmcblk0p1
Multiple parameters can also be used so if you wanted to force check and make no changes to filesystem you might run:
e2fsck -fn /dev/block/mmcblk0p1
I don't really know what to suggest for sure, I guess auto fix sounds like a good start so the -p is what I might start with but I'm no expert either. Chances are, it's going to give you a warning if it sees something it doesn't like. Also, I'm not 100% sure about the ending of the command. I'm going with /mmcblk0p1 since it's my belief that is the /data partition and the one most likely to be causing the problem.
Also a little tip. While in recovery, check the mounts/storage and make sure /data is not mounted while performing this. It should be the case by default but no sense in taking chances since that may end poorly. I REALLY like Stotty's idea of loading up the new Parted and the binaries it provides. It may even output different results and negate the need for the additional commands, never know.
e2fsck -p /dev/block/mmcblk0p1
Multiple parameters can also be used so if you wanted to force check and make no changes to filesystem you might run:
e2fsck -fn /dev/block/mmcblk0p1
I don't really know what to suggest for sure, I guess auto fix sounds like a good start so the -p is what I might start with but I'm no expert either. Chances are, it's going to give you a warning if it sees something it doesn't like. Also, I'm not 100% sure about the ending of the command. I'm going with /mmcblk0p1 since it's my belief that is the /data partition and the one most likely to be causing the problem.
Also a little tip. While in recovery, check the mounts/storage and make sure /data is not mounted while performing this. It should be the case by default but no sense in taking chances since that may end poorly. I REALLY like Stotty's idea of loading up the new Parted and the binaries it provides. It may even output different results and negate the need for the additional commands, never know.
Hey everyone. I know this has been a dead thread for almost a month now, but I was looking at my poor, dead, dusty Incredible yesterday thinking, "you deserve better than this." I'm gonna give this more effort. I just would like to say that the Incredible 2 community is nothing like this one. I miss all you guys...
-I just thought I'd check, has this become a more common problem since my phone died? Is there a known cause?
-I just thought I'd check, has this become a more common problem since my phone died? Is there a known cause?
iowabowtech
root@android:/ #
I haven't been around as much lately but I haven't seen much about it since your thread.
sry for my crappy english...
Mine is acting the same way, used several different ROM`s, Darky Ress Edition, EZBase, XXJVU, XXJPU, Heimdall, XXJPC, XXJVS, tried using ADB but the eMMC don't remove my partitions so i can create them manually and it does'nt accept /dev/block/mmcblk0 mkfs ext2 either.
Almost giving it up... Oh yes, i can enter recovery mode and download mode, change kernels, but it does'nt pass though the Galaxy S logo. Through all this testing, i'm almost sure the problem is with /data. It seems like my internal memory became read-only.
I live in Brazil and my sister bought this Galaxy I9000 in USA. Installed MIUI with a little bit difficulty, used some stock ROM that forgot which one... And threw MIUI on top. Since everything's was working fine, i deleted the files used. A month ago, the battery ended and shut off automatically. As soon as i could i recharged it and the phone would'nt turn on anymore. Cleared all though CWM and it was usable again. Since i lost all the apps and stuff, decided to update the MIUI. It failed and since then i have the /mmcblk0p2 problem. Tried RiffBox too, but could get nothing to work.
If anyone have any ideas, feel free! I'm almost buying a Galaxy S Advanced in exchange... Android caught me too!
Mine is acting the same way, used several different ROM`s, Darky Ress Edition, EZBase, XXJVU, XXJPU, Heimdall, XXJPC, XXJVS, tried using ADB but the eMMC don't remove my partitions so i can create them manually and it does'nt accept /dev/block/mmcblk0 mkfs ext2 either.
Almost giving it up... Oh yes, i can enter recovery mode and download mode, change kernels, but it does'nt pass though the Galaxy S logo. Through all this testing, i'm almost sure the problem is with /data. It seems like my internal memory became read-only.
I live in Brazil and my sister bought this Galaxy I9000 in USA. Installed MIUI with a little bit difficulty, used some stock ROM that forgot which one... And threw MIUI on top. Since everything's was working fine, i deleted the files used. A month ago, the battery ended and shut off automatically. As soon as i could i recharged it and the phone would'nt turn on anymore. Cleared all though CWM and it was usable again. Since i lost all the apps and stuff, decided to update the MIUI. It failed and since then i have the /mmcblk0p2 problem. Tried RiffBox too, but could get nothing to work.
If anyone have any ideas, feel free! I'm almost buying a Galaxy S Advanced in exchange... Android caught me too!
iowabowtech
root@android:/ #
The instructions may vary for your phone. This discussion is in the Droid Incredible forum. It may work for your phone also but some of the commands and the dev block enumeration may be different in your case. I'm sorry, I am not well versed in the Galaxy S.
Yeah, I don't know how much we can help, but I would try doing a format of /system, then /data. It is done under the "mounts and storage" sub-section of recovery. See if you get an error for either of these actions. My bad /data screws with me after boot, and it fails to format. If you can't boot at all, it may be /system (its a guess). But I'm curious: do you remember what things you had flashed recently when you had this problem?
It shows: Done. Well.. after the phone stopped turning on, i tried to flash many Stock Rom's, tried so many that i can't remember them all... Before the problem i was using a stock rom to install MIUI. It was working well for many months, suddenly it stopped working.
I've tried to format via Gparted and Mini Tool Partition (since the sdcard seems screwed and write-protected). No luck for either. Tried Samsung program and next is HP USB Disk Storage.
When i first installed MIUI i remember those errors coming up (mmcblk0p2) but one miraculous ROM installed well (i remember it had one file only). The bad thing is that i deleted the file and can't remember wich one was....
Any more ideas?