yashsingh1/xdaforums huggingface dataset:
[Android Software Development] hg42:
Sorry, I don't know anything about going the warranty way (because I revived my phone and could live with the 2GB loss).

But you may find info about that somewhere on xda.

This certainly depends on how the service center works. They seem to be very different in knowledge and how much work they apply before going to exchange the motherboard. There also seem to be service centers repartiotioning an emmc brick instead of really repairing it (which is much cheaper, so if this is good or bad very much depends on the customer).

Often you can still flash a stock kernel and then you could kill the writable (= not bricked) parts of the rest of the memory (usually FACTORYFS and up) via adb and something like dd if=/dev/zero of=/dev/block/PARTITIONNAME (~ mmcblk0pXX).
[Android Software Development] ragemode:
emmc_find_brick_start.zip & emmc_find_brick_end.zip did not install on my I9100 stock recovery. Installing them via CWM worked fine however.

Thanks to you I managed to get my phone up and running again :) Thanks!
[Android Software Development] hg42:
Nice...

thanks for reporting.

"did not install" means you did not see any messages (which seems to be standard on stock recoveries)?

Or did you get an error (which one)?
[Android Software Development] I.am.zahid:
Dear Sir Pls Help

I recovered my phone from the brick, ICS rom installed, I checked by adb and ur scanner file every block is shown OK but stil it freeze so often, when the phone wants to read write data to internal memory,

In this case how to know that where is the problem and adb and scanner file is showing that every block is OK but why still the problem going on.................I feel some problem still remains in internal memory but could not find as adb and scanner file is showing that every block is OK

In this case what will I do to make my note normal
[Android Software Development] swagarr10:
I was having similar problems with my note after trying to flash a jelly bean rom. and everything pointed to a corrupt internal sd card. i obtained from http://xdaforums.com/attachment.php?attachmentid=1081280&d=1337870248 which allowed me to now enter recovery mode. and then i ran the emmc scanner and it came up with no problems which i thought odd. when i explored the phone in recovery mode i found out that it was recognizing my internal sd card as an external sd card and vice versa. how do i fix this please?
[Android Software Development] neier24:
Guys, post your stories here. It will help other users. What obstacles you've encountered. What path was easier, etc.
[Android Software Development] neier24:
Did you do this step? As people we tend to rush a lot when the situation complicated

note: the running counter is the amount written yet. It is not related to the partition size.

important:

The internal sd is determined by an environment variable EXTERNAL_STORAGE.

Despite it's name it should be the *internal* sd, instead SECONDARY_STORAGE contains the external sd.

I hope, this applies to all android OSes...please report if not.

For now you shouldn't use the tool, until you checked this:

adb shell set

If EXTERNAL_STORAGE isn't your *internal* sd, the tool will not help, because it writes on the external sd.
[Android Software Development] neier24:
I hope samsung will bring up a fix for this... never its too late.
[Android Software Development] neier24:
How to run the scanner from x to y on a determined path. What are the step by step

Help
[Android Software Development] hg42:
sorry, please ignore this post, I got confused by tapatalk which didn't show all my posts
[Android Software Development] hg42:
Recovery is wrong on some roms. This started when sd mount points where made swappable. I think the recovery doesn't know of the swap.

My scanners try to find internal memory by other means (via information from kernel).

Look at the device names listed by the scanner. Are they correct?
[Android Software Development] hg42:
It cannot scan from x to y

That's because android/kernel uses too small integer numbers to address the amount of blocks directly.

As a consequence I can only scan sequentially from start or end.
[Android Software Development] DerBusisVoll:
Excellent, I apprechiate your work. With that, you might be able to help me with my SGS1 problem, which seems that my internal scdard is not writable any more.

For reference you could scan through http://xdaforums.com/showthread.php?t=2300639 which describes the state of my investigations and what I conclude so far.

Running your scanner in read mode returns no problems, and writing just seems to have no effect, like the partitioning and formatting I mentioned in the other thread.

So I think that either the MMC SEM08G has a physical damage or for some reason the write protect bits in the CSD registers are set. Maybe you could help me to move forward?
[Android Software Development] julienvt:
tested via adb on a galaxy nexus

