yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Chaosin1983:
Hi all...I need some help! I have been running ParanoidAndroid for a good while now, updating regularly...I updated to their latest version 3.15 released on 17th of April and everything was working fine until this morning. I woke up and saw that my phone wasa at the start screen (where it says Galaxy Note GT-N7000), so I tried rebooting a couple of times and the phone will not go past that screen.

So I tried to go to CWM recovery to clear cache, but I cannot go into recovery, it will either be stuck at the start screen or display just a blank screen.

Since I could not enter CWM nor the ROM, but I can go into Download mode I decided to go back to stock through ODIN and re-root and re-flash everything, so I downloaded the Germany JB TW ROM and tried flashing it, but ODIN hangs on NAND write and no progress bar is displayed on the phone as usual. I tried downloading it again thinking the download might be corrupted but I got the same results.

So I tried going back to the old stock GB ROM that came with the phone, and it has the same result, ODIN hangs at the same point. ODIN displays this:

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> factoryfs.img

<ID:0/007> NAND Write Start!!

Now i got worried...started reading around and concluded that my phone is bricked! I found this thread and tried to use the "2.0. Custom Pit that works for most cases of emmc brick", but it also hangs where it says DO NOT TURN OFF TARGET... tried the other custom Pit files from all the way up to 2.5...and they all hang. ODIN displays this:

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

So now is my only option to try to do the Manual re-partition? I just wanted to confirm with someone that knows about this since I had never experienced anything like this before, and I've been flashing customs ROMs for a couple of years now.

Thanks
[Galaxy Note GT-N7000 General] nokiamodeln91:
once try to run odin as admin, disable AV, use samsung original USB cable. reboot PC and phone to download mode. flash again. Use the original PIT file this time http://d-h.st/FVh.

