Database Develop

Soft bricked N7000. How to?

Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.

Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)

I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?

btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.

True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.

Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.

btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?

N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han

choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you

mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium

I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]

[Q] newbie - HELP PLS - bricked?

Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty

strangermyself said:
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
First you should t have flash abyss through odin since now you are not rooted and do t have the warranty too, the counter of flashes increased to 1 (look at the download mode small text), for rooting you can use chainfire's tool (in the cf-root kernel thread look for it in devolepment section) next get a stock rooted kernel and flash using the tool (read instructions).
For now use pc odin 1.87 and get a firmware 2.3.6 use the pc odin select the file on PDA and flash it, make sure phone is charged 100% and press start, if it doesn't work then uninstall drivers, reboot machine, reinstall them and kill kies process if present in task manager and then goto download mode connect USB and open pc odin wait for the port to be ready aka green and select file then start.... you should be fine its a soft brick afterall.
Sent from my GT-N7000 using Tapatalk 2

Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.

strangermyself said:
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
Click to expand...
Click to collapse
When connected to charger make sure phone is off the battery meter will show as soon as you connect, case it doesnt leave it for like 3 hours is fine... next about that ROM redownload. The package cleanup you temp directories in PC and try again if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2

REVERSiN said:
... if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?

strangermyself said:
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444

Whiskeyjack4855 said:
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Click to expand...
Click to collapse
Dude its a GB rom not superbrick bug in it and he didn't mention LPY yet.
Sent from my GT-N7000 using Tapatalk 2

strangermyself said:
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
Click to expand...
Click to collapse
Sorry for tea doubled post its a dumb app X's
You wipe using the CWM file in the Iss root section, and a normal recovery wipe would do too (aka restore defaults)
Sent from my GT-N7000 using Tapatalk 2

Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help

strangermyself said:
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
Click to expand...
Click to collapse
If you have the stock recovery, restore default wipes everything.
If you have stock re every and want CWM temporary just to wipe goto n7000 devolepment and check how to root by dr.ketan and get files there
If you have CWM then wipe data, wipe cache, wipe dalvik.... and try. Old download another firmware like kk5.... something else not the new LC1 LX1 releases.... (Latest GB) get an old one to get root easly
Sent from my GT-N7000 using Tapatalk 2

[SOLVED] [Q] Galaxy Note won't flash original firmware

