yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] mrjraider:
if got similar issues with my old eight gig SD card. able to read but unable to write. also caused by Android..

also could it be possible that the partition is formatted on the wrong way?

Verstuurd van mijn GT-I9001 met Tapatalk
[Galaxy S Plus I9001 Android Development] -ION-:
Would they believe me?

Well after reboot into recovery I can format my /cache again,

here's the output of cat proc/partitions

~ # cat proc/partitions
cat proc/partitions
major minor #blocks name

179 0 7552000 mmcblk0
179 1 106495 mmcblk0p1
179 2 500 mmcblk0p2
179 3 3596 mmcblk0p3
179 4 1 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 20000 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 7000 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 7680 mmcblk0p13
179 14 5120 mmcblk0p14
179 15 532480 mmcblk0p15
179 16 102400 mmcblk0p16
179 17 1413120 mmcblk0p17
179 18 204800 mmcblk0p18
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27
179 28 5024768 mmcblk0p28
[Galaxy S Plus I9001 Android Development] LiiQuoR:
Is it possible to unbrick /data without ADB and without waiting too long? :D
[Galaxy S Plus I9001 Android Development] broodplank1337:
I think when you rename the cache.img.ext4 (or ext4.img) to userdata and try again. it might work

it might be 100mb but if it's fixed you can reformat it to it's original size.

I did this once as well and i have never got a bricked /data.

but I cannot guarantee you it will work.

oh and it doesn't care if your device has a stock rom or a custom rom or is bricked or whatever, you can always send it to samsung no matter what. the warranty bull**** is fake (they just want to make you keep their bloatware)

someone I know found a device outside (so generally it's a stolen one), bricked it by accident and sent it to samsung, and they fixed it lol
[Galaxy S Plus I9001 Android Development] Ledo13:
I took my phone today at service, and I did flash it with stock rom. When i get it back, i'll post here what they told me, did they notice i messed it up.
[Galaxy S Plus I9001 Android Development] -ION-:
Why would we try so many different things if there was an easy solution?

So ill have to try

dd if=/dev/zero of=/dev/block/mmcblk0p17 count=102400

And than format it with CWM and than it will be the original size again?

And it's free? within a year of purchase?
[Galaxy S Plus I9001 Android Development] mrjraider:
Well, KIES is Samsung Software, so yes. You have some guarantee that they will fix it for ya if their software ruins it.
[Galaxy S Plus I9001 Android Development] broodplank1337:
Well, I once flashed an empty 100mb userdata just to test if it was possible. and it was. it also didn't brick my device. and idd I was able to format it to the normal size again after that.

So I advice to first use odin and if it doesn't work you can try it with dd.

And I have no clue actually. it's probably free within a year of purchase but again I don't know so can't say much about it.
[Galaxy S Plus I9001 Android Development] -ION-:
Thank you all for your great support!!:good:

I'll report back once I tried it
[Galaxy S Plus I9001 Android Development] broodplank1337:
No problem :) and good luck
[Galaxy S Plus I9001 Android Development] -ION-:
Just came back from school, tested both ways to flash the 100MB image to the partition (odin and adb), both finish without errors but the partition is still broken :(

What exactly did ivendor fuq up with the 6.0.2.8 recovery? maybe we should start from there...

EDIT:

Has anybody already fixed their /data brick with this, I see no success reports?
[Galaxy S Plus I9001 Android Development] mrjraider:
Try to format it?

Edit: I think that the way the recovery formatted was wrong. The way should is ext4.. The way it could be formated is either ntfs or rfs, both are not acceseble via android.. Via computer? I dont know.

So i think that is the major issue. Trying to get it back to ext4. Normaly i would have used ccleaner to write 32 times to my sdcard to completley wipe it and after that format to the correct way.
[Galaxy S Plus I9001 Android Development] broodplank1337:
That sucks :( I think there's only the whole repartitioning left (as in mmcblk0, which is a 8gb partition, I cannot dump it since I have no external sdcard, but if someone would dump it you would also have his IMEI, which makes your or his phone unusable)

The cwm included wrong partition sizes :X you should contact him about it. it's not the version tho, because my broodRecovery works just fine (and its cwm 6.0.2.8)

you can search for "emmc brick" or "emmc bug" maybe you will find more about it.

I think it's ext4 for a wrong size, which causes a emmc brick (strangely this doesn't happen when you change the partition size with odin)

And the thing you say about wiping it is only for /sdcard. and not for /data
[Galaxy S Plus I9001 Android Development] sklaes:
possible solution?:

comparing some efs dumps to finding out where the IMEI is storred and change it
[Galaxy S Plus I9001 Android Development] mrjraider:
Shall i make a dump? My sdcard is 16 gig.. I can make some space. since i have almost 10 gig in use for music :silly:
[Galaxy S Plus I9001 Android Development] broodplank1337:
That's very friendly of you but you have to realize that this includes your IMEI number
[Galaxy S Plus I9001 Android Development] mrjraider:
Can i trust u :silly: Haha.

I wanna help but yes it is a thing to consider.. ;)
[Galaxy S Plus I9001 Android Development] broodplank1337:
Of course you can trust me but i'm not the one who has a bricked /data ;)
[Galaxy S Plus I9001 Android Development] mrjraider:
Yes but why do u need a dump then? Perhaps to take a look to the entire partion layout to filter important ones (EFS etc) ??

If so i would like to help.. ;)
[Galaxy S Plus I9001 Android Development] -ION-:
Damn never thought I'd fuq up my phone like this :( I think I'll just return it to the store (KPN).

I've got 2 backups as you can see :angel:

Thank you all for the effort! hopefully the others with bricked phones will get their devices back to life!
[Galaxy S Plus I9001 Android Development] janesz1981:
with odin i cant flash alireza7991's cwm but with ivendor's cwm i was success. I just checked, the diffrence was recovery.img (ivendor) recovery.img.ext4 ( alireza7991 ). Maybe a new tar with userdata.img inside better?
[Galaxy S Plus I9001 Android Development] alireza7991:
Hi

I had a mistake in naming img ! recovery uses mmc file system and dont need .ext4 so you should change name to recovery.img and tar it and retry to flash ! It will works !

also cwm flashable one is ready for use ;
[Galaxy S Plus I9001 Android Development] janesz1981:
Can i have a .tar with userdata.img inside? :] i dont wanna do something wrong :]
[Galaxy S Plus I9001 Android Development] alireza7991:
no problem ... use this command for building userdataimage

su
dd if=/dev/zero of=/sdcard/userdata.img.ext4
[Galaxy S Plus I9001 Android Development] janesz1981:
thx but thats why i want a zip because i dunno how to use codes. i dont have linux ( i think need for codes)
[Galaxy S Plus I9001 Android Development] ivendor:
I've investigated around of this issues (i've bricked my data parition too last night however).

First of all it's not a problem of partition sizes, they are correct. (cat /proc/partitions multiplied by 1024)

Our issue has the same symptoms of this: http://pinoydroid.net/samsung-galaxy-ii-galaxy-note-mmccaperase-bug-potentially-brick-device

Summarizing, this issue happens on galaxy note and galaxy s 2 with stock ics firmware. There's a bug in theirs EMMC hw firmware (i think in ours too) that cause the bricking on wiping data or restoring nand backup from recovery.

That bug it's caused by a wrong handling of the firmware of MMC_CAP_ERASE capability introduced in kernel 3. So gingerbread kernels doesn't has a bug, and i fear that all recoveries based on kernel 3 has the bug too. I cannot verify this theory but i think it's reasonably true.

However, if you don't want to send your phone to samsung center you can parittiion your external sd card to make an ext4 partition for data, i could provide boot images for booting using data partition on the sd card. (it's enough to edit the fstab.qcom and change /data row to tagert /dev/block/mmcblk1p2 (i use the first partition of sd card in fat32 for the user, and the second ext4 for rom data partition replacement)
[Galaxy S Plus I9001 Android Development] Jonboy2011:
but.. your phone works and you continue development ? :o

anyways thanks for the information , but My question is : is twrp 2.2.1 based on 3.x kernels or on 2.x.x ?
[Galaxy S Plus I9001 Android Development] buffo1987:
Kernel 2.x.x
[Galaxy S Plus I9001 Android Development] serfmen:
IMHO strange is this bricks happends only in last time (never before bricked /data like this on i9001?), if you say it makes with kernel 3 before this "bricks" no one use kernel 3 in recovery ?
[Galaxy S Plus I9001 Android Development] sava92ns:
I didnt undertood half of this but if someone can help that is you, I am really worried cuz of this. Hope you will find some true solution.I dont see anybody here that have repaired this to this point (or nobody reported), i saw one guy with fully bricked his phone on another thread... so i hope you will be able to provide some valid tutorial on how to do this... Looking forward, while my phone waits covered with dust. :(
[Galaxy S Plus I9001 Android Development] tsirhcitna:
I helped my friend to flash Paranoid on his note so I've read about it, they solved disabling mmc_cap_erase on their kernel, it should be easy (I hope), I dont know which funcionality will be affected btw

Sgnef
[Galaxy S Plus I9001 Android Development] :
On galaxy SII, devs solved this problem by disabling the MMC_CAP_ERASE on both SDcards.. but, since I'm not a dev, i don't if this is all we need.. anyway Galaxy SII, now, is 100% safe with kernels which aren't using that MMC_CAP_ERASE. In my opinion, we could send a Private Message to Phil3759, asking him about the emmc issue, but only one of our devs should do this in order to prevent spam!
[Galaxy S Plus I9001 Android Development] alireza7991:
Hey Ivendor ;

I said before that we can solve this issue with using another partition instead of blk17 for data in this thread :

http://xdaforums.com/showthread.php?t=2223469

but no one replied ! I can edit recovery.fstab but I need a kernel dev to help me by editing qcom.fstab in kernel . If you made the boot img I will make edited cwm

--------

but I think thats better to move data to blk15 (system) and pull system to ext-sd ! thats really better than changing data partition in data ! because system partition needs more read spead which can found at an class 4 ext-sd too ! and data partitons needs lot more write speed which can be found at blk15 ! if you swap system and data and then make system partition in ext-sd you will have a lot lot more speed in rom than normal mod !

regards

alireza

:good:
[Galaxy S Plus I9001 Android Development] LiiQuoR:
So.... the developpement of this fix has stopped or you are working on it ?
[Galaxy S Plus I9001 Android Development] sava92ns:
Im asking myself the same question. Dont want to be anoying, but im without my phone and sending to samsung is not an option for me so you guys are my only hope...
[Galaxy S Plus I9001 Android Development] janesz1981:
u tried this way to unbrick? http://xdaforums.com/showpost.php?p=40077942&postcount=141
[Galaxy S Plus I9001 Android Development] sava92ns:
I havent seen this, thank you, ill investigate...
[Galaxy S Plus I9001 Android Development] goliat88:
I dont know if im understanding this brick thing right. Its something with partition right? If phone is bricked it just wont boot or partion sizes are broken. I have that bad chipset and was using CWM 6.0.1.2

Are my partitions ok cause 1,33+4,79=only6,12?
[Galaxy S Plus I9001 Android Development] Jonboy2011:
yes because the rest is the Android os
[Galaxy S Plus I9001 Android Development] XeLLaR*:
I think you didnt read his full post. He said if someone needs a suitable boot image he will provide it. Just PM him.

You can edit the partition layout in the fstab.qcom file.

Gesendet von meinem GT-I9001 mit Tapatalk 2
[Galaxy S Plus I9001 Android Development] hydeh24:
I saw your post on the other thread, so I get that solution is not working for us... :(
[Galaxy S Plus I9001 Android Development] sava92ns:
Well for a minute I thought that there is no solution, but if you have same errors as I do, we need to see what Ivendors have to say and how he managed to make his phone running.

Check the other thread and read my last posts if you have same problems than there might be a solution...

Lets hope and wait.
[Galaxy S Plus I9001 Android Development] Jonboy2011:
i Make an edited kernel , just look at my thread , no Need of custom recovery :)
[Galaxy S Plus I9001 Android Development] banu_hashem:
Problem!!!

Hi,

I connected my I9001 to backup but samsung kies showed me there is an update when started it restarted & then stoped at 3% for hours when I disconnected it & restarted i it shows me its bricked u can see the attachment. I tried with Odin it doesn't ditect it What should I do please help.

Regards,

Hash
[Galaxy S Plus I9001 Android Development] alireza7991:
There 's a nice tutorial for fixing this written by [MENTION=4354408]broodplank1337[/MENTION] . Just google to find.
[Galaxy S Plus I9001 Android Development] LuqmaanMathee:
Will this work on the i9000 too?
[Xperia Z Q&A, Help & Troubleshooting] p.c:
my problem with rear cam in xperia z c6603 . there is a sound of camera lens during focusing , the sound is like "clicks" is this normal ?
[Xperia Z Q&A, Help & Troubleshooting] Hellscythe:
mine does that sometimes, i wouldn't worry about it
[Xperia Z Q&A, Help & Troubleshooting] DeathlessOne:
This is normal, as this cam have high end lens and optics it has to focus like a normal cam leaving the lens to project a lil (if zoomed and auto focused) causing this sound. To be precise, i had this in my arc itself. So there's nothing to worry about!

Sent from my C6602
[Asus Transformer TF700] lartomar2002:
Where on the tab should it feel hot if it is over heating. At what temperature should I start being concerned?
[Asus Transformer TF700] Tylorw1:
I been told anything under 60C is good. Yet my tablet feels very hot at 50C so it can get pretty hot to the touch, but it does not mean much. I suggest download Trickster Mod Kernal app to look at the temps and such.

Tylor

Rom: CleanRom Inheritance 3.4.7 Odex

Kernal: _That's Stock V6 Kernal

Theme: Timberwolf's Blues & Jazz Theme V2.1

UPDATE FOR TF700 USERS!!! AND THE 4.2.1 UPDATE

http://xdaforums.com/showthread.php?t=2204100
[Asus Transformer TF700] _that:
The CPU is near the upper left corner. And you should be concerned if it's too hot to hold. :)
[MDA, XDA, 1010 Software Upgrading] andhy:
Could some experts please kindly explain how to by pass the above mentioned WARNING111.

I need to upgrade the ROM RUU16006WWE_T-mobile_NL.exe through activesync (i.e. not SD/ bootloader methods), but have a problem with the battery as the device won't charge.

thanks an HAPPY NEW YEAR!!
[MDA, XDA, 1010 Software Upgrading] Biso007:
I believe there should NOT be a way for this bypass. It is originally made to prevent having a $500 worthy paper weight if the XDA went out of power during the ROM upgrade.

BTW, what your gonna do after the upgrade if your battery doesn't charge anyway ????
[MDA, XDA, 1010 Software Upgrading] andhy:
It doesn't matter what I want to do with the device after upgrade even if the device won't charge....

FYI, I have a problem and one of the important step to cure (I believe) is to be able to successfully flash all ROMs (CE & GSM). THen (I hope) all the programs loaders are functoning properly i.e. recognizing the power plugged in / battery charging etc. etc.) (this has been dicussed in full length in another thread).

So, I just want to know if there is any tricks to get around this...

But thanks for your comments..anyway..
[XPERIA X10 Q&A, Help & Troubleshooting] TheSharinganNinja:
Hi I recently tried to root my phone using flashtool, and from then on it isn't working.

The exact update I used was X10_aZuZu_Kernel_Downgrade_Generic.ftf

and I followed this tutorial:

www(dot)xperiax10(dot)net/2011/09/08/root-your-gingerbread-xperia-x10-tutorial/

When I boot up my phone, it gets stuck on the "Sony Ericsson" screen. PLEASE If anyone can help me it would be highly appreciated :)

I am not experienced when it comes to this.

:(
[XPERIA X10 Q&A, Help & Troubleshooting] NuLLV01D:
I'd also faced the exact same problem. Simply Flash your Phone again with "X10_aZuZu_Kernel_UpGrade_Generic.ftf" and it'll boot as normal. For rooting your phone, try DoomLord's Easy Rooting Toolkit:- Link

Worked on 1st try for me and is also pretty simple and straightforward.
[Desire Q&A, Help & Troubleshooting] d4mian:
Hi there,

I spent half a day trying to fix my, seems like, regular problem with sdcard, which is not possible to mount.

Of course I tried "fastboot oem enableqxdm 0" and "fastboot oem eraseconfig" resulting in OKAY message (everything's fine with fastboot, my phone is seen there by fastboot devices).

I formatted my Adata class 6 card using Gparted, Windows Disk Management and SDFormatter4. Tried also three other microsd cards, one of them works perfectly with Samsung GT-S5830. Made fat32 partition only , ext4 partition + fat32, a few combinations.

I used "usb unbrick" in 4EXT recovery, changed it also to clockworkmod 5 touch, it doesn't work there, too. Further in 4EXT: if i choose "partition sd card", it shows "There are 0MB of space on your sd-card"

Flashed radio one more time to make sure it's ok.

I can still use my phone, but only to write a message, make a call or browse the net... No more functionality, because most of the applications were on the card.

Any ideas, what can I do now?

\\one sign that gives a hope: if I open bootloader, there are green messages about looking for PB99IMG.zip. If I remove the card, they don't show
[Desire Q&A, Help & Troubleshooting] jmcclue:
probably faulty sdcard, try another.
[Desire Q&A, Help & Troubleshooting] d4mian:
hey, I tried four.
[Desire Q&A, Help & Troubleshooting] kubiseg:
, Hi, I've been facing this issues while my Desire works in Safe Mode... Do you have any problems with hardware buttons? Try to boot while holding the MENU button until the phone is fully loaded. Hope will help
[Desire Q&A, Help & Troubleshooting] d4mian:
No problems with hardware buttons... Holding MENU booted my phone in Safe mode, but it didn't help.

Hm, at the end of 4EXT loading there's message "Booring safe mode", but I don't know whether it's related with your safe mode.

\\\okay, it works now. Basically no idea, why. Haven't done nothing new...
[Desire Q&A, Help & Troubleshooting] hbsyhjf:
I also met this problem , and solved it with this solution.

By the way ,I am using "4ext recovery touch v1.0.0.5 rc9".
[Desire Q&A, Help & Troubleshooting] jarojetu:
What is the size of your SD? I had the same problem even with 32GB size. Same vendor, same class, 16GB working fine...
[HTC One S] Lirankn:
I dropped my phone a couple of times and while the screen and the back remain undamaged, the sides and the top all have some small damage made to them..

Now it's not something that many people would like to get fixed since it's not that noticeable, but since I really like this phone I want it to look as new as it looked at first.. Is it possible to just replace the frame itself?

Thanks
[HTC One S] djsubtronic:
http://xdaforums.com/showthread.php?t=1856427
[Galaxy Note II Q&A, Help & Troubleshooting] cswithxda:
Hello people!

Looks like I might have become the first in the U.S. to experience the SDS issue, at least among those who attend this forum regularly? Because I searched and searched, read and read, and could not find a single sign that anyone in the U.S. has experienced this SDS issue and filed a warranty claim to someone/somewhere. I contacted Samsung USA and they said this device is not supported and they're not trained to provide the support to me, and directed me to their international website... I had not luck with their international website either, so I contacted Amazon seller who I bought my N7100 from. And they have not replied in the past couple days...

So I wanted to see if anyone here has imported his/her n7100 into the U.S. and happened to encounter any issue with the phone and successfully filed warranty claim against Samsung. If so, how can that be done?

Worst case scenario, I pay to repair n7100 in the U.S., who should I go to? Or do I have to send the phone overseas either way?

Many thanks in advance.
[Galaxy Note II Q&A, Help & Troubleshooting] cswithxda:
bump for help please :crying:
[Galaxy Note II Q&A, Help & Troubleshooting] dsims7_2000:
I did not import my phone, I got it from Sprint, BUT..................given the choice, ship it back to Korea for Warranty!!! Have you ever a conversation with repair tech's in most mobile shops here??? And even with TEP they will give you every excuse how YOU messed it up or dropped and and your claim is denied.

If you send it back and likely they will get you someone that actually BUILDS the note's, original part, or give you a brand new (not referb) Note!!

This is JMO! Good Luck!!
[Galaxy Note II Q&A, Help & Troubleshooting] cswithxda:
Thanks for your reply. However, who would I contact before I ship it to Korea? I'd guess I'll have to have Samsung open an RMA for me or something?
[Galaxy Note II Q&A, Help & Troubleshooting] BABAK236:
Hi

if you have N7100 SDS,,Usually You Need Replace eMMC....

I Have and i can replace eMMC ,,,Please Read :http://forum.gsmhosting.com/vbb/9306319-post324.html

i'm product manager on RIFF-Jtag Box and I can do it,,,Plz Contact Me Via eMail or Sonork

babaknuri@gmail.com

Thanks
[Galaxy Note II Q&A, Help & Troubleshooting] cswithxda:
Thanks for the info. How much do you charge for the repair though? Also, where am I gonna send it to? Your location shown under your name or did you implicate (if you implicated at all) that you have stores in the U.S.?
[Galaxy Note II Q&A, Help & Troubleshooting] clearday:
How long have you had the phone? Is it within 30-day return period? For return/replacement reasons I only buy items from Amazon that are Prime Eligible even if the non-Prime ones are dirt cheap.
[Galaxy Note II Q&A, Help & Troubleshooting] cswithxda:
I wish! :crying: I've had it for well over 5 months. It wasn't prime even tho I do have prime membership, because at the time I bought it, only ones available are from all kinds of importers/sellers that sell THRU amazon. Even though it's prime (fulfilled by Amazon), im not sure if it's Amazon that you can contact for warranty claim after 5 months, because it is not sold by Amazon but only "fulfilled".

It's unlucky to say the least. It is essentially "mistake by mistakes" made by me. I shouldn't have assumed that there should be no issue like SDS on an Samsung device; I shouldn't have assumed that if something happens, it's easy as a breeze to just call Samsung UK to get things fixed; I shouldn't have assumed that the seller I chose on Amazon is willing to help me if Samsung UK and Samsung USA kicks me back n forth; etc etc...

Bad assumptions, bad luck.

If anyone had any experience with this, please please help me :good:. I swear I'm not gonna be so trusting next time. I will buy from a seller that's known to be helpful with their customers' warranty claim, i.e., expansys. I would even buy a carrier subsidized phone just for the sake of the proper support. I thought the worst case with this dead phone for me was to pay high bills to fix it and sell it to cover partial cost, but now it looks like the worse case is that I don't know where to go to fix it...