i dont see anything you have done that could brick the phone.
[Galaxy Note GT-N7000 General] Chaosin1983:
Thanks for replying. I ran ODIN as admin, no AV, original USB cable, re-installed Samsung drivers, rebooted...and tried to flash the PIT file you provided...and it hangs as well in exactly the same part. (just to make sure, I flash the the PIT file by itself right? or do I have to flash along with the stock ROM?)

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!
[Galaxy Note GT-N7000 General] nokiamodeln91:
you flash it with the rom. set the pit in the PIT tab. make sure repartition is checked.. then select the rom in PDA tab
[Galaxy Note GT-N7000 General] Chaosin1983:
Oh ok... but it still hangs :(. Any other clue?

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> KIES_HOME_N7000XXLSZ_N7000OXALSZ_906407_REV02_user_low_ship.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!
[Galaxy Note GT-N7000 General] nokiamodeln91:
odin hangs here?

<ID:0/003> DO NOT TURN OFF TARGET!!

is that the full log?. this could mean there is no proper connection.. check if kies is running in task manager.. end process of kies. you have to reboot the phone into download mode for every flash. dont continue from the previous download mode.
[Galaxy Note GT-N7000 General] Chaosin1983:
Yup, that is the end of the log, I've left it like that for more than 30 mins, and no change. I don't have Kies installed on my computer, only the samsung drivers, so i doubt there is anything interfering with the communication. I've also tried rebooting the PC before flashing, and everytime I am rebooting the phone as well. I've never had problems flashing before :S. I've also tried several USB ports. Any other idea?

Thanks again for your help.
[Galaxy Note GT-N7000 General] nokiamodeln91:
the rom is not flashing on to the phone. try a different PC or try with a different version of odin like 3.07.. diff PC will be the best bet. also you could try uninstalling the usb drivers.. then install kies. let it install the dirvers.. then kill all kies from task manager use odin again. Win 8 might need updates drivers
[Galaxy Note GT-N7000 General] Chaosin1983:
I updated the drivers to the latest from Samsung, tried with ODIN 1.83, 1.85 and 3.07 and a different PC...everytime is the same :(. In my desperate need to fix this I tried flashing a Speedmod Kernel and apparently it was not safe to do so with ODIN and now I have a big nice yellow triangle on my phone :( I;ve been flashing my Note for almost two years without this happening to it :(... and now I can't even lie to Samsung in order to get them to look at it!
[Galaxy Note GT-N7000 General] nokiamodeln91:
you still can get into recovery after flashing speedmod? remove the usb cable from the phone. remove the battery. then put the battery back in press vol up+home+power till you see N7000 logo and leave the buttons and check what happens
[Galaxy Note GT-N7000 General] Chaosin1983:
Nope, I can't get into recovery because ODIN never finishes installing it, it hangs at "NAND Write Start", it is definitely not writing on the phone, yet I still got the yellow triangle, I tried it again and only upped my count, but I cannot get into recovery no matter what, without cable, changed batteries, tried to get into recovery and no luck...it will go into a blank screen...:(

Tried again with PhilZ-cwm6 - Safe Stock Based Kernel, and still cant access recovery, just got another binary count (3 now) :(
[Galaxy Note GT-N7000 General] nokiamodeln91:
even the kernel gets stuck in odin?
[Galaxy Note GT-N7000 General] Chaosin1983:
Apparently it is not writing anything on the phone AT ALL....everything hangs... yet it still affects the binary count :( is there a way to remove the triangle from ODIN or without accessing recovery or the ROM?
[Galaxy Note GT-N7000 General] nokiamodeln91:
I remember reading a thread to remove yellow triangle using jig. Check in general section. Could the usb port be the problem. Try cleaning it with battery out.
[Galaxy Note GT-N7000 General] Chaosin1983:
Yeah I read it too, but it assumes that I am able to flash things on my phone, which apparently I am unable to do :(.
[Galaxy Note GT-N7000 General] prince4p91:
Need help installing JELLY bean

forest man i need your help.

i'e installed JELLY bean ROMS tried every1 of 'em out there stock, AOSP, CM, etc.

but my GNOTE would keep freezing randomly on everyone of 'em.

please help me.

ya one more thing this happens mainly after i flash GAPPS (in case of AOSP and CM).
[Galaxy Note GT-N7000 General] forest1971:
Not sure I can be of much help. You just need to scan partition and make sure they are free from bad block. Then try to use som cm 9 or ics rom see if that work. Best.

Sent from my LT30p
[Galaxy Note GT-N7000 General] prince4p91:
so that means i'm stuck with ICS or CM9 (no JELLYBEAN for me).

SAD.
[Galaxy Note GT-N7000 General] forest1971:
You can continue to try different roms. I guess cm10 is a good one. Btw, I have move om to a new device so I'm not update on Note develoment. Best.

Sent from my LT30p
[Galaxy Note GT-N7000 General] claptnei:
I have exactly the same issue, just posted in the pit method thread about it.
[Galaxy Note GT-N7000 General] neier24:
After many attempts to find a good partition, even as tiny as 350 mb, still haven't made it perfect.

7: mkpartfs primary ext2 9258 9328 name 7 CACHE

9: mkpart primary 3750 4150 name 9 FACTORYFS

10: mkpart primary 8428 9258 name 10 DATAFS

11: mkpartfs primary fat32 14900 15100 name 11 UMS

I tried these... While the data partition has some non contiguous, and the factoryfs... the cache partition is causing me the most headaches. I've shrinked it even down to 12 mb... still freezes from times to times. I'm unable to scroll the web without freeze... programs i could instal, still have to watch out every few mb though
[Galaxy Note GT-N7000 General] forest1971:
Noncontiguous is not a problem. Just ignore it.

Sent from my LT30p
[Galaxy Note GT-N7000 General] neier24:
That cannot be... i don't have any other idea to what is making the problems. I flashed many times, on lot's of different partitions. I guess i have to try a different rom... my best guess is to try install a gb rom, while i tried slim bean for now.

Its good news then, ill make bigger partitions without worrying about contignuous
[Galaxy Note GT-N7000 General] forest1971:
Try an ics or cm9. In the hg42 thread someone report ica work perfectly for.him while jb does not.

Sent from my LT30p
[Galaxy Note GT-N7000 General] teamerx:
Does this fix the /efs ?

specially if you have no backup ?
[Galaxy Note GT-N7000 General] forest1971:
No.

The recover method does not touch the efs so it should be still there. in case you have lost it somehow, then probably have to flash a multi-part rom shared by dr.Ketan. http://xdaforums.com/showthread.php?t=1423514

It has efs folder and it will create a generic emei.

Also the XDA member cvxcvx provides a service to restore emei which is confirmed working for Note. cheers.
[Galaxy Note GT-N7000 General] grandcity89:
Hi everyone...

I was brick (superbrick, I guess) 3 month ago, and i had solves by a custom pit ... at that time my galaxy note didnt have any hang/freeze issues with JB rom(official/Custom), but this few weeks my phone starting freeze/hang ramdom... i am using same pit and i had tried to format everything/fullwipe but the problem still the same ...

anyone got this problem ?

@_@ Why last time didnt have this issues?
[Galaxy Note GT-N7000 General] forest1971:
Quite a few questions remain with no answers. Still, for your case, some people report they can use custom ics roms without problems, while jb roms cause freeze, after recover from superbrick. So that can be one option.
[Galaxy Note GT-N7000 General] grandcity89:
thank for reply and any solution?
[Galaxy Note GT-N7000 General] forest1971:
I would try a good ics rom. Cheers.
[Galaxy Note GT-N7000 General] grandcity89:
any good Custom ICS rom ?
[Galaxy Note GT-N7000 General] forest1971:
I move to a new device for a long time now. I remember ICS Clearnote or Rocket used to be good.ones. Guess will need to search to find them now.
[Galaxy Note GT-N7000 General] TheNoticer:
Stunner ics, cm 9

Gesendet von meinem GT-N7000 mit Tapatalk 2
[Galaxy Note GT-N7000 General] SammyBoyWonder:
I was bricked too but revived my note using the pit method. The phone worked fine, Then after a few months my phone started to freeze and hang randomly. I tried several different roms but nothing worked.

My phone was still under warranty so I eventually unrooted and sent it back to samsung. In less than 4 days they had fixed the phone and returned it to me. I'm not sure what exactly they did, but on the repair invoice that came back with the phone it said that the motherboard was rebuilt. I haven't had a single freeze/hang since. And that was about a month or two ago.

If your phone is under warranty. I strongly recommend you have it repaired. I think samsung have extended the period to 24 months now, but double check.
[Galaxy Note GT-N7000 General] grandcity89:
actually i bought my phone without register and my resit gone ...

i not familiar samsung mobile's warranty ...Some people said 24 months,but people who work in the service centre and they told me 12 months warranty only
[Galaxy Note GT-N7000 General] mrhooof:
help

i can install jb stock rom after abit repartetion but ia had alot of freezes when using wireless in rom

so i made another test

in first four tests every thing is ok

in the three tests it gave me

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

Free blocks count wrong for group #0 (2, counted=0).

Fix? yes

Free blocks count wrong for group #1 (1565, counted=1562).

Fix? yes

Free blocks count wrong (91305, counted=91300).

Fix? yes

/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****

/dev/block/mmcblk0p10: 7586/131072 files (12.4% non-contiguous), 432988/524288 b

locks

~ #

is there is any problame that ican fix

thanks alot for your supports
[Galaxy Note GT-N7000 General] forest1971:
It is a known issue that after reviving Note using repartition jb rom does not work properly anymore. Should use stock based custom ics or cm9 or cm10.
[Galaxy Note GT-N7000 General] jacobisrael:
How can i say my Greatest gratitude to your very supportive thread?

Mr. Forest, well i dont know your name so i just used ur username. i had superbricked my N7000 because i am new to rooting. well not that new because 2 years ago i rooted my X10i but this samsung device is different. i was so excited in flashing different ROMS on my note and because of my stupidity and lazyness in reading some guides, i flash an md5 ROM in recovery, and that had superbricked my note. i spent many days searching on how to unbricked it, well few sites has their own method but when i finally found your thread, it took me 2 days to do the workaround. i carefully read your instructions and followed all your guides, and thank God i was able to go to download and recovery method now. but still something is wrong because i cant flash any ROMS, Stock or Custom wont work so i also tried using the HG42 method and suddenly i was able to flash the slim bean Custom Rom. now, i am so happy coz stock or custom ROMS i can flash it victoriously. i only have 1 problem now, my note works fine but the emmc bricked bug check always say, i have an insane chip. anyway i am using a 32gb Sandisk 10 speed. i hope that wont do any harm to my device. please pardon me if i posted wrong because its my first time to post and comment here in XDA. Mr. Forest money i have none, but what i have is prayer for you and your family. thank you so much and may you have many more blessings to come. my Thanks to you....
[Galaxy Note GT-N7000 General] maddie77:
exynos-mem' bug issue urgent reply please

i have samsung galay s2, ICS installed on it. instead of showing its internal USB storage as 11Gb , its showing 4.11Gb. i installed an app called

"exynos-mem bug checker". it says "this device is affected by the 'exynos-mem' bug issue".

what is actually the problem ? and whats the solution ?

whats the best way to get my lost memory back ??

m much worried abt it ..because i recently bought it.

kindly reply asap :(
[Galaxy Note GT-N7000 General] :
well every note has the bug, but was it triggered, scan with same app to check if thats the case.
[Galaxy Note GT-N7000 General] forest1971:
The phone you bought probably has suffered from brick bug and was recovered using repartition. Probably you cannot get back the lost memory, and should use an ext sdcard to make up for it. You can also try hg42 scanner to check. Cheers.

Sent from my LT30p
[Galaxy Note GT-N7000 General] HTC Chris:
There was an issue with the latest nightly build not having recovery. I ran into this issue and all you have to do is

1.) Put your phone in download mode.

2.) Flash this via Odin http://d-h.st/JYC to get your recovery back.

3.) Once you have flashed that, your phone won't boot, but this is normal, since you just need recovery mode.

4.) Reboot into recovery and flash a previous build.

Also for the yellow triangle, just download chainfires app on the play store.

Hope this helps. :)
[Galaxy Note GT-N7000 General] forest1971:
I would go back to Dr Ketan's thread to get guide and tools for flashing to find solution there.

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

Hope you can find a way out. cheers.
[Galaxy Note GT-N7000 General] G0bble:
Hey Chris

It didnt work. Same story. No recovery mode. Whats the diff between PhilZ-cwm6-DDLSC-ODD-4.93.6-signed.zip and PhilZ-cwm6-DDLSC-ODD-4.93.6-signed.zip?

Gad! now its not even flashing after the last one ...

Initialising connection...

Detecting device...

ERROR: Failed to detect compatible download-mode device.

Edit download works now, after a reconnect.

Will try that now. First lemme go buy a new cheap phone to use for a few days while I fix this.(and also enquire about what Samsung will do to fix how much to replace a mobo .. in case ...)

Thanks again!

Edit: I am not allowed to post in that thread as a newbie to this forum :(

--G0bble
[Galaxy Note GT-N7000 General] G0bble:
New mobo, need advice

So I didnt get any useful advice over the last few days and I sent it to an unauthorised service centre. Getting the mobo replaced. Cost me about 100+ euros equivalent or 8.3K INR.

When I get it back I want to retry but I am afraid of bricking it again and screwing a brand new motherboard.

Can somebody clarify what the difference is between Kernel_CM10.1_Official_20130605_n7000_Exynos4.zip and PhilZ-cwm6-DDLSC-ODD-4.93.6-signed.zip? What do you recommend I flash the first time I boot into recovery mode?

The last time around I used PhilZ-cwm6-DDLSC-ODD-4.93.6-signed.zip and a gapps zip and cleared dalvik cache and wiped everything.Can I use CM10.1 official instead? Is my understanding correct that the 5 to 6mb sized ROM images only root an existing unrooted Android build? What do I install after that to be on JB 4.2 or 4.3 that is stable release and not a stock Samsung android? I couldn;t find anything that said stable above CM 9.1. Whats the difference between official and stable?

Guys please help clarify my doubts so I dont brick my phone again. The information on xda is too scattered to make sense of.

Thanks

--G0bble
[Galaxy Note GT-N7000 General] G0bble:
FYI - Got my note with a new mobo. Installed 10.1 RC1 for now.

Before the replacement, unfortunately I had run out of battery and could not go into download mode. An alternate battery which I thought was atleast 30% charged also did not work. So I had lost not just recovery but download mode as well and the idea of waiting a few days for the CM 10.2 bug fix that originally prevented recovery on my phone was forgotten. I suspect the unauthorized service centre also acted lazy and decided to profiteer from replacing my mobo rather than spend time debugging the phone. Maybe they even just decided that finding a new battery to boot it into download mode and attempt to re-flash was not worth their money. :rolleyes:

Moral of the story for new comers - dont upgrade on a whim and lark without re-reading update procedures. And always stay a few releases behind on the nightly releases ensuring it has no major bugs that are a show stopper. Or only do stable release installs a few weeks after release date in the hope that any nasty surprises are fixed. My phone would have been recoverable if I had waited a few days in troubleshooting and repairing the problem because it was rebooting initially and going into download mode. I guess I ended up making more mistakes (like flashing wrong image(s) recommended from other posts on other threads that I should have ignored) in my desperation and tearing hurry to fix it NOW. In the end I had to wait 3 days for service centre to repair anyways - 3 days that I could have put the phone aside, researched further and collected my thoughts on how exactly to fix the problem, which image etc., and possibly saved a lot of money, if not the time)

I wonder why the developers dont grey out or block the update from phone settings menu feature - when it is so dangerous and risky to brick your phone?

Happy Note'ing everyone. :)

--G0bble
[Galaxy Note GT-N7000 General] :
well, because what we do is not originally intended to be done, thats why.

Agree, it is something that could be managed better
[Galaxy Note GT-N7000 General] Sam322:
I have spent hours and hours looking for a solution. YOU SAVED MY N7000. Thank you so much! I am so happy right now :)
[Galaxy Note GT-N7000 General] Hassan_Elyas:
I flashed JonRom V14.5 last night and today morning when i woke up i saw my phone stuck at boot logo..i then flashed stock lt6,lt9,lt5 and i still cannot boot..its stuck at the logo and when i access the recovery mode i get this error (photo) i cannot access recovery mode it shows all this kind of error.

An hour back I flashed stock ics firmware and everything was fine..i then flashed xxlt6 firmware and i got the error again..why is that so?

ICS is fine but jellybean gives error in recovery.

Note : i accidentally wiped data on stock ics recovery/

Please. help.
[Galaxy Note GT-N7000 General] JulioQc:
Just wondering if the PIT files provided could work on the SGH-i717 version of the GNote?
[Galaxy Note GT-N7000 General] forest1971:
You need use efs pro tool, magic pit or adb parted to check if the stock pits are the same. If they are then the custom pits can be used

Sent from my phone.
[Galaxy Note GT-N7000 General] JulioQc:
Thank you for your reply.

I want to use PIT files because adb parted doesnt work (gives me error: "can't have a partition outside the disk") and also i've being searching forums/google but cannot find the method to "extract" the PIT file from my current device to then compare it as you suggested. Also, a guide to understanding PIT files would be nice, but that might be too much asking :o
[Galaxy Note GT-N7000 General] forest1971:
Efs pro has a function to get pit from phone with root. Then you can use pit magic to see if the pits are the same. You can find these tool in searching xda.

Sent from my phone.
[Galaxy Note GT-N7000 General] JulioQc:
Sorry, I should of specified the difficulties I encountered with EFS; the tool isn't capable to read the PIT file (get error msg) from the device and also only reads one partition from the mmcblk0 block. Im searching info to troubleshoot the problem.