Hello guys!
My friend gave his Galaxy Note for me to get a brick fix. He said that he flashed the German ICS STOCK ROM and wiped using CWM. He said that he entered in a bootloop. Then he tried to flash using ODIN, but it stopped at factoryfs, as known at the eMMC bug. In the bug, he disconnected the USB cable and he is seeing a message which says to connect to Kies and select recovery. But he said that didn't worked and Kies didn't recognized the phone. Even with ODIN, loaded with PIT and PDA, the phone wasn't able to receive factoryfs, the same file from the 1st error. I followed a lot of tutorials here on XDA and used the search to find a similar thread. He needs help, since recovery mode, charging mode and normal mode are blocked by the message. I need a ROM which contains the PDA, the CSC and the MODEM files. I already have the PIT, so I need those 3 files to try again.
--PHONE DETAILS--
Samsung Galaxy Note N7000
16GB Storage
LAST Firmware completelly flashed: XXLRQ (I think that is the firmware which you can't wipe)
ICS Stock
Thanks!
EDIT: I tried with another GB firmware and with an ICS firmware. Still NOT WORKING.
EDIT #2: The phone still have Download mode open!
BIGGEST EDIT:
All of the methods in this thread are NOT WORKING. Still stops at factoryfs and CWM says "Installation Aborted". SO, WHAT I CAN DO? He is desperated, I'm desperated. PLEASE ANSWER FAST !!

Mr.Indigo said:
Hello guys!
My friend gave his Galaxy Note for me to get a brick fix. He said that he flashed the German ICS STOCK ROM and wiped using CWM. He said that he entered in a bootloop. Then he tried to flash using ODIN, but it stopped at factoryfs, as known at the eMMC bug. In the bug, he disconnected the USB cable and he is seeing a message which says to connect to Kies and select recovery. But he said that didn't worked and Kies didn't recognized the phone. Even with ODIN, loaded with PIT and PDA, the phone wasn't able to receive factoryfs, the same file from the 1st error. I followed a lot of tutorials here on XDA and used the search to find a similar thread. He needs help, since recovery mode, charging mode and normal mode are blocked by the message. I need a ROM which contains the PDA, the CSC and the MODEM files. I already have the PIT, so I need those 3 files to try again.
--PHONE DETAILS--
Samsung Galaxy Note N7000
16GB Storage
LAST Firmware completelly flashed: XXLRQ (I think that is the firmware which you can't wipe)
ICS Stock
Thanks!
EDIT: I tried with another GB firmware and with an ICS firmware. Still NOT WORKING.
Click to expand...
Click to collapse
He did successfully bricked his devices.. If you are not able to enter into download mode you have a paperweight in your hands... If he has warranty try to get it replaced.. If he doesn't then try the pit file method on the general forum..
You don't need any 3 files.. It's the same or at least the effect its the same with 1 or 3 files
Tapatalking on my n7000

msedek said:
He did successfully bricked his devices.. If you are not able to enter into download mode you have a paperweight in your hands... If he has warranty try to get it replaced.. If he doesn't then try the pit file method on the general forum..
You don't need any 3 files.. It's the same or at least the effect its the same with 1 or 3 files
Tapatalking on my n7000
Click to expand...
Click to collapse
He is able to enter into DL mode. Even PIT doesn't work.

Mr.Indigo said:
He is able to enter into DL mode. Even PIT doesn't work.
Click to expand...
Click to collapse
Well then your only option its the warranty or pay samsung either for a new phone or a mother board replacement...
That pit file method its only a partial solution to help you get your device partially working maybe a couple of months.. When the emmc bug happens it does damage the Emmc chip so the hardware its fried and there's no software that can repair it..
The pit method could work for someone but not for others.. Depends on the damage
Tapatalking on my n7000

Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!

andreaonelove said:
Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!
Click to expand...
Click to collapse
I tried it, but didn't work. This solution is too much dangerous?

andreaonelove said:
Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!
Click to expand...
Click to collapse
It's doesn't matter if it's 1 or 3 files.. The pit file just repartition the emmc in order to reacomodate the memory and so you can flash the rom.. Flashing separately phone csc and PDA won't make any difference..
Tapatalking on my n7000

Have you tryed to flash a GB ROM with three files?
And the solution proposed here?

andreaonelove said:
Have you tryed to flash a GB ROM with three files?
And the solution proposed here?
Click to expand...
Click to collapse
Mr.Indigo said:
Hello guys!
My friend gave his Galaxy Note for me to get a brick fix. He said that he flashed the German ICS STOCK ROM and wiped using CWM. He said that he entered in a bootloop. Then he tried to flash using ODIN, but it stopped at factoryfs, as known at the eMMC bug. In the bug, he disconnected the USB cable and he is seeing a message which says to connect to Kies and select recovery. But he said that didn't worked and Kies didn't recognized the phone. Even with ODIN, loaded with PIT and PDA, the phone wasn't able to receive factoryfs, the same file from the 1st error. I followed a lot of tutorials here on XDA and used the search to find a similar thread. He needs help, since recovery mode, charging mode and normal mode are blocked by the message. I need a ROM which contains the PDA, the CSC and the MODEM files. I already have the PIT, so I need those 3 files to try again.
--PHONE DETAILS--
Samsung Galaxy Note N7000
16GB Storage
LAST Firmware completelly flashed: XXLRQ (I think that is the firmware which you can't wipe)
ICS Stock
Thanks!
EDIT: I tried with another GB firmware and with an ICS firmware. Still NOT WORKING.
EDIT #2: The phone still have Download mode open!
Click to expand...
Click to collapse
I have the same problem!!!
I'm desperated, since it's my main phone!
I will try the last solutions!!!

andreaonelove said:
Have you tryed to flash a GB ROM with three files?
And the solution proposed here?
Click to expand...
Click to collapse
That's what I need.... I didn't found the 3 files. I will try!

andreaonelove said:
Have you tryed to flash a GB ROM with three files?
And the solution proposed here?
Click to expand...
Click to collapse
This solution is based on a GB kernel. I'm in the same situation as Mr.Indigo, with the same ROM and the same problems. I need to use CM9 kernel to use with ICS, right? Or I can use GB kernel?

Aldenucci said:
This solution is based on a GB kernel. I'm in the same situation as Mr.Indigo, with the same ROM and the same problems. I need to use CM9 kernel to use with ICS, right? Or I can use GB kernel?
Click to expand...
Click to collapse
IDK, you must do it at your own risk.

andreaonelove said:
Here I think you may find a solution for your problem.
If you think you need to flash the 3 files with odin try flashing an old GB ROM, you can find it here, some (NOT ALL) of the ROM in this post has PDA, CSC and PHONE part.
Good luck!
Click to expand...
Click to collapse
I tried this solution. The cellphone starts to make strange noises and a lot of characters entered in ADB command. Any other solution??

Mr.Indigo said:
I tried this solution. The cellphone starts to make strange noises and a lot of characters entered in ADB command. Any other solution??
Click to expand...
Click to collapse
Yeah already told you.. Walk to the nearest samsung center and claim the warranty or pay for a replacement
Tapatalking on my n7000

unfortunately sound like a brick to me. failed flashing via pc odin and stuck at factoryfs has something to do with your root. so i heard.. the best way is to send it to SSC for repair while you still have the warranty

msedek said:
Yeah already told you.. Walk to the nearest samsung center and claim the warranty or pay for a replacement
Tapatalking on my n7000
Click to expand...
Click to collapse
He didn't have warranty. I'm trying to flash any PIT which owns factoryfs. He said that fails to wipe into some minutes and I have 88 factoryfs PITs. So I have to flash ALL of them to know. BTW I can flash a kernel using ODIN!

mistajoe83 said:
unfortunately sound like a brick to me. failed flashing via pc odin and stuck at factoryfs has something to do with your root. so i heard.. the best way is to send it to SSC for repair while you still have the warranty
Click to expand...
Click to collapse
My problem is SOLVED!
I found 88 PITs, whick it was intended for factoryfs. I tried the first ten PITs, and the 7th WORKED!
It was 17xx MB. Now the phone is working! THANKS FOR ALL OF YOUR GUYS HELP!

[Q] Soft Bricked N7000

I was trying to install Ultimate_N7000_LSC_JB_4.1.2_v5.1 on non-rooted device.
After booting into Recovery and installing CWM, i tried Data wipe/Factory reset.
(Battery was 100%)
The screen switched of suddenly and now i am stuck.
Here are somethings i have tried:
1) Tried flashing N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 using ODIN. Never goes beyond NAND flashing (Tried in Admin mode, with ODIN Mode)
2) Tried flashing cm-9.1.0-n7000 and had status 0 and status 7 error many times.
Most of the flashing methods mention : "wipe data/Factory reset". Whenever i do that, i get stuck in "Wiping Data... .Formatting /data"
I have tried "Fix permissions", it wont work.
I didnt take a ROM backup and now i really regret it.
Currently when i navigate using CWM i can see all my internal as well as external memory files. So, i guess my OS is gone and files are still there.
The Custom Rom Counter says: Yes (Count 4) in ODIN mode.
Can someone help ? Please i am desperate.

What rom you on before flashing?..GB or ICS?
Sent from my GT-N7000 using Tapatalk 2

ICS 4.0.4
I had not done any Modifications, rooting to my N7000 before yesterday.
Would like to go back to Any ROM.
Unrooted ROM (ICS 4.0.4), Leaked JB Rom, CM9, CM10. Any ROM. Just want to get my phone up and running

What error do you get when flashing with Odin?
Does it stop at "factoryfs.img"?
How did you install CSM on your stock Rom ICS 4.0.4?

Your "soft bricked" sounds more like "super bricked" to me.. Did you use CWM.zip to wipe?
Tapatalking on my n7000

Yes. I used CWM.zip.
But now that my phone is not working, how do know what is the firmware version?
(http://forum.xda-developers.com/showthread.php?t=1656635)
Can you tell me the exact file names i should use
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
What does xxxx stand for? I have the Serial No. of my phone. And have done normal OTA updates only.
Brought from flipkart in August (if it helps narrow down the xxxx)
Superbricked or soft, please help.
Just downloaded some CWM file (Sorry i searched a lot, i couldnt remember the source)
Here are the steps:
Flash it with Odin 1.85, (Click PDA, choose the file and press Start)
After this you will have Root on your phone.
Now you can go into CWM and flash the Rom.
1) Download Ultimate XXLSC Jelly Bean 4.1.2 custom ROM for Galaxy Note to the PC
2) Connect the device to PC using USB cable and transfer the downloaded ROM zip file to the phone's SD card
3) Unplug the USB cable from the phone and then turn it off
4) Enter into Recovery mode by switching on the phone while pressing and holding Volume Up, Home and Power buttons together
5) In CWM Recovery, perform a full data wipe
Here is where it suddenly stopped and the screen went blank. (I am double sure battery was 100%)
Thanks for the prompt replies

Yup..its a wrong way to flash costum rom on stock ics...
try flash stock rom using odin, if its stuck on "factoryfs.img".. I'm sure your super bricked your phone..
Sent from my GT-N7000 using Tapatalk 2

zai89 said:
Yup..its a wrong way to flash costum rom on stock ics...
try flash stock rom using odin, if its stuck on "factoryfs.img".. I'm sure your super bricked your phone..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
ok. But please help me. How to take it out of super-brick.
In ODIN it gets stuck in "NAND write start"
I already tried flashing Stock ROM N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 in ODIN and it gets stuck in "NAND write start"
I found this post. http://forum.xda-developers.com/show....php?t=1656635
Should i follow this?
Can you tell me the exact file names i should use
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
What does xxxx stand for? I have the Serial No. of my phone. And have done normal OTA updates only.
Brought from flipkart in August (if it helps narrow down the xxxx)
(Thanks in advance)

If you have warranty then claim it.. Super brick means that the emmc chip it's burned.. There's some methods to get it to partially work but you lose around 3Gb of memory and generally you can not use TW roms.. Or at least stock TW.. Not to mention the random reboots and freezes..
So most likely if you don't have warranty then use the pit file method or pay for a motherboard replacement..
Tapatalking on my n7000

Thanks for the suggestion.
I managed to flash 4.0.3 ROM and stock Kernel and it somehow worked. (did too many things)
Here's the current status: Running 4.1.2 (XXSLO, ZSLM5). Unrooted and stock ROM. (Updated from 4.0.3 to 4.1.2 in kies)
Everything is back. The phone runs good. But when i try installing any software, it will freeze. The apk/app installs eventually but after 2-3 reboots.
Can you tell me the issue?
I read it somewhere that the "Cache" partition is damaged.
Can someone please tell me any way to avoid freezes.
msedek said:
If you have warranty then claim it.. Super brick means that the emmc chip it's burned.. There's some methods to get it to partially work but you lose around 3Gb of memory and generally you can not use TW roms.. Or at least stock TW.. Not to mention the random reboots and freezes..
So most likely if you don't have warranty then use the pit file method or pay for a motherboard replacement..
Tapatalking on my n7000
Click to expand...
Click to collapse