no bricked partition detected (i have another issue, can't access userdata partition)
[Android Software Development] julienvt:
A quick question: the scanning of my /dev/block/mmcblk0p12, which is supposed to be mapped to my userdata partition goes fine

However, i can't flash this partition, or wipe it, format it, etc....

i initially thought the emmc might be dead, but the fact that the scan works it totally puzzling to me... the scan proves that it's fine right ? i am not really sure at which level it's performed

?

---------- Post added at 11:46 AM ---------- Previous post was at 11:07 AM ----------

i want to try the write scan, but gives me an error:

~ # emmc-scan -w /dev/block/mmcblk0p12
option: write scan
/dev/block/mmcblk0p12
cannot change to directory /dev/block/mmcblk0p12
ERROR: no default for write scan

any idea why ?

EDIT: must be because it's not mounted, and i can't mount it (that is my problem...)
[Android Software Development] infoshayan:
I had /cache problem and with your tutorial I could fix my phone ,

Thanks
[Android Software Development] hg42:
the read scans are performed on byte level (blocks), either scanning the whole memory (if something like /dev/block/mmcblk0 is used, which is the whole emmc device) or scanning a single partition, if the partition is used (e.g. /dev/block/mmcblk0p0)

The write "scanner" repeatedly writes a file to a directory and deletes it afterwards. This is only a kind of "scanning" in the sense that the emmc device may assign different blocks on every write because of the wear leveling algorithm. This is an experimental feature of emmc-scan (not recommended, only for testing).

emmc-scan -w [-a] [-p] DIRECTORY

-w write to writable partitions (fill with small files)

DIRECTORY directory to be filled with files (e.g. /data, /sdcard )

/dev/block/mmcblk0p12 isn't a directory but a block device
[Android Software Development] astonmartin214:
okay I have a S2 & I've hard bricked it can't get to download mode or anything is there a fix for this issue
[Android Software Development] peakbagger66:
OK, newbie question - how do I run this? From odin? I see the instruction "The tools are started via "install zip" from a recovery." but how do I get to that point?

[EDIT] Ehh, OK,I read further down and found that it is for people who can get to recovery. I can't do that so, I guess I am SOL!
[Android Software Development] hg42:
correct.

(If it's an emmc brick, you can still use a guess first to bring a recovery to live and then scan)
[Android Software Development] panda822:
hi

Hello,

I have scanned my internal sdcard but there are no errors, but I can not access it from Android 4.4.2 and I can not mount it in CWM. I could mount it and access it in CWM from Cyanogen 10.2 for Samsung Galaxy 2 older version of CWM but the OS could not be installed. What can be the problem and how can I fix it?
[Android Software Development] hg42:
I hope I understand you correctly (I'm german), so I'll try to summarize:

You have a SGN2 and used cm10.2 before.

Now you have tried to "upgrade" to some other ROM (Samsung?) of Android 4.4.2.

You didn't tell how you installed the new CWM, from where you got it and which version it is.

So I'll try some general thoughts:

The internal sd should never be touched by a ROM installation, because it contains pure user data like music, pictures etc.

Installation may eventually copy some files to folders like "Android" or "data". But all this shouldn't effect the mountability of the partition.

Because of this, the internal sd shouldn't have an effect on installation of a ROM (it doesn't fail because of this partition).

Usually the internal sd is formatted with FAT32. So every recovery and ROM should be able to mount/read/handle this.

Some (expert) users may decide to format the internal sd to ext2 or ext3 or ext4 file system, which could eventually make a difference (may be a recovery doesn't support such a file system and therefore cannot use it).

But newer recoveries should be able to handle at least the same or even more file systems than older ones.

But apart from that, I assume you didn't do something like this?

So, what can you do?:

You should scan all partitions, not only the internal sd.

You may format the internal sd to make it mountable again, but be aware, that you will loose it's whole contents.

The internal sd may also be damaged by repartitioning the phone memory in some way, e.g. by using a PIT in Odin, or by using parted on it.

Repartitioning makes all moved partitions invalid (because the borders are moved, but not the contents), so that they have to be formatted or restored from a backup.
[Android Software Development] panda822:
I have a Samsung Galaxy S2 and I have resurrection remix 4.4.2. I have played with Aparted application and copied some files from my external sdcard to my internal one. And suddenly I could not read the content of my internal sdcard. I went to CWM and could not mount or format it. Then I have installed CM 10.2 but I could not boot, it was in a loop mode and I have booted in CWM from this 10.2 Cyanogen so was an older version of CWM and surprise I could mount and read the content of the internal sdcard. I have retrieved the files from my internal sdcard with adb and then format everything and then restored the OS from backup RR 4.4.2 and still internal card can not be accessed. Tried again CM 10.2 format the sdcards and try to install CM 10.2 and still boot loop mode.

I have scanned every partition I have pulled out my external sdcard and run the scripts everything was OK. I don't know what to do more!
[Android Software Development] panda822:
I've fixed it. I have re-partitioned it with original pit with stock kernel for my phone rooted again and restored my OS from backup. My SDCARD now is working!
[Android Software Development] hg42:
Nice to hear, you have solved the problem.

Indeed, using Aparted explains the behaviour (would have been helpful, if you had mentioned this).

Btw., how did you copy "some" files? I don't see such an option in Aparted (from the images in play store, I cannot start it on my phone).

From a tool like Aparted I would only expect to copy whole partitions, but not single files.

When using GUI tools (like Aparted), you always have the risk, that you don't see error messages from underlying tools (parted in this case).

Sometimes(often?) developers only detect errors, they already know and expect from the tool.

That is, why I prefer using command line tools directly.

I think, GUI tools make some things a little bit too easy, which most people probably wouldn't try in adb etc.
[Android Software Development] panda822:
Hi.

I was playing with aparted and copy some files in the same time with file manager. Anyway now I have changed the partition data to 6 GB. Everything its OK. Thx for help!
[Android Software Development] mcongosto:
Desperate

Hello, guten morgen :)

I've been struggling with a similar problem with my chinesse Cubot X6 (MTK6592). It boots fine on MIUI but basically everything I do with my phone: format, flashing, etc is lost after restarting. I'm Stuck on MIUI but after a couple it becomes unusable due to many app craches.

If I try to flash the stock rom via Flash Tool, everything goes fine as it should but the phone restarts again in MUIU.

Your solution seems to be the closest one for my problem so far, however i cant find PIT files for my phone, I don't know if they even exist or of just a Samsung think. None of your tests gives an error though. But I am pretty sure it is a partition problem, produced by either trying the CMW partition option or by trying to install a bogus ROM (fake CyanogenMod 11 at needrom).

Is there light you can throw on my problem?

Danke schön!!
[Android Software Development] mcongosto:
Also, I get an error at FlashTool, but no hints...

============ Memory Detection Report ===========

Internal RAM:

Size = 0x00020000 (128KB)

External RAM:

Type = DRAM

Size = 0x40000000 (1024MB/8192Mb)

NAND Flash:

ERROR: NAND Flash was not detected!

EMMC:

EMMC_PART_BOOT1	Size = 0x0000000000400000(4MB)

EMMC_PART_BOOT2	Size = 0x0000000000400000(4MB)

EMMC_PART_RPMB	Size = 0x0000000000400000(4MB)

EMMC_PART_GP1	Size = 0x0000000000000000(0MB)

EMMC_PART_GP2	Size = 0x0000000000000000(0MB)

EMMC_PART_GP3	Size = 0x0000000000000000(0MB)

EMMC_PART_GP4	Size = 0x0000000000000000(0MB)

EMMC_PART_USER	Size = 0x00000003a3e00000(14910MB)

============	EMMC Test	============

thanks again
[Android Software Development] hg42:
first:

from your description, when writing something to your phone's flash memory the phone doesn't lock up or become very slow.

So I think this isn't an emmc erase brick.

Instead:

It's just a theory looking at your description of the problem.

I think your flash memory is now permanently write protected.

This would look like this:

Probably all file system writes go to the cache and can be seen there (reading from the cache).

Flashing some ROM etc. goes to nirwana.

In both cases you don't see any changes after rebooting.

I had this behaviour with two different 64gb sdcards (Sandisk and Transcend, but I think the company doesn't matter).

These cards were in use with my N7000, so this may eventually have to do with it's emmc brick.

The write protection seems to be at a very low level, because the OS doesn't notice any problem.

Writing to the memory or flashing seems to work but it doesn't really write at the end.

I think, no Android developer ever expected that writing to a flash memory can go wrong, so they don't check (at low level) if the data has really been written.

I don't have any clue why this situation can occur.

The flash memory seems to disable write access by itself (in hardware).

I found very few about such a write protection. But it was mentioned at the chip (hardware) level.

I'm sorry, if you really have such a problem, you probably can trash your phone...

But first check, if you can prove my theory.

So check which memory parts (internal memory, external sdcard) can be written to and return the written data after a reboot.

You may make a backup before, and a backup after several write operations and compare them.

If you are lucky, it's something totally different.
[Android Software Development] bigbenjo:
Hi, nothing for my stock rom/recovery?

With adb sideload is impossible to open your .zip files. Same thing with recovery.

In Download mode Odin can't write Nand.

I have an N7100 Galaxy Note 2.

Thanks....
[Android Software Development] hg42:
the first I do with a phone is installing a custom recovery, so I never see a stock recovery.

From my memory, I think there's only an option to install a file called update.zip but you probably cannot install arbitray zip file names.

So you might rename the file to update.zip.

It think I also remember that it should be at a certain location (something like /cache?).

But you better ask someone with knowledge about stock recoveries.

I am quite sure this is covered somewhere on xda or else.
[Android Software Development] kaspertje100:
is it possible to use your tool without root access (on the android device)? If so from which directory can I execute the file? I just tried from the emulated sdcard (internal storage) in the userdata folder but I get operation not permittetd error.
[Android Software Development] hg42:
as described in the text you quoted, there are three ways to execute the tool:

1. the zip file via recovery similar to an update file

2. via adb (see example session)

3. via terminal

The recovery is already running in root mode.

adb or terminal need root. That's why you find the line "adb root" in the session.

"Permission" can also refer to the executable permission of the program file. The "chmod 555 ..." line sets all executable bits on the file. You cannot execute the file without this. The FAT file system doesn't store permission bits, so you might need to store the executable file on a linux file system (that's why I used /cache). However, the FAT file system is mounted with fixed permission bits (all files have the same bits), that usually have all executable bits set. Try "ls -l /sdcard" or a file manager, if the "x" bits are set, every file could be executed.

As a conclusion "not permitted" probably refers to the "operation" as expressed in the error message and not the execution permission.

Accessing block devices at block level is a privileged operation.

So, in short: you need root
[Android Software Development] kaspertje100:
Thanks for the detailed explanation. Too bad I need root for this action since I was hoping to scan the block devices in order to compile a custom TWRP for my device in order to get root.. A bit of the chicken and the egg problem hehe. Anyway I might already have found an overview with the existing partitions which might just do the job.
[Android Software Development] hg42:
so you need the partition layout of your device?

I just had a look, you can indeed only read the partition layout or any low level data from the disk if you have enough permissions. The storage devices are all restricted to the owner alone (no rights for group or other), and the owner is root.

But even if you could, my scanner wouldn't help you, because it only checks readability by reading samples from the disk in big steps while printing the position. It doesn't output any other information usable for your goal. It's a very specialized tool for emmc bricks of a certain kind with the only purpose to find the block with the first error (because the program hangs in this case, you can read the last position).

For Samsung devices you could probably use a tool like Odin or heimdal that reads the so called PIT data structure from the device (containing the partioning, only Samsung).

This should work without root (using the Samsung specific download mode).

I don't know about other devices. Though in general, because Android is a Linux derivate, you could use a tool like fdisk.

But any tool like fdisk would need root.
[Android Software Development] kaspertje100:
Hmm too bad I don't have a samsung device hehe. I got a LEMFO lem8 watch with a mediatek chipset (6739) so ill look for other tools I guess. Thanks for the info anyways:)
[Nexus 7 Q&A, Help & Troubleshooting] offender1992:
Hi, i've just ran into a bit of a problem. I was planning to watch Avatar (1080p) (.mkv format it is in) on my Nexus 7 to see how well it would cope. I started using mxplayer but it had no sound, dice player would play the movie so i then use BSplayer FREE and it worked. Job done. Until i found that i forgot to enable subtitles for the na'vi speech so i could understand. In BSplayer Free when i press in the top right, then select subtitle, then select active subtitle it doesnt find any, but when i use my computer there are 3 subtitle tracks within the video. I've also tried putting the .srt file in the same place, called the same as the movie, but it still wont find it.

Any ideas?
[Nexus 7 Q&A, Help & Troubleshooting] Ravynmagi:
Try Moboplayer?
[Nexus 7 Q&A, Help & Troubleshooting] Nordendorf:
did you try SW decoding for MX?

Also, the full version of DICE player was made free last week. There is an option to manually select your sub file.

~
[Nexus 7 Q&A, Help & Troubleshooting] farandel:
MX player works beautifully for me.. no lag at all
[Nexus 7 Q&A, Help & Troubleshooting] Logan_M:
MX works perfectly for me, just remember to keep it set to S/W mode and not S/W(Fast mode).
[Nexus 7 Q&A, Help & Troubleshooting] Nordendorf:
hmm. That sucks. I haven't run into the AC3/Tegra issue yet as SW mode has been able to handle my files, but I've only tested 720p stuff for MKV. 1080 MP4 was fine.

I'll check if I have any 1080p MKVs later tonight. I have a feeling most if not all my 1080 stuff is mp4 though. I really try and avoid MKV since it's a PITA for 360/PS3 and i've never gotten those "on the fly" converting media servers to work. Curse you MKV! :mad:
[Nexus 7 Q&A, Help & Troubleshooting] juami:
you should use custom plugin and libffmpeg.so on sdcard.

it may be a DTS issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] keeper22:
With all the development going on for the SG3 I find my self flashing and wiping constantly. Does anyone have tips for a good playlist manager that you can export the playlist to the external sd card? I love the Apollo Player but you can't export playlists. I'm hoping the only answer is not to use player pro or poweramp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Back-up "Media Storage 4.04 (PLAYLISTS)" in titanium backup. Restoring should bring back your playlists.
[Motorola Triumph] turboeddie:
I saw this tweak on a different page, I've tested it and it helps. Anyway, open the build prop file, after the last ro command, write the following:

ro.product.rat=EvDo only

then restart the phone and that's it! What does it do? It prevents your phone from loosing 3g. Aka the 1xrtt status. Like I said I saw this post so, I do not take credit for it! Oh & like anything else BACK UP your build. prop.
[Motorola Triumph] Apk07:
There are many scenarios when 1x (especially 1x roaming) can be more reliable for texts/calls than evdo
[HTC Incredible S] GeoffreyMtl:
Hi,

Two weeks ago, I had a rom (Nik_Project_X_v3_By_Nikhil007) who worked. I decided to come back to RUU rom bu when during the installation of this one my cell turned off and from this time I am not able to turn it on...

When I plug my cell on my laptop I am able to execute fastboot, it recognizes it. I tried to reinstall my RUU rom but a error message appear :

I tried to downgrade my hboot using this command : fastboot flash hboot vivo_downgrade.img but I received this message :

I'm a little bit lost now... I don't know what can I do more..

Your ideas will be the welcome :)

