Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,809,359 Members 40,131 Now Online
XDA Developers Android and Mobile Development Forum

[Q] I think Internal Flash memory of my Android Device has some allocations dead

Tip us?
 
Seyokentai
Old
(Last edited by Seyokentai; 11th June 2014 at 05:55 AM.)
#1  
Junior Member - OP
Thanks Meter 0
Posts: 7
Join Date: Jun 2014
Unhappy [Q] I think Internal Flash memory of my Android Device has some allocations dead

Greetings dears XDA members!

I read out many many many of posts before postings, and also used "search" feature in order to find a topic like mine, but with no success.

Well, I start to explain my problem..

====

A few days ago, my Samsung Galaxy Tab 2 (10'1)'s tablet caused some reboots without really beings really very common, but now .. reboot frequency has greatly increased since yesterday day.

A quick check using the "Reboot Checker" (you can find it through the Google Playstore: https://play.google.com/store/apps/d....rebootchecker), and I can see that reboots are really common now as showed by the log reports showed in "RebootCheckerLogReports.png"'s file attachment to my post.

So.. What I do of specials before reboots are produced??

Hmm.. Really nothing, really:
  • I always deactivate the "AutoUpdate" for Apps from Google Play
  • Before reboots are encountered, I not installed any applications
  • I never install applications and Games out of Google Play official market
  • I just play to few games (like usually I do): Fantasica, Rage of Bahamut, Legends of Cryptids, Arcana Magic, DarkLords, Bingo Blitz, Chaos Drive, and that's all..
  • All applications I install from Google Play are recommanded/unlocked by AppGratis (and other websites like this)..
  • I never rooted my system (And I see now, I'll have to do on Day 1 of the purchase of the tablet ... since no-rooted an Android System doesn't permit recovery things at an advanced state..)

So, due to that reboot, I firstly thought that was a memory storage issue like, not enough diskspace. (with all that AppGratis applications, I have less disk storage memory indeed xD).. Then, I uninstalled some apps which I installed some months ago and I less used..

Bad Tought: Reboots hasn't been discontinued... ** sigh **


I think then it was update of Google Apps (like Google+, Google Talkback, Google Mail, Google Youtube etc..), so I updated them from Google Play..

Again, Bad Toughts: Reboots still here.. ** big sigh **

Well.. my hope was then at this state ported to Internet...

So I read many topics on "Unattended Reboots"..

And I finally found something of VERY useful.
On here: http://android.stackexchange.com/que...device-reboots

Glad I find that StackExchange question, I now that the "su" (Linux SuperUser if I well understand my Linux course), is not possible under a non-rooted Android (that a stupid behavior for an Operating System that.. But.. Well.. I continue)..

So, I started to think how I will be able to catch this file... and save in a readable folder..

Hopefully, 1 year ago I installed an app named: "ES Explorateur de fichiers" (find out this here: https://play.google.com/store/apps/d...gs.android.pop)

And this great apps was letting me accessing to the wanted file: /proc/last_kmsg
(I shared it to my DropBox linked account, and then I was able to open it on my Windows 7 Computer).

I then provide the log here: https://www.dropbox.com/s/u9ble2ui30io5x8/last_kmsg

So.. In the meantime, I started to analyze the log, and visiblely, my main (and sad) problem is that my Internat Flash Drive is dead.. Since I/O errors are the only main reason to Kernel Panic and reboots..

Well.. My warranty is void since months now.. (well well.. well..)

I then can't RMA the product (the tablet if I understand well).

I don't want wipe datas/cache and anything before try some new XDA tricks.. (I don't expect do much like that, but hey.. Hope is Hope.. my datas aren't important, it's true, it's mainly Game Saves and Unlock keys for AppGratis recommanded applications, but then, if I wipe datas, I will lose ALL of theses free unlocked apps.. This is a thing I doesn't really want, if you mean what I want mean..)

... so... I started to think what we can do for fix bad sectors on Linux (since Android is based on Linux and Dalvik if I (again) understanded well).

I hink that fixing bad sectors allocations it will fix the problem, since if I analyze my Internal storage (called sdcard0) there is sometimes the scan is finished without reboots!

So I was directed on XDA-Developers (which I know that you are famous for your system hacks and morever) here by Google : http://forum.xda-developers.com/goog...panic-t2553949

I saw this post: http://forum.xda-developers.com/show...38&postcount=3

And then a quick search on Google again on the words "Android + fsck the filesystems through adb shell" redirected me to that excellent post: http://forum.xda-developers.com/show....php?t=2165870

This is a great information, but... I don't know how to go in recovery mode from my Galaxy Tab 2. So.. I searched on the web for it, and found that: http://forums.androidcentral.com/sam...2-s3-tab2.html

So.. I started blink my eyes, and go for hard work, and since I already in the past installed the Android SDK (for develop personal mobile apps with Titanium Studio, Adobe Cordova, PhoneGap), and do all update especially installed adb..):

Once plugged to my PC and booted in recovery mode, I was able to access to the famous recovery mode
(This was so exciting due to the fact I like the way of it look: especially the Android bot unfixed in the background ^_^).

So, on my PC I started to open a command line in the folder: C:\SpecialAppDevelopper\Google Android SDK\platform-tools
(this is where I installed the Android SDK)
and typed this:

Code:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb devices
This showed me that:

Quote:
List of devices attached
c16073dc82dc68f recovery
So it worked! My device was successfuly attached to ADB !! What an excitation !

I then continued typing other commands:

Code:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb shell
This output that:

Quote:
shell@android:/ $
Good. Now In this shell access I typed :

Code:
mount /system
Not good here since all I get is a USAGE warning with options recommanded. (like a return of a MAN command..)

Quote:
shell@android:/ $ mount /system mount /system Usage: mount [-r] [-w] [-o options] [-t type] device directory
Well.. tryied the next command in order to listing report file system disk space usage:

Code:
df
all I got as output was occuped space, not the path of the mounted images...

Well...
Now, I started to reanalyze my last_kmsg log in order to find which path they are..

I found it!
[ 94.965454] C1 [jbd2/mmcblk0p10]

So... I started to return to my ADB commandline window and typing:

Code:
ls -l /dev/block/mmcblk0p10/
This outputed that:

Quote:
/dev/block/mmcblk0p10/: Not a directory
So as it looks a good path, I started typing this:

Code:
e2fsck -n /dev/block/mmcblk0p10
And even if it is the right path (one of the right path, I don't tryied with others...), I got this output:

Quote:
e2fsck -n /dev/block/mmcblk0p10
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Permission denied while trying to open /dev/block/mmcblk0p10
You must have r/o access to the filesystem or be root
Yeah... I'm not root, cool, even in a Recovery Mode on a non-rooted Android Operating System (Logic in a way, but very difficult to fix problems then occuring then )..

Ok.. So, My mind blinked in an idea when looking at this: You must have r/o access to the filesystem or be root
So.. This is not needed to be root for executing a e2fsck command in Recovery Mode, but in that case I need having access to the filesystem in a READABLE mode. OK.

So, Hope started to bringed back, and I made new Google research, on "mount an android filesystem in recovery mode"

I was then directed here:
- http://forum.xda-developers.com/show....php?t=1396864 - Very complex for me, I don't want brick my system.. So I skipped.

- http://androidforums.com/droid-all-t...ml#post6347416 -

So.. For being root in recovery mode, I can also type the simple command: adb root

Ok... What I do..
And, as expected it doesn't worked for me:
Quote:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb root
adbd cannot run as root in production builds
Ahaha.. Well starting to be hopeless now.. I'm finally just an user of my OWN tablet.. How it's ridiculous.

This is a bit tedious, because all my future Google research in order to find how to simply "mount" a filesystem as readable (and then replace it as it was after the process..) aren't really efficient, I founded nothing of useful..

Nothing usefull but that: http://android.stackexchange.com/a/69307

So, it seems I will be able to mount as readable a filesystem through Production Recovery Mode (the one I'm forced to use then..)..

BUT..

Well.. Now, since I don't know what I can type for mounting my filesystem... as readable just for make a e2fsck... Seriously..

Help me dear gurus, i'm completely lost because my Linux knowledge stop here !
Attached Thumbnails
Click image for larger version

Name:	RebootCheckerLogReports.jpg
Views:	6
Size:	150.9 KB
ID:	2791907  
 
Seyokentai
Old
(Last edited by Seyokentai; 11th June 2014 at 11:05 AM.) Reason: add something to the end.
#2  
Junior Member - OP
Thanks Meter 0
Posts: 7
Join Date: Jun 2014
New informations..

I tryied an another method in order to list devices symlinks names:


Another way to check is to use adb to view the devices file system.
Related to this thread: http://forum.xda-developers.com/show....php?t=1463756
Thanks to it (even if it isn't how mounting in RW)

So, when plugged in Recovery Mode I typed:

Code:
adb devices
adb shell "ls -R /dev/block"
The -R is because I want have the realpath of each items listed
Well, this was the output:

Quote:
/dev/block:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9

/dev/block/platform:
omap

/dev/block/platform/omap:
omap_hsmmc.1

/dev/block/platform/omap/omap_hsmmc.1:
by-name
by-num
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9

/dev/block/platform/omap/omap_hsmmc.1/by-name:
CACHE
DATAFS
EFS
FACTORYFS
HIDDEN
KERNEL
MODEM
PARAM
RECOVERY
SBL1
SBL2

/dev/block/platform/omap/omap_hsmmc.1/by-num:
p1
p10
p11
p2
p3
p4
p5
p6
p7
p8
p9
Also, I read from here: http://forum.xda-developers.com/show...3&postcount=10

That E2FSCK will better be secure when executed on a named partition, can you confirm me it or no?

Now, I think..
Since, I know on my Windows when a sectors in corrupted or broken state, I can simply tell to the OS (Windows so) that I want it IGNORE it !

How I can do the same things to my Galaxy Tab 2?

It certainly fix my problem like that no?
 
Seyokentai
Old
#3  
Junior Member - OP
Thanks Meter 0
Posts: 7
Join Date: Jun 2014
Well well..

It is not better than it was, I really need advices and moreover help to know what I can do with the "mount" command and plus..

I was at 4'th page of the forum, so I think my thread just goes skip from your eyes, this is why I want up it..

Anyway, I read somewhere there is a lot of commands available.. due to the fact I'm not aware suffisely with Linux, and due to the fact Android recovery commands (and moreover the System) is based on Linux.. I prefer ask here..

So please, please.. answer me
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes