yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] nuramohammed26:
You did everything for me and i really appreciate it,at times i wonder how some people could be very nice and Helpful,God bless you.....but it is already late,i instal AllianceRom RE through odin,then i flash AllianceRom 3.4.1 EE through CWM with wipe but phone still lags and crashes so i decide to go back to ICS but during the final flashing with Odin,the phone finally BRICKS. It refuse to switch on,it refuse to enter download/recovery mode and it also refuse to show battery icon when i plugged it to the charger.i guess i was not patient enough to wait for your guidance, nevertheless i love you for your help and concern:D
[Galaxy Note GT-N7000 General] hg42:
Gingerbread kernels are safe.

Also cm9 derived kernels

I would recommend Abyss and thor (see first post )or anynon ics kernel
[Galaxy Note GT-N7000 General] hg42:
Odin cannot mmc_cap_erase brick your phone

So it should be a soft brick

You should find enough instructions for this kind.

I think, you should try an USB JIG to get into download mode, if you cannot get into by the three finger grip
[Galaxy Note GT-N7000 General] nuramohammed26:
i already sent it Samsung service center:(maybe i can get my phone back in the next two or three weeks:eek:
[Galaxy Note GT-N7000 General] sabiq:
Superbricked

hey ,,, isnt this the same guide as given by " Forest 1971 " ,,,

My phone is superbricked,

should i follow the full manual method given by forest1971 ,,,,, or is ths some kind of shortcut method ,,,,

Thank you
[Galaxy Note GT-N7000 General] hg42:
(if you got to this page from the android.gs thread, you should restart reading from the first post, because there you find all the important information)

I think forest1971 and I did the same method at the same time, so it's more or less the same. Later I developed those PIT files, which I think are a lot easier to use for the average user.

you simply follow these steps (in short, please read the first post):

* flash PIT

* install system

* wipe data

* format internal SD

so you don't need adb and you don't need to copy a parted binary etc.

Naturally, with adb and parted etc. you have far more possibilities, if you know how to use them and you understand the principles of this method:

* retain the partition numbers, so all software treats them as before (mounts), 9=system=factoryfs, 10=data=datafs, 11=internal-sd=ums

* leave other partitions untouched (all partitions <9 and 12=hidden)

* retain the partition sizes, so flashing images to them with Odin works as before

especially you can workaround other cases, my current PITs only work for system and/or data bricks, but you could eventually also work around additional ums bricks etc.
[Galaxy Note GT-N7000 General] sabiq:
My phone certainly gets stuck on Factoryrys and when i try to install zip from sd card it shows [ E: can't mount /emmc/ ] ,,, it is a superbrick ,, u myt even know but which method should i now use according to u ,,,

thank you
[Galaxy Note GT-N7000 General] hg42:
I would first try the PIT method with one of the two standard files ("patched" without "regain", for 16GB or 32GB SGN)...

I created those PITs to make repartitioning easier for average users. If you have further wishes you have to manually repartition with parted etc.
[Galaxy Note GT-N7000 General] mrcasmir:
I have decided to return this phone

I have done these

Reset flash counter with Triangle away

I will set it back to original partition mapping

flash a stock ROM

but my problem is whenever I go into recovery mode, I get

# MANUAL MODE #

-- Applying Multi-CSC...

Applied the CSC-code : XME

Successfully applied multi-CSC

Who knows how to get rid of that?

And is there any other step that am missing just so Samsung will not see any traces as to what I have done?
[Galaxy Note GT-N7000 General] petevo:
I had used ur Q1_20110914_16GB-patched.pit w stock GB. Then factoryfs ran smooth again. But then got stuck at recovery...so i choose wipe cache n then wipe partition. Went back to download mode n installed GB again through Odin3 v1.85. And wallah! My SGN came alive again. Checked storage, now my SGN is with 8.24GB...Thts fine w me, I could install all apps n move them to ext SDcard. Cn opt for 8, 16 or 32GB if its insufficient. At least I got it to work again Thx to u hg42 sir! Thank you sooooooooooo much!
[Galaxy Note GT-N7000 General] murattiy:
hi

please , tell me step step

firt step : best pit ?

secont step : rom flash (odin or cvm )

bla bla

my devices new part (281-6362 bad block )

Number Start End Size File system Name Flags

1 4194kB 25.2MB 21.0MB ext4 EFS

2 25.2MB 26.5MB 1311kB SBL1

3 27.3MB 28.6MB 1311kB SBL2

4 29.4MB 37.7MB 8389kB PARAM

5 37.7MB 46.1MB 8389kB KERNEL

6 46.1MB 54.5MB 8389kB RECOVERY

7 54.5MB 264MB 210MB ext4 CACHE

8 264MB 281MB 16.8MB MODEM

9 6362 7255 893mb ext4 FACTORYFS

10 7255 MB 9402MB 2147mb ext4 DATAFS

11 9402MB 15.2GB 5798mb fat32 UMS

12 15.2GB 15.8GB 537MB ext4 HIDDEN
[Galaxy Note GT-N7000 General] nuramohammed26:
@hg42 now that i ve already sent my Gnote to Samsung service center and the custom Binary counter before the phone bricks is around 22 or 23,do you think they will not repair it under warranty? and about the bad blocks in the UMS, is their a way to repair it with a JTAG?
[Galaxy Note GT-N7000 General] mrcasmir:
lwkmd-seriously, you sent your Gnote with custom binary and with the counter up, sorry but they will not fix it. The correct procedure is, have issues, hop onto XDA and look for a solution, if there is no solution here just reverse all your steps just so its not traceable by Sammy technicians. When you get it back, you can come back here and use this alternative unless if you want to pay them for the repairs which would be almost the price of a new Gnote.

My advice, go and get back your Gnote from them just to save yourself that 3-5 wks it takes them to deal with warranty issues.
[Galaxy Note GT-N7000 General] nuramohammed26:
@mrcasmir The problem is that the Gnote refuse to switch on,enter recovery/download mode or even show the battery Icon when i plugged it to the charger.
[Galaxy Note GT-N7000 General] mrcasmir:
Well u should have used the jig to enter bootloader now that you have sent it to them, they will use it and then see that you have custom binary in it.
[Galaxy Note GT-N7000 General] nuramohammed26:
am in deep ****,just bought the note new and use it for 5 days
[Galaxy Note GT-N7000 General] mrcasmir:
Just pray the jig will not work on it else you gonna have to pay for the repair which is almost like the price of new one or they will return it to you unfixed.
[Galaxy Note GT-N7000 General] nuramohammed26:
I hope so,i saw it somewhere that JIG will not work but am not sure:( i will check again and pray so
[Galaxy Note GT-N7000 General] nuramohammed26:
Who ever took his Gnote after bricking it to Samsung service center(under warranty) while on a custom rom due to eMMC problem should please share so that people like me can actually have a rest of mind.
[Galaxy Note GT-N7000 General] hg42:
Please don't ask this kind of questions via private messages.

Anyway I will answer publicly, if it's of public interest.

please read all posts, I wrote some simple steps already for some people in the thread. Sorry, I cannot repeat myself all the time...

However, if you don't understand something, please ask.

(but in your case my PITs don't seem to fit, so please read on below...)

As I wrote multiple times, there's no best PIT for everyone.

Start with the "patched" PIT without "regain", use 16GB or 32GB according to your phones (internal) memory (you may find it on the back of the sales packaging at the top left corner).

(but again read on below...)

hmm, what do you mean by that? did you already repartition the phone?

Or is this what you want to get after repartitioning with one of the PITs?

The standard scheme is like this:

...

8 264MB 281MB 16.8MB MODEM

9 281MB 1174MB 893MB FACTORYFS

10 1174MB 3322MB 2147MB ext4 DATAFS

11 3322MB 15.2GB 11.9GB fat32 UMS

12 15.2GB 15.8GB 537MB ext4 HIDDEN

so, looking at your new partition table, I assume, you had bad blocks in your former UMS partition, too. I did not generate any PIT for this case mainly because this would be too many PITs to cover all cases.

If there is more interest in it, I could generate some more PITs but with a bigger step. I used 100MB steps for "regain", I would use 500MB or 1GB for the other case.

As you have already calculated the partition scheme, I think you should manually repartition with parted in recovery (by following forest's method in his thread), if you didn't do this already.

If you already repartitioned, there is no need for a PIT.

Or didn't your new scheme work for you? Then, what problems do you get?
[Galaxy Note GT-N7000 General] hg42:
(another private message of public interest, sorry for publishing it here)

I assume you did a stock samsung firmware update? Or did you already use Odin (or Heimdall)? Did you have ICS before? Why do you think you could have a brick? Note, this kind of brick doesn't occur as long you don't use some kind of ICS firmware, Gingerbread didn't have the problem.

If you used samsung update, I would first download an appropriate firmware from samfirmware (please click on the correct model in "models" section).

Then you need a multi part firmware with a CSC.

Then I would try to flash the CSC file. If this gets stuck (but wait 10 minutes or so), you may have a bricked partition (again: only, if you ever had a kind of ICS on your phone).

Unfortunately, I have no experiences with CSCs, so I don't know where this is stored. I read somewhere it's files live in cache.img, but because the cache partition is cleared all the time, this should only be a temporary place.

Can anyone shed some light on this?

Other things to try:

You could flash a complete firmware via Odin.

You could try to use adb in a good recovery (CWM.zip, thor kernel+recovery, you need one with some tools in it's /sbin directory) to check the partitions.

On ext4 partitions you can try commands like

e2fsck -c /dev/block/mmcblk0p9

You can also read them byte for byte (which works for all partitions) with a command like this:

dd if=/dev/block/mmcblk0p9 of=/dev/null

in both cases just use the right partition numbers.

(please note, you should know what all this means, else you could easily do bad things to your phone, especially never use the partition path in the of=... part, this would write bytes to the partition)

If a partition is checked or read completely without error, it should be ok.

Otherwise you can have

* soft errors (correctable by formatting the partition or flashing an image to it via Odin, but note that you shouldn't simply format if you don't have the right content for it, and please never format the EFS and SBL partitions) or

* hard errors (shouldn't be correctable, so you would have to circumvent them by an appropriate partition table).

What to do next depends on the results
[Galaxy Note GT-N7000 General] hg42:
(another private message of public interest)

You can flash via Odin without having root.

(note, if you flash a custom kernel you will probably increment the counter -> yellow triangle + loss of warranty).

Sorry, I don't know anything about the jtag box, perhaps you can tell me, what you can do with it?

Does "3GB loss" mean, you already have a new partition scheme?

Then you wouldn't need my PIT files.

Rooting a Gingerbread ROM is a bit tricky and I'm no more up to date with that. I think you have to go back to an older ROM, then use the zergrush exploit.

Rooting an ICS ROM is much easier, but you need a safe kernel anyway.

Instead I would use some ICS ROM or ICS kernel which doesn't have the mmc problem.

E.g. you could install CM9. Or install stock ICS together with an alternate kernel (speedmod, franco, thor etc.). Look there for instructions how to install.

Just never flash (or restore or format or wipe) via recovery or wipe in any way while having a stock ICS or pre-ICS kernel running to prevent a brick.
[Galaxy Note GT-N7000 General] Djezpur:
Life saver!

hg42, thank you so much for this solution!!!

Just bought a Note yesterday and already managed to super-brick it the very same evening by inadvertently trying to wipe data in ClockWork Mod - I should have known better, I know.

Small question, Samsung is saying they're working on a new ROM without the firmware bug. Will this eventually restore the damaged blocks, or are they gone forever?
[Galaxy Note GT-N7000 General] Morality:
Hello hg42 and thanks for all if your hard work on this issue!

I am currently in a situation where I've been fighting with the note for weeks now - originally brought it back to life with the manual repartitioning. However, after several manual repartitions and many attempts with your pit files, I am still stuck with the issue I've had ever since the first repartition: Random freezing of the phone. Also, a new phenomenon occurred when using your pits: my internal sdcard is unmountable. Changing mount points to/from /sdcard and /emmc was of no help.

Due to my current life situation, i am unable to battle the bug constantly, so I will be going head to head with it probably tomorrow evening and I have a few questions to help me go on with it.

Firstly, does the e2fsck -c do anything else to the partition than filecheck? Can I run it on, for example, modem partition with it still being ok?

Second, I briefly read you mentioning another partition check method, cc in the front and /dev/null in the end, whats that about? Would you recommend it instead if e2fsck?

Third, do you have any alternate theories to the random freeze issue than undealt-with bad blocks?

Lastly, any other suggestions regarding investigating/fixing this issue? I am quite stubborn on fixing this and will damn sure report back in case I succeed, for the joy and possible usefulness of others.
[Galaxy Note GT-N7000 General] poserw6815:
Hello, Could you make one more pit offset file, but with an offset of 6 gb and not 3? I have a big problem ..
[Galaxy Note GT-N7000 General] baz00ka:
Hi, sory i m kinda confused a little bit... Can anyone plz explain to me in noobish words wat exactly i have to do to mke my note working again?

From wat i understand is tht all i need to do is download the pit file from page 1 and using odin i flash it , ryt?

So my question is tht there are so many pit files in there, which one shud i use? And also where do i put this file in odin? PDA or Phone? Also any other options he ked/unchecked? E.g repartition option etc

Kindly reply anyone plz... Thank u
[Galaxy Note GT-N7000 General] hg42:
wow, that's really fast...

I am pretty sure that these damaged blocks cannot be repaired with normal software. They may eventually be repairable by some special JTAG equipment, but not the usual but for the emmc chip (internal flash memory). But I was told it would need too much time, so changing the motherboard is cheaper.

So if you don't make use of your warranty (after deleting all traces of custom software), you would have to live with the bad blocks.
[Galaxy Note GT-N7000 General] hg42:
sorry for answering late, my time is currently very limited...

1. e2fsck -c would(!) build a bad block list in the file system, so the file system doesn't use them afterwards. But with the brick e2fsck will hang when reading the bad blocks, so never gets far enough to write a block list.

Creating a bad block list will not harm, so it can be used for undamaged partition, too.

e2fsck can only handle ext2/ext3/ext4 partitions, which you can see with parted DEVICENAME print:

1 4194kB 25.2MB 21.0MB ext4 EFS

7 54.5MB 264MB 210MB ext4 CACHE

9 2168MB 3062MB 893MB ext4 FACTORYFS

10 3062MB 5209MB 2147MB ext4 DATAFS

12 15.2GB 15.8GB 537MB ext4 HIDDEN

2. I assume you meant "dd"?

dd is a standard unix program to copy a stream. Streams can also be any files in a unix system, which includes block devices and partitions. So you can also stream the raw partition to /dev/null (which means into nowhere land, nirwana). dd if=PARTITIONFILENAME of=/dev/null will only read from the partition ("if" = "input file") and copies it to nowhere ("of" = "output file").

The point of dd for checking the blocks is, that you can use it for any kind of partition, including fat32 (sdcard/UMS) and yaffs2 (the other internal partitions), because it works on byte level.

3. hmm, which random freezes?

If you have random freezes (you mean complete freezes, the whole system not usable?), this could have many causes, including undervolting, overclocking, bad root apps, etc. If you get them you have to analyse the situation.

A unix system isn't easily killed. E.g. cannot do it from user software.

If it's only the gui, you are often able to access the system via network. You could install and run a ssh server (QuickSSH) and try to connect to the phone via ssh when a freeze occurs. I always have system-settings/developer.../kill-app-back-button enabled in cm9, so I can force close a forground app by long pressing the back button.

4. first try the dd commands for /dev/block/mmcblk0p9 to ...p11 to be sure if it's a emmc brick or not.
[Galaxy Note GT-N7000 General] hg42:
well, if you don't understand what I wrote in the first post, you will probably be on higher risk with the operation.

At first, you have to be sure it's this kind of brick. E.g. there are many other bricks, which may look all similar for you. So checking the partitions is mandatory.

Second, there is more than one way to use this PIT method.

It mainly depends on what you are familiar with, so the method is kept on lower risk.

I also described some methods in the whole thread, you should read the thread first.

I am adding an update to the first post for some cleaner instructions for unexperienced users...please look there after some minutes...
[Galaxy Note GT-N7000 General] Morality:
No problem sir, I am glad you answered :) I'll write a report on what occurred sometime this evening.
[Galaxy Note GT-N7000 General] hg42:
please look at the new update section, named pit files for bricked ums partition
[Galaxy Note GT-N7000 General] hg42:
I recreated the pit files of the first post and sorted them into different zips.

You should use the pits*patched-standard.zip (and take the pit with the memory size of your phone).
[Galaxy Note GT-N7000 General] hg42:
I think, it's simply caused by reading or writing a damaged block.

The situation should be very different, depending on which blocks got damaged.

I didn't try to evaluate, but I assume the bad block areas are only small compared to the file system size (several kB?).

If their positions are in important areas like the main file system structures, their impact is fatal. But if they are in other areas (data areas for the file system, where the file data will be placed) they will only get in the way, when someone actually uses this data.

So, where are your bad blocks? at the beginning of system / data or somewhere inside?

Thanks, I didn't know this app.

I tried it myself and got a positive test result (which is definitely wrong). The test duration was about 3 sec, so it was certainly interrupted.

may be the ROM is a bit smaller (if the cause lies in the system partition) or you simply didn't get to the damaged areas.

I think modern file systems "walk" through the available space and do not overwrite the same area over and over. So it's kind of random if you get in touch with the bad blocks.

As a cm9 user, I don't know which ROM is derived from which base.

I think PA is based on cm9, right?

Are Kingdroid and Asylum based on stock?
[XPERIA X8 Q&A, Help & Troubleshooting] FueLiZ:
Hello everyone, so i think there was this kind of topic somewhere, but i can't find it. So anyone could give me HTC ime mod apk for mdpi compatitible with ICS? :) because hdpi isn't working for x8
[XPERIA X8 Q&A, Help & Troubleshooting] wilbso:
The keyboard?
[XPERIA X8 Q&A, Help & Troubleshooting] FueLiZ:
Yes, the keyboard ;)
[XPERIA X8 Q&A, Help & Troubleshooting] FueLiZ:
Sorry for double post, but I've managed to fix HTC IME keyboard for MiniCM9. I add the apk.
[Motorola Photon 4G] brandonfranck:
Can anyone host this? Or tell me how.
[Motorola Photon 4G] brandonfranck:
I have the apk.
[Motorola Photon 4G] moparfreak426:
attach apk link?......

#ICS-lessMotorolaElectrify, ThanksMotorolaForYourIgnorance
[Motorola Photon 4G] CCallahan:
Why not just snag from original thread?

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

Might remind peeps this is for those running ICS roms only.

**If you want to post it just select the "Manage Attachments" option when creating and add file.
[Motorola Photon 4G] moparfreak426:
dang locked bootloader! !!!!

#ICS-lessMotorolaElectrify, ThanksMotorolaForYourIgnorance
[Motorola Photon 4G] brandonfranck:
Thank Callahan.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Moschino02:
if so,

Does the unlock tool cab work on all wp7 roms?

just need some clarification? thanks
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Masterslice:
Only BTTF-Rom from XbMod/Yuki locks the SD Card, therefore you need only in this ROM the Unlock.cab.
[HTC Sensation] he_saw:
Hi, this morning i tried to update my Sensation 4G to ICS via OTA, i downloaded the update an everyting was fine, however when the phone reboots in order to install the update i get a screen with a triange and exclamation mark with the android logo. Does anybody know Why this is happening?

Thanks in Advanced
[HTC Sensation] realsis:
is your device rooted?
[HTC Sensation] he_saw:
Yes it is,
[HTC Sensation] NinetoFive:
Exact same thing happens to me.

Is it the root that's causing it or is it the bootloader not being stock?
[HTC Sensation] davebugyi:
It was told a million times (if not a billion) not to update your rooted phone via OTA :)

However this issue can be resolved easily - search Developement forum stickies for solution.
[Galaxy S II Q&A, Help & Troubleshooting] naveediftikhar:
Hey guys before my s2 time i was using v6 on my dhd n it was really effective...so has anyone tried it on s2 i ask as i dun see anyone using although it is a for all phone script!
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
I used the v6 supercharger script on my Motorola Milestone... but that phone only had 256MB of RAM.

The S2 has tons more memory, so I just left the default memory settings. Never once did I consider using v6 on it.

I don't see any reason why it wouldn't work though.
[Galaxy S II Q&A, Help & Troubleshooting] chrisgall:
I used v6 superchargher script on my previous rom...it is effective it made my s2 even faster!try it and see for yourself!
[HTC Amaze 4G] labiker:
is there a setting page for microphone on Amaze?

the microphone works for recording a video, not working when phone call, record a voice clip or voxer. actually on voxer, it is really low.

do I have a defective phone or some setting is not right.

stock rom, just updated to ICS, didn't really try before updates, just got the phone.
[HTC Amaze 4G] glacierguy:
LMAO... There's a volume rocker on side of phone buddy... Prolly a broken device
[HTC Amaze 4G] labiker:
what is that be funny about? volume is for microphone too.
[HTC Amaze 4G] ickedmel:
Pretty much the only way I know to adjust volume for phone calls is with the rocker button on the side. So you need to be like on a call then press the rocker button and it should adjust the volume for phone calls. As far as voxer I've never used that app but know the concept maybe there's a volume setting within the app. But if you continue with these issues maybe try a factory reset and reinstall everything, or maybe you do have a defective phone.

Sent from my HTC_Amaze_4G
[HTC Amaze 4G] ickedmel:
There's also some volume control apps on the market free, maybe you could give those a try.

Sent from my HTC_Amaze_4G
[Motorola Triumph] blackout720:
I tried all the fixes posed on Xda, sdx and every other site but i get the same problem when i put my GPS on, it things im in the middle of the ocean right under Africa. Kinda funny and when i go back to stock it don't pick a signal up at all i tried it in other locations and nothing. is anyone else having this problem? I read that it works for other people but nothing I tried other roms and I still don't get a gps fix on anything.