Thanks very much !
[HTC Incredible S] 77777777777777:
Is your bootloader locked or unlocked ?
[HTC Incredible S] GeoffreyMtl:
I don't know... How can I check that ?

Thanks
[HTC Incredible S] 77777777777777:
1 Put out of battery en put it back in

2 press volume button down end the power button

In display ?

Write everything and email it to my !
[HTC Incredible S] GeoffreyMtl:
Unfortunately nothing because my phone doesn't start :(
[HTC Incredible S] 77777777777777:
battery empty ?
[HTC Incredible S] GeoffreyMtl:
no... battery is full I tested it.
[HTC Incredible S] 77777777777777:
Put Battery out and back in

First press the volume button down and than power button
[HTC Incredible S] GeoffreyMtl:
I tried 4 times, but it doesn't work.

Thanks for your help
[HTC Incredible S] 77777777777777:
No problem !
[HTC Incredible S] GeoffreyMtl:
So, it's official ? It is bricked ? :(
[HTC Incredible S] Alasdairyee:
Maybe you can give us more information about your phone? What have you tried?

Bootloader working? Version?

Recovery Working? Version?

What's working and what's not?
[HTC Incredible S] abissel22:
If it doesnt even boot into the bootloader then you should send it in to someone or use a jtag to fix it. That i believe is called a hard brick.

Sent from my SCH-I535
[HTC Incredible S] 77777777777777:
You can olso Try it whit removing battery en sd-card and sim. Put battery back in

First volume button down dont release power button down dont release (normely display goes on)
[HTC Incredible S] Nonverbose:
Any charge light or screen backlight appear when phone plugged in? Link to the ruu you used could be helpful.