[Q] Galaxy note N7000 32G bricked ?

Hello,
I Purchased on Ebay a 32G Galaxy note N7000
It received it with Android 4.03, but I don't know the history of this device...
I carefully read all the posts about bricked phones.
So I decided to flash my phone using an original GB stock rom which is supposed to be safe.
I directly flashed it without wiping anything before... I didn't even enter in recovery mode
But the flash operation blocks in odin at factoryfs.img... and now, the phone can only enter download mode (not recovery).
Edit 1 : I just tried exactly the same operations with another PC.. and it works !
I presume now that my phone is not bricked...
Edit 2 : the flashing operation in "edit1" succeded, but when I reboot the phone, I have error messages so I can't initialise the phone...
Edit 3 : I tried to flash again with another GB rom, and I'm again blocked in odin at factoryfs.img. Idem with the Rom which worked one time..
I noticed a stange thing before flashing : the phone had only 24G memory when I received it : is it the clue that it has been repartitionned before I bought it, avoiding detroyed parts of its memory ?
Could someone help me to know what to do now..
Is my phone bricked or am I doing something wrong while flashing?
Are there special roms to use with 32G versions ?
One more thing : I uninstalled kies and I stopped my avast but I've the same problem.
Thank you.

Reboot the note and flash Gb again. If successful, boot into recovery mode and wipe data.

I rebooted and tried to flash with a GB rom several times unsuccessfully.
Each time, I'm blocked at factoryfs.img in ODIN....

pmu5757 said:
I rebooted and tried to flash several times unsuccessfully.
Each time, I'm blocked at factoryfs.img in ODIN....
Click to expand...
Click to collapse
That's the strong indicator for a bricked device!
And with your information that from 32 only 24 GB were available it seems to be clear that the previous owner used the repartition workaround (see hg42's thread) to revive it.
And after that selling it on ebay!
You should get in contact with the seller and try to get your money back. If he didn't hint in his selling information then you should think about the normal ebay "fraud help desks" (I never used them, so I do not know how this works).

Thank you for your first answer, but something is always strange in my situation : the flashing operation worked once : odin succeded up to the end of the flash operation. I only got problems after reboot. It shouldn't happen if parts of my memory are broken... or there is something I don't understand...
After that, if I decide to try to revive my note, are there special things to do for a 32G version (special rom, special pit file) ?

Flash the abyss kernel u can get from rootgalaxynote.com when in download mode, them youll habe cwm recovery and flash amy zipped rom from there. Goodluck
Sent from my GT-N7000 using xda app